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.

RTOS/CC2640R2F: Bluetooth stack library holds after first event.

Part Number: CC2640R2F

Tool/software: TI-RTOS

Hi. The project grows from Project Zero. It works but the stability is bad. I’m trying to figure out the problem and after small refactoring device just does not start. Or the same happens after optimization. I figured out that the ICALL task becomes blocking just after start. In osal.c file in void osal_run_system( void ) function.

activeTaskID = idx;

events = (tasksArr[idx])( idx, events );

It calls the LL_ProcessEvent (idx = 0, events = 0x2000) from the stack library and it never returns and makes ICALL task blocked. Later the application calls the stack API by ICALL and it breaks with timeout assert .

How can I debug this issue? And which is the method of debugging the stability for the long time being?

  • Hello,

    Are you able to share your code based on ProjectZero?

    Is this issue reproducible on the LaunchPad?
  • "Are you able to share your code based on ProjectZero?"

    Unfortunately I can't. It's big enough and comprise of HID, OAD and proprietary protocols.

    "Is this issue reproducible on the LaunchPad?"

    It can work only with our board. The project has 4 tasks: ICALL, gapRole, Application and Idle. But even if I set infinite hook at the start of Application task I had ICall_abort from VOID osal_snv_read(BLE_NVID_CSRK, KEYLEN, gapRole_SRK); in void gapRole_init(void). It looks like ble stack sometime breaks down after re-linking.
  • And another question. Is there hooks for inspecting all packets between stack layer. For example I want to inspect all LL packets and log last few packets before connection losing.