Part Number: MSPM0G3507
Hello Forum,
I'm encountering an issue with my MSPM0G3507 development kit and require assistance.
Yesterday, I successfully flashed the kit with new firmware using a J-Link Plus connected to XDS110-In, enabling a target I2C peripheral. This initial flash was done after removing all external MCU jumpers except for 3V3 and GND, and debugging via VS Code.
Following this, I modified the firmware to use PB2 and PB3 for the I2C peripheral, aiming to connect an Antratek USB-ISS dongle. However, after attempting to debug this new configuration, the MSPM0G3507 became unresponsive. Believing the device might be locked, I first tried a factory reset via J-Link, which unfortunately failed.
Next, I reconnected the jumpers and attempted a factory reset through CCS. I initiated a project-less debug session and ran the MSPM0_Mailbox_FactoryReset_Auto command. The process repeatedly hangs on:
GEL EXPRESSION: GEL_DAPInit_SECAPCommand()
GEL_EXPRESSION: MSPM0_Mailbox_FactoryReset_Auto()
with the following output:
CS_DAP_0: Initiating Device Factory Reset
CS_DAP_0: Attempting CS_DAP connection
CS_DAP_0: Attempting SEC_AP connection
CS_DAP_0: Command Sent
CS_DAP_0: Start hardware Reset using NRST
CS_DAP_0: Initiating BOOTRST Board Reset
CS_DAP_0: Reset line asserted
CS_DAP_0: Reset line de-asserted
CS_DAP_0: Board Reset Complete
CS_DAP_0: Reset done
CS_DAP_0: SEC_AP Disconnect
CS_DAP_0: SEC_AP Reconnect
After that, I attempted a standard debug session yields the error:
Texas Instruments XDS110 USB Debug Probe/CORTEX_M0P Error connecting to the target: Connection to MSPM0 core failed. Possible root causes: 1) Debug access within NONMAIN was disabled or enabled with password. 2) Peripheral mis-configuration (e.g improper watchdog or clock). To see a more detailed diagnostic of the issue, please press the 'Read boot diagnostic' button.
Upon pressing the 'Read boot diagnostic' button, the console displays:
CS_DAP_0: Device diagnostic read = 0x00000036
CS_DAP_0:
Possible root causes could be one or multiple of the following:
1) Invalid CRC configuration
2) Invalid BCR configuration
3) Invalid BSL configuration
The suggested recovery methods are:
Perform a DSSM factory reset
If method one does not work, remove power, hold nRST low, connect the device while nRST is held low, and then perform a DSSM factory reset
I have attempted both of these recovery methods without success.
Given these persistent errors, my question is: if there are any other recovery methods or strategies to regain access to this MSPM0G3507?
If addionital information is needed please contact me.
Kind regards,
Luuk
