FDS_ERR_OPERATION_TIMEOUT with fds_record_update

RE: FDS_ERR_OPERATION_TIMEOUT with fds_record_update

Panda — Sat, 09 May 2020 11:11:00 GMT

Hi tesc,

Do the FDS_ERR_OPERATION_TIMEOUT have good method to slove? I have met the similar issue . changing FDS_VIRTUAL_PAGES has no effect.

This is topic Linking. Could you give me some help?Thank you in advance.

Best Regards,

Panda.

RE: FDS_ERR_OPERATION_TIMEOUT with fds_record_update

Aurele — Sun, 07 Jul 2019 11:55:16 GMT

Hello @tesc,

Thank you very much for the help, i have finally found what was the issue. Actually, it was coming from FDS_VIRTUAL_PAGES that was set at 128. It was much too high and it seems it was the cause of the ramdom behavior i was observing. i wanted to reserve 128kB so i just needed to set FDS_VIRTUAL_PAGE at 32.

When the issue happened, the BLE was not started and the timeout was occuring after a certain number of fds_record_update and i really think it was coming from the FDS_VIRTUAL_PAGES wrongly set.

Now all is working fine.

Best regards,

Aurélien

RE: FDS_ERR_OPERATION_TIMEOUT with fds_record_update

tesc — Thu, 04 Jul 2019 13:57:12 GMT

Hi,

If you are using the SoftDevice actively at the same time that you are using FDS, you may experience that FDS operations cannot be scheduled between all the SoftDevice operation. In that case, the FDS operation will time out. Other SoftDevice activities are typically prioritized over flash operation, see SoftDevice timing-activities and priorities.

Typically, a timeout happens because of scanning or advertising, where the interval is so short there is not enough time for the FDS operation in-between the advertising or scan events.

You should find quite a few other threads here on DevZone on the topic of FDS and SoftDevice usage.

Regards,
Terje