No softdevice Events reaches the freeRTOS application

RE: No softdevice Events reaches the freeRTOS application

SatzTechGeek — Fri, 14 Dec 2018 06:41:56 GMT

Thanks, Susheel Nuguru solution which you mentioned solve one of our issues. But when we pass the BLE event handler as a function argument to BLE stack init function and register the function results in a deadlock mechanism. Is that we cant able to register the event handler function by passing as an argument to stack init

RE: No softdevice Events reaches the freeRTOS application

Susheel Nuguru — Thu, 13 Dec 2018 12:25:36 GMT

[quote user="SatzTechGeek"]but the problem there is no clear picture about freertos init and hookup function and how the events are triggered ?.[/quote]

The freeRTOS is using RTC1 for its timekeeping and you can see the port files in SDK\external\freertos\portable\CMSIS\nrf52\port_cmsis_systick.c
not sure which hookup functions are you mentioning here?
in nrf_sdh_freertos.c you can see that the softdevice events are notified to app using SD_EVT_IRQHandler (also called SWI2_IRQHandler). In freertos, instead of handling these events in IRQ context, we pass them to softdevice_task. Softdevice task will be in blocked state until the SD_EVT_IRQHandler unblocks it.

RE: No softdevice Events reaches the freeRTOS application

SatzTechGeek — Wed, 12 Dec 2018 16:20:31 GMT

we have use two task one to control and monitor sensors and used another task to capture ble events . we modify the nrf_sdh_freertos file as per the solution but the problem there is no clear picture about freertos init and hookup function and how the events are triggered ?.

RE: No softdevice Events reaches the freeRTOS application

Susheel Nuguru — Wed, 12 Dec 2018 14:05:44 GMT

There was one known race condition that was introduced in 15.2.

Looks like this is the main problem in your application. Can you check if this solution helps?