• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 538 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/TMS320C6713B: CCS/TMS320C6713:CCS connection error with Spectrum Digital XDS510 USB

user3456100
Prodigy 60 points
Part Number: TMS320C6713B

Tool/software: Code Composer Studio

Hello.

When trying to connect TMS320C6713B and CCS(Code Composer Studio) by Spectrum Digital XDS510 USB,
sometimes I can't connect to CCS.
I measured the waveform of JTAG interface(TCK,TDO,TMS,TDI) when I can't connect to CCS.
The waveform of connect error occurs is diffrent from normal waveform.
However, we have confirmed that the power supply, reset, clock and JTAG connection are normal.
Please tell me why the error waveform occurs.
The acquired waveform is shown in the attachment.(Left is normal,right is error)

  Attachment.pdf

For reference, error messages are shown below.
『Error connecting to the target:Error 0x80000200/-1060
Fatal Error during: OCS, An unknown error prevented the emulator
from accessing the processor in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each
target from the emulator.The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.』

Regards,

Manabe

  • 0
    TI__Guru**** 171034 points

    Manabe,

    Please apologize for the delay and thanks for sending such detailed post. 

    As you pointed out, a glitch on the data output by the XDS510USB Debug Probe (TDO pin) is happening - the failed scenario is missing a transition. Just out of curiosity, did you zoom into the transition itself to see if this s a single pulse to zero or more? Not that this will be terribly relevant to this scenario, though. 

    One possible explanation for this scenario is a processing load on the server that may have caused the Debug Probe to fail to send the proper data. This explanation stems from the fact that XDS510 Debug Probes are "soft" probes - i.e., the JTAG protocol stack and managing is handled by the host computer. The probe itself has a FPGA that handles the bit banging and some data formatting. 

    Another theory could be of physical/electrical nature. However, apart from a small difference in the voltage levels, looking at the waveforms I can't see any significant differences between the two scenarios. I don't think there are any ground loops that are affecting this (noise is quite low), I don't see reflections and the load on the lines seem to be the same (reflected by both GND and Vcc levels). 

    All that said, unfortunately I can't provide much more than a few comments. The XDS510 technology is not supported anymore and therefore our options to further investigate and provide a fix are quite limited. Sorry.

    Regards,

    Rafael