• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 110 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.

TMS570LS0914: During debugging using an XDS110 debugger, it will disconnect from debug state and show error which is in the Issue Description

Varalakshmi Y
Prodigy 10 points

Part Number: TMS570LS0914

Controller : TMS570LS0914

IDE : Code composer studio 12.3.0

Debugger : XDS110 Debug Probe

CortexR4: Unable to determine target status after 20 attempts
CortexR4: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging.

  • 0
    TI__Guru* 75096 points

    Hi Varalakshmi,

    Apologies for the delayed response!

    1. Try this Resolution:
    • First, completely power cycle your board and the XDS110 debug probe
    • Close Code Composer Studio (CCS)
    • Disconnect the USB cable from the XDS110
    • Wait for about 30 seconds
    • Reconnect the USB cable
    • Restart CCS
    1. If the issue persists:
    • Clear any existing debug configurations in CCS
    • Reset the emulator before attempting to connect again
    • Reload your program before continuing debugging
    1. Additional Configuration Steps:
    • If you continue to experience issues, try lowering the TCLK frequency in your debug configuration
    • Check that you're using the correct target configuration file for your device
    • Ensure all JTAG connections are secure and properly connected
    1. Known Issues with CCS 12.3.0:
    • There have been some reported connection issues with recent CCS versions
    • Consider temporarily downgrading to CCS 12.7.0 if the problem persists, as some users have reported better stability with this version
    1. Hardware Considerations:
    • Verify that there isn't any electrical noise affecting the JTAG signals
    • Check the integrity of your JTAG connections
    • Ensure your power supply is stable and clean

    The error message "Unable to determine target status after 20 attempts" typically indicates one of these issues:

    1. Communication problems between the debugger and the target
    2. Improper initialization of the debug interface
    3. Potential corruption of breakpoint operations in program memory

    --
    Thanks & regards,
    Jagadish.