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: latest tool version inconsistency, debug issues, problem changeging launchpad version

Part Number: CC2640R2F
Other Parts Discussed in Thread: UNIFLASH, CC2650

Tool/software: Code Composer Studio

Hi there,

latest activity using latest TI toolchain left me with quite a bit frustration.

Starting witn the same problem like in this threat

I figured that Uniflash Version: 5.0.0.2289 and CCS Code Composer Studio
 Version: 9.0.1.00004
on
OS: Windows 10, v.10.0, x86_64 / win32
Java version: 1.8.0_144


are not looking for the same XDS110 firmware. Both reflash the XDS110 with their own firmware they think is the newest.

Starting with the issue that I can debug only one time, then a mass erase is required to allow another debug session and so forth, just like as in the threat above.

Trying the same steps then recommended there, made me aware, that I accidentally connected a CC2650 Launchpad Rev. 1.2 when a debug session was started with the virgin central project from Stack 3.10.

Then when I tried to correct the chip version settings I was ending up with flash overlap errors.

further steps I tried:

made sure that the right device is selected for both stack and app

run a clean for the entire projct

deleted the target directories with the make and .obj files for both stack and app

what else needs to be done?