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.

TMDSCNCD263: no connection to target

Part Number: TMDSCNCD263

I have a  TMDSCNCD263 controlCard, CCS v12 is in Linux, when I was trying to download binary today, it says there is an update for the XDS110 driver, I entered yes. after it came back, no way to connect o to the target.

is there a way to reconnect to the board  to reload or get back to previous version, so I can connect to the card.

thanks

Yanmin

  • Hello Yanmin,

    Please take a look at this page:

    https://dev.ti.com/tirex/explore/node?node=A__ALFqIj4dX6S.TZRERoSphA__xdsdebugprobes__FUz-xrs__LATEST

    When you run xdsdfu -e, what result do you see?

    What exact version of CCS are you using?

    Thanks

    ki

  • I powered down everything, including linux, restarted, therror is slightly different now .

    Error connecting to the target:
    (Error -1170 @ 0x0)
    Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 9.13.0.00201)

    ------------------

    the ccs is Version: 12.5.0.00007 

    The xdsdfu result is:

    yh@tower:/opt$ ./ti/ccs1250/ccs/ccs_base/common/uscif/xds110/xdsdfu -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 Embed with CMSIS-DAP
    Version: 3.0.0.26
    Manufacturer: Texas Instruments
    Serial Num: S26A0375
    Mode: Runtime
    Configuration: Standard

    Found 1 device.

    -----------------------

    still not able to connect.

    Thank you very much.

  • <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 Embed with CMSIS-DAP
    Version: 3.0.0.26
    Manufacturer: Texas Instruments
    Serial Num: S26A0375
    Mode: Runtime
    Configuration: Standard

    Found 1 device.

    This looks good.

    Can you try running a JTAG connectivity test and provide the results? They can copy and paste to a file that you can attach to this thread.

    https://dev.ti.com/tirex/explore/node?node=A__AMCrhRy9n80ZsUrBFVdo1Q__ccs_devtools__FUz-xrs__LATEST

  • I ran the test for this board with cc13xx_cc26xx_2pin_cJTAG_XDS110

    it is slightly differ from the video. but the ir AND dr TEST WERE successful.

    log file( not able to attache file, so paste here:

    Start: Texas Instruments XDS110 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


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

    /home/yh/.ti/ccs1250/0/1/BrdDat/testBoard.dat

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

    This utility has selected a 100/110/510 class product.
    This utility will load the adapter 'libjioxds110.so'.
    The library build date was 'Sep 6 2023'.
    The library build time was '09:54:42'.
    The library package version is '9.13.0.00201'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

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

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • Thank you. The low level JTAG connection is actually good.

    The error 1170 DAP issue is documented in the below document (see section called "Cannot access the DAP"):

    https://dev.ti.com/tirex/explore/node?node=A__ANoamrIZPWD2-6T-NDDWGg__ccs_devtools__FUz-xrs__LATEST

    One potential issue could be that the target board is not correctly configured/initialized. Check the SDK User's Guide:

    https://dev.ti.com/tirex/content/mcu_plus_sdk_am263x_09_01_00_41/docs/api_guide_am263x/EVM_SETUP_PAGE.html