CC1310: Debug CC1310 using Contiki

Apurva Ankleshwaria89

Part Number: CC1310
Other Parts Discussed in Thread: CC1350,

Hi,

I am running Contiki on CC1310 to create a mesh network. Initially we used TI CC1350 sensortag to build the Contiki code which is up and running. Now, we have made our custom board using CC1310. However, the code written for sensortag is not working in CC1310. I want to debug the code to figure out the issue here. However, I can't seem to figure out a way to debug the code on our custom CC1310 board.

Please note that hardware has been tested and is working fine. Software stack seems to be issue here. Also, note that I am currently using Contiki on Eclipse platform in Windows 10.

Any leads appreciated.

over 6 years ago

0 YiKai Chen over 6 years ago

Guru 735455 points

Do you try to use UART to output some information for debugging?

0 Apurva Ankleshwaria89 over 6 years ago in reply to YiKai Chen

Intellectual 460 points

Hi YK Chen,
I want to use hardware/breakpoint debugging with CC1310 using Contiki
-Apurva

0 YiKai Chen over 6 years ago in reply to Apurva Ankleshwaria89

Guru 735455 points

As I know, there’s no IDE for debug Contiki OS.

0 Richard W. over 6 years ago in reply to YiKai Chen

TI__Genius 14860 points

YiKai Chen said:
As I know, there’s no IDE for debug Contiki OS.

The following approach might be the quickest way to debug an externally build ELF file with Code Composer Studio:

Import and build a No-RTOS example from the SimpleLink SDK with GCC toolchain.
Remove all files in that project except the target configuration XML file and of course the CCS project files
You might now either pull in your Contiki code or move the proejct files into the desired directory.
Adjust the build steps to call your Contiki makefile + the necessary target options
In the CCS debug configuration, make sure that the .elf file produced by the Contiki build is being used.

I am using a somehow similar approach to debug some private projects that I develop using QtCreator and the Qt Build Suite. CCS sucks a lot. But for debugging GCC applications on CC13xx chips, it is the only working solution that I know.

You can also still use your favorite IDE/environment to develop and build your application and then you only need to take a CCS/GCC project from the SimpleLink SDK and replace the ELF file to be debugged.

0 Abhed Misra over 6 years ago in reply to Richard W.

TI__Genius 13685 points

In addition to above, if you just want to port the already built code then you will have to update the board file being used in the build. It can be found at this location platform\srf06-cc26xx\srf06 and also the respective board.h file.

0 Apurva Ankleshwaria89 over 6 years ago in reply to Richard W.

Intellectual 460 points

Hi Richard,

Thanks for your response. Tried the steps you have mentioned. Now, I am able to do breakpoint debugging but breakpoints can only be put in assembly code rather than C code. CCS Debug ignores any breakpoints which are put in C code. Please let me know if you are able to put breakpoints in C code at your end. Thanks!

0 Apurva Ankleshwaria89 over 6 years ago in reply to Abhed Misra

Intellectual 460 points

Hi Abhed,

Thanks for your response. Already changed the board file. On a separate note, I designed my custom board keeping in mind Sensortag CC1350. The pinout connection are same in my custom board(CC1310) and Sensortag(CC1350). Also, both CPU family are same. So, ideally the code which I developed on Sensortag should have worked without any changes in my custom board. Let me know if I am missing something here. Thanks!

0 Richard W. over 6 years ago in reply to Apurva Ankleshwaria89

TI__Genius 14860 points

Hi,

yes this is possible, but there is a pitfall. If the files where you set the breakpoints are not exactly the same files that have been used for building, then the breakpoints will not work. Usually, CCS sets an automatic breakpoint at the begin of the main function. Do you reach that? If yes, try to step-debug further. CCS should either open the files automatically or will ask you for the location.

0 Apurva Ankleshwaria89 over 6 years ago in reply to Richard W.

Intellectual 460 points

Hi Richard,

The files which i set the breakpoints on are the same files which are used for building(I use CCS itself for building the project). Yes, CCS does set an automatic breakpoint at the beginning of the main function and I reach that. However, while doing step debug, it goes to the next assembly code line rather than next C code line.

0 Richard W. over 6 years ago in reply to Apurva Ankleshwaria89

TI__Genius 14860 points

Could it be that you use the green "Assembly Step" buttons instead of the yellow "Step" buttons? They look almost the same, only the color is different.

0 Apurva Ankleshwaria89 over 6 years ago in reply to Richard W.

Intellectual 460 points

No, I am using Yellow step buttons only. Infact, both green and yellow step buttons respond in similar way.

0 Richard W. over 6 years ago in reply to Apurva Ankleshwaria89

TI__Genius 14860 points

Ah, I think the ELF file is missing debug symbols. Contiki does not compile with debug symbols by default, so add the following to your makefile:

CFLAGS += -g

Does that help?

0 Apurva Ankleshwaria89 over 6 years ago in reply to Richard W.

Intellectual 460 points

Yes. This works. Thanks a lot, Richard!

0 YiKai Chen over 6 years ago in reply to Apurva Ankleshwaria89

Guru 735455 points

Apurva Ankleshwaria89 I see you make this success and it will be great if you can share your steps using a read case so others have similar issue can be benefited.

Sub-1 GHz

Sub-1 GHz forum

CC1310: Debug CC1310 using Contiki