I'm using version 0.18 of mspdebug. I start it using the command 'mspdebug
rf2500'. I am seeing something unusual with the startup output. The device
I'm using is the F2252 but it's getting identified as F2272. It also is
showing the code start at 0x8000 instead of 0xc000. Here is the output of the
startup:
$ sudo mspdebug rf2500
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
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 interface 1 on 039
Initializing FET...
FET protocol version is 30001000
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
Device ID: 0xf227
Device: MSP430F2272
Code memory starts at 0x8000
Number of breakpoints: 2
fet: FET returned NAK
fet: warning: message 0x30 failed
Available commands:
= delbreak gdb load opt reset simio
alias dis help locka prog run step
break erase hexout md read set sym
cgraph exit isearch mw regs setbreak
Available options:
color gdb_loop iradix
fet_block_size gdbc_xfer_size quiet
Type "help <topic>" for more information.
Press Ctrl+D to quit.
(mspdebug)
When hook up a luanchpad with a G2552 all looks good and works as expected. In
both cases I get the NAK from the FET and the warning.
$ sudo mspdebug rf2500
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
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 interface 1 on 036
Initializing FET...
FET protocol version is 30001000
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
Device ID: 0x2553
Device: MSP430G2553
Code memory starts at 0xc000
Number of breakpoints: 2
fet: FET returned NAK
fet: warning: message 0x30 failed
Available commands:
= delbreak gdb load opt reset simio
alias dis help locka prog run step
break erase hexout md read set sym
cgraph exit isearch mw regs setbreak
Available options:
color gdb_loop iradix
fet_block_size gdbc_xfer_size quiet
Type "help <topic>" for more information.
Press Ctrl+D to quit.
(mspdebug)
When I try the --fet_force_id to MSP430F2252 I get errors:
$ sudo mspdebug --fet-force-id MSP430F2252 rf2500
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
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 interface 1 on 039
rf2500: warning: can't detach kernel driver: No data available
Initializing FET...
FET protocol version is 30001000
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
85 00 89 00 00 00 00 00 00 00
fet: identify failed
Trying again...
Initializing FET...
FET protocol version is 30001000
Configured for Spy-Bi-Wire
Sending reset...
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
85 00 89 00 00 00 00 00 00 00
fet: identify failed
Thanks,
Bob.
On Aug 22, 2012, at 4:10 PM, Daniel Beer wrote:
> On Wed, Aug 22, 2012 at 11:36:10AM -0700, Robert Henig wrote:
>> I have a custom board with a F2252 that is programmable using a FET-UIF from
>> a windows system using IAR and FETPro-Lite. On Ubuntu 12.04 I am unable to
>> get the FET-UIF to work with mspdebug ( I did see the thread about this
>> problem with OS X and non of that helped ). By hijacking the pins from a
>> Lanchpad I am able to program the F2252 only if the FLASH is empty. I am
>> also able to look at memory and step through the code. When I try to
>> program a non-empty FLASH it turns the code to garbage (looks like it just
>> changes 1's to 0's as if it was trying to program an erased FLASH).
>>
>> I am not able to re-program the part or erase the flash using the erase
>> command. Has anyone seen this and hopefully have a solution?
>
> What version of mspdebug are you using, and how are you invoking it? You
> might want to try using --fet-force-id to force the 2252 to be
> identified as a different (but compatible) chip. If you find something
> that works, let me know.
>
> Otherwise, are you able to capture USB data from your working setup on
> Windows?
>
> As for your FET-UIF, do you know what firmware version you have
> installed on it? If it's V3, you'll need to use the tilib driver.
>
> - Daniel
>
> --
> Daniel Beer <dlb...@gmail.com> www.dlbeer.co.nz
> IRC: inittab (Freenode) PGP key: 2048D/160A553B
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
