How do I get my program into the JTAG-ISO’s internal FLASH memory so that I can use the programmer in standalone mode?
I normally use GCC and GDB to load programs directly and debug. I have also used the Olimex MSP Programmer application for programming with a PC and the JTAG-ISO adapter, but I can’t figure out how to actually use the adapter with only a 12V power adapter. I can’t find any documentation either. Am I just looking in the wrong places?
Ok, so I figured out that you can [only?] load the JTAG-ISO’s internal FLASH in standalone mode using the yellow read button. That’s working and I can now program in standalone mode.
HOWEVER I can now no longer connect to gdb. gdbproxy says:
error: MSP430: The FET tool version does not match this program. Update required.
I made sure I had the latest dlls and msp430-gdbproxy installed, but I can’t fix this error. I even cleared the JTAG-ISO’s FLASH, but I’m stuck not being able to debug now. What gives?
OK, so I’m answering my own post again.
This problem appears to be related to the fact that the Olimex windows programming application reprograms some part of the MSP430-JTAG-ISO’s firmware. Apparently gdbproxy gets unhappy with the MSP430-JTAG-ISO programmed this way.
The fix is to force gdbproxy to “update” the MSP430-JTAG-ISO to it’s liking by running: gdbproxy -port=xxxx msp430 --update-usb-fet TIUSB (xxxx is your favorite port setting, in my case 3333).
This apparenly reprograms the MSP430-JTAG-ISO’s firmware and then gdbproxy is happy again.
When I run the Olimex MSP430 Programmer application after using gdbproxy, I see that the first thing it does is update the firmware. After this, gdbproxy is unhappy again. I suppose this firmware update process needs to be done every time you switch between using gdbproxy and the Olimex MSP430 Programmer application.
The reason I didn’t realize this before was that I was using two separate MSP430-JTAG-ISO adapters and just happened to never interchange them. One was always used with the Olimex MSP430 Programmer application and the other always with gdbproxy (and at some point in the past, it must have gotten updated to gdbproxy’s liking by someone).
Is there anything else I (we) should know about this?