• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 304 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.

MSPM0G1506: Error -616 while trying to connect/debug via external XDS110 Debug Probe

Vikror Ostapiuk
Prodigy 10 points
Part Number: MSPM0G1506
Other Parts Discussed in Thread: UNIFLASH, CC3220S, CC3220S-LAUNCHXL, CC1352P

While trying to load the sample application via Code Composer Studio(version 12.7.0) to MSPM0G1506 could be seen the error -616 and advice to lower the TCLK frequency.

The same error could be seen in Uniflash while trying to read MCU memory or perform mass erase.

The TCLK frequency has been tried to be lowered in the CCS project target configuration, but it  made no difference with the error

As XDS110 debug probe has been used the CC3220S Launchpad(CC3220S-LAUNCHXL) and MSP432P401 Launchpad.

With the same debug probes the CC1352P MCU has been debugged successfully without errors

MSPM0G1506 MCUs have been ordered on the DigiKey online store

I would be grateful to hear the possible causes of this error and how it could be fixed

Respectfully yours,

Viktor Ostapiuk

  • 0
    TI__Mastermind 25620 points

    Hi Viktor,

    Is this a custom board? Have you been able to successfully program any chips previously? I have you scoped the SWDIO and SWCLK pins to verify the signal integrity is good?

    Send us a scope capture of the SWDIO and SWCLK signals.

    Regards,
    Luke

  • 0 in reply to Luke Ledbetter
    Prodigy 10 points

    Hello Luke,

    Yes, it is the custom board on which was placed MSPM0 MCU

    After your suggestion to capture the scope of SWDIO and SWCLK signals, some unstable signals were detected during the start of the connection sequence. 

    After that discovery, such steps were done:
    1. The length of wires between the debugger and MSPM0 MCU was reduced

    2. Wires, which connect SWDIO to the debugger and SWCLK to the debugger were separated

    3. Verified stable connection to the ground and the wire length between grounds was also reduced

    After completing these steps, the MCU was successfully connected via Uniflash and programmed with an SDK sample via Code Composer Studio.

    Thank you very much for suggesting checking signals on SWDIO and SWCLK pins.

    Respectfully yours,

    Viktor Ostapiuk