LAUNCHXL-CC1352P: Cannot run a debug session

Hi Suvashan,

Please follow the task 2 in this training and make sure you have followed the procedure. Simplelink academies are a good resource to get you started with simplelink devices.

dev.ti.com/.../node

But in your case, can you please click on the highlighted portion in the image and not on the project. It should give you access to pause and the step over and step into functions. 

Hi Sid

Thank you for the resource, I will definitely go through that ASAP.

Regarding your advice, when I select the highlighted portion after setting a breakpoint in my main_nortos.c in the while loop, I've suspended the debug session and instead of the debugger hitting the breakpoint, I get the following error, which is the same error mentioned in my post. See the image attached.

Hi Suvashan, 

Did you follow the steps in the drivers quick start guide to import the project into CCS?

https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_7_10_02_23/docs/simplelink_mcu_sdk/html/quickstart-guide/tidrivers-quick-start.html

This walks you through the way to import the project. If you have indeed followed the steps, please import another example and check if that works.

Regards,

Sid

Hi Sid

I've actually done this, when I imported the project in the initial post itself. The same thing happens. 

Hi Sid

I've been digging through the forum and found this related question now, but there is a link provided that supposed to help, but does not exist.

Hi Suvashan,

The link you have pointed out is related to a project that needs the boot image manager. But in your case the gpio interrupt project must work without the BIM. It does not need the BIM. 

I just tested the the gpioInterrupt nortos gcc project in the SDK. It seems to work fine.

Which version of the SDK are you using? And are you using a Launchxl-CC1352P1 launchpad as your hardware?

Please check if you are using LP-CC1352P7-1. I ask this because the error message in the call stack seems to indicate the wrong chip.

Regards,
Sid

Hi Sid

Apologies for the inactivity. 

I am using version 7.10.02.23 of the SDK. I can also confirm I am using the Launchxl-CC1352P1.

Just a note, I tried to flash a Launchpad-CC1310, using a CCS project of uart2echo and that worked fine. I looked for a CCS version of the uart2echo project for the Launchxl-CC1352P1, but there are only gcc, ticlang and iar projects. Could there be a possible issue with the gcc compiler on the IDE install on my side? I've not changed anything on the original IDE install.

Hi Suvashan,

I would assume the build would itself fail if it was a compiler issue.

The "CCS" compiler option has been deprecated and now the ticlang compiler is the recommended default compiler for CCS. Can you try the TiClang version of the project?

You can find if the compiler has been discovered by CCS correctly in the menu: Window->Preferences->Code Composer Studio->Build->Compilers

Regards,

Sid

Hi Sid

Thanks for responding to me all this time.

However, the TIClang version does not work. Same situation occurs where the program cannot be debugged. 

Hi Suvashan,

When I connected a LP-CC1352P7-1 launchpad and debugged the Launchxl-CC1352P1 project, I got the same error as you have in your original screenshot. 

The error you see is typically seen in this scenario.

Not sure why else this error shows up.

Regards,

Sid

Hi Sid

I am not sure what to do at this stage, other than thank you for trying to help me.

As a sanity check, I used my CC1352, and attempted to debug an LP-CC1352P7-1 project, which unsurprisingly did not work and yielded the same error as you. I also tried a different version of the SDK (6.41.00.17), to no avail as well. I've had to resort to using a CC1310 Launchpad which seems to work fine and I am able to debug. 

Hi Suvashan,

Can you please open a SmartRf Studio session and check if device gets detected as CC1352P.

Regards,

Sid

Hi Sid

I believe it is being detected as CC1352P. See the image attached. 

Hi Suvashan,

Please can you download uniflash. https://www.ti.com/tool/UNIFLASH

 And in the memory section, you can select FCFG1, press go and send the screen shot of the memory addresses here. Please check the screenshot uploaded here for reference.

We need to know why the device is not being evaluated as CC1352P1.

Regards,

Sid

Hi Sid

Apologies for the inactivity. Attached, you may find a screenshot of the memory ranges.

. 

Hi Suvashan,

I am really sorry the late response on this thread.

Please can you also upload the FCFG1 content which includes the address 0x50001318? 

Thanks in advance

Regards,

Sid

Hi Suvashan, 

In addition to the FCFG1 content from that address, please can you also check the revision of the device in SmartRF studio. Your previous screenshot was from SmartRF flash programmer 2. Smart RF studio gives out the version number in more detail. 

https://www.ti.com/tool/download/SMARTRF-STUDIO-7

Regards,

Sid

Hi Suvashan,

Is this issue still happening? Or you found the solution for it?

Regards,

Sid

Hi Sid

I've attached the FCFG1 content for the LP. 

Hi Sid

Thanks for this. Can you please send the full link to the forum post that you quote. The link has been truncated and appears just as text.

Regards

Sorry, Here is the link

e2e.ti.com/.../2982624