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

XDS510 debugger usually does not connect to TMS302C6713B

Kennon Conrad
Prodigy 40 points
Other Parts Discussed in Thread: TMS320C6713B

We are using a XDS510 USB debugger with a TMS320C6713B processor on a custom circuit board.  The DSP is working fine on our prototypes except for one aspect.  When we try to connect the debugger to the target, it fails to connect about 80% of the time.  When it fails to connect, we get the following error message:

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 follwed by an emureset and reconnect to each target.

I/O Port = 510

Board Name: C6713 DSK via XDS510 USB Emulator

Cpu Name: DSP_C671x

Abort:  Close Code Composer Studio.

Retry:  Try to connect to the target again.

Cancel:  Remain disconnected from the target.

Diagnostic:  Run diagnostic utility.

The JTAG chain always scans correctly and passes all of the tests in the SDConfig utility.  I tried a slower JTAG clock speed, but that had no impact on the problem.  This problem is occuring on several copies of the prototype.

What are the possible causes of the "Error 0x80000200/-1060" error message?

  • 0
    TI__Guru**** 169874 points

    Hi,

    The OCS errors are usually related to unreliable JTAG connections, therefore I am almost positive either the board or the routing have something to do with it. The procedure you used to verify the connection is correct, but I am afraid the utility is sending just a small amount of data that does not trigger the issue. 

    From within the SDConfig, can you try to run a continuous loop of scans and see if it still passes? Go to the menu Emulator --> Diagnostics and set the Test Loop count to "0" (for infinite passes) and an arbitrary Stop Error count (it will stop after 'n' errors) - check the attached screen (I am using SdConfigEx4 but SdConfig should be similar).

    If it fails, then I would investigate the hardware-related topics in the Debugging JTAG Connectivity page. Also, if you have other devices in the same scan chain (configured as bypass devices), they may be destabilizing a power supply or resetting the DSP at the moment the emulator attempts to connect. This scenario happened in the past.

    If it still does not fail, then it can be an issue with CCS configuration. One thing that tripped me some times in the past was that I used the DSK6713 configuration (that has an embedded XDS510USB emulator) instead of a standalone XDS510USB connected to a C6713 device. I know they are different and may cause connection failures. All the other software configurations you mentioned indicate a good approach to workaround the problem.

    Please give these tests a try and in the meantime I will see if I can think of any additional details and tests that can help you.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 40 points

    Hi Rafael,

       As I previously stated, the boards passes all of the tests in the SDConfig utility.  This includes a continuous loop of scans.

       I would have appreciated a list of possible causes for the Error 0x8000200/-1060 "unknown" error.  Texas Instrument's Tim Love has already suggested all of the standard things to try from SDConfig, reviewed our schematic, asked questions about the layout and found nothing wrong, so he asked me to post here, even though I had lost faith in TI's ability to provide a specific and detailed answer to my question about the possible causes of error code -1060.

       It appears that we have solved the problem, but are still verifying things.  We found that one of our peripheral DRAM memories was not being configured correctly and this was causing intermittent failures in our built in test software.  For some reason the failure path put the CPU in a state that made it unreachable from the JTAG interface.  I will try to post additional details if they become available.

    Regards,

    Kennon