The attached file is on Fedora 13. The system was shutdown and the first time I
tried, mspdebug did not see the LaunchPad at all which has never happened
before. After a reboot it seems to behave normally.
Note that this is for two rev 1.4 LaunchPads. One w/ the F2012 and one w/ the
G2553.
When I unplugged the first and plugged in the second it seems to have caused
some mspdebug confusion.Linux also seems to have added a new USB device.
I've not noticed any problem w/ the G2553 other than my new LaunchPads were old
stock and I had to buy my G2553s :-( However, I've also done very little other
than load and run a simple blinky light program.
Have Fun!
Reg
[rhb@fedora-13-wrk tst5]$ 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 004
Initializing FET...
FET protocol version is 30066536
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
Device ID: 0xf201
Device: MSP430F2012
Code memory starts at 0xf800
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)
[rhb@fedora-13-wrk tst5]$ 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.
usbutil: unable to find a device matching 0451:f432
[rhb@fedora-13-wrk tst5]$ mspdebug --usb-list
Devices on bus 003:
003:006 0451:f432 eZ430-RF2500
003:003 058f:9360
003:002 0430:0100
003:001 1d6b:0001
Devices on bus 002:
002:003 2222:0005
002:002 2222:1001
002:001 1d6b:0001
Devices on bus 001:
001:001 1d6b:0002
[rhb@fedora-13-wrk tst5]$ 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 006
rf2500: warning: can't detach kernel driver: Operation not permitted
rf2500: can't claim interface: Operation not permitted
rf2500: failed to open RF2500 device
[rhb@fedora-13-wrk tst5]$ 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 006
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)
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
