Flash write issue

RE: Flash write issue

Jørgen Holmefjord — Tue, 22 Sep 2020 14:55:56 GMT

Looks like there should be plenty of space in the FDS area to store 22 bytes. Can you debug the application and check the content of the parameters passed to addr_is_within_bounds (dest, len), then you get the error?

RE: Flash write issue

Aftab — Mon, 21 Sep 2020 10:03:45 GMT

The error prompts in response to following commands:

rc = fds_record_update(&desc, &scr_dummy_record);
APP_ERROR_CHECK(rc);

fds_stat() give:

00> <info> app: Event: FDS_EVT_INIT received (FDS_SUCCESS)
00> <info> app: Running garbage collector...
00> <info> app: Event: FDS_EVT_GC received (FDS_SUCCESS)
00> <info> app: Garbage collection complete
00> <info> app: Reading flash usage statistics...
00> <info> app: Found 5 valid records.
00> <info> app: Found 0 dirty records (ready to be garbage collected).

Garbage collection is done here in the pm_evt_handler in main.c:

case PM_EVT_STORAGE_FULL:
        {
            // Run garbage collection on the flash.
            err_code = fds_gc();
            if (err_code == FDS_ERR_NO_SPACE_IN_QUEUES)
            {
                // Retry.
            }
            else
            {
                APP_ERROR_CHECK(err_code);
            }
        } break;

Flash dump:

devzone.nordicsemi.com/.../3630.flash.hex

RE: Flash write issue

Jørgen Holmefjord — Sun, 20 Sep 2020 17:00:18 GMT

Hi,

Is the write/update completed successfully, or is there any errors reported from the FDS function call?

Could be that the FDS area is full, preventing you from storing more data to flash. What values do you get if you call fds_stat()?

Are you running garbage collection somewhere in your application?

Can you provide a dump of the flash? You can do that using "nrfjprog --readcode flash.hex" command.

Best regards,
Jørgen