Hi, There is some information about msp430x5xx MCUs that I have discovered. Please correct me if I wrong.
1) gdbproxy is not work and not even going to work with the 54XX devices, regardless of version HIL.dll and MSP430.dll. This is because the 54xx are devices with X architecture and there are some changes in JTAG for thouse MCU's. JTAG version is changed too, that's one of reasons (but not the only one) why gdbproxy is broken for the 54XX. JTAG Memory writing routines are changed also. 2) fetproxy is in the same situation. Probably it works with the older series, but not with 54XX. 3) Parallel port JTAG adapters (like Olimex) do not work for the same reason 4) BSL for the 54XX is significantly changed too. So old BSL tools are also useless for the 54XX. For the moment I see only one way to program 54XX under Linux / mspgcc toolchain - to use self-made programmer like GoodFET11 ( see http://goodfet.sourceforge.net/ ) and implement JTAG functions manually. Personally I have got the GoodFET11 board and make some JTAG functions to work. Actually, I have ported a code from the SLAU265a (for MSP430Xv2). For the moment it may read, write RAM and FLASH, set registers, acquire and release JTAG and so on. I'm going to write kind of working programmer to read, write and erase flash memory in a week. If anyone interested in the results or have any questions or need sources - please write to [email protected] The useful documents regarding this issue: SLAU265a, SLAU208d PS. Why there are only attempts to use the MSP-FET430UIF with proprietary TI's code or with reverse-engeenered protocol as fetproxy does, but there is no any attempts to write an open firmware for MSP-FET430UIF ? The FET is well-documented, the source code from SLAU265a seems enough to implement all functions required by gdb and gdbproxy. --- Regards, Dmitry
