Hi,
The gdbproxy update I did a few days ago supports the F161x devices. In
fact, it uses the very latest code from TI, and should anything you will
find out there.
Regards,
Steve
ni...@signalmetrics.com wrote:
I have some prototype msp430f1611 parts from TI (10K ram!).
I tried the latest gdbproxy from ftp.opencall.org/pub/msp430-gdbproxy
and get the following:
./msp430-gdbproxy --debug msp430
Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc.
MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood
GDBproxy comes with ABSOLUTELY NO WARRANTY; for details
use `--warranty' option. This is Open Source software. You are
welcome to redistribute it under certain conditions. Use the
'--copying' option for details.
debug: msp430: msp430_open()
info: msp430: Target device is a 'Device unknown' (type 0)
notice: msp430-gdbproxy: waiting on TCP port 2000
Should the latest gdbproxy support this chip? It is possible that
the prototype chips have faulty id bits. Is there any way to
manually set a device type, so gdbproxy will ignore the faulty
chip? I can't seem to get anywhere with the 'Device unknown'
condition.
Thanks,
Niels LaWhite
Hi,
I just updated the files ftp://ftp.opencall.org/pub/msp430-gdbproxy
(Linux) and ftp://ftp.opencall.org/pub/msp430-gdbproxy.exe (Windows) so
they support the latest MSP430 devices.
Regards,
Steve
