RE: fds_record_find returns files that do not exist

Mon, 21 Aug 2017 13:20:59 GMT

Thanks. I was calling fds_record_find() almost immediately after power up. After waiting a couple seconds and calling the function as I normally would during operation, it functioned normally. I don't know if the early call to fds_record_find() exposed a bug in fds, or (probably more likely) moving the call changed something else in my code. Either way it works now.

RE: fds_record_find returns files that do not exist

RichieJH — Sat, 19 Aug 2017 09:34:46 GMT

If you have truly erased the chip, the flash would be cleared and there would be no records. So calling fds_file_delete() would be ineffective and there would be no records to find. If you didn't erase the chip, a successful fds_file_delete() would also prevent you from being able to find a record with that FILE_ID, even if you didn't use gc since the library marks the file as unavailable. The nRF will predominantly find a record faster than it can be deleted due to the asynchronous nature of deleting so you need to use a flag when calling fds_file_delete() that is then cleared in the fds_evt_handler before calling fds_record_find(). Something like this:

static void my_fds_evt_handler(fds_evt_t const * const p_fds_evt)
{
    switch (p_fds_evt->id)
    {
        case FDS_EVT_DEL_FILE:
            if (p_fds_evt->result == FDS_SUCCESS)
            {
		        write_flag=1;
            }
            break;

        default:
            break;
    }
}