• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1671 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/LAUNCHXL-F280049C: Help launchpad LAUNCHXL-F280049C XDS debugger failling

Robbie Valentine86
Expert 1550 points

Part Number: LAUNCHXL-F280049C

Tool/software: Code Composer Studio

Hello,

I bought the LAUNCHXL-F280049C launchpad and opened the fir_f32 example project.  The project compiles fine, but when I click "Debug" I get the error shown below.

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.3.0.00003)

 


I haven't changed any jumper settings on the board from default and the board powers up and blinks leds with whatever default application is loaded.  I downloaded the latest CCS so I'm running version Version: 9.2.0.00013 .  During instillation I chose full install so I should have the drivers etc...  I've attached two screen shots as well showing my project configuration and the XDS ports in device manager.  I've also attached a screenshot of the error message.

Does anyone have any idea what might be going on or where I should look next??

  • 0
    Expert 1550 points

    Also - when I click the verify button in the first screenshot I get the following:

    [Start]

    Execute the command:

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

    [Result]


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

    C:\Users\RVALEN~2\AppData\Local\TEXASI~1\
    CCS\ccs920\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 'Aug 26 2019'.
    The library build time was '13:34:49'.
    The library package version is '8.3.0.00003'.
    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).

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

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

    The value is '-233' (0xffffff17).
    The title is 'SC_ERR_PATH_BROKEN'.

    The explanation is:
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

    [End]

  • 0 in reply to Robbie Valentine86
    Expert 1550 points

    I also tested the xdsdfu (very cool utility by the way) and managed to pull this information out of the debug probe.  It looks like the xds110 does infact have a serial number that is 8 char long.

  • 0 in reply to Robbie Valentine86
    Expert 1550 points

    I also tested the xdsdfu (very cool utility by the way) and managed to pull this information out of the debug probe.  It looks like the xds110 does infact have a serial number that is 8 char long.

  • 0 in reply to Robbie Valentine86
    TI__Guru**** 485691 points

    Hi Robbie,

    Please see: 

    Section A1 FAQ 3d (page 25) of: http://www.ti.com/lit/ug/spruii7a/spruii7a.pdf

    And also: https://www.youtube.com/watch?v=4ZoXwM3-Szw&feature=youtu.be

    Thanks

    ki

     

  • 0 in reply to Ki
    Expert 1550 points

    Hi Ki,

    Thank you for the reply!  Great catch!  I have made the recommended changes to my config and have gotten closer.  I can now successfully test the connection by clicking the "test connection" button in the ccxml file target config.  Result shown below.  Unfortunately this hasn't allowed me to connect to the target via debug - I still have the same error message.

    Test connection results

    [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\RVALEN~1\AppData\Local\TEXASI~1\
    CCS\ccs920\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 'Aug 26 2019'.
    The library build time was '13:34:49'.
    The library package version is '8.3.0.00003'.
    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]

  • 0 in reply to Robbie Valentine86
    TI__Guru**** 485691 points

    Robbie Valentine86 said:
    Unfortunately this hasn't allowed me to connect to the target via debug - I still have the same error message.

    Which error message? If you mean:

    Robbie Valentine86 said:
    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.3.0.00003)

    The above error is a failure when attempting to communicate with an XDS100 debug probe. The launchpad has an integrated XDS110 probe instead. I don't know why an error message for the XDS100 appears. Make sure you are using the correct target configuration file when launching a debug session.

    Thanks

    ki

  • 0 in reply to Robbie Valentine86
    Expert 1550 points

    Sorry Ki - your recommendation fixed it.  

    For anyone else - check to make sure that the debug configuration is using the correct target config / ccxml file.  That was where I went wrong.  I hadn't realized my debug configuration pointed to the wrong one.

    Thanks Ki!!

  • 0 in reply to Robbie Valentine86
    TI__Guru**** 485691 points

    Great to hear it is all working now. Thanks for the update!