SLAU654E November   2015  – February 2019

 

  1.   MSP Flasher
    1.     Trademarks
    2. 1 Introduction
    3. 2 Compatibility
    4. 3 Triggers and Arguments
    5. 4 Exit Specifications
    6. 5 Firmware Update
    7. 6 Segment Erase
    8. 7 Example Cases
      1. 7.1 Loading and Executing Target Code From a TXT File
      2. 7.2 Reading Device Memory
      3. 7.3 Accessing a Device With a Device Activation Code
      4. 7.4 Securing the Target Device
      5. 7.5 Unlocking a Password-Protected Target Device
    9. 8 Using MSP Flasher on Unix
    10. 9 Error Codes
  2.   Revision History

2 Compatibility

MSP Flasher supports the following operating systems:

  • Windows® 7 32 bit or 64 bit
  • Windows 8 32 bit or 64 bit
  • Windows 10 32 bit or 64 bit
  • Ubuntu® 12.04 32 bit or 64 bit
  • Ubuntu 14.04 32 bit or 64 bit
  • Ubuntu 16.04 32 bit or 64 bit
  • OS X® 10.9 or newer

NOTE

MSP Flasher for Linux does not support eZ430™ development tools. This includes the Value Line LaunchPad™ development kit with eZ430 onboard emulation, eZ430-Chronos™ development tool, and older MSP-EXP430 experimenter boards with eZ430 onboard emulation.

MSP Flasher requires a hardware interface to communicate with MSP target devices. The following TI flash emulation tools (FETs) are supported:

NOTE

Do not disconnect the JTAG or emulator USB cable while MSP Flasher is running. Wait until MSP Flasher execution is finished before disconnecting the debugger or target device.

NOTE

To differentiate between multiple eZ430 tools (for example, two or more Value Line LaunchPad tools connected to the same host PC), connect each tool individually or use the unique identifier that is reported by MSP Flasher.
("Found USB FET @ HID0xxx:COMxxx").

Use this identifier with the –I switch whenever more than one eZ430 debugger is connected.