• State TI Thinks Resolved
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 450 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.

SK-AM69: Issue with Debugger USB560v2 using SK-AM69

Kim Radmacher
Prodigy 70 points
Part Number: SK-AM69
Other Parts Discussed in Thread: TMDSEMU560V2STM-U, AM69

Hi TI,

I'm using a SK-AM69 and a brand new usb560v2 debugger connected to J15 20-pin CTI header for the first time.

I've installed Bh560v2Config v 1.0.0.14 and it's recognizes the debugger. But if I run the tests I am receiving the following error:

Blackhawk Configuration Utility Tests
    CMD: dbgjtag -X emulator,driver=bh560v2u,ioport=0 -S integrity -Y reset -S pathlength
    Loaded FPGA Image: C:\ti\ccs1260\ccs\ccs_base\common\uscif\dtc_top.jbc

    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 '-180' (0xffffff4c).
    The title is 'SC_ERR_CTL_NO_TRG_POWER'.

    The explanation is:
    The controller has detected a target power loss.
    The user must turn-on or connect the power supply for the target.

    RES: dbgjtag -X emulator,driver=bh560v2u,ioport=0 -S integrity -Y reset -S pathlength
    RES: Fail

Via CCSv12.7 I'm receiving this error:

CCS Test Connection
    [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\549KRA~1\AppData\Local\TEXASI~1\
        CCS\ccs1260\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\ccs1260\ccs\ccs_base\common\uscif\dtc_top.jbc
    The library build date was 'Mar 13 2024'.
    The library build time was '12:55:46'.
    The library package version is '12.7.0.00105'.
    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 '-180' (0xffffff4c).
    The title is 'SC_ERR_CTL_NO_TRG_POWER'.

    The explanation is:
    The controller has detected a target power loss.
    The user must turn-on or connect the power supply for the target.

    [End: Blackhawk XDS560v2-USB System Trace Emulator_0]

Both mention the power loss of the targets device, but checking the targets voltage on pin 5 of J15, I measure 3.3V.

The onboard debugger XDS110 is working fine though.

Does anyone has seen this before?

To me it seems that the USB560v2 debugger is broken.

Best,
Kim

  • 0
    TI__Mastermind 36307 points

    Kim,

    Quick test, are the two (XDS110 and XDS560v2) connected at the same time? There should only be one connected at a time, otherwise it defaults to the XDS110.

    Regards,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 70 points

    Hi Erick,
    no they were not connected at the same time. I disconnected XDS110.

  • 0 in reply to Kim Radmacher
    TI__Mastermind 36307 points

    Kim,

    I've tried the same setup, and for some reason the "Test Connection" and similar test on the Blackhawk Config Tool is failing. Not sure why this is the case. But I am still able to launch the CCS Target Configuration for J784S4:

    Can you please try connecting even though the test connection is failing? I suspect something in the SW needs updating but I don't see firmware updates for the XDS560 since 2017.

    Regards,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 70 points

    Erick,

    actually I did not try to launch the Target Configuration thanks for pointing this out. But unfortunetely I receive the same message.

  • 0 in reply to Kim Radmacher
    TI__Mastermind 36307 points

    Kim,

    I'm getting the same result as you actually, I thought once it connected it was correct but when connecting to a core I get the same error.

    I've tried across different boards (the EVM and the SK board for J784s4) but no luck. I also tried Windows and Linux, same result. It does not seem to be related to the USB560v2 drivers then, but with the EVM. Let me try a different board to ensure the debugger works, then perhaps narrow down if this is a debugger issue or a board issue.

    Thanks,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 70 points

    Thanks for your support on this Erick.

    The reason why I want to use XDS560v2 over the on-board XDS110 is to speed up the time to load a program onto C71x. Currently it takes about 7...8 minutes.

    Do you have any experiences regarding other debuggers being faster than XDS110, and of course are working with SK-AM69, maybe XDS100?

    Best,

    Kim

  • 0 in reply to Kim Radmacher
    TI__Mastermind 36307 points

    Kim,

    Yes, XDS560v2 is definitely the way to go to speed up that loading, I've experienced this myself in the past as well.

    My first recommendation is the XDS560v2 Spectrum Digital debugger, I tested that one as part of this thread because I wanted to ensure I had no issues in my setup. That one worked out of the box with no issues. And it's also the one the team here locally uses.

    The next recommendation is probably more costly and does not use CCS, but Lauterbach provides much more capability, but it is probably much more than what you need for your exercise.

    I don't think that we've used the XDS100 locally much, I can check internally and see if anyone has one and uses it.

    For now, the issue seems isolated to the USB560v2. I wanted to try downgrading my software to test it, perhaps to an old version of Linux (Ubuntu 14.04) and an old version of CCS (v10 or less) to see if that changes the behavior at all. It could be that some updates introduced this incompatibility with the Blackhawk drivers as even the utility can't connect with the device.

    Another thought is that it is an issue with HS-FS devices, but I tried on a GP EVM for J784s4 and it still portrayed the same issue.

    Regards,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 105 points

    Hi Erick, we purchased the TMDSEMU560V2STM-U which was recommended by TI and is listed as compatible with Sitara processors, as well as TDA4x CPUs. Can you confirm whether this CPU is supported by the debugger? All devices I can find for sale under the code XDS560v2 are supplied by Blackhawk. Can you recommend a supplier where we can get the Spectrum Digital version?

    Best,

    Simon

  • 0 in reply to Simon Williams
    TI__Mastermind 36307 points

    Simon,

    Simon Williams said:
    Can you confirm whether this CPU is supported by the debugger? All devices I can find for sale under the code XDS560v2 are supplied by Blackhawk. Can you recommend a supplier where we can get the Spectrum Digital version?

    It is supported, and we are looking into why these Blackhawk debugger are experiencing issues. I have not checked where the Spectrum Digital version of the debugger can be purchased myself, I believe it is discontinued based on other E2E threads: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/974867/tmdsemu560v2stm-u-spectrum-digital-debug-tools

    Are you seeing the same issues as Kim? Power-loss related failures?

    Kim Radmacher said:

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

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

        The value is '-180' (0xffffff4c).
        The title is 'SC_ERR_CTL_NO_TRG_POWER'.

        The explanation is:
        The controller has detected a target power loss.
        The user must turn-on or connect the power supply for the target.

    Can you please provide me your setup details (CCS version and OS version)?

    Kim,

    Likewise, can you provide me your CCS version and OS version? I need to check that this is not a regression that has occurred in newer versions of CCS or OS.

    Regards,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 105 points

    Hi Erick, sorry for not being clear, yes I am working with Kim on the same project and we're both looking into the debugger for AM69, Kim has the setup info that you asked for.

    Best regards,

    Simon

  • 0
    TI__Mastermind 36307 points
    Kim Radmacher said:
    Via CCSv12.7 I'm receiving this error:


    I see the CCS version here, it's the latest. What OS are you using?

  • 0 in reply to Erick Narvaez
    Prodigy 70 points

    Erick, I am using Windows 11.

  • 0 in reply to Kim Radmacher
    TI__Mastermind 36307 points

    Kim,

    Thanks for sharing that data point. I'm using Windows 10 and Ubuntu 22.04.

    For my next test I will try Ubuntu 14.04 with CCS v9 to see if it was a regression on the software side.

    On your side, do you have multiple USB XDS560v2 debuggers that you have tested, or only one?

    Regards,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 70 points

    Currently, we have just that one here

  • 0 in reply to Kim Radmacher
    TI__Mastermind 36307 points

    Likewise, I've got one, looking for a second that is known to work to test.