I have gotten the FDS_ERR_NO_PAGES issue multiple times now. In our last pre-production run, it randomly happened to a few units (4 out of 60). For 3 of the units, the error resolved itself after a few reboots but with time it happened more and more often and after a while all the time. The last unit got the error after a DFU (application). Since this happened to the 4 most used units I thought that a part of the flash memory could be exhausted. After changing the firmware to be more flash-conservative I got the units working by changing FDS_VIRTUAL_PAGES (application) and DFU_APP_DATA_RESERVED (bootloader). But not after the first update, it took more like 20 updates until it worked for each unit. After that, they have worked.
Now we are using the same hardware to develop a similar product. The new firmware is based on ble_app_ancs_c and while debugging it works flawlessly but when I try to run in on an actual unit by updating it through DFU I get the FDS_ERR_NO_PAGES error. I tried deleting the first application_data pages if the error occurs and how it works but they are deleted on every reboot.
if (ret != NRF_SUCCESS)
{
if(ret == FDS_ERR_NO_PAGES){
for(uint8_t rc = 0; rc < 3; rc++)
{
while(sd_flash_page_erase(118 + rc) != NRF_SUCCESS);
}
}
NRF_LOG_ERROR("Could not initialize flash storage. fds_init() returned 0x%x.", ret);
return NRF_ERROR_STORAGE_FULL;
}
What is happening and what am I doing wrong?
Could the application_data area be corrupted? How do I clear it? Deleting the pages does not seem to work.
Could the flash memory be exhausted? It should be good for 10k deletes?
| Info | |
| Pre-production | |
| SDK | 15.0.0 |
| Softdevice | 6.0.0 |
| Bootloader | secure_bootloader_ble_s132_pca10040 |
| New version | |
| SDK | 17.1.0 |
| Softdevice | 7.2.0 |
| Bootloader | secure_bootloader_ble_s132_pca10040 |
| FDS_VIRTUAL_PAGES | 10 |
| FDS_VIRTUAL_PAGE_SIZE | 1024 |
| NRF_DFU_APP_DATA_AREA_SIZE | 40960 |
Steps I took for updating:
- Device was running pre-production fw and bootloader.
- Built a new bootloader: nrfutil pkg generate --hw-version 52 --bootloader secure_bootloader_ble_s132_pca10040.hex --bootloader-version 3 --sd-req 0xA8 --sd-id 0x0101 --softdevice s132_nrf52_7.2.0_softdevice.hex --key-file xtactor_fw_private.key ancs_update_bootloader.zip
- Updated the bootloader with DFU.
- Built a new firmware: nrfutil pkg generate --hw-version 52 --application-version 200 --application ../pca10040/s132/ses/Output/Release/Exe/ble_app_ancs_c_pca10040_s132.hex --sd-req 0x0101 --key-file xtactor_fw_2_private.pem xtactorfw_2_v200.zip
- Updated the fw with DFU.
Again am I doing something wrong?
