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.

TMDSEMU110-U: Test Connection is throwing error value= -266 title=SC_ERR_XDS110_CPLD_UPDATE

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: AM4378

I am goal is to connect JTAG to AM437x-GP EVM to Read some register values.

Here is the steps i fallowed:

 1. installed latest CSS software on windows. i.e CCS12.1.0.00007_win64 

 2. installed ti emulator package from XDS110 website i.e ti_emupack_setup_9.2.0.00002_win_64.

 3. Created a Debug Target Configuration file i.e NewTargetConfiguration.ccxml  with Connection as TI XDS110 USB Debug probe.

     Board or Device type as AM4378

4. I updated XDS110 probe firmware  also to latest version.

>xdsdfu.exe -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 Probe with CMSIS-DAP
Version: 3.0.0.13
Manufacturer: Texas Instruments
Serial Num: 00000000
Mode: Runtime
Configuration: Standard

Found 1 device.

When i click TestConnection button. i am getting below error.  

 

[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)]------------------------------------

C:\Users\NALLAM~1\AppData\Local\TEXASI~1\
CCS\ccs1210\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'May 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
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 '-266' (0xfffffef6).
The title is 'SC_ERR_XDS110_CPLD_UPDATE'.

The explanation is:
An internal error occurred. The CPLD image update failed. Unplug and
re-plug the XDS110, and try again.

[End: Texas Instruments XDS110 USB Debug Probe_0]

  • Hi Siva,

    My only suggestion would be to try reprogramming the bootloader and firmware as shown in the XDS110 Debug Probe User's Guide. You can find the version of the bootloader and firmware provided by your Code Composer Studio installation at C:\ti\ccs1210\ccs\ccs_base\common\uscif\xds110, if you did default installation location on Windows. You could get the newest version of CCS if you wan the newest XDS110 firmware, but I don't know if that would be important.

    I will reach out to someone that is more knowledgeable about this debug probe to see if they have further suggestions.

    Best Regards,

    Ben Collier

  • Hi Ben

    I updated both bootloader and firmware as mentioned in xds110 Debug probe user Guide. 

    >xdsdfu.exe -b boot_loader.bin -r

    >xdsdfu.exe  -f firmware_3.0.0.13.bin -r

    After Update i power cycled xds110 debug probe  by unplugging & plugging the USB cable to the PC.

    I am getting same error after updating binaries.

    dbgjtag -f @xds110cjtag -S integrity


    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 '-266' (0xfffffef6).
    The title is 'SC_ERR_XDS110_CPLD_UPDATE'.

    The explanation is:
    An internal error occurred. The CPLD image update failed. Unplug and
    re-plug the XDS110, and try again.

    Regards,

    Siva.

  • Hi Siva,

    Could you try updating to CCS 12.1 and using the firmware included with that version? 

    I am waiting to hear back from someone that dealt with a similar issue in the past, but it is not clear if they found a solution.

    Best Regards,

    Ben Collier