I managed to get my hands on a PICKit2 from microchip, reflashed the bootloader hex file and... The bootloader now properly programs the firmware using the python programmer utility!
I connected using cutecom and everything seems to work perfectly now! The mode light extinguishes after connecting the bus pirate, and it responds to commands according to the manual.
I'm not sure what was wrong with the bootloader, but reflashing it with an external programmer seemed to do the trick. Maybe this will help somebody else who's having problems installing firmware on a v2go.
Ok, I'm on my linux box right now and I just tried using the Python bootloader. It looks like there's a repeating pattern that fails verification at the very beginning:
Verification failed at 0x00000000: 0 != 4 Verification failed at 0x00000001: 4 != 12 Verification failed at 0x00000008: 255 != 28 Verification failed at 0x00000009: 255 != 111 Verification failed at 0x0000000A: 255 != 0 Verification failed at 0x0000000C: 255 != 28 Verification failed at 0x0000000D: 255 != 111 Verification failed at 0x0000000E: 255 != 0 Verification failed at 0x00000010: 255 != 28 Verification failed at 0x00000011: 255 != 111 Verification failed at 0x00000012: 255 != 0 Verification failed at 0x00000014: 255 != 28 (etc, etc)
After the repeating pattern ends the bootloader verification is skipped...
Then I get what seems to be a failure from the C00 area of the firmware to the very end:
Verification failed at 0x00000C00: 255 != 4 Verification failed at 0x00000C01: 255 != 12 Verification failed at 0x00000C02: 255 != 0 Verification failed at 0x00000C04: 255 != 0 Verification failed at 0x00000C05: 255 != 0 Verification failed at 0x00000C06: 255 != 0 Verification failed at 0x00000C08: 255 != 239 Verification failed at 0x00000C09: 255 != 192 Verification failed at 0x00000C0A: 255 != 33 Verification failed at 0x00000C0C: 255 != 0 Verification failed at 0x00000C0D: 255 != 127 Verification failed at 0x00000C0E: 255 != 34 Verification failed at 0x00000C10: 255 != 0 Verification failed at 0x00000C11: 255 != 1 Verification failed at 0x00000C12: 255 != 136 Verification failed at 0x00000C14: 255 != 0 Verification failed at 0x00000C15: 255 != 0 Verification failed at 0x00000C16: 255 != 0 Verification failed at 0x00000C18: 255 != 10 etc, etc.
The command I used for the programmer was:
python P24qp.py -s /dev/ttyUSB0 -a v25-Firmware-v2.1.hex -v
The -a arguement should erase, flash, and exit the bootloader. The -v switch enables verification.
So something is definitely getting messed up during the bootloading process. Any suggestions? Maybe the bootloader needs to get reflashed from ICSP to properly program the firmware area? Hardware failure? Something else?
Hi! I just got a v2go bus pirate from seeedstudio and installed the new v2.1 firmware. The problem is... It's still not responding to any serial commands!
My serial setup seems to be ok, and it can connect fine to the bootloader in both the windows PIC utility and linux python script running at 9600 baud. Aside from the verification error on the Windows utility, it flashed the hex file over the course of a few minutes.
I tried using cutecom and tera term at 115200, but no luck!
The "mode" led is lit constantly after plugging it in.
Does this mean it's stuck in bootloader mode for some reason (firmware not flashing correctly), or is there something wrong with my setup on the software side?
