On Nov 8, 2007 10:07 PM, I wrote: > I'm running Fedora 7, w/ updates. > > I have a brand new, just out of the box MSP-FET430UIF. > [...] > I try the --update-usb-fet option, and here is what I get: > [an...@ermintrude foo]$ msp430-gdbproxy msp430 --update-usb-fet > /dev/ttyUSB1 > > 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. > > notice: msp430: TI USB FET update requested > notice: msp430: Initializing bootloader... > error: msp430: Could not initialize device interface (1) > debug: MSP430_Initialize() > error: msp430: The FET tool version does not match this program. > Update required. > debug: MSP430_Initialize() > error: msp430: The FET tool version does not match this program. > Update required. > debug: MSP430_Initialize() > error: msp430: The FET tool version does not match this program. > Update required. > ... [repeats until ^c] > > Not good when the updater complains the same way. > [...] > I lack the secret decoder ring to know what this exchange is trying to > tell me, but it looks like the device is > not just plain DOA, it is saying _something_ back. > > Has anyone seen this before, or can any of the keepers of the secrets > decode the messages and > tell me what is going on ? > > As an aside, I do notice that despite my specifying /dev/ttyUSB1 on > the command line, the > program is _still_ trying to open /dev/ttyUSB0 (the source of the > "error: msp430: Could not initialize device interface (1)" > message.) I assume that would lead to other problems if permissions > didn't get in the way.
With Steve's help I was able to understand what is going on here, and the UIF is now working fine with both msp430-gdbproxy and msp430-jtag now. The problem revolves around the special modes (--selftest-usb-fet and --update-usb-fet) - these will _only_ work with /dev/ttyUSB0 at present. I was able to temporarily reconfigure my USB dongles so that the UIF was /dev/ttyUSB0 and the update step then worked flawlessly. It is only these special modes that require special treatment, now my UIF has been upgraded, it works for all normal msp430-gdbproxy usage regardless of device name (e.g. /dev/ttyUSB1..) -- Andy
