Using FDS with BLE and Scheduler

RE: Using FDS with BLE and Scheduler

Sorrow91 — Fri, 22 Dec 2017 09:15:10 GMT

I don't understand why the NRF_LOG_INFO function not executed properly, after the fds_setup()

RE: Using FDS with BLE and Scheduler

Sorrow91 — Fri, 22 Dec 2017 08:59:21 GMT

Hey emdi, thanks for your answer. I updated my code a bit in my main post.

RE: Using FDS with BLE and Scheduler

emdi — Fri, 22 Dec 2017 08:42:55 GMT

Hi,

when dispatching system events through the scheduler, the check

 while(write_flag == 0);

in your main function will never pass, since the code that is supposed to set that flag is run in app_scheduler_exec(), in the foor loop, that you never reach.

What you could do is to schedule the operations in the fds event handler: after receiving the INIT event, schedule the WRITE.

Does that make sense?

RE: Using FDS with BLE and Scheduler

Sorrow91 — Thu, 21 Dec 2017 22:11:54 GMT

Hey Jørgen, I uploaded my code again. If I only want to write a FDS record, the FDS handler I initialize never gave a something back.

 case FDS_EVT_WRITE:
    {
        if (p_evt->result == FDS_SUCCESS)
        {
							NRF_LOG_INFO("FDS_EVT_WRITE");
        }
    } break;

For me it seems, that the events are not called right from the schedueler. I know that I did something from, but I can't figure out what...

And thank you again for your effort to help me!

Kevin

RE: Using FDS with BLE and Scheduler

Jørgen Holmefjord — Wed, 20 Dec 2017 13:35:28 GMT

Hi,

I don't think the code on GitHub that you linked is updated. It only have scheduler_ncs_s_file_update, which will end in FDS_ERR_NOT_FOUND error in the FDS event handler. I changed the code to schedule ncs_s_file_create() instead, and this seems to work. However, I get a FDS_ERR_NOT_FOUND error code from the scheduled call to ncs_s_file_read() right after.

You do not have any mechanism to make sure the record is written before reading it. Note that FDS writes are asynchronous, meaning that it will schedule the write/erase event between softdevice/BLE events. You must wait until for the FDS_EVT_WRITE/FDS_EVT_UPDATE event in the FDS event handler before you can read the record.

Best regards,

Jørgen

RE: Using FDS with BLE and Scheduler

Sorrow91 — Tue, 19 Dec 2017 12:47:13 GMT

Yes sorry I forget to uncomment:

//		err_code = fds_setup();
//		APP_ERROR_CHECK(err_code);

Can you try to write and read something by uncomment this lines:

//		ncs_settings.sync = 5;
//		ncs_settings.buffer = ncs_settings.sync;
//		ncs_settings.file = 1;
//		ncs_settings.key = 1;
//				
//		err_code = app_sched_event_put(NULL, 0, scheduler_fds_write);
//		read_error(err_code);
//		APP_ERROR_CHECK(err_code);
//	
//		err_code = app_sched_event_put(NULL, 0, scheduler_fds_read);
//		read_error(err_code);
//		APP_ERROR_CHECK(err_code);

This doesn't work and after fds_setup() the NRF_LOG_INFO() function doesnt work right.

Thanks for your affort

RE: Using FDS with BLE and Scheduler

Jørgen Holmefjord — Tue, 19 Dec 2017 12:23:56 GMT

I can't see anything wrong with your code. I commented in call to ncs_s_file_setup() in your main.c file (as this was the only reference, except peer_manager, I could find in your code to fds_init() function). This is the output I see on RTT:

 0> <info> app: log_init
 0> <info> app: timers_init
 0> <info> app: buttons_leds_init
 0> <info> app: ble_stack_init
 0> <info> app: scheduler_init
 0> <info> app: gap_params_init
 0> <info> app: gatt_init
 0> <info> app: peer_manager_init
 0> <info> app: services_sr_init
 0> <info> app: advertising_init
 0> <info> app: db_discovery_init
 0> <info> app: services_init
 0> <info> app: conn_params_init
 0> <info> app: gpiote_init
 0> <info> app: saadc_init
 0> <info> app: twi_init
 0> <info> ncs_s_file_m: FDS initialization success.

I am able to see the device advertising, and connect to it. What is the issue?

RE: Using FDS with BLE and Scheduler

Sorrow91 — Tue, 19 Dec 2017 09:31:30 GMT

Hey Jørgen, did you found what I'm doing wrong in my code? Thanks for you help

RE: Using FDS with BLE and Scheduler

Sorrow91 — Fri, 15 Dec 2017 21:19:39 GMT

Hey I tried to debug it, but I can't figure out whats wrong. I uploaded my project to github for you: LINK SDK: 14.2. I hope you can see what I'm doing wrong, thanks for your help anyways. And I'm sorry for any noobi things I do in my code, I'm at the beginning... :)

RE: Using FDS with BLE and Scheduler

Jørgen Holmefjord — Fri, 15 Dec 2017 13:50:23 GMT

It should not be a problem to register another user with FDS along Peer Manager. The call to fds_init will simply realize FDS is already initialized and return success. You should debug your application to see exactly where it hangs. If you need help with this, please upload your entire project for debugging.

RE: Using FDS with BLE and Scheduler

Sorrow91 — Tue, 12 Dec 2017 19:59:10 GMT

Found that it's the peer manager, if I comment it out the fds_init and fds_register function work normal as they should. Here is my skd_config.h, do I forgot something?

RE: Using FDS with BLE and Scheduler

Sorrow91 — Tue, 12 Dec 2017 11:22:37 GMT

Thanks for your answer. It doesn't work when I disable the scheduler too. It seems that it hangs anywere after init_fds(). The fds_init and the fds_register gave me NRF_SUCCESS. Can it be a problem with the order in my initialization in my main()?

RE: Using FDS with BLE and Scheduler

Jørgen Holmefjord — Mon, 11 Dec 2017 14:27:57 GMT

Could you describe the issue in more detail, what is not working? Have you tried debugging to see if there are any error codes? sys_evt_dispatch was replaced by NRF_SDH_SOC_OBSERVER macro in SDK 14, as described in the Migration Guide. Is FDS working without scheduler?