Steve,
Great! Thanks for the attention on this problem.
Tom
Steve Underwood wrote:
Hi Tom.
I now know what is going on. The last revision of the 169 (June 2003)
has a revised JTAG interface, with more features. This requires a
newer version of the TI library code. I have this, but I have not
released an updated gdbproxy using it. I have been overhauling
gdbproxy to try to speed up writes to flash by buffering them. I was
going to wait until that is done. Since this is causing you problems I
will get an interim update out in a couple of days.
Regards,
Steve
Tom Schroeder wrote:
Hello Steve,
First things first, thanks for the great tool! One of the wonderful
things about it is that I can and do use gdbproxy under both Windows
and Linux.
I should have been a little more clear in my error description.
gdbproxy returns "msp430: Target device is a 'Device unknown' (type
0)". This error started occurring after replacing a 149 part with a
169 part on our board (the 149 part would identify correctly). The
same problem has occurred on two different boards and has also been
verified by placing a 169 part into the ZIF socket of our TI FET
kit. This same error occurs under both Windows and Linux ports. 149
parts work great, but 169 parts (or at least this lot of parts) don't.
Tom Schroeder
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
