nRF52840 - FDS init FDS_ERR_NO_PAGES problem (SDK 15.0.0)

[leoc7]

Hi everyone,

My hw/sw configuration:

- nRF52840
- sdk 15.0.0
- softdevice: s140_nrf52_6.0.0
- bootloader + softdevice + application

We're in production stage and we're encountered some problems with the data stored in FDS area.
In particular, in some products fds_init() function return FDS_ERR_NO_PAGES error. 

Below, the FDS initialization function:

bool int_flash_init(void){
	ret_code_t ret = FDS_SUCCESS;

	ret = fds_register(fds_evt_handler);
	if (ret != FDS_SUCCESS)
	{
	    NRF_LOG_ERROR("Registering of the FDS event handler has failed.");
		return false;
	}

	ret = fds_init();
	if (ret != FDS_SUCCESS)
	{
	    NRF_LOG_ERROR("FDS handle init error = 0x%x", ret);
		return false;
	}

	return true;
}

I try to read the memory area using "nrfjprog --memrd" command and the memory content is not corrupted. The data are valid but the fds_init return error.

Please, could you help me?
Could you suggest me a "workaround" to correctly initialize the FDS area? I don't want and I can't erase the memory otherwise the product will lost important configuration data.

Thanks

[Jimmy Wong]

You can check with the SDK 16.0 ( in the release note) which has fixed the problem of the FDS issue.  You can do the difference files on fds.c and fstorage.c.

[leoc7]

Thanks for reply.
I try to add the fds library of SDK16 in my project, but the problem persists. Initialization fails with error FDS_ERR_NO_PAGES. I updated the firmware with OTA.

[leoc7]

I don't want to erase chip because I don't want to lost data stored in FDS area. Please, could you help me? Could you suggest me a "workaround" in order to avoid full chip erase? thanks

[Susheel Nuguru]

You need to increase the FDS_VIRTUAL_PAGES count in your sdk_config.h file as written here. to solve the problem with NO_PAGES error.

But i think when you recompile and flash the new application, the debugger will overwrite the FDS reserved flash area.

II think the best is to use a new bootloader and flash the new bootloader with DFU_APP_DATA_RESERVED set to the number equal the FDS number of pages. After you flash the new bootloader, use the OTA firmware upgrade to flash the new application that updates the application but keeps the FDS specific app data.

[leoc7]

Dear Susheel,
I can't flash anything with the JTAG programmer. I have to perform all countermeasures only with OTA.
Could you suggest me an approach using only OTA update?
Thanks

[Susheel Nuguru]

Over OTA, update the bootloader first with correct  DFU_APP_DATA_RESERVED  and then update the application using the new updated bootloader

[leoc7]

Summarize:

1. APPLICATION: Increase the number of FDS_VIRTUAL_PAGES from 3 to 4 in sdk_config.h

#ifndef FDS_VIRTUAL_PAGES
#define FDS_VIRTUAL_PAGES 4
#endif

2. BOOTLOADER: Increase the number of DFU_APP_DATA_RESERVED from 3 to 4 in sdk_config.h

#ifndef DFU_APP_DATA_RESERVED
#define DFU_APP_DATA_RESERVED               (CODE_PAGE_SIZE * 4)
#endif

3. Update new Bootloader with OTA

4. Update new Application with OTA

Is it correct?

Thanks

[Susheel Nuguru]

Great summary. Yes, That should work in my opinion.