• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 122 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.

LAUNCHXL-F280049C: Communication error

Diego Munera
Prodigy 20 points
Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: C2000WARE
when I try to establish communication with my LAUNCHXL-F280049C, using CCS v8, I get the following message:

-----[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.

I appreciate any help you can give me.

Thank a lot,

Diego
  • 0
    TI__Guru 50430 points

    Hi Diego,

    Is it possible for you to update the CCS to the latest one? It will update all the driver files.

    Also, please make sure you are using XDS110, 2-pin cJTAG mode in the target configuration file.

    Also, please refer to C2000 Academy which walks through step-by-step guidance how to get started with C2000 Devices.

    dev.ti.com/.../node

    Thanks & Regards,

    Santosh

  • 0
    Prodigy 20 points

    Hi Santosh,

    Today I updated the CCS 8.3.1.00004 version. I am using connection via USB port: XDS110, but I still cannot connect with the card

    thaks and regards,

    Diego

  • +1 in reply to Diego Munera
    TI__Guru 50430 points

    Hi Diego,

    Can you not update to CCS 11 or CCS12? That is the latest CCS.

    Looks like it enumerated properly, so probably driver is not the issue. Are you running any example or creating your own target configuration file?

    If you are using example from C2000Ware, please make sure you have CPU1_LAUNCHXL_RAM build configuration and also launchpad target configuration is active.

    If you are manually launching the target configuration, then make sure you are selecting xds110 as emulator and then use 2-pin cJTAG mode. Please refer to the Launchpad user's guide:

    https://www.ti.com/lit/pdf/spruii7

    Thanks & Regards,

    Santosh