• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 234 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSPM0G3519: Error While Debugging or flashing the code. Unable to reset the board

Dibyarekha Maharana
Prodigy 100 points

Part Number: MSPM0G3519
Other Parts Discussed in Thread: UNIFLASH

Hello,

 

I am using MSPM0G3519 TI's Launchpad. while debugging/ Flashing the code I am getting the following error. I am uanble to reset the board too. Please help me to get out of this.

 

Error:  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.
Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 20.4.0.3835) 
Error:  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.

  • 0
    TI__Expert 7881 points

    Hi Dibyarekha,

    Can you try the following steps:

    1. Disconnect the LaunchPad from power
    2. Open a Uniflash session for the device
    3. Press and hold the NRST button (S3)
    4. Connect the LaunchPad to power while continuing to hold the NRST button
    5. Click on the Settings & Utilities tab and issue a manual Factory Reset DSSM command
    6. Release the NRST button when the console prompts you to press the NRST button

    If this doesn't work, see section 7.1 of the MSPM0 MCUs Development Guide to see if any of the other methods work.

    If the device is not recoverable, then it is likely bricked. This can happen for many reasons, but the most common reason is from erasing NONMAIN and not writing anything to NONMAIN before power cycling the board.

    Best,

    Owen