CCS/LAUNCHXL-CC2640R2: CCS/LAUNCHXL-CC2640R2:

Les,

Given the launchpad used to work previously on this laptop (I assume with prior versions of CCS), I suspect you may be running into the issue I mention on this e2e thread. 

e2e post said:

But before doing that, I would like to cover one important detail that I learned today from the development team that did the newer XDS110 emulation package software (emupack). 

The emupack that ships with CCSv9.0.x versions (8.1.0.00012) has some jitter on the clock edges when running at 2.5MHz (the maximum speed of this version(, which may cause very random communication errors with the target. Although errors are not regularly seen with the compact Launchpads, the longer cconnections of your setup (or even the use of isolation adapters, for example) can contribute to this problem. 

The remedy for this is to lower the TCK speed to 1.25MHz. This will reduce the jitter and should warrant a reliable connection. 

This issue will be fixed in the next release of the emupack, to be available publicly soon. 

Please let me know if the workaround helps you.

Regards,

Rafael

Thank you for the info provided Rafael

The launchpad previously worked on the CCS v9 installation.

Please advise where/how to change the TCK setting to 1.25 MHz

some more info...

it appears the XDC tool version has been superseded -  v3.51.2.21 required for the project. v3.55.xx loaded

Can the XDC version be changed by the end-user to a specific version?

I have started a new workspace folder and will see if I import project/s again-

In the new workspace I get the following error msg

Regards

Les

Regards

Les

Hi Rafael

Thanks for the help

I tried the firmware reload options as suggested but I could not get it working.- tried 2 different Launcpad CC2649R2 with same error in both cases

I reloaded CCS, tried the older version  of the emulation package and then the latest v8.1.0.00012

Both gave similar errors.

I got it going eventually for a short while  (from the XDS config page as suggested) and then the XDS110 disconnected again with the following msg

The system appers to be very inconsistent all of a sudden??

Ithink after the last prompted CCS update??

Regards

Les

Hi Rafael

debugger still does not work

CCS prompted for a emulation package upgrade to v 8.2.0.0004 (wasv8.1.0.00012)

Launchpad reported the same error after loading emulation package and running program by clicking 'debug'

restarted CCS  - launchpad LED is green and XDS110 can be seen in windows device manager.

When CCS loads debug probe the same message as previously displays. It promted for an XDS firmware upgrade but displayed msg - cannot connect when upgrade was attempted.

I tried to load firmware using XDSDFU utility -  the firmware.bin file only has a date stamp of  03/06/2019 (3 June 2019)

Is there another way to upgrade the XDS110 to v8.2.0.0004 emulation package?

Regards

Les 

Les,

Please apologize for the delay; I couldn't reproduce the scenario here on my environment, but I recalled the thread below, which does not help much given this error is quite elusive and without a clear root cause. 

https://e2e.ti.com/support/tools/ccs/f/81/t/737649 

I tested both CCSv9.0.1 (with emupack 8.1.0.00012) and CCSv9.1.0 (with emupack 8.2.0.00004) but the problem did not show itself. 

One important aspect when updating the firmware is that, due to a bug on the Dialog box, it stays open even after you click ont he "Update" button. If you click a second time, the probe gets disconnected and the firmware update process fails. 

Re-launching the debugger or fully power cycling the board (disconnect/re-connect teh USB cable) seems to restore the previous condition with the updated firmware. 

The method you are using in your last post (via the xdsdfu utility) is the safest one. 

http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#updating-the-xds110-firmware 

This behaviour will be fixed in a future release of our tools. 

Regards,

Rafael