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

3 Triggers and Arguments

MSP Flasher runs from an executable file called MSP430Flasher. This file accepts a number of triggers and arguments to access the full capabilities of the software. Table 1 lists all available triggers and arguments.

Table 1. Available Triggers and Arguments(1)

Trigger Arguments Description and Additional Information
-h / -? N/A Displays usage information (displays this table of command line switches)
-x N/A Displays available exit specifications (see trigger -z)
-i TIUSB or USB (default) Communication port for the FET debugger. TIUSB (or USB) is the default. Use COMn (for example, COM15) on Windows or ttyACMn (for example, ttyACM15) on Linux or usbmodemn (for example, usbmodem1421) on OS X to choose a debugger connected to COM port n. Use HIDn:COMn for specific eZ430 tools on Windows (see note in Section 2).

Use -i DETECT to execute a FET detection sweep, to display detailed information about all connected debug tools, and to prompt to select a FET.
COMnor ttyACMn or usbmodemn
HIDn:COMn
DETECT
-j fast Configures the MSP Debug Stack to increase or decrease the JTAG or SBW frequency of the FET.
medium (default)
slow
-n Device name Optional for MSP430™ MCUs, mandatory for MSP432™ MCUs.

The name of the device being accessed (prompt if mismatch between found and selected device).

-n NO_TARGET executes MSP Flasher without attempting to connect to a target device. Choose this option to detect if a certain FET is connected or when the FET firmware should be updated only.
NO_TARGET
-r [Filename, mem_section] Triggers a read operation in target device memory section specified by mem_section. The memory content is written to a file specified by Filename. Available memory sections are:

MAIN = the main memory of the device

INFO = info memory (see trigger –u)

BSL = bootloader memory (see trigger –b)

RAM = random access memory

0x****-0x**** = custom memory section

Specify .txt as the extension for Filename to write data in TI-TXT format, or specify .a43 (or .hex) to write data in Intel-Hex format.
-w Filename Triggers a memory write operation. The accepted formats are TXT (TI-txt) or HEX (Intel-hex).
-v filename (optional) Triggers verification of the target memory against a target code file. If -w is used, no argument is required. For a stand-alone verify, provide the path to a target code file as an argument.
-u N/A Unlocks locked flash memory (INFOA) for writing.
-b N/A Unlocks the BSL memory for writing.
-e ERASE_ALL (default) Triggers an erasure of the device's MAIN memory (ERASE_MAIN) or MAIN and INFO memory including the INFOA segment if unlocked (ERASE_ALL).
ERASE_MAIN
ERASE_SEGMENT See Section 6. Use only with the -w switch.
ERASE_TOTAL Triggers a complete erase of the target device memory, which overrides and resets any memory protection settings. Use this command for SimpleLink™ MSP432 devices to force a factory reset. This will avoid the pop up if active JTAG/SWD lock is detected.
ERASE_USER_CODE Applicable for FR4xx devices only. Overrides and clears FRAM memory protection (also see the MSP430FR4xx and MSP430FR2xx family user's guide) and erases INFO and MAIN memory.
NO_ERASE Target memory is not erased prior to programming.

Caution: Overwriting previously programmed memory section without prior erase might result in data corruption on devices with flash memory. Use only with –w switch.
-p JTAG password Specifies the JTAG password that should be used to open a password protected target device (supported on FRAM devices only). The user is prompted if the password is incompatible with the password length specified by trigger -l.
-o L Operating mode for L092 and RF430FR152H family devices.

L = L092 mode (normal mode)

C = C092 mode (ROM development mode)
C
-f N/A Permanently secures JTAG access to the target MSP.

Caution: The device will no longer be accessible through JTAG or Spy-Bi-Wire. This action is irreversible.
-g N/A Disables the logging mechanism.
-a N/A Causes a nonintrusive target connection: use this switch if no reset should be applied to the target device on start up. Correct target device name must be specified using the -n switch.
-s N/A Suppresses the FET firmware update user prompt. In case of a mismatch between MSP Debug Stack and FET firmware, an update is forced.
-q N/A QUIET mode. No system messages will be displayed (except for errors and user prompts).
-z [exit_spec,…] Specifies the state of the device after programming.

For available exit specifications, see Table 2.

Use "," as a delimiter.
-m AUTO (default)
SBW2, SBW4, JTAG		 DEPRECATED. The applicable JTAG protocol is automatically detected by MSP Flasher. This trigger is ignored.
-l password_length DEPRECATED. The JTAG password length is automatically detected by MSP Flasher. This trigger is ignored.
-d [breakpoint addresses] DEPRECATED. The hardware breakpoint functionality is no longer maintained and will be removed in a future release of MSP Flasher.
-t Timeout_in_ms DEPRECATED. The hardware breakpoint functionality is no longer maintained and will be removed in a future release of MSP Flasher.
(1) Omitted mandatory arguments are replaced by the default options if possible, or the user is prompted to provide them later.