Here's the output of the mspdebug session:
kims-mac:msp430-test-program-1-sep-2010 kim$ mspdebug -j -d
/dev/tty.MSP-FET430UIF620 uif
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/tty.MSP-FET430UIF620...
Initializing FET...
FET protocol version is 20405003
Configured for JTAG (2)
Set Vcc: 3000 mV
Device ID: 0x5437
fet: unknown device
msg28_data: [0x1a bytes]
54 37 10 10 08 0a 15 ae 83 46 2d 00 16 00 f8 fe
00 00 91 00 01 00 1a 00 00 05
fet: identify failed
and here's the response when I tell it it's a MSP430F5438A:
kims-mac:msp430-test-program-1-sep-2010 kim$ ls
/msp430-gcc-4.4.4/bin/kims-mac:msp430-test-program-1-sep-2010 kim$ mspdebug
-j -d /dev/tty.MSP-FET430UIF410 --fet-force-id MSP430F5438A uif
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/tty.MSP-FET430UIF410...
uif: can't open serial device: /dev/tty.MSP-FET430UIF410: Bad file
descriptor
kims-mac:msp430-test-program-1-sep-2010 kim$ mspdebug -j -d
/dev/tty.MSP-FET430UIF620 --fet-force-id MSP430F5438A uif
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/tty.MSP-FET430UIF620...
Initializing FET...
FET protocol version is 20405003
Configured for JTAG (2)
Set Vcc: 3000 mV
Device ID: 0x5437
Device: MSP430F5438A
Code memory starts at 0x5c00
Number of breakpoints: 8
Available commands:
= dis hexout opt reset step
break erase isearch prog run sym
cgraph gdb md read set
delbreak help mw regs setbreak
Available options:
color gdb_loop
Type "help <topic>" for more information.
Press Ctrl+D to quit.
(mspdebug)
On Tue, Sep 7, 2010 at 9:34 PM, Daniel Beer <[email protected]> wrote:
> On Tue, Sep 07, 2010 at 09:03:08PM -0400, Kim Toms wrote:
> > Thanks for the suggestions. Here's the results.
> >
> > I downloaded the binary package as described, and installed also as
> > described. For some reason I couldn't get Filer to browse to the
> directory
> > containing the Info.plist file, and when I opened it with the property
> list
> > editor, I could not save the file, in spite of being root. So, I used
> > trusty old vi to do the editing.
> >
> > I was able to plug in an eZ430-F2013 and connect to it with mspdebug; the
> > default program it was running (flashes LED) instantly stopped, and when
> I
> > typed 'run' it continued (to flash). Experience with the MSP-FET430UIF
> was
> > not so successfull.
> >
> > The device node created for the eZ430-F2013 is named
> > /dev/cu.MSP-FET430UIF620. The device node created when the MSP-FET430UIF
> is
> > plugged in is /dev/cu.MSP-FET430UIF410. When I attempt to start mspdebug
> on
> > the MSP-FET430UIF, I get the following output:
> >
> > 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/cu.MSP-FET430UIF410...
> > Initializing FET...
> > FET protocol version is 20405003
> > Configured for Spy-Bi-Wire
> > 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
> >
> > I have not yet looked at the source to see if I can figure out the
> problem.
> >
> > Later, it occured to me that I could try the JTAG mode. When I did, I
> was
> > able to stop and start the system just like I was able to do with
> > spy-bi-wire and the eZ430-F2013. I'm going to try loading a program (we
> > tried, but the module was made wrong, so it didn't work, I found that
> > problem after I got home). I also have an eZ430-RF2500 which I will try
> > tomorrow.
> >
> > The CPU I'm using returns id info that is not listed in the fet-db;
> should I
> > work on getting commit access to the repo, or send a diff to someone?
> I'm
> > not sure of the meaning of all of the bits, so I can supply what's
> printed
> > out as part of the error message, but it looks like there are 3 parts and
> > what's in the other two is unknown to me (at least at this point).
>
> Hi Kim,
>
> You can send any information you can gather to me. If you send me:
>
> (1) The name of the chip you're using.
>
> (2) The name of a similar chip configuration which works
> well-enough if you set --fet-force-id <name> (you can get a
> list with --fet-list).
>
> (3) The output when MSPDebug fails to identify (the lines labelled
> "msg28_data:").
>
> ...then I should hopefully be able to cook something up which will
> work. Alternatively, if you have access to IAR or similar on a machine
> which you can run a USB sniffer on (like sniffusb 2.0), then I can
> definitely get it working using the information logged when you
> connect using the debugger.
>
> Cheers,
> Daniel
>
