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

Debugging CC1310 using XDS100v3

Darnell Melvin
Prodigy 20 points

Other Parts Discussed in Thread: CC1310

The following is the error message that I am getting.  We are using the xds100V3 to debug our cc1310 MCU. I am using Windows 10, CCS v6, using a bread board to temporarily build our circuit, and the following image is the circuit design.

Error connecting to the target:
(Error -233 @ 0x0)
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
(Emulation package 6.0.83.1)

Could you help me figure what's going on with our debugging process?

  • 0
    TI__Guru**** 171649 points
    Hi,

    This error can be found at section 5.13 of the page below:
    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    Given your device supports both cJTAG and JTAG and your schematics shows all four JTAG pins connected, can you make sure the device is actually using JTAG? The reason for my suspicion is that section 5.2 of the CC1310 TRM shows that cJTAG is the default mode after power up.

    www.ti.com/.../swcu117d.pdf

    I would also double check the pins used for TDI/TDO (the diagram does not show pin numbers) and follow the guidelines for JTAG shown at section 7.1 of the wiki page below:

    processors.wiki.ti.com/.../XDS_Target_Connection_Guide

    Hope this helps,
    Rafael
  • 0
    Mastermind 9135 points
    Are you using J1 to connect JTAG header of XDS100v3?
    For now, what I can see is there is not GND pin in J1. There should be common ground between target board and XDS100v3.

    After you add GND connection, you will encounter another issue "cable break". This is because there is a detection pin in XDS100v3 header which must be pulled low in target board. If this pin is not pulled low, the debugger will think the debugger cable is not connected.

    In summary, I would suggest you to use standard TI-14 pin JTAG header in your target board. This will save you a lot of trouble and time.