• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 2903 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/MSP432P401R: Error -261 @ 0x0 Invalid response was received from the XDS110 (JTAG comm error)

Javier Hoffmann
Prodigy 60 points

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hello everyone,

I am having some troubles with Energy Trace+ (XDS110-ADD-ON) 

the message I am getting is the following: 

 

CORTEX_M4_0: JTAG Communication Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 7.0.188.0) 

CORTEX_M4_0: 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

 

This happens in the main Blinky as well as in the project that I am working with. 

Without the Extension EnergyTrace works fine

*CCS v 8.0

*Xds110Addon 

*MSP432 connected via JTAG to the XDS110 (also powered)

 

  • 0
    TI__Guru**** 169754 points
    Hi,

    This error is quite elusive but it seems related to a timeout on data communications between the XDS110 and the host. The thread below links to a few others that have similar discussions and some possible workarounds.
    e2e.ti.com/.../735772

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 60 points

    The error has disappeared! 

    I went back to the settings, unclicked all Energytrace stuff and run the program again, run normally as it should, changed back to EnergyTrace and run it again, it worked again. finally I set it to Energytrace+ and it worked again just fine!

    I was also amazed, what kind of sorcery is this

  • 0 in reply to Javier Hoffmann
    TI__Guru**** 169754 points
    Hi,

    Although I am glad the issue is gone, I supect the source of the problem may have been a slowdown on the host (due to a concurrent program running on it) or maybe even a busy USB connection (that could cause slowdowns and thus trigger some of the data corruption seen).

    As mentioned in the thread I linked, the problem is still very elusive without a clear way to reproduce it.

    I will report back if I find anything more conclusive.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to Javier Hoffmann
    Prodigy 60 points

    Though the error randomly appears, can be solved by restarting changing configuration / hard reseting the module.

    really awkward and annoying error