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

1 Introduction

The typical MSP Flasher execution flow consists of the following steps. Optional steps can be activated or deactivated by using special triggers or parameters (see Section 3).

  1. Initialize FET debugger
  2. Perform FET recovery (if a corrupted FET firmware is detected)
  3. Update FET firmware (if a mismatch between firmware and MSP Debug Stack versions is detected)
  4. Power up the target MSP device
  5. Configure the target MSP for JTAG or SBW communication
  6. Connect to the target MSP and display device information
  7. Optional: Erase (parts of) the target device memory
  8. Optional: Load target code into the device from a TXT or HEX file
  9. Optional: Verify target code transfer
  10. Optional: Read device memory and write it to a TXT or HEX file
  11. Optional: Reset the device
  12. Optional: Lock JTAG access
  13. Optional: Reset the device
  14. Optional: Power down the device
  15. Optional: Start target code execution
  16. Disconnect from the target MSP device
  17. Close the FET connection

Status reports are written to a text file named log.txt. This file is saved in the Log folder under the folder where the MSP Flasher executable resides. If the Log folder does not exist, it is automatically created. New instances are appended to the log file, and old logs are never overwritten.

NOTE

For a GUI-based alternative to MSP Flasher, see UniFlash. As of version 4.0, UniFlash features a command line interface with MSP Flasher compatibility mode.