• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 101 subscribers
  • Views 300 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.

TMS320C5535: Error while downloading code to device:- C55xx: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (E

Sangeeta Gunwani
Intellectual 580 points
Part Number: TMS320C5535

Hi,

I am getting this error

C55xx: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.222.0)

Please let me know what to check

I checked the Emulation package by executing "Test Connection" it its 6.0.222.0 

And I get this error

[Start: Texas Instruments XDS100v2 USB Debug Probe]

Execute the command:

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

[Result]


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

C:\Users\hjvaid\AppData\Local\TEXASI~1\CCS\
ti\2\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 'jioserdesusb.dll'.
The library build date was 'Apr 8 2016'.
The library build time was '02:44:08'.
The library package version is '6.0.222.0'.
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: Texas Instruments XDS100v2 USB Debug Probe]

Thanks and Regards,

Sangeeta Gunwani

  • 0
    TI__Guru**** 161600 points

    Hi,

    Is this  a custom board? If yes, check if you have the correct voltage leveles, when you power up the board. 


    Also check this e2e thread:
     

    Best Regards,
    Yordan

  • 0 in reply to Yordan Kovachev
    Intellectual 580 points

    Yes, its a custom board and we checked the voltage levels. Vcc is 3.29V

    We were testing GPIOs and SPI interface just two days back and it was working fine. But now its giving this error 1063.

    Tried reinstalling CCSv6.1.3. Changed the emulator cable and target board and tried updating the device driver.

    Nothing seems to work.

    Still getting this error

    C55xx: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.222.0)

    Thanks and Regards,

    Sangeeta Gunwani

  • 0 in reply to Sangeeta Gunwani
    TI__Guru**** 161600 points

    Hi,

    Check the following guide:
     

    Best Regards,
    Yordan

  • 0 in reply to Yordan Kovachev
    Intellectual 580 points

    Thanks for the reply.

    We are able to connect and download the code to the target device. 

    We tried reinstalling the CCSv6.1.3 and then restarting the computer. Also reinstalled the device driver software for the emulator.

    Now I am able to download the code and debug it.

    I am not sure what fixed the device ID error. Or will it happen again. It really costed us time.

    When we did test Connection it gave the following result but I am able to download the software to the target device.

    [Start: Texas Instruments XDS100v2 USB Debug Probe]

    Execute the command:

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

    [Result]


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

    C:\Users\hjvaid\AppData\Local\TEXASI~1\CCS\
    ti\2\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 'jioserdesusb.dll'.
    The library build date was 'Apr 8 2016'.
    The library build time was '02:44:08'.
    The library package version is '6.0.222.0'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    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 FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 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).

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 64 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 38 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[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 XDS100v2 USB Debug Probe]

    Is there anyone I can talk to over the phone. Any technical person who is local so that we dont fall into this issue again as it costs us a lot of time.

    Thanks and Regards,

    Sangeeta Gunwani