SLAAEQ5 March   2025 MSPM0C1103 , MSPM0C1104 , MSPM0C1104-Q1 , MSPM0C1105 , MSPM0C1106 , MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G1518 , MSPM0G1519 , MSPM0G3105 , MSPM0G3105-Q1 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3505 , MSPM0G3505-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3518 , MSPM0G3518-Q1 , MSPM0G3519 , MSPM0G3519-Q1 , MSPM0H3216 , MSPM0L1105 , MSPM0L1106 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346 , MSPM0L2228 , MSPM0L2228-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Cyber Security Requirement Introduction
    1. 1.1 Cyber Security Requirement for MSPM0
  5. 2MSPM0 Debug Register Introduction
  6. 3Implementation
    1. 3.1 Debugger with Mailbox
    2. 3.2 MCU
      1. 3.2.1 Usage and Configuration of Nonmain
      2. 3.2.2 MSPM0 Software Implementation
  7. 4Execution
    1. 4.1 First Time Flashing
    2. 4.2 Access to Locked MCU
  8. 5How to Customize Passwords
    1. 5.1 Password
    2. 5.2 Password Length
  9. 6Summary
  10. 7References

4.2 Access to Locked MCU

If the MCU has been password locked, then the following steps show how to reconnect the MCU and debug a new project.

Since the Nonmain has been configured during the first programming, there is no need to configure Nonmain for subsequent programming. For projects that are burned or debugged later, some changes need to be made. First, disable Nonmain flashing in the project properties, then comment out the Nonmain configuration code in boot_configwithPassword.c, as shown in Figure 4-2 and Figure 4-3.

Disable Nonmain Flashing Figure 4-2 Disable Nonmain Flashing
Comment Nonmain Configuration Code Figure 4-3 Comment Nonmain Configuration Code

After modification is completed, the following steps need to be performed to unlock and debug the MCU.

  1. Connect MCU and open target configuration in CCS to load CCS scripts.
    Open Target Configuration Figure 4-4 Open Target Configuration
  2. Add two CCS scripts into project.
    Add Scripts Figure 4-5 Add Scripts
  3. Enter in the password by CCS GUI interface and Ctrl + S to save the configuration.
    Input Password by GUI Figure 4-6 Input Password by GUI
  4. Launch the configuration.
    Launch the Configuration Figure 4-7 Launch the Configuration
  5. Use the scripts. Keep pulling down the reset pin, set MCU in reset mode and do not run the code. Then click the MSPM0_PasswordAuthForMSPM0C. Keep pressing the reset button.
    Run the Script Figure 4-8 Run the Script
  6. After this interface appears, which shows the DAP and SEC-AP has been connected and wait for the response, pull up the reset pin.
    Message Showing The Process of Mailbox Figure 4-9 Message Showing The Process of Mailbox
  7. When reset is pulled high, the debugger tries to connect to the DAP and start authentication of the MCU. If the verification passes, then the following information as shown in Figure 4-10 is displayed. In addition, the password sent by the debugger is also displayed in the console.
    Console Information Figure 4-10 Console Information
  8. MCU is unlocked and access the memory or flash code.
Note: Note, that once debugging is finished, execute boot reset to make the Nonmain configuration effective. The MCU is locked again. For easy reset, pull down reset pin for 1s, then power off and on again. Figure 4-11 shows an error message for users who do not have enough password attempts to access the MCU.
Fail to Connect MCU Figure 4-11 Fail to Connect MCU