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.

RTOS/TMDSCNCD28M36: I got build but I cant debug

Part Number: TMDSCNCD28M36

Tool/software: TI-RTOS

Hi i'm using TMDSCNCD28M36 but i cant connect target by an error about XDS100v3.

the code is down.

Error connecting to the target:
(Error -151 @ 0x0)
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.
(Emulation package 8.2.0.00004)

i have controlsuit4.9 installed already and using ccs_v9

and i using xds100v3 usbdebugprobe is my connect setting

let me know what do i need i to do

  • This is code which is about Test Connection

    ==================================================

    [Start: Texas Instruments XDS100v3 USB Debug Probe_0]

    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\User\AppData\Local\TEXASI~1\CCS\
    ccs901\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 'jioserdesusbv3.dll'.

    An error occurred while soft 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 '-151' (0xffffff69).
    The title is 'SC_ERR_FTDI_OPEN'.

    The explanation is:
    One of the FTDI driver functions used during the connect
    returned bad status or an error. The cause may be one or
    more of: no XDS100 is plugged in, invalid XDS100 serial number,
    blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
    Use the xds100serial command-line utility in the 'common/uscif'
    folder to verify the XDS100 can be located.

    [End: Texas Instruments XDS100v3 USB Debug Probe_0]

  • ps i already used ccs_7 and that time i got connected and i uninstalled and reset my computer environment

    but now i changed 9 and setting my ide again

    and thats it so what am i going to say is the code is ok and the connecting usb cable and the microchips are done

  • This is a host connection error below reported by CCS when the device driver is unable to communicate with the JTAG debugger.

    Please have a look at this page. All of the recommendations we have for troubleshooting this type of error is documented there: 
    http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html#host-connection-error