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/LAUNCHXL-CC1352R1: Cannot run debugging on example projects from new SimpleLink CC13x2 26x2 SDK - v2.40.00.81

Part Number: LAUNCHXL-CC1352R1

Tool/software: Code Composer Studio

Hello,

I am running what I presume is the latest version of Code Composer Studio - CCS8.3.0.00009.

For some reason I am unable to debug any examples from the newest CC13x2 26x2 SDK.  I click debug, they upload to the board, but the "Resume" button is grayed-out and the board is unresponsive. 

In the debug window if I highlight the XDS110 Debug probe I am given the option to suspend, and when I do that I am given the following error: 

"Can't find a source file at "C:\Jenkins\jobs\FWGroup-DriverLib\workspace\modules\output\cc26xx_aga_2_0_ext\driverlib\bin\ccs/./../../../driverlib/chipinfo.c" 

Locate the file or edit the source lookup path to include its location."

At that point I now have the option to click "Resume", but the board still does nothing.  I have tried two separate boards to no avail. 

If I downgrade to examples from SDK v2.30.00.45 then I have no problems.  In all cases I have been deleting the "tirtos_builds....." project entirely from my file system and allowing it to be re-imported with the example.  I also attempted to roll back the version of XDCTools being used by the v2.40 SDK build and still got the same results.

  • Are you sure you have a rev. E device?

    From the release note:

    "This release supports CC13x2 and CC26x2 devices with silicon revision E (PG 2.1). No support for previous silicon revisions or LaunchPad™ development kits using earlier silicon revisions. If you’re unsure of the revision number of your device, please see the Package Symbolization and Revision Identification section of the Errata Note."

    Please see: e2e.ti.com/.../767771

    Siri
  • Hi Siri, thanks for the reply. That's exactly the issue. I was not aware that there was a new hardware revision.

    Best,

    Scott