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

4 Exit Specifications

Select the desired state for the device to be set to when MSP Flasher finishes its operation. This can be done using the trigger -z and passing the arguments [exit_spec,…], where exit_spec is a valid exit specification shown in Table 2.

NOTE

The specifications are delimited with the ',' (comma) character and enclosed by square brackets.

Table 2. Available (Combinations of) Exit Specifications

Exit Specification Description
default (-z not used) The device does not receive a 'hard' reset and is powered down after programming. Target code execution does not start.
-z [VCC] VCC is set to the default value of 3000 mV. Target code execution starts.
-z [VCC=3600] The target VCC is set to a custom value (specified in millivolts). Valid voltages range from 1800 to 3600 mV. Target code execution starts. The eZ430 and eZ-FET debuggers do not support target voltages other than 3000 mV.
-z [RESET] The device receives a 'hard' reset (using the RST/NMI pin) after programming and is powered down.
-z [VCC(=x), RESET]-z [RESET, VCC(=x)] The device receives a 'hard' reset (using the RST/NMI pin) after programming and VCC is left on. Target code execution starts.