On Tue, Oct 19, 2010 at 10:27:58AM +0200, Michiel Konstapel wrote: > Hi Daniel! > > > Probably the reason erase doesn't work is that MSPDebug is sending the > > wrong address for the segment in the erase request. If you could do: > > > > mspdebug uif -d /dev/ttyUSB0 --fet-force-id foo > > > > And copy/paste the msg28 data, I could probably put together a patch > > that'll get this working. If you really need to get it working in the > > meantime, the hack below should do it, if you apply it on top of the > > git version. > > Cool :) Here's the output you asked: > > msg28_data: [0x1a bytes] > f2 49 03 60 00 00 00 00 00 00 02 02 01 00 f2 2b > 82 00 89 00 00 00 00 00 00 00 > > I'm afraid the patch didn't work for me: > > $ mspdebug uif -q -j -d /dev/ttyUSB0 'prog ../main.ihex' > Trying to open UIF on /dev/ttyUSB0... > fet: FET returned error code 4 (Could not find device (or device not > supported)) > fet: command C_IDENT1 failed > fet: identify failed > Trying again... > Device: MSP430F249 > Erasing... > > It looks like it's only erasing now? No worries though, I'll manage :) I > can just use the old tools for now. It's just great to have a fast, > native solution on Linux available, so thanks again!
That's a bug... it should actually be programming, but it doesn't say so in quiet mode. I've just pushed a fix for this through to the git repository. Aside from that, does it look like the chip actually got programmed? - Daniel ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
