• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 414 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/CC2640R2F: CC2640R2F

Dmitriy Konstantinov
Intellectual 550 points

Part Number: CC2640R2F

Tool/software: Code Composer Studio

Hello!

After upgrading CCS to 9 version(from 8). As upgrading i mean download new CCS from TI site and install.

So i do with new CC2640R2 simplelink pack (3.10 ) and xdc tools(3.55)


And after all of that CCS said me that software of debugger(XSD110) have to be upgraded too. So after upgrading to new firmware XDS 110 i have this problem:

When i trying to connect by flash programmer or rf studio all is ok, but firstly programmer or rf studion places it's firmware to XDS110.

So what can i do to have debugger from CCS v.9 again?

Best regards, Dmitiry.

  • 0
    TI__Guru**** 171729 points

    Dmitriy,

    After CCS updated the firmware of the XDS110, did you unplug and re-plug it from the USB port? 

    Sometimes the update process fails to fully reset the XDS110 Debug Probe, thus failing any subsequent connection attempts until the probe is fully turned off. 

    If that does not work, can you see if the XDS110 Deubg Probe is being acknowledged by the host? Check the section Troubleshooting of the page below:

    http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html

    Alternatively you can try to update the firmware via the command line. Details are shown at section Updating the XDS110 Firmware of the link above.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 550 points

    Yeah, i've fully re-plugged XDS110 from usb port - nothing changes expect the types of errors in console.

    So, often the errors are different - what does it mean?

    Best regards, Dmitiry.

  • 0 in reply to Dmitriy Konstantinov
    TI__Guru**** 171729 points

    Dmitiry,

    Thanks for sending the last errors. You seem to have moved up one level in the connection layers - i.e., the previous error was between the host and the Debug Probe, which was solved as the host can properly communicate with your Debug Probe and connect to your CC2640R2F device (the Cortex_M3_0 messages).

    The issue now is located on the actual Flasher routine that performs the code writing to the target. In other words, this may indicate either a problem with the flasher or perhaps a problem uncovered with the newer version of the software. 

    Can you check the section JTAG Clock speed considerations of the XDS110 page below? It contains useful information that may be the root case for this problem. 

    downloads.ti.com/.../emu_xds110.html

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 550 points

    Hello, Rafael!

    Yeah, this chapter of the link was the key to my problem!

    So, reducing jtag speed has resolved my issue, thank you!

    Best regards, Dmitriy.