CCS/LAUNCHXL-CC26X2R1: Debugger loses control while stepping through the code

Hermann Menning

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hi,

I am working with the BLE5 cc26x2 SDK 2.3 on the simple peripheral project. There is certain function that, whenenver I jump into it and I am stepping through the code, at a certain line of code when I want to step over it, the debugger does not step over but resumes. The code works just fine (with or without debugging) and if I place a breakpoint at a later point in the function the debugger will stop there. Optimization is off. This is a pretty curious case and I would like to understand how this can happen.

The code where it happens runs in user task context. The stack is advertising at the same time. Could this be a re-entrant problem when the usertask is preempted?

The code where it happens just consists of a switch case and some conditional if-else branching.

Best Regards.

over 6 years ago

0 Hermann Menning over 6 years ago

Expert 1305 points

I rewrote parts of the code and now when single setpping the assambler code I end up in hwi_asm.sv7m:

; Arriving here can only happen if interrupts were globally disabled
; when the pendSV interrupt was posted above. This can happen if
; user code has set the PRIMASK and not cleared it, or when single
; stepping with interrupts disabled.

ti_sysbios_family_arm_m3_Hwi_interruptsAreDisabledButShouldNotBe:

0 Marie H over 6 years ago in reply to Hermann Menning

TI__Guru* 81401 points

Hi Hermann,

Where in the code does this happen? Are you using brekpoints in the c code or in the assembly view?

I would say this behavior is expected.

BTW did you see the BLE5-Stack User's Guide on Breakpoints? ( dev.ti.com/.../debugging-index.html )

Bluetooth®︎

Bluetooth forum

CCS/LAUNCHXL-CC26X2R1: Debugger loses control while stepping through the code