SLAU847E October 2022 – May 2025 MSPM0L1105 , MSPM0L1106 , MSPM0L1116 , MSPM0L1117 , MSPM0L1227 , MSPM0L1227-Q1 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346 , MSPM0L2227 , MSPM0L2227-Q1 , MSPM0L2228 , MSPM0L2228-Q1
DSSM commands are serviced by the bootcode upon a BOOTRST. If passwords are enabled for DSSM commands, the commands do not execute until the correct password sequence is entered. Refer to DSSM Commands for possible DSSM commands and values.
| DSSM Command | DSSM Value |
|---|---|
| Factory Reset | 0x020Ah |
| Mass Erase | 0x020Ch |
| Password Authentication | 0x030Eh |
| Data Exchange | 0x00EEh |
| Wait for debug | 0x0206h |
The "Factory Reset" command erases all contents within main and nonmain memory, then nonmain is re-populated with default contents. This command is useful in the cases of:
The "Mass Erase" command erases all contents within the main memory but nonmain remains untouched. This command is useful in the case of:
The "Password Authentication" command unlocks debug access after the correct password has been processed.
Data exchange is the only DSSM command that does not require a BOOTRST to process the command. This command is used in combination with factory reset, mass erase, or password authentication which do require a password. After sending the initial command to the mailbox and performing a reset, the user must begin sending the password to the TXDATA register. After each word 0x00EEh must be written to the TXCTL register.
The "Wait for Debug" command resets the peripherals defined by the reset level and then forces the device into the reset handler.
The user can also create a custom DSSM command and perform actions defined by the user. This is done by having the debugger communicate to the M0+ core through the TXDATA and TXCTL registers. The core can then receive messages from the debugger and send responses back by using the RXDATA and RXCTL registers for the debugger to read. CPU interrupt events can be configured for activity seen in the TX_DATA buffer, RX_DATA buffer, and DAP connection.