Can't get a callback from FDS no matter what - help!

RE: Can't get a callback from FDS no matter what - help!

FormerMember — Tue, 10 Jul 2018 12:20:23 GMT

Could you have a look at the suggestions in this thread and check if any of them solves the problem?

RE: Can't get a callback from FDS no matter what - help!

darrenji — Thu, 05 Jul 2018 18:52:26 GMT

I am having this same problem, with a slightly different slant. I'm using the latest SDK (15) which doesn't have softdevice_ble_evt_handler_set(). I have the fds backend set to use NRF_FSTORAGE_SD, however fds will only work if I don't call nrf_sdh_ble_enable(). If I do enable the soft device, I get the problem reported here: the init event is received, but no other events. If I don't enable the sd, fds works as expected and I get all of the callbacks. fds is failing silently. I've been debugging this for 3 days now. Incredibly frustrating.

RE: Can't get a callback from FDS no matter what - help!

Lola — Tue, 23 May 2017 15:07:07 GMT

Thanks, I read the fds doc 4 times, no single word about this line.would be simple to just create classes that are encapsulated with things like saveToMemory(fileID,Key) , instead of huge messy example projects..

Anyway - thank you again .

RE: Can't get a callback from FDS no matter what - help!

FormerMember — Tue, 23 May 2017 14:19:00 GMT

Good to hear that it works now!

1) Yes, that's correct, the flow is the following: The softdevice pushes events to fs_sys_event_handler (fstorage.c) --> fs_event_handle (fds.c) --> my_fds_event_handler (main.c)

2) We want to make things clear, and we try to make the documentation good. But I do see that it lacks some small, but important details. I will report what you mentioned regarding PWM internally, I see that sdk_config.h always mentioned in the documentation for other library as well. Hopefully the documentation can be updated!

RE: Can't get a callback from FDS no matter what - help!

Lola — Tue, 23 May 2017 12:20:25 GMT

I love you :) Thanks Kristen. first of all adding that line solved the problem right away. Then I have questions, please if I may .

There are 2 things to register and I don't understand if your explanation is regarding the first or second. The softdevice_sys pushes from the soft device to the FS, and the fs_sys from fs to the application ?
As I see you are a Nordic employ, I must ask, why, why you are making things so hard? :) You built an amazing chip, and yet for every little thing I have to fight because it's not on the docs. I would never find out that I have to put this line without you, and the same happened to me with the PWM and config file where you have to enable anything you do on the config in many other modules. If you would make things super clear and friendly (put things in classes with clear setup like arduino) you would become super popular. Thanks again!

RE: Can't get a callback from FDS no matter what - help!

FormerMember — Tue, 23 May 2017 09:29:55 GMT

I have updated my answer to answer your questions.

RE: Can't get a callback from FDS no matter what - help!

Lola — Tue, 23 May 2017 08:52:03 GMT

At the init_ble_stack function I have this :

err_code = softdevice_ble_evt_handler_set(ble_evt_dispatch);
APP_ERROR_CHECK(err_code);

Do I have to add also your lines ? if so , why ? can you explain please ?

RE: Can't get a callback from FDS no matter what - help!

FormerMember — Tue, 23 May 2017 08:44:12 GMT

What does setupBluetoothWithDelegate(..) do?

Do you add sys_evt_dispatch() to softdevice_sys_evt_handler_set():

static void sys_evt_dispatch(uint32_t sys_evt)
{
// Dispatch the system event to the fstorage module, where it will be
// dispatched to the Flash Data Storage (FDS) module.
fs_sys_event_handler(sys_evt);

...
}


static void ble_stack_init(void)
{
    ...
    err_code = softdevice_sys_evt_handler_set(sys_evt_dispatch);
    APP_ERROR_CHECK(err_code);
}

Update: The purpose of registering an event handler through softdevice_sys_evt_handler_set() is to have an event handler for SOC events "going through"/forwarded by the softdevice. For doing write operations, fstorage uses sd_flash_write(). When sd_flash_write() has successfully completed or upon an error, an event will be fetched. This event is handled by fs_sys_event_handler() in fstorage.c. If no event handler is registered to the softdevice, the softdevice will not have any place to forward the event.

Therefore, softdevice_sys_evt_handler_set(sys_evt_dispatch) has to be called, with sys_evt_dispatch() containing the relevant event handlers.