• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 82 subscribers
  • Views 479 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.

TMS320F2812: Can't connect target to Debug with Blackhawk XDS560v2 - The controller has detected a cable break far-from itself.

l r
Prodigy 40 points
Part Number: TMS320F2812


We have a legacy board using the TMS320F2812 which we used to connect to with the obsolete Spectrum Digital XDS510.

We are now attempting to upgrade to the Blackhawk XDS560v2. However whenever I try to connect to the target I get this error:

Error connecting to the target:
(Error -183 @ 0x0)
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
(Emulation package 9.11.0.00128)

I am using the latest CCS 12.3, but also tried CCS 6.2 (which I also had installed) with the same effect.

This is the output I get when using the Test Connection routine:

[Start: Blackhawk XDS560v2-USB System Trace Emulator_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\Myself\AppData\Local\TEXASI~1\
    CCS\ccs1230\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'bh560v2u.out'.
Loaded FPGA Image: C:\ti\ccs1230\ccs\ccs_base\common\uscif\dtc_top.jbc
The library build date was 'Mar 10 2023'.
The library build time was '22:11:02'.
The library package version is '9.11.0.00128'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

[End: Blackhawk XDS560v2-USB System Trace Emulator_0]

Does anybody have any clue on what the issue might be?

  • 0
    TI__Mastermind 36526 points

    Hi,

    This issue can be caused by a number of things, including some pins not being connected between the JTAG debug probe and the MCU. If you have access to an oscilloscope, could you try probing TDO (yellow), TMS (purple), TCK (blue), and TRST (green) as shown below. The screenshot below was captured using the XDS100, but it should be similar for XDS560. It was a single-capture triggered on the falling edge of TMS. Could you try doing the same and see if your probed signals look the same? 

    Also, are you able to share the schematic of your target board, or at least the JTAG connections? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 40 points

    Hi, thanks for your response. Sorry for the late reply.

    Here's the schematic for the JTAG on theboard. The signals are connected to a 14-pin adapter.

    Note that this routing works for the Spectrum Digital XDS510 (actually works sometimes amidst resetting things and deleting the .launches folder, one of the reasons why I'm trying to migrate JTAG programmers).

    With the Spectrum Digital XDS510 I could see the JTAG signals (TRST, TCK, TDO, TMS respectively):

    However when I tried the same with the Blackhawk XDS560v2 I never get a trigger, no matter which signal and if the board is connected or not.

    Would this point to a faulty Blackhawk XDS560v2? The one I have is brand new, so it couldn't have been damage before.

    Regards,

  • 0 in reply to l r
    TI__Mastermind 36526 points

    Hi,

    I do not see anything wrong with your schematic, and it is not a good sign that you cannot see any signals when you try to trigger on different channels. Did you buy the debug probe directly from Blackhawk? Do you have any other boards that you would be able to try with the XDS560v2? Do you have any TI boards such as a controlCARD or other EVM? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 40 points

    I tested on a TI evaluation board and I got the same error. I'm currently contacting the XDS560 seller to try to get a replacement.

  • 0 in reply to l r
    TI__Mastermind 36526 points

    Hi,

    Just curious, have you been able to use the XDS560 successfully in the past? The only extra step for using the XDS560 vs any other debug probe would be to connect the 5V barrel jack, so I'm not sure what could be going wrong except for the XDS560 being damaged. 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 40 points

    No this was the first time we attempted to use a JTAG programmer other than the Spectrum Digital XDS510.

  • 0 in reply to l r
    TI__Mastermind 36526 points

    Hi,

    I am sorry to hear that. Is there a specific reason that you chose the XDS560, or would you be open to trying a different JTAG debug probe? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 40 points

    No there isn't a specific reason for using the XDS560 over another JTAG probe (given that it's not obsolete). I was also looking into trying the XDS110 if I can get one.

  • 0 in reply to l r
    TI__Mastermind 36526 points

    Ok, I would recommend getting an XDS110 from ti.com. Please let me know if you have any more questions.

    Best Regards,

    Ben Collier