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

5 Firmware Update

During runtime, if MSP Flasher detects a conflict between the firmware version of the debug probe (FET) and the version of the MSP Debug Stack (MSP430.dll), it prompts the user to let MSP Flasher update the firmware:

>> The firmware of your FET is outdated. >> Would you like to update it? (Y/N): _

Type Y to update the firmware of the FET, display status reports, and on success continue execution of the MSP Flasher routine. Type N to resume the running instance with the outdated firmware. TI recommends not using MSP Flasher while the FET firmware does not match the version of the MSP Debug Stack.

If an error is detected during the update, MSP Flasher prompts the user to retry or cancel the update:

>> Update failed. (R)etry/(C)ancel? _

Type R to repeat the attempt to update. Type C to resume the running instance with the outdated firmware.

NOTE

The -s switch suppresses this user prompt. If there is a mismatch between the FET firmware version and the MSP Debug Stack version, a firmware update is done automatically.

NOTE

For fully automated FET firmware updates, run the following command:

MSP430Flasher -n NO_TARGET -s

MSP Flasher updates only the FET firmware and does not attempt to connect to any target MSP device.