Hi Dmitry, Dmitry Zuikov <dzuikov <at> gmail.com> writes: > 2) fetproxy is in the same situation. Probably it works with the older > series, but not with 54XX.
fetproxy doesn't yet "work" with any chips yet. It will hopefully work with some when I get time to develop on it. In the meantime, it's not yet suitable for real use. > 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. My friend had success with running the windows version of msp430-gdbproxy under wine. The windows version of msp430-gdbproxy has been updated to include support for some of the 5xx series, whilst the Linux version has not. > Personally I have got the GoodFET11 board and make some JTAG functions > to work. [snip] Cool. (When I get some time) I hope to get fetproxy working with the GoodFET. > 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. Unfortunately SLAU256a doesn't contain information about how to *debug* a device through it's "JTAG" port. TI have chosen not to release that information for some reason. I went down the road of reverse engineering the UIF protocol because: (a) The reverse engineering process is simpler, as it's just a case of monitoring serial port interaction. (b) I felt that TI might be less kind when it comes to the release of information about the JTAG protocols. I could be wrong here, I don't know. (c) I already have a UIF. TI claim that they are coming out with an open source MSP430 debugging solution by the end of the year. Fingers crossed. Cheers, Rob
