fstorage callback not called

RE: fstorage callback not called

Daniel Dakhno — Sun, 06 Apr 2025 00:39:46 GMT

You are right, and I was missing the file indeed.

I was also using an old sdk_config.h version, which was missing the following fields:

NRF_SDH_SOC_ENABLED=1
NRF_SDH_SOC_OBSERVER_PRIO_LEVELS=2
BLE_ADV_SOC_OBSERVER_PRIO=1
NRF_SDH_SOC_STACK_OBSERVER_PRIO=0

RE: fstorage callback not called

Daniel Dakhno — Wed, 02 Apr 2025 13:42:08 GMT

That is unfortunate...

Anyway, thanks, I'll try it out!

RE: fstorage callback not called

Vidar Berg — Wed, 02 Apr 2025 13:40:29 GMT

Yes, that is the problem, is completely decoupled from the other code, so you won't get any linker errors if you forget to include it.

RE: fstorage callback not called

Daniel Dakhno — Wed, 02 Apr 2025 13:38:07 GMT

I am not quite sure atm the moment. Would my project even link without nrf_sdh_soc.c?

RE: fstorage callback not called

Vidar Berg — Wed, 02 Apr 2025 12:50:02 GMT

Hello,

Does your project include the nrf_sdh_soc.c source file? This module is responsible for propagating the FLASH and other SoC events to registered NRF_SDH_SOC_OBSERVERs such as the nrf_fstorage_sys_evt_handler() in nrf_fstorage_sd.c.

[quote user=""]2. Can multiple modules register SD observers using NRF_SDH_BLE_OBSERVER with the same priority, or does every observer need to have its own priority?[/quote]

Yes, this is not a problem if you don't care about which order the observers are called.

Best regards,

Vidar