FStorage event handler interrupts not forwarded by soft device in bootloader

RE: FStorage event handler interrupts not forwarded by soft device in bootloader

Einar Thorsrud — Fri, 18 Sep 2020 16:06:18 GMT

Hi,

[quote user="rmcfadden"]Is it possible to get to the nrf_fstorage_sys_evt_handler() call in queue_process() without the soft device being initially enabled?[/quote]

No, the SD backen cannot work without the SoftDevice being enabled. But you should have seen an error if this was the problem (unless you ignore return values). The SoftDevice must be enabled before you make any calls to the SoftDevice API (directly or indirectly).

[quote user="rmcfadden"]And regarding the waiting for interrupt, I dont block while waiting for the operation to complete, I come back and poll it on a tick based approach, which lets other operations occur. Is that what you are asking?[/quote]

Yes, that was what I was asking about. That should not be the problem, then.

RE: FStorage event handler interrupts not forwarded by soft device in bootloader

rsoc16 — Fri, 18 Sep 2020 14:07:45 GMT

Hi Einar,

Yes, I am using the nrf_fstorage_sd backend. I have been watching with breakpoints in the nrf_fstorage_sys_evt_handler() and never receive any events. My debugging process was first watching for the erase to execute in queue_process() in the nrf_fstorage_sd.c file. I confirmed this happened, but I never get a breakpoint hit in the event handler. Nor do I get a breakpoint on the event handler function call, located in the queue_process() switch statement.

One thing I noticed is the nrf_fstorage_sys_evt_handler() call in queue_process() is only triggered when the soft device is enabled, which makes sense. I assume this backend cant operate without that being enabled? Is it possible to get to the nrf_fstorage_sys_evt_handler() call in queue_process() without the soft device being initially enabled? Could that be an issue (some kind of race condition?).

And regarding the waiting for interrupt, I dont block while waiting for the operation to complete, I come back and poll it on a tick based approach, which lets other operations occur. Is that what you are asking?

RE: FStorage event handler interrupts not forwarded by soft device in bootloader

Einar Thorsrud — Fri, 18 Sep 2020 12:48:56 GMT

Hi,

I assume you are using the nrf_fstorage_sd backend and not the nrf_fstorage_nvmc? Assuming so, this is event based, and the fstorage event handler is nrf_fstorage_sys_evt_handler(), which is registered by the NRF_SDH_SOC_OBSERVER macro in nrf_fstorage_sd.c. This makes the SoftDevice handler forward events to fstorage. Do you get any events in the event handler (checked with a breakpoint or similar)?

I did not get a chance to look closely at your code today, but could it be a problem of interrupt priorities or similar? Do you wait for a fstorage event (or something completely different) in a interrupt priority, so that the thing you are waiting for doesn't get CPU time to run, making a deadlock?