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-CC1310: BIOS_start(); What build and debbugger settings are required for source code stepping in BIOS_start()

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310, SYSBIOS

Tool/software: Code Composer Studio

Hi,

I'm looking for the proper build and debugger settings to get the source code to display during single stepping in BIOS_start(). As soon as I step into BIOS_start() or user application driver, only the disassembly is available. Is this an optimization issue as to why it does not link to the source code during debugging but does during building?

I am using CCS V901 with the CC1310 launch pad and adcsinglechannel driver. The driver builds, compiles, samples 2 adc inputs and displays 1 time before locking up to a Tera term, and I am unable to step through the source code to find problem areas. 

Thanks,

Dan Dudek

  • Hi Dan, 

    according to my experience there is more than 99% chance that your issue is related to an application part. 
    Which SDK version do you use?
    What modifications you did to an original adcsinglechannel example?

    In most cases your issue could be related to a stack, heap usage or a deadlock. 

  • You need to manually add the driver files to your project to be able to step through them.

    BR

    Siri

  • The SDK is CC13x0_sdk_3_10_00_11. And I did not change the application, just imported, built, started debug, and single stepping. C code trace ends at BIOS_start().

  • Ok. Will take a look. Thanks.

  • After reviewing the readme.html file for the adc example, I noticed a note at the very bottom of the readme under TI-RTOS. This note states that the "release" kernel is the default project used, not the debug and then references one to the SimpleLink MCU SDK User's Guide. So I went back into Resource Explorer and into the Documents folder of my SDK and selected Documentation Overview. At the top of this document are links to various sections, I selected the MCU SDK, then, in this document selected the Debugging Output section, and then Under Configuration with TI-RTOS. So I imported the debug version and modified the build selections to remove release and add debug. Rebuilt the project, single stepped to BIOS_start(), and can now step into the BIOS code. I do fail down stream on missing source code inside the sysbios_knl_Task_startup(), missing aon_rtc.c that apparently the developer in FW had in his or her local directory. C:\Jenkins\jobs\FWGroup-DriverLib\workspace\modules\output\cc13xx_cha_2_0_ext\driverlib\bin\ccs/./../../../driverlib/aon_rtc.c. When I locate this file I would think I need to add it to my debug configurations using file system path. If there is a better way to do this, pleas let me know, else thanks and the initial problem is resolved.

  • Dan, 

    ./source/ti/devices/cc13x0/driverlib/aon_rtc.c within your SDK folder. 

  • Thank you Tom. I added that file system folder to my debug configurations source lookup and yes, I am now in good shape for setting break points, single stepping, stepping over and step return though the c++ code RTOS and application driver. Thanks.