• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1985 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.

CCS/LAUNCHXL-F280049C: Cannot connect to the target

Mokan kanna Venugopal
Prodigy 170 points
Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi,

                         Recently i've bought Lauchxl-F280049C. As given in the quick start guide, i've downloaded & installed C2000Ware in the specified path (C:\\ti\C2000_xxx) and imported the examples given in the same folder for the respective device in CCS v7. As mentioned in the quick start guide page no.25 changed the target configuration file's JTAG/SWD/cJTAG Mode to cJTAG 2-Pin & tried connecting to the target. But it gives the following error


-----[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: Texas Instruments XDS110 USB Debug Probe_1]

I've attached the log files for your consideration.

I would appreciate if someone could help me out.

Test connection log with 2pin cJTAG.txt 
[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\Mokan\AppData\Local\TEXASI~1\CCS\
    ti\1\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 'Nov  6 2017'.
The library build time was '10:36:36'.
The library package version is '7.0.100.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 '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: Texas Instruments XDS110 USB Debug Probe_0]

[Start: Texas Instruments XDS110 USB Debug Probe_1]

Execute the command:

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

[Result]


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

C:\Users\Mokan\AppData\Local\TEXASI~1\CCS\
    ti\1\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 'Nov  6 2017'.
The library build time was '10:36:36'.
The library package version is '7.0.100.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 '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: Texas Instruments XDS110 USB Debug Probe_1]

  • 0
    TI__Guru**** 169444 points
    Hi,

    The error is reported in the reference below (just search for the error number)

    dev.ti.com/.../

    Given this launchpad can have a completely isolated connection between the debug probe and the device, I would double-check all the jumpers and see if they are correctly configured. The board documentation should have additioanl details about this.

    One detail: although not related to the error message itself, the first screenshot shows an additional XDS110 Debug Probe in your target configuration file. Can you remove the second "Texas Instruments XDS110 USB Debug Probe" entry just to be sure you don't run into any issues in the future?

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 170 points

    Hi,

    could you please send me the board document. If it is spruii7, then we require the jumper settings. Since It is not very clear in the document.

    thanks and regards,

    Mokan kanna

  • 0 in reply to Mokan kanna Venugopal
    Prodigy 170 points

    We have removed the additional XDSprobe as shown above. still unable to connect. gives the same error is generated byUSCIF driver or utilities

  • 0 in reply to Mokan kanna Venugopal
    TI__Guru**** 169444 points
    Mokan,

    Please apologize for the delay; I just returned from vacation. Are you still having this issue?

    If so, do you have a photograph of the board with the jumper settings? I suspect that something else may be at fault in your case.

    I also ordered the same launchpad, but it should take a few days to arrive.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    Prodigy 170 points

    The problem is not resolved yet. the jumper settings is shown in the photo attached herewith.

    please help us to solve the problem.

    thanks and regards,

    Mokan kanna

  • 0 in reply to Mokan kanna Venugopal
    TI__Guru**** 169444 points
    Mokan,

    Thanks for the photograph. I just received my board here and I can tell the jumpers seem to be in the same positions - however, to my surprise, my board can't connect as well.

    I tested many things to no avail until I finally ran into the following thread.
    e2e.ti.com/.../753823

    Following the procedure at the thread restores the connection back.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    Prodigy 170 points

    Dear Rafa,

    thanks for the reply. we were able to connect the board as per your advice.we chose to build LED blinky program and flashed it to the the board. the LED b;inks only for a few seconds. how to verify if the program is loaded properly.

    thanks and regards,

    Mokan kanna