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.