• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 56 subscribers
  • Views 717 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.

CC2652R: XDS110 error in CCS11.1

N3xus132
Intellectual 345 points

Part Number: CC2652R
Other Parts Discussed in Thread: UNIFLASH,

Hello,

In the past I always used the XDS110 for debugging of our SimpleLink based products. It happened very often in the last weeks that it was not possible to start a debug session because the XDS failed with the following 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.6.0.00172)

Today it reached a point where I can say that it is not usable anymore because it doesn't work to connect to a target or if it randomly does it will break up during the debug session. I downloaded the last CCS (11.1) because I thought that possible bugs will be solved in this version. Unfortunately it still doesn't work. After a restart it almost always work to connect to the target but if I stop the debug session and start it again it doesn't work.

I also checked it with the xdsdfu utility and if it is in this state where I cannot debug it also shows 0 devices in this tool. If I reconnect the device it shows up in xdsdfu.exe -e normally.

Flashing using Flash Programmer 2 also works without any problem. Uniflash doesn't always work perfectly.

Can you help me with this issue?

Thanks
Armin

  • 0
    Guru 735695 points

    Can you take a picture to show me your connection between CDS110 and your CC2652R? Do you use long debug cable between XDS110 and your CC2652R? If so, make the cable as short as possible.

  • 0 in reply to YiKai Chen
    Intellectual 345 points

    I can send a photo tomorrow. I tried 3 different cables and the shortest was about 20cm. I also tried to reduce the frequency without any effect.

  • 0 in reply to N3xus132
    Guru 735695 points

    It’s not recommended to use debug cable longer than 10 cm.

  • 0 in reply to N3xus132
    TI__Guru**** 223577 points

    Hello N3xus132,

    Based on the debug information given, I agree with YK's assessment that this is a hardware connection issue and recommend that you improve upon the robustness and reliability of your setup to increase the success of communicating with the XDS110.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Intellectual 345 points

    That is also what I thought. I tried 3 different cables that I used in the past for debugging and I know that they worked. I cannot accept that you say that the USB cable should have 10cm maximum if you deliver 50cm cables with the launchpads. It would mean that you ship a solution that you know is not working robust enough.

    I will try even more cables tomorrow but I don’t believe that it will work because I even tried to lower the JTAG frequency…

    Do you have any other suggestions that I could try?

  • 0 in reply to N3xus132
    TI__Guru**** 223577 points

    Are you testing multiple boards, and are they all displaying similar behavior?  I assume this experienced with a custom design and not a TI LaunchPad?  Has anything happened to the board or cables recently which could have degraded performance?

    Regards,
    Ryan

  • 0 in reply to N3xus132
    Guru 735695 points

    I think “deliver 50cm cables with the launchpads” is USB cable not the ribbon cable between XDS110 and CC2652R. What I described debug cable is recommended not longer than 10cm is ribbon cable between XDS110 and CC2562R.

  • 0 in reply to YiKai Chen
    Intellectual 345 points

    Oh ok. I didn't realize that you meant the ribbon cable. Nevertheless I have the problem that I don't see the XDS110 itself anymore. The debugging problem is a secondary problem. The main problem I have is that the tools are not finding the debugger anymore after starting a debug session once.

    Here a short description of my process:

    - Connecting Launchpad or Debugger via USB to the PC
    - Starting Debug Session in CCS 11.1
    - Debug Session fails or is stopped manually
    - Launchpad / Debugger disappears. Starting a debug session again is not working. I have to connect it to another USB port or restart the PC for beeing able to start again a debug session

    Ryan Brown1 said:
    Are you testing multiple boards, and are they all displaying similar behavior?

    Yes, I saw this behavior with different custom designs but i accepted it and was able to cope with it. Now I cannot really continue my work. There also was nothing that could have degraded the performance of the hardware.

  • 0 in reply to N3xus132
    Guru 735695 points

    If you use flash programmer 2 or Uniflash, can they recognize your XDS110 debugger?

  • 0 in reply to YiKai Chen
    Intellectual 345 points

    If I connect it without starting a debug session in CCS I can use Flash Programmer 2 without any issues. I am not sure if it always works with Úniflash because I mainly used Flash Programmer 2.

    After a CCS debug session also Flash Programmer 2 doesn't recongize the XDS110 anymore, I have to reconnect the USB cable to see it again.

  • 0 in reply to N3xus132
    Guru 735695 points

    Try to restart your Windows and CCS to see if it works.

  • 0 in reply to YiKai Chen
    Intellectual 345 points

    What I did now:
    Copied the project to a new workspace, Updated the SDK to the newest 5.30.
    Now it seems that the error disappeared. I can debug now without issues...