freeRTOS xTaskResumeAll lockup when using BLE and TWI

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Susheel Nuguru — Mon, 15 Aug 2022 08:18:11 GMT

[quote user="Rambooka"]

I have been running Stack Overflow Detection - Method 2 for a few weeks now and the API vApplicationStackOverflowHook() has never been called

[/quote]

This is useful for this does not guarantee that it will catch the stack overflow. I still suggest you to increase the stack sizes for your threads just to do some experimentation. I understand that you are using nRF52820 and RAM might be limited in your case.

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Rambooka — Mon, 15 Aug 2022 04:54:45 GMT

The SPI and COMP are being used in polling mode.... so there should be no problem

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Susheel Nuguru — Mon, 15 Aug 2022 04:35:13 GMT

I can see that SPI and COMP are using higher app (legal) priorities. Hard to say just looking at the priorities if they are causing a deadlock. It might help if you show what you are doing in the that ISR (or app callbacks from the ISR)

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Rambooka — Mon, 08 Aug 2022 03:33:53 GMT

Hi...

I have been running Stack Overflow Detection - Method 2 for a few weeks now and the API vApplicationStackOverflowHook() has never been called

I posted a simular question freeRTOS forum here and they are suggesting the problem i am facing is due to incorrect interrupt priorities. Such that one ISR is in the middle of adding an event to a queue and another ISR occurs and writes an event to the same queue... which results in the queue getting corrupted.

I am using all the settings for ISR priorities that nordic setup for the example BLE UART App.

Do the ISR priorities I posted initially look correct ?

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Susheel Nuguru — Fri, 05 Aug 2022 07:43:29 GMT

I feels like I have seen this error before.

It is very strange that this is happening inside the idletask, seems like a stack corruption (memory overflow in nearby task structures). Can you try to enable stack checking to see if we luckily see the kernel detecting stack overflow?f Also try increasing some of your app tasks' stack sizes.

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Rambooka — Thu, 04 Aug 2022 21:10:01 GMT

here is the values of pxTCB

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Rambooka — Thu, 04 Aug 2022 21:07:15 GMT

here is the call stack

When my App locks up, I pressed the pause button and took a screen capture...

the stack trace shows 0x1dd28 , so I also attached screen capture of that disassembly code

Hope this helps

RE: freeRTOS xTaskResumeAll lockup when using BLE and TWI

Susheel Nuguru — Thu, 04 Aug 2022 05:31:03 GMT

Can you please show us the function call stack when your app is stuck in the xTaskResumeAll->while( listLIST_IS_EMPTY. Gives us more context on what is happening.