Soft device somtimes don't want to start advertising

RE: Soft device somtimes don't want to start advertising

eshaul — Tue, 19 Nov 2019 07:47:53 GMT

Already done, and solved - thanks

RE: Soft device somtimes don't want to start advertising

Susheel Nuguru — Tue, 19 Nov 2019 07:32:59 GMT

Is it the exact same environment you are using Erez? if not please open a new case.

RE: Soft device somtimes don't want to start advertising

eshaul — Sun, 10 Nov 2019 08:18:39 GMT

Dear Susheel Nuguru

Can you suggest a solution?

Erez.

RE: Soft device somtimes don't want to start advertising

eshaul — Wed, 06 Nov 2019 12:11:42 GMT

Dear Susheel Nuguru

I seem to suffer from the very same issue, I am using: S132 SoftDevice v2.0.0

in my case also, after flashing the application will not start advertising (only after 2-4 reset cycles)

I am not using: ble_app_hrs_freertos from SDK14 or other FreeRTOS

I am only exposed to the nRF5_SDK_00.11.00

I am looking for a solution that I can implement on my application and not on the Softdevice.

What can be done on the application level?

Erez

RE: Soft device somtimes don't want to start advertising

Susheel Nuguru — Tue, 19 Dec 2017 18:48:56 GMT

yes, it should be fixed in latest SDK14.2

RE: Soft device somtimes don't want to start advertising

jmag999 — Tue, 19 Dec 2017 18:46:24 GMT

Has this been fixed in newer versions of the SDK?

RE: Soft device somtimes don't want to start advertising

janR — Mon, 16 Oct 2017 12:42:45 GMT

Thanks,

I tried tihs now, and it seems to work fine.

The problem occurred mostly after first-time flashing of the nRF52. Now, after the fix, It seems to start advertising immediately after application has started, as it should.

Thanks for help, Jan

RE: Soft device somtimes don't want to start advertising

Susheel Nuguru — Mon, 16 Oct 2017 08:22:14 GMT

Sorry for the late reply. I somehow missed this thread.

I think this is related to a bug we found recently in nrf_sdh_freertos.c. After flashing softdevice and initializing peer manager it tries to format internal flash memory to be ready for usage and emits NRF_EVT_FLASH_OPERATION_SUCCESS event which then fires SD_EVT_IRQHandler. Then using FreeRTOS, a notification is sent to softdevice_task task from SD_EVT_IRQHandler, but if a task is not yet created during that moment this notification gets lost. After softdevice_task task is created by calling nrf_sdh_freertos_init(), softdevice_task blocks on ulTaskNotifyTake() and waits for other BLE stack events before calling nrf_sdh_evts_poll(). So in the example, where the order of calls is first peer_manager_init() and then nrf_sdh_freertos_init(), then flash system is busy, NRF_EVT_FLASH_OPERATION_SUCCESS gets lost, and as a result, delayed advertising doesn't start.

solution
my suggestion is to switch the order of calls in softdevice_task() to firstly do a nrf_sdh_evts_poll() and only then block ulTaskNotifyTake(), so those first events in the queue could be properly read:

static void softdevice_task(void * pvParameter)\{

    NRF_LOG_DEBUG("Enter softdevice_task.");

    if (m_task_hook != NULL) \{

        m_task_hook(pvParameter);

    }

    while (true) \{

        nrf_sdh_evts_poll();   // <<--- now called before locking on the binary semaphore

        (void) ulTaskNotifyTake(pdTRUE, portMAX_DELAY);

    }

}