Maximum number of records per file ?

[QuentinFarizon]

I am writing 3305 records into a single FDS "file" (0x1000)

But when looping through them with `while ((err_code = fds_record_find_in_file(data_type_to_file_id(data_type), &record_desc, &find_token)) == NRF_SUCCESS) {` it loops through only 2304 records.
For the last one, err_code is FDS_ERR_NOT_FOUND, exactly like if there was no more records in this file.

For the first 2304, I have no issue retrieving, writing, updating them, ...

I have launched my program several times, it always loops through 2304 records. Is this a known limit of maximum number of records for one file ?

Code :

    ret_code_t err_code;
    fds_flash_record_t flash_record;
    fds_record_desc_t record_desc;

    fds_find_token_t find_token;
    memset(&find_token, 0x00, sizeof(fds_find_token_t));


    while ((err_code = fds_record_find_in_file(data_type_to_file_id(data_type), &record_desc, &find_token)) == NRF_SUCCESS) {
        < check record >
    }

[Einar Thorsrud]

Hi,

There is no defined maximum number. You can even have multiple records with the same ID within the same file.

Are you sure the additional records are there? Could it be that records after number 2304 are not written for some reason? Perhaps because of no more room in FDS, or some other reason, but you fail to handle an error that occurred before so that it failed silently so that it is not notices before attempting to read?

[QuentinFarizon]

Ok this was tricky to debug. To see correctly the writing process I added a 1 ms delay (nrf_delay_ms(1)) between each write (if I don't do that I lose RTT output)

But in fact this 1 ms delay "fixed" the issue, so I guess there is something wrong when making several FDS write too quickly

Note that for each write I wait for the FDS_EVT_WRITE before proceeding to the next write.

Any idea why this 1ms delay is necessary ?

[Einar Thorsrud]

That is right, the POF comparator is disabled by default, so if you don't enable it that can not be the issue here.

[QuentinFarizon]

We encounter this problem on ~10% of our customers.

Instead of 3000 writes, they got only a few hundreds (never the same amount)

What would you recommend ?

[Einar Thorsrud]

Hi,

This is not a generic issue or an issue I have seen earlier reports of (assuming it is correct that POF warning is not enabled). We need to understand what the cause of this issue is first in order to be able to fix it. Have you done more testing and debugging to learn more about the issue and in which conditions it is can occur and in which conditions it never occurs (if any)? If that gives some indications, perhaps it is possible to instrument the code with some additional debug printouts or similar, or to inspect the code with that in mind.

[QuentinFarizon]

I have done lots of testing and debugging (not easy since we do not reproduce in Debug mode or with logs enabled).
We pushed in production as-is, and measured which customers had the issue by counting the written records in a separate service. About 10% of them had the issue.

At office, we have one board that reproduce the issue randomly, at a rate of about 15%, and one board where we do not reproduce at all.

I'm out of ideas on what happens, how to reproduce it more often, and on when conditions it occurs (hardware or software).

[Einar Thorsrud]

Hi,

I am not able to see any reason the nRF in itself (or the SDK) should cause this, so I think we need look at this broadly. Could there be some other part of the application that cause issues? Same or higher priority interrupts that prevent flash operations, or perhaps something corrupts memory or something else?

If this is consistently only reproducable on about 10% of the devices, perhaps there is some physical reason for that? Some input that is not in the same state, or an analog input that is slightly different, or similar? Perhaps floating input pins cause different problems on different boards? If we don't have any more specific things to go on, perhaps you could take a known failing device and comment out different parts to see if you can isolate a part that seems to affect the issue (could be anything). If you are able to isolate at least a factor in the issue this way, tro to see how much you can narrow it down, and then investigate closely from there.