Yes, that does work and is how I've been using mspdebug (for which I thank you; it's really helped a lot).
Peter On Tue, Aug 10, 2010 at 7:50 PM, Daniel Beer <dan...@tortek.co.nz> wrote: > On Tue, Aug 10, 2010 at 08:13:42AM -0500, Peter Bigot wrote: > > Could you add the CC430F5137 as well? tHANKS. > > > > $ mspdebug -d /dev/ttyUSB0 -j uif > > MSPDebug version 0.10 - debugging tool for MSP430 MCUs > > Copyright (C) 2009, 2010 Daniel Beer <dan...@tortek.co.nz> > > This is free software; see the source for copying conditions. There is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. > > > > Trying to open UIF on /dev/ttyUSB0... > > Initializing FET... > > FET protocol version is 20401000 > > Configured for JTAG (2) > > Set Vcc: 3000 mV > > Device ID: 0x5137 > > fet: unknown device > > msg28_data: [0x1a bytes] > > 51 37 10 10 08 0a e9 00 b0 46 1f 00 1f 00 f8 fe > > 00 00 91 01 11 00 1a 00 04 05 > > fet: identify failed > > Hi Peter, > > This information is enough to identify the chip, but we also need a > working configuration. It looks like the 5137 and 6137 are fairly > similar. Try this: > > mspdebug -d /dev/ttyUSB0 -j uif --fet-force-id CC430F6137 > > If that works, we could copy the DB entry for this chip and add the > ID information you've gathered. > > - Daniel >
