I'm looking for the equivalent program or tool for the MSP430 LaunchPad as LM Flash Programmer (LMFLASHPROGRAMMER) is for the Stellaris boards. Does this exist? Yes.
Requirements:
Options that meet the requirements:
Here are the other options I considered:
What other options could I consider?
MSPDebug is free and supports different hardware options. It's for linux though.
http://mspdebug.sourceforge.net/
Gustavo
---------------------------------------------------------------------------------------------------------Please click the Verify Answer button on this post if it answers your question.---------------------------------------------------------------------------------------------------------
Gustavo L MSPDebug is free and supports different hardware options. It's for linux though.
MSPDebug has since added these features (among others):
I think having such a software would be advantageous. It will likely need to be written by TI. It makes evaluating software easy when you just want to get going in 5 minutes. I remember doing that on the Stellaris evaluation kits and I was happy I could at least use the hardware before digging into a compiler.
Gustavo L I think having such a software would be advantageous. It will likely need to be written by TI. It makes evaluating software easy when you just want to get going in 5 minutes. I remember doing that on the Stellaris evaluation kits and I was happy I could at least use the hardware before digging into a compiler.
Agreed. I want to build demo boards that will piggyback on the LaunchPad board. Then when I give them to a customer they can easily load different binaries to evaluate different examples/features.
Hi Jason,
I think you can use Elprotronic's Lite- FET Pro-430 with Launchpad , i programmed a G2452 using Launchpad and Lite-FETPro-430. Elprotronic S/W has the required dlls and works with all TI's USB FETs
Regards
Nischay
Mr.Nischay Kumar V I think you can use Elprotronic's Lite- FET Pro-430 with Launchpad , i programmed a G2452 using Launchpad and Lite-FETPro-430. Elprotronic S/W has the required dlls and works with all TI's USB FETs
Yes, you're right Nischay. Thank you. I just verified it with the attached files.
2677.regularFlash.txt2475.fastFlash.txt
I can program one and then the other to see the difference.
One thing I noticed is you need to reset the board using the GUI in the box called, "Power Device from Adapter." Otherwise you'll need to unplug and plug in the board again to power it and get the program running. This was the case with either setting of "final target device actions."
MSP430 Flasher also works. It only appeared not to have worked the first time I tried it because I did not set the state of the device on exit.
This time I programmed a board with MSP430G2452. The board piggybacks on the MSP-EXP430G2. Since the target MCU is on the piggybacked board, there is not MCU in the DIP socket.
This is the command I used in MSP430 Flasher:
MSP430Flasher.exe -n MSP430G2452 -v -w uart.txt -i USB -z [VCC]
uart.txt is the name of my binary file.
I had forgotten about MSP430 flasher. Haven't used it much but I'll give it another try.
Gustavo L MSPDebug is free and supports different hardware options.
MSPDebug is free and supports different hardware options.
I verified using MSPDebug to program a file to a MSP430G2452 on the LaunchPad. Here’s my setup.
Operating System: Microsoft Windows XP Professional Version 2002 Service Pack 3Hardware: LaunchPad MSP-EXP430G2 (Hardware ID USB\\Vid_0451&Pid_f432&Rev_105 as seen in device manager)Device: MSP430G2452MSPDebug tools: MSPDebug mspdebug-0.19.tar.gz Download Install instructions Commands Minimalist GNU for Windows mingw-get-inst-20120426.exe GnuWin regex-2.7-bin GnuWin readline-5.0-1-bin libusb-win32-bin-1.2.6.0 (used inf-wizard.exe to install new driver)
The Intel-hex files I programmed are attached. There are two files, so I could observe a change.
3124.blinky2452Slow.zip
Here is my log file showing the commands used:
cmd Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\a0123456>cd ../.. C:\>cd MinGW C:\MinGW>cd mspdebug-0.19 C:\MinGW\mspdebug-0.19>mspdebug --usbDevices on bus 000: 000:000 0451:f432 eZ430-RF2500 [serial: 19FF469286D91E2B] C:\MinGW\mspdebug-0.19>lsAUTHORS README formats mspdebug.man ti_3410.fw.ihexCOPYING blinky2452.hex history5.dll readline5.dll ti_3410.fw.txtChangeLog blinky2452Slow.hex libusb0.dll regex2.dll uiMakefile drivers mspdebug.exe simio util C:\MinGW\mspdebug-0.19>mspdebug rf2500 "prog blinky2452.hex"MSPDebug version 0.19 - debugging tool for MSP430 MCUsCopyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open interface 1 on \\.\libusb0-0001--0x0451-0xf432Initializing FET...FET protocol version is 30394216Configured for Spy-Bi-WireSet Vcc: 3000 mVDevice ID: 0x2452Device: MSP430G2452Code memory starts at 0xe000Number of breakpoints: 2Erasing...Programming...Writing 178 bytes to e000...Writing 2 bytes to fffe...Done, 180 bytes written C:\MinGW\mspdebug-0.19>mspdebug rf2500 "prog blinky2452Slow.hex"MSPDebug version 0.19 - debugging tool for MSP430 MCUsCopyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open interface 1 on \\.\libusb0-0001--0x0451-0xf432Initializing FET...FET protocol version is 30394216Configured for Spy-Bi-WireSet Vcc: 3000 mVfet: FET returned error code 4 (Could not find device (or device not supported)) fet: command C_IDENT1 failedfet: identify failedTrying again...Initializing FET...FET protocol version is 30394216Configured for Spy-Bi-WireSending reset...Set Vcc: 3000 mVDevice ID: 0x2452Device: MSP430G2452Code memory starts at 0xe000Number of breakpoints: 2Erasing...Programming...Writing 178 bytes to e000...Writing 2 bytes to fffe...Done, 180 bytes written C:\MinGW\mspdebug-0.19>
Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\a0123456>cd ../..
C:\>cd MinGW
C:\MinGW>cd mspdebug-0.19
C:\MinGW\mspdebug-0.19>mspdebug --usbDevices on bus 000: 000:000 0451:f432 eZ430-RF2500 [serial: 19FF469286D91E2B]
C:\MinGW\mspdebug-0.19>lsAUTHORS README formats mspdebug.man ti_3410.fw.ihexCOPYING blinky2452.hex history5.dll readline5.dll ti_3410.fw.txtChangeLog blinky2452Slow.hex libusb0.dll regex2.dll uiMakefile drivers mspdebug.exe simio util
C:\MinGW\mspdebug-0.19>mspdebug rf2500 "prog blinky2452.hex"MSPDebug version 0.19 - debugging tool for MSP430 MCUsCopyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Trying to open interface 1 on \\.\libusb0-0001--0x0451-0xf432Initializing FET...FET protocol version is 30394216Configured for Spy-Bi-WireSet Vcc: 3000 mVDevice ID: 0x2452Device: MSP430G2452Code memory starts at 0xe000Number of breakpoints: 2Erasing...Programming...Writing 178 bytes to e000...Writing 2 bytes to fffe...Done, 180 bytes written
C:\MinGW\mspdebug-0.19>mspdebug rf2500 "prog blinky2452Slow.hex"MSPDebug version 0.19 - debugging tool for MSP430 MCUsCopyright (C) 2009-2012 Daniel Beer <dlbeer@gmail.com>This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Trying to open interface 1 on \\.\libusb0-0001--0x0451-0xf432Initializing FET...FET protocol version is 30394216Configured for Spy-Bi-WireSet Vcc: 3000 mVfet: FET returned error code 4 (Could not find device (or device not supported))
fet: command C_IDENT1 failedfet: identify failedTrying again...Initializing FET...FET protocol version is 30394216Configured for Spy-Bi-WireSending reset...Set Vcc: 3000 mVDevice ID: 0x2452Device: MSP430G2452Code memory starts at 0xe000Number of breakpoints: 2Erasing...Programming...Writing 178 bytes to e000...Writing 2 bytes to fffe...Done, 180 bytes written
C:\MinGW\mspdebug-0.19>
I then checked to see that I could program the same files using FET-Pro430 Lite 3.0.7 TI dll 3.2.3.15. I uninstalled the USB device. Unplugged it. Plugged it back in (now default driers). The Elprotronic tool programmed the same two files successfully also.
Hello from Germany,
I run the latest version of Code Composer Studio (Version: 5.3.0.00090)I'm not able to connect my Launchpad EXP430G2 (Target is MSP430G2553).The Compiler/Linker says: MSP430: Loading complete. Code Size - Text: 1604 bytes Data: 12 bytes.After disconnect/connect the USB-Cable the Demo-App (Temperature_sense_Demo) startsto toggle the red/green LES's.access with the MSP430Flasher results:
****************************************************************************
Evaluating additional triggers...doneInitializing interface on TIUSB port...doneChecking firmware compatibility...doneReading FW version...doneReading HW version...donePowering up...doneConfiguring...doneAccessing device...doneReading device information...doneResetting device...doneRefreshing registers.../* ---------------------------------------------------------------------------- * UseCase : MSP430Flasher.exe * Arguments : -n MSP430G2553 -i TIUSB * ATTENTION: Default options used due to invalid argument list. * ---------------------------------------------------------------------------- * Driver : loaded * Dll Version : 20409001 * FwVersion : 30394216 * Interface : TIUSB * HwVersion : E 2.0 * Mode : AUTO * Device : MSP430G2xx3 * EEM : Level 1, ClockCntrl 1 * VCC ON : FALSE * UseCase specific tasks: ---------------------------------------------------- * Disconnecting from device... * ---------------------------------------------------------------------------- * Driver : closed (No error) * ----------------------------------------------------------------------------*/ **************************************************************************** To me it's seems like Code Composer Studio performs a downloadwhile "Run/ConnectTarget" is disabled (greyed out).I've also tried to change the COM-Settings (COM17->COM3 and back)without results...What is wrong ??Pleas give me a little suggestion.regards Thomas