<first time I wrote daniels address wrong> Hi Daniel,
mspdebug 0.10 has a db entry for the msp430f2616 but I have a msp430f2618 that isn't recognized by mspdebug. I initially tried --fet-force-id msp430f2616 but that didn't work. So I then tried to duplicate the procedure to list the msg28_data that Andres Vahter used.... On Tue, Aug 10, 2010 at 09:03:39AM +0300, Andres Vahter wrote: > Here it is: > > mspdebug uif -d /dev/ttyUSB1 --fet-force-id foo > MSPDebug version 0.10 - debugging tool for MSP430 MCUs > Copyright (C) 2009, 2010 Daniel Beer <[email protected]> > 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/ttyUSB1... > Initializing FET... > FET protocol version is 20405003 > Configured for Spy-Bi-Wire > Set Vcc: 3000 mV > Device ID: 0xf227 > fet: unknown device > msg28_data: [0x1a bytes] > f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 > 82 00 89 00 00 00 00 00 00 00 > fet: identify failed Note that Andres is using spy-by-wire. I'm using uif-jtag and forcing jtag using the -j switch. It doesn't behave at all closely to what Andres got... zot (2): mspdebug uif -d /dev/ttyUSB0 -j --fet-force-id foo MSPDebug version 0.10 - debugging tool for MSP430 MCUs Copyright (C) 2009, 2010 Daniel Beer <[email protected]> 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 20404000 Configured for JTAG (2) Set Vcc: 3000 mV fet: FET returned error code 4 (Could not find device (or device not supported)) fet: command C_IDENT1 failed fet: identify failed zot (3): I'll dig into the code later today but it seems that -j changes the behaviour pretty significantly. eric -- Eric B. Decker Senior (over 50 :-) Researcher -- Eric B. Decker Senior (over 50 :-) Researcher
