RE: Result 0x000A from fds event hanlder

Ignacio — Wed, 17 Mar 2021 11:52:27 GMT

Sorted! I set a flag on when an fds operation is called and then it is clear by the fds event handler. It was a recurrent request issue when the first request has not been processed yet.

RE: Result 0x000A from fds event hanlder

Edvin — Tue, 16 Mar 2021 20:38:09 GMT

Hello,

[quote user=""]First I get a 0x0000 result and then a 0x000A result in the fds event hanlder after calling the fds_record_update function[/quote]

So what sort of event has the FDS_ERR_NOT_FOUND status? What is the event ID (p_evt->id)?

Do you use CRC in your FDS configuration? What are these definitions set to?

FDS_CRC_CHECK_ON_READ
FDS_CRC_CHECK_ON_WRITE

Are the calls that sometimes returns FDS_ERR_NOT_FOUND called a very short time after another FDS call? Please remember that e.g. an fds write will return NRF_SUCCESS immediately, but the record is not actually written until you receive the callback.

Is there some way for me to reproduce this on a DK?

Best regards,

Edvin