SDK14 application and peer manager using FDS simultaneously

[Jray]

Test code：SDK14 ble_app_ancs_c

Hey guys, When I used ble_app_ancs_c demo to do FDS, there was a problem！ I initialize FDS and register the drop back function。

When I was working with FDS, I found that I didn't go in and complete the callback function！

I consulted the related issues in the forum and found that many of them needed to add fs_sys_event_handler (sys_evt);Is this solution feasible for SDK14?And I didn't find the function in SDK14.

So I have two questions at the moment:

1.How does peer manager and application program operate FDS at the same time in SDK14?

2.Do you need to add fs_sys_event_handler (sys_evt) to SDK14?

Looking forward to your help!

[emdi]

Hi,

1. Not sure about what you are asking..
2. The fs_sys_event_handler() function is registered automatically in SDK 14.

[Jray]

Hi emdi,

I used ble_app_ancs_c demo to do FDS and I initialize FDS and register the callback function(my_fds_evt_handler),When executing fds_write(), I found that it didn't go in the callback function(my_fds_evt_handler)！Is the application FDS conflict with the peer manager operation?

Looking forward to your help!

[emdi]

• No, the application and the peer manager don't 'conflict' when using fds.

• How do you determine that my_fds_evt_handler is not called, do you step or do you only look at logs? If so, try adding a log entry in the default case in the switch to make sure you are not missing any event.

• Does the fds_record_write() return FDS_SUCCESS?

[Jray]

Hi emdi,

1.the fds_record_write() return FDS_SUCCESS.

2.I single step debugging, found that there is a callback initialization, write data without callback！

3.The program stops waiting for the write status flag.

4.If the program does not wait for the write completion flag, then everything is OK!

Thank you for your help！

[emdi]

Have you perhaps updated your project from an older SDK version?