• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 406 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.

MSPM0G3507: DAP Connection Error when using the Texas Instruments XDS110 USB Debug Probe

Son Goku
Prodigy 149 points
Part Number: MSPM0G3507


Tool/software:

Hi experts, 
I have trouble with this issue, and it isn't very pleasant.

I've double-checked the connection and tried a few different approaches, but the problem still isn't fixed. Can you suggest a way to resolve this?

Best Regards,
Son

  • 0
    TI__Expert 5285 points

    Hi Son thanks for reaching out! Does this also happen when you disconnect the USB cable and reconnect? You may need to go into the XDS110 folder within the TI installation folder and do an XDS110 reset from there.

    -Brian

  • 0 in reply to Brian Dempsey
    Prodigy 149 points

    Thanks very much Brian!
    Today I encountered a rather puzzling issue. When I flashed a firmware onto my board for the first time, everything worked fine and I used __BKPT(0) for debugging. However, after terminating that debug session, the second firmware upload—and all subsequent attempts—resulted in an error: 

    Can you guess what might be causing this issue? If it's related to the firmware, I can provide it for you to review. Or the problem might be CCS or an outdated LaunchPad firmware programming tool?

    Thanks and regards,
    Son

  • 0 in reply to Son Goku
    TI__Expert 5285 points

    Hi Son, it may be that because you added the breakpoint in the firmware, and if you terminated the debug session at this point in the code this could be why you are seeing that. Can you go up to the top menu in CCS under scripts and do a manual factory reset? This should fix the issue hopefully. You will need to right click on the target configuration for your board in the project explorer window, right click and select start a project-less Debug. Next, in the debug tab under threads, right click Cortex_M0P and connect target. Then the scripts for the device should become available for you to reset the device.

  • 0 in reply to Brian Dempsey
    Prodigy 149 points

    Thanks Brian!
    - I just tried your way, but I don't know if I did it right as you said. Can you give me more detailed steps?
    - I also tried factory reset auto, but the MCU just stuck here.

    Why is that? I also tried factory reset MCU before, but it didn't work and stuck

    Thanks and regards,
    SON

  • +1 in reply to Brian Dempsey
    Prodigy 149 points

    Hi Brian!
    I did a factory reset auto and I can load and debug normally. And maybe all errors will be fixed if the mcu does a factory reset right? Except for the incorrect Nonmain-flash

    Best regards,
    SON

  • 0 in reply to Son Goku
    TI__Expert 5285 points

    Yea when you do the factory reset (manual, you have to press the reset on the board, apologies for failing to mention that. You should be good to go now with the full reset.