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.
Part Number: CC1310
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.
If my post answers your question, please click on "This Resolved my issue" button to benefit others who have the same issue.
How to use two UARTs in CC26x2 and CC13x2
How to add you own custom board files to CC26xx BLE stack
SwitchBot DIY using LPSTK-CC1352R , SG90 servo motor, and ProjectZero to away from COVID-19.
How to use two endpoints in SIMPLELINK-CC13X2-26X2-SDK Z-Stack.
CC13xx TRX WOR project.
How to create a periodic event to toggle BLE Advertising in CC26xx simple_peripheral example
How to use indication in simple_peripheral example and use Btool to enable indication
How to check APS ack in TI Z-Stack
How to detect button hold in CC26x2, CC13x0, CC13x2 SDK.
660 Zigbee devices in the same Zigbee network!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to YiKai Chen:
In reply to Apurva Ankleshwaria89:
YiKai ChenAs 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:
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.
In reply to Richard W.:
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.
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!
In reply to Abhed Misra:
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!
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.
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.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.