On 2007-11-26, Steve Underwood <[email protected]> wrote: > msp430-gdbproxy msp430 --update-usb-fet <device name>
After wasting some more time, I figured out that <device name> is REQUIRED to be /dev/ttyUSB0. I'd like to meet whoever made that, um, "decision". It would be nice if stuff like that was documented in the gdb-proxy "help" output. So now I've gotten the USB interface brought up to the same level of brokeness as the parallel interface (you've got to love that about TI's JTAG stuff: there are so very many levels and flavors of brokeness from which to choose): $ msp430-gdbproxy msp430 /dev/ttyUSBez430 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_Initialize() debug: MSP430_Configure() debug: MSP430_VCC(3000) error: msp430: External power detected (38) debug: MSP430_Identify() info: msp430: Target device is a 'Device_unknown' (type 0) debug: MSP430_Configure() notice: msp430-gdbproxy: waiting on TCP port 2001 I'm using the latest versions of msp430-gdb exectuable and libraries downloaded from http://www.soft-switch.org/downloads/mspgcc/. Unfortunately, those are a 1-1/2 years old -- apparently too old to support the '2330. So which piece needs to be updated and how do I go about updating it? -- Grant Edwards grante Yow! WHO sees a BEACH BUNNY at sobbing on a SHAG RUG?! visi.com
