TI has released a firmware updater for their Launchpads. The exe is a GUI-based utility to update the emulator firmware of the MSP430 Value Line LaunchPad kit (MSP-EXP430G2). With this update, your LaunchPad will be able to support all new and future MSP430G2xx Value Line devices.
You can get more information on TI’s wiki page.
CAUTION:
Please exercise caution while upgrading your firmware. There have been reports of Launchpads getting bricked with this update. Perform an update only if you need to program new devices. Also make sure to read the e2e and 43oh thread links below.
Important README notes, so that you avoid bricking your Launchpad:
- Make sure the USB driver for LaunchPad is installed correctly on the used PC. Usually this requires either an MSP430 IDE being installed on the PC (either CCS or IAR Embedded Workbench for MSP430) or an internet connection to load the driver from Microsoft. The LaunchPad USB driver is NOT provided with the update utility, the tool relies on a correctly installed USB driver.
- Plug in LaunchPad via USB with MSP430G2xx device on DIP socket. The update utility checks for the presence of the target device. No update will be performed if the DIP socket is empty.
- Make sure only ONE LaunchPad is connected to the PC at a time . The update utility will detect if more than one LaunchPad is connected and refuse to perform an update of the emulator firmware.
- Double click the LaunchPadFirmwareUpdater2.0.exe and follow instructions on the screen. IMPROTANT: Do not disconnect the LaunchPad from USB while the update is running! This might cause an unrecoverable error state of the LaunchPad!!!
I think this just screwed my launchpad board up.
It errored out during this upgrade. Now it still finds the launchpad board – in device manager, com port still found, and the updater tool does as well but it says to make sure a MSP430* device is installed in the socket. can’t seem to program it any more, either.
Hopefully there is some procedure to unscrew this. I knew I shoulda ordered to or 2 of these things so i’d have a spare..
Wait for a few days and keep an eye on the e2e thread. If not, let TI know. Or maybe we could figure something out.
I contacted TI’s tech support on the issue. Waiting to hear back from them now.
I’ve played around with the thing some – the USB device ID number actually changed after this.. It is now 0xf432
the microcontroller is still running on the board.. Just that glue between the UART and the rest of the board is gone.
My launchpad remains bricked, but the tech support guy after several email exchanges getting details from me informed me he had placed an order for a new board for me.
Not bad service on a board that costs 4 bucks… Just wanted to make clear that they took very good care of me..
did you try a different MSP430? just a thought
In the readme file it says that the update is to give support to windows 7, so linux folks don’t need to upgrade
sucotronic: Read the E2E thread, this update is not for Windows 7 support. This update is to correct an issue with a range of Launchpads that have a bad firmware from the factory. This update will allow those Launchpads to work correctly with the new 20 pin G series.
Worked flawlessly on all five of my LP’s that were in that range.
Ups, sorry for that. I only read the readme file and not the e2e forum
Same here (have not tried flashing the msp vie ccs). See my comment on http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update
You got the link to 43oh forum wrong..
I think you meant this: http://www.43oh.com/forum/viewtopic.php?f=8&t=705
Thanks! fixed.
The exe seems to be an archive, at least 7-zip extracts a couple of files (.rsrc/, .data, .rdata, .text) , maybe someone is able to extract the firmware?
The error I got was the very descriptive “something went wrong. the application needs to close.” You can find that string in the extracted data.
Neat find! Those are separated HEX/TI-Text files of the firmware… someone with a decent disassembler could look at this and see what’s up, possibly reinsert to the exe for custom firmware.
wouldn’t this allow cloning of the Debugger MSP430? If yes, then wow!
It’s a possibility. If someone wants to have a hand at hacking the firmware, I have a LaunchPad I don’t care if I brick. I’d definitely be willing to test this. It could open up new possibilities for third-party programmers
(MSPhere with an IDE ala Arduino?)
Can you be more specific (” …separated HEX/TI-Text files of the firmware …”)?
They are either hex files, to be written directly to the chip, or TI-Text files, which are a TI-proprietary format, which can be read, translated, and written to the chip. I say separated, because the .data and .text (and .rdata and .rsrc) are different sections of the codespace on the MSP430s. TI probably split the firmware into chunks to facilitate flashing with the internal tool in the update program.
I’m curious as to if the update program contains any validation code–i.e. if those files are replaced, will it flash them or reject them for being tampered with.
You’re just guessing from the extension, right? Then please don’t make it sound like facts. The MSP has 55kB Flash, .data (32kB) contains lots of strings that only make sense for the update Software, the others are > 200 kB. However, the firmware seems to be embedded in .rdata starting at 0x76E .. 0xD22D (compare with firmware read out http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/p/97931/346074.aspx#346074).
Those (.rsrc, .data, .rdata, .text) those are the sections in the .exe file, not ‘zipped’ files. They can be used to rebuild the exe, but dont have anything that the .exe didnt have (they actually have less, because you dont know where those sections go, or how big they actually are).
I have 2 batches of Launchpads – and only the newer ones needed an update. I tested beforehand whether they would program the new chips, and updated only the ones which failed at this test. Everything worked without problems.
Hello, to all of those who bricked their Launch Pads.
If you could get access to either a bootstraploader adapter or MSP430 flash JTAG programmer. I can submit the extracted firmware files both old and new. Before I did my update, I connected the board to the Elprotronic flash/BSL adapter, I had at my disposal, and extracted the firmware file in TI txt format. So it can be directly re-loaded into the chip.
Actually, the update worked for me just fine even with MSP430 UART driver missing.
Good luck.
Hi Alex, thanks for this. You should put up a webpage documenting your files. We will be willing to host your article. Just message us at admin AT 43oh.com or use the “Contact Us” link in the header of this page..