nRF52840 Eddystone connectable mode issue with FreeRTOS

RE: nRF52840 Eddystone connectable mode issue with FreeRTOS

Susheel Nuguru — Tue, 27 Apr 2021 12:01:44 GMT

The error you mentioned happens if you have SD_EVT_IRQHandler triggered before the nrf_sdh_freertos_init has been completed.

Why was vTaskNotifyGiveFromISR called with a NULL task handle? If you get an answer for that then you are close to finding the issue here. My suspect is that you BLE activity has started way before the FreeRTOS tasks have been initialized properly

RE: nRF52840 Eddystone connectable mode issue with FreeRTOS

ffwali — Mon, 26 Apr 2021 22:00:19 GMT

Hi Susheel,

Thank you for the replying.

We fixed the es_security_init() function by adding some modifications in our previous code and fixed that error.

The scenario is that we are now able to advertise the beacons and able to see the beacons in nRF Connect application but when we try to make a connection by using "Connect" button the application crashes with the below log:

<error> app: ERROR 3735928559 [Unknown error code] at /external/freertos/source/tasks.c:4796
PC at: 0x00035C83
<error> app: End of error report

We are getting the below function call stack:

We also tried by updating the configTOTAL_HEAP_SIZE from 20kB to 30kB but it didn't workout.

There is one more thing that we are observing in our code that there is a function NRF_SDH_BLE_OBSERVER() which is used to register the BLE events handler but whenever we are getting a BLE event i.e. the Connect event (mentioned above), our code doesn't reach this function. We have verified this by adding various breakpoints. Whereas in the "ble_app_hrs_freertos_pca10056" exampl (which we are using for reference) the code reaches the function.
We are assuming that maybe there is some flag due to which the NRF_SDH_BLE_OBSERVER() function is not being compiled etc. or if there is something we are missing.

Thanks

RE: nRF52840 Eddystone connectable mode issue with FreeRTOS

Susheel Nuguru — Mon, 26 Apr 2021 06:15:19 GMT

What is the context in which es_security_init is called? Could you post the functional call stack snapshot when this error happened. You can put a breakpoint at the place where the error happens and view the call stack when the breakpoint hits. If this is called in FreeRTOS task, then i am suspecting that there is some stack overflow corrupting the memory which in turns make the softdevice use a pointer pointing to this corrupted memory.

If this is a task, then i suggest you increase the stack_size for this task ( and if necessary increase the heap size in FreeRTOSConfig.h )