So I was hoping that I wouldn't need help with this, but I do.
First, here is what the mod consists of. It is a rapid fire mod for Xbox 360 contollers. It has 6 different speed settings from 8 rps to 30 rps. It has an option of full auto, 3 round burst, or 5 round burst. Also, any of this can be applied to left trigger (LT) as well. So 6*3*2 makes for 36 possible configurations. And at any point, you can pause the mod and go back to normal mode.
This is all accomplished through an extra button attached to the back of the controller. Pressing it changes the speed from 0 - 7. Pressing it and RT changes through full auto, 3 round burst, and 5 round burst. Pressing the button with LT toggles left trigger on and off. And finally, holding the button for 1 second pauses the mod for normal use.
Ok, now the problem. Every thing was going great, I had gotten full auto working, then burst, and while I was working on adding extra button support, the chips became unresponsive. The chips still work when I put them in the controller, they do the last thing I told them to. But when I plug them into my computer, it can't read them or write to them.
At first I thought that maybe the chip had reached it max writes or something. So I pulled out a brand new one and tried it. It did just what I wanted it to. But when I tried to reprogram it, nothing.
I find it very unlikely that it fried or anything. The highest rating on one of the pins is 4mA. The only thing that seems likely is that some internal setting got changed. It stopped working shortly after I started using the internal timer, but I had still used it before.
And the specifics, the chip is a pic10f200. Here is the source if anyone wants to look. I guess all the problems started happening when the program flashed the LED for the first time. (It's flashed before, just not with this code.) So I guess that little section at the bottom of mainLoop might be the culprit. To kill it, you would follow, buttonPressed, and then it jumps back to mainLoop and dies.
Hopefully someone has an idea.
First, here is what the mod consists of. It is a rapid fire mod for Xbox 360 contollers. It has 6 different speed settings from 8 rps to 30 rps. It has an option of full auto, 3 round burst, or 5 round burst. Also, any of this can be applied to left trigger (LT) as well. So 6*3*2 makes for 36 possible configurations. And at any point, you can pause the mod and go back to normal mode.
This is all accomplished through an extra button attached to the back of the controller. Pressing it changes the speed from 0 - 7. Pressing it and RT changes through full auto, 3 round burst, and 5 round burst. Pressing the button with LT toggles left trigger on and off. And finally, holding the button for 1 second pauses the mod for normal use.
Ok, now the problem. Every thing was going great, I had gotten full auto working, then burst, and while I was working on adding extra button support, the chips became unresponsive. The chips still work when I put them in the controller, they do the last thing I told them to. But when I plug them into my computer, it can't read them or write to them.
At first I thought that maybe the chip had reached it max writes or something. So I pulled out a brand new one and tried it. It did just what I wanted it to. But when I tried to reprogram it, nothing.
I find it very unlikely that it fried or anything. The highest rating on one of the pins is 4mA. The only thing that seems likely is that some internal setting got changed. It stopped working shortly after I started using the internal timer, but I had still used it before.
And the specifics, the chip is a pic10f200. Here is the source if anyone wants to look. I guess all the problems started happening when the program flashed the LED for the first time. (It's flashed before, just not with this code.) So I guess that little section at the bottom of mainLoop might be the culprit. To kill it, you would follow, buttonPressed, and then it jumps back to mainLoop and dies.
Hopefully someone has an idea.