• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 1049 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.

CCS/TMDSEMU110-U: "Invalid response" and others problems

Egor Karlin
Intellectual 690 points

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: ENERGYTRACE, CC2642R, CC2650STK

Tool/software: Code Composer Studio

We have 2 XDS110:

1) XDS110 from "SensorTag DevPack"

2) TMDSEMU110-U

The first device works fine with no errors. Many problems arise when working with the second debugger:

Errors: IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.2.0.00002)
CS_DAP_0: Error: (Error -215 @ 0x0) The semaphore for the test bus controller is in a time-out state. Unified-SCIF was unable to acquire the semaphore used to express ownership of a controller by a utility or debugger. You may have to exit other clients because the timeout occurred. (Emulation package 9.2.0.00002)
Cortex_M4_0: JTAG Communication Error: (Error -215 @ 0x0) The semaphore for the test bus controller is in a time-out state. Unified-SCIF was unable to acquire the semaphore used to express ownership of a controller by a utility or debugger. You may have to exit other clients because the timeout occurred. (Emulation package 9.2.0.00002)
Cortex_M4_0: Breakpoint Manager: Remove job failed: Register/memory write failure[22005]


Such errors occur periodically during debugging. Sometimes debug mode is interrupted. Sometimes breakpoints don't work. But none of this occurs in the first debugger.

We do not use EnergyTrace.

System characteristics:

Debian GNU/Linux 9

Code Composer Studio  Version: 10.1.0.00010

Target: CC2642R

  • 0
    TI__Guru**** 483451 points

    Hello,

    Just to confirm:

    1) CC-DEVPACK-DEBUG + CC2650STK target environment is fine

    2) TMDSEMU110-U + CC2642R target environment has the errors mentioned above.

    Assuming the above is correct, for the #2, is the CC2642R a custom board? Are both environments above running in Debian 9?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 690 points

    Hello Ki!

    One amendment: CC-DEVPACK-DEBUG + CC2642R target environment is fine.

    Yes, we use custom board with CC2642R. CC-DEVPACK-DEBUG  + custom board cc2642r is fine. TMDSEMU110-U + custom board cc2642r has the error.

    Both environments are running in Debian 9.  Now I upgrade my Debian to ver. 10. I'll try to run environments in Windows 10.

    Thanks

    Egor

  • 0 in reply to Ki
    Intellectual 690 points

    I tried to run environments in Debian 10. Errors appear less often, but still remain.

    I tried to run environments in Windows 10. No errors occurred.

  • 0 in reply to Egor Karlin
    TI__Guru**** 483451 points

    Thank you for the clarification and testing on Debian 10 and Windows.

    Sounds like it may be Linux specific. We do not officially support Debian distro, but many people do use CCS with it with minimal issues. I have used CCS on Ubuntu and have not experienced the issue you describe. I will try setting up a Debian 10 environment to see if I can reproduce the issue.

    How often does the errors appear on Debian 10? Does it happen (eventually) during every debug session?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 690 points

    Hi Ki,

    thanks for your reply.

    It's strange that under the same conditions CC-DEVPACK-DEBUG works fine.
    Error frequency: I ran debug mode 10 times. 4 times there were problems: 2 times the mode did not start and there was a JTAG error; 2 times there were non-critical errors that occurred 1 time during the operation of the mode.
    This is true for debian 10. On debian 9 there was a flurry of errors every time it was started.

    Indeed, the error is specific. It may not be possible to reproduce it. Perhaps this is due to the peculiarities of setting up my operating system or CCS. I can try running in CCS 9. If the error persists, then it can be assumed that the problem is in the OS settings. I didn't reinstall debian, I just updated it. All settings remain the same.

    Egor

  • 0 in reply to Egor Karlin
    TI__Guru**** 483451 points

    Thank you for the extra data points. I will try setting this up on Debian 10 and let you know how this goes.

    ki