• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 1263 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SensorTag Debugging: "No source available for"

Andreas Fischer
Expert 1180 points

Hello,

i use the SesorTag with the DevPack debugger.

CCS Version: 6.1.0.00104

BLE Stack 2.1

I can download the SensorTag Firmware, but when i pause debugging i always get:

No source available for "NOROM_CPUdelay() at C:/ti\simplelink\ble_cc26xx_2_01_00_44423\Projects\ble\SensorTag\CC26xx\CCS\SensorTag\FlashOnlyOAD\SensorTag.out:{3} 0x10000486{4}"

But i can connect to SensorTag with the App, everthing works fine.

Same problem with SimpleBLEPeripheral: "No source available for"

How i download:

1. Set the Application project as the active project and build the project using Project  Build All.

2. Set the Stack project as the active project and build the project using Project  Build All.

3. Download the Application by selecting the Application project as the active project and choosing Run  Debug.

The Application can be debugged from this point.

4. Download the Stack by selecting the Stack project as the active project and choosing Run  Debug.

What do i do wrong ?

Thanks.

Regards,

Andy

  • 0
    TI__Mastermind 29650 points
    Drave,

    You are doing nothing wrong. A lot of driverLib and the TI RTOS kernel are in ROM by default (adress 0x1*******). When halting at this point it causes the IDE to become a bit confused as it doesn't recognize this as part of the image flashed onto the device.

    In your case you would see that the previous instruction (in assembly view) is "WFI" (wait for interrupt), which is the Cortex M3 instruction used to trigger sequencing into a low power mode (Idle or Standby). This is where your device typically spends most of its time as it is only active for a very short period of time.

    Regards,
    Svend
  • 0 in reply to svendbt
    Expert 1180 points
    So the only way to debug is to make brake points and step through ?
  • 0 in reply to Andreas Fischer
    TI__Mastermind 29650 points
    The application code is typically what you want to debug and that you can debug as usual. If you halt the CPU at some random time it will most likely have stopped at WFI.

    Usually there are no need to have this information but you can include it by building the RTOS kernel with debug symbols:
    - Open project ,goto TOOLS->appBLE.cfg in project explorer
    - Select the "cfg Script" tab in the opened window
    - Replace BIOS.libType = BIOS.LibType_Custom; with BIOS.libType = BIOS.LibType_Debug;
    - Rebuild project

    Note that this will significantly increase the size of your application as the kernel compilation will no longer be optimized for size.

    Regards,
    Svend