This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Is there a simple flash programmer for the MSP430 LaunchPad?

Other Parts Discussed in Thread: MSP430G2452, MSP430G2553

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:

  • Free
  • Small enough to email
  • Can program binaries (flash image: TI-TXT) onto MSP430G2xx2 parts on LaunchPad (MSP-EXP430G2)
  • Will use USB and emulation on board the LaunchPad and not just a separate piece of hardware (like the MSP-FET430UIF)
  • Works on Microsoft Windows

Options that meet the requirements:

Here are the other options I considered:

  • IAR, Free for smaller value line parts but it's a full IDE.  I want something small enough I can email
  • CCS.  Same as IAR (but free for all value line parts).
  • MSP-PRGS430 Software.  Requires MSP-PRGS430 hardware
  • Uniflash Too big to email (~200 MB)

What other options could I consider?

  • MSPDebug is free and supports different hardware options. It's  for linux though.

    http://mspdebug.sourceforge.net/

    Gustavo

  • Gustavo L said:

    MSPDebug is free and supports different hardware options. It's  for linux though.

    MSPDebug has since added these features (among others):

    • Windows support
    • LaunchPad support
    • MSP430 value line phase 2 device support

     

  • 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

  • Gustavo L said:

    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 said:

     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 targeted for the MSP430G2452.

    • regularFlash.txt is the binary (flash image: TI-TXT) made from the unmodified "LaunchPad Temperature Sense Demo - Source files" that are found here.
    • fastFlash.txt is the binary (flash image: TI-TXT) made from the above project but I double the LED flash rate in PreApplicationMode()

    2677.regularFlash.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    @f800
    21 82 B1 40 E8 03 00 00 B2 40 80 5A 20 01 B0 12
    48 FD B0 12 14 FD B0 12 92 FD B0 12 52 FC D2 43
    01 02 B0 12 C0 F9 B0 12 D8 FC 32 D2 B2 D0 03 00
    B0 01 32 D0 18 00 5F 42 28 02 0E 4F 5E 53 C2 4E
    28 02 4F 4F 0F 5F 0F 5F 9F 42 B4 01 08 02 8F 43
    0A 02 F2 92 28 02 02 20 C2 43 28 02 82 43 2A 02
    82 43 2C 02 C1 43 02 00 F1 92 02 00 0F 2C 5F 41
    02 00 0F 5F 0F 5F 92 5F 08 02 2A 02 92 6F 0A 02
    2C 02 D1 53 02 00 F1 92 02 00 F1 2B 1C 42 2A 02
    1D 42 2C 02 B0 12 CC FB 82 4C 2A 02 82 4D 2C 02
    91 83 00 00 03 24 C2 93 04 02 28 24 B0 12 FA FC
    C2 93 04 02 07 24 B2 40 F8 00 06 02 B0 12 5E FB
    C2 43 04 02 1C 42 2A 02 1D 42 2C 02 3E 40 F9 02
    0F 43 B0 12 B2 FC 3C 80 C6 50 3D 70 07 00 3E 40
    00 04 0F 43 B0 12 1E FB 4C 4C 82 4C 06 02 B0 12
    5E FB B1 40 E8 03 00 00 B0 12 D8 FC 1E 42 2A 02
    1F 42 2C 02 1E 82 2E 02 1F 72 30 02 82 4E 32 02
    82 4F 34 02 B2 93 34 02 05 38 12 20 B2 90 FB FF
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    2475.fastFlash.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    @f800
    21 82 B1 40 E8 03 00 00 B2 40 80 5A 20 01 B0 12
    48 FD B0 12 14 FD B0 12 92 FD B0 12 52 FC D2 43
    01 02 B0 12 C0 F9 B0 12 D8 FC 32 D2 B2 D0 03 00
    B0 01 32 D0 18 00 5F 42 28 02 0E 4F 5E 53 C2 4E
    28 02 4F 4F 0F 5F 0F 5F 9F 42 B4 01 08 02 8F 43
    0A 02 F2 92 28 02 02 20 C2 43 28 02 82 43 2A 02
    82 43 2C 02 C1 43 02 00 F1 92 02 00 0F 2C 5F 41
    02 00 0F 5F 0F 5F 92 5F 08 02 2A 02 92 6F 0A 02
    2C 02 D1 53 02 00 F1 92 02 00 F1 2B 1C 42 2A 02
    1D 42 2C 02 B0 12 CC FB 82 4C 2A 02 82 4D 2C 02
    91 83 00 00 03 24 C2 93 04 02 28 24 B0 12 FA FC
    C2 93 04 02 07 24 B2 40 F8 00 06 02 B0 12 5E FB
    C2 43 04 02 1C 42 2A 02 1D 42 2C 02 3E 40 F9 02
    0F 43 B0 12 B2 FC 3C 80 C6 50 3D 70 07 00 3E 40
    00 04 0F 43 B0 12 1E FB 4C 4C 82 4C 06 02 B0 12
    5E FB B1 40 E8 03 00 00 B0 12 D8 FC 1E 42 2A 02
    1F 42 2C 02 1E 82 2E 02 1F 72 30 02 82 4E 32 02
    82 4F 34 02 B2 93 34 02 05 38 12 20 B2 90 FB FF
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    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

  • Gustavo L said:

    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 3
    Hardware: LaunchPad MSP-EXP430G2 (Hardware ID USB\\Vid_0451&Pid_f432&Rev_105 as seen in device manager)
    Device: MSP430G2452
    MSPDebug 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 said:

    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 --usb
    Devices on bus 000:
        000:000 0451:f432 eZ430-RF2500 [serial: 19FF469286D91E2B]

    C:\MinGW\mspdebug-0.19>ls
    AUTHORS    README              formats       mspdebug.man   ti_3410.fw.ihex
    COPYING    blinky2452.hex      history5.dll  readline5.dll  ti_3410.fw.txt
    ChangeLog  blinky2452Slow.hex  libusb0.dll   regex2.dll     ui
    Makefile   drivers             mspdebug.exe  simio          util

    C:\MinGW\mspdebug-0.19>mspdebug rf2500 "prog blinky2452.hex"
    MSPDebug version 0.19 - debugging tool for MSP430 MCUs
    Copyright (C) 2009-2012 Daniel Beer <dlbeer@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 \\.\libusb0-0001--0x0451-0xf432
    Initializing FET...
    FET protocol version is 30394216
    Configured for Spy-Bi-Wire
    Set Vcc: 3000 mV
    Device ID: 0x2452
    Device: MSP430G2452
    Code memory starts at 0xe000
    Number of breakpoints: 2
    Erasing...
    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 MCUs
    Copyright (C) 2009-2012 Daniel Beer <dlbeer@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 \\.\libusb0-0001--0x0451-0xf432
    Initializing FET...
    FET protocol version is 30394216
    Configured for Spy-Bi-Wire
    Set Vcc: 3000 mV
    fet: FET returned error code 4 (Could not find device (or device not supported))

    fet: command C_IDENT1 failed
    fet: identify failed
    Trying again...
    Initializing FET...
    FET protocol version is 30394216
    Configured for Spy-Bi-Wire
    Sending reset...
    Set Vcc: 3000 mV
    Device ID: 0x2452
    Device: MSP430G2452
    Code memory starts at 0xe000
    Number of breakpoints: 2
    Erasing...
    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) starts
    to toggle the red/green LES's.

    access with the MSP430Flasher results:

     ****************************************************************************

    Evaluating additional triggers...done
    Initializing interface on TIUSB port...done
    Checking firmware compatibility...done
    Reading FW version...done
    Reading HW version...done
    Powering up...done
    Configuring...done
    Accessing device...done
    Reading device information...done
    Resetting device...done
    Refreshing 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 download
    while "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


     

     

     

**Attention** This is a public forum