• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 294 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.

LAUNCHXL-CC2640R2: LAUNCHXL-CC2640R2

Shweta Savdekar
Prodigy 110 points
Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: CC2640,

I am working on LAUNCHXL-CC2640R2 Development Board for Custom PCB CC2640

IDE – CCS Cloud Version 1.2.0

SimpleLink CC2640R2 SDK - 5.30.00.03

TI Code Generation Tools for Arm: 18.12.2.LTS

XDCTools: 3.51.03.28

Imported Simple Peripheral Project and have defined it for CC2640R2DK_CXS

I am getting the below error while building the project.

IcePick_C: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 12.7.0.00059)

Could you please help me resolving the issue?

what could be the possible cause for this?

  • 0
    TI__Expert 3980 points

    Shweta,

    Thanks for reaching out! I am going to attempt and recreate your setup on my end and get back to you on a resolution. Can you share some more details on how you are setting up the device when you run into this error? 

    It doesn't appear that this is a build error but an error when connecting to the launchpad. 

    Thanks,

    Luke

  • 0
    Prodigy 110 points

    Hello Luke,

    Thank you for your quick response.

    I just recompiled my existing Simple Peripheral project and it suddenly lost connection to the target Board.

    We have checked the Hardware connections and their connectivity as well.

     

    I have tried to verify the debug probe connection and below is the error I have received.

    This utility has selected a 100/110/510 class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'Sep 6 2023'.
    The library build time was '09:57:39'.
    The library package version is '9.13.0.00201'.
    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 '-260' (0xfffffefc).
    The title is 'SC_ERR_XDS110_OPEN'.

    The explanation is:
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: no XDS110 is connected, invalid
    firmware update, invalid XDS110 serial number, or faulty USB
    cable. The firmware and serial number may be updated using the
    xdsdfu utility found in the .../ccs_base/common/uscif/xds110
    directory of your installation. View the XDS110SupportReadMe.pdf
    file there for instructions.

    [End]

     

    The program is getting build without errors. While Debugging getting below error message.

    Error initializing emulator:
    (Error -260 @ 0x0)
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: no XDS110 is connected, invalid
    firmware update, invalid XDS110 serial number, or faulty USB
    cable. The firmware and serial number may be updated using the
    xdsdfu utility found in the .../ccs_base/common/uscif/xds110
    directory of your installation. View the XDS110SupportReadMe.pdf
    file there for instructions.
    (Emulation package 9.13.0.00201)
     

    Please let me know what the possible cause for the errors could be and how to resolve this.

  • 0 in reply to Shweta Savdekar
    TI__Mastermind 42420 points

    Hi,

    To clarify, is this error occurring when you attempt to connect to the launchpad or to your custom PCB?

    Best Regards,

    Jan