fds_init failure and recovery options

RE: fds_init failure and recovery options

joel-sc — Tue, 30 Nov 2021 14:32:56 GMT

Hello,

There is an update on this?

RE: fds_init failure and recovery options

MarieMaurer — Wed, 27 Jan 2021 14:22:54 GMT

Hi Kenneth,

I think we reached the same point. Can you please give us an current update on this topic?

Many thanks!

Best regards,
Marie

RE: fds_init failure and recovery options

cbrown_cdi — Sat, 03 Oct 2020 20:36:09 GMT

Hi Kenneth,

Can you provide an updated implementation of this for the current SDK? Looks like fstorage_internal_defs.h no longer exists.

Thanks!

RE: fds_init failure and recovery options

bart — Tue, 12 Nov 2019 15:53:11 GMT

Hi Kenneth,

I also ran into this problem, and implemented a pages erase.

But then I still have to reboot, as fds_init already set some variable that remembers it's initializing (m_flags.initializing), and then refuses to initialize. So I hope the team doesn't just implement a page erase method, but make sure we can init fds after that as well.

RE: fds_init failure and recovery options

Jordan Archer — Mon, 12 Aug 2019 16:40:35 GMT

That's what I did.

An enhanced fds_stat that always worked (even if init had failed), would have helped debugging. I had to hand examine every page to figure out what was wrong.

Thanks!

RE: fds_init failure and recovery options

Kenneth — Mon, 12 Aug 2019 12:05:12 GMT

I have added your input and suggestions to internal Jira for the SDK team to look at for future improvement of the FDS.

For now you would need to make your own implementation of "cleaning up" storage area reserved for FDS yes, e.g. something like:

#include "fds_internal_defs.h"
#include "fstorage_internal_defs.h"
#include "nrf_nvmc.h"
...
{
  uint32_t const *addr = FS_PAGE_END_ADDR;
  uint32_t pages = FDS_PHY_PAGES;
  uint32_t curr_addr = 0;
 
  sd_softdevice_disable();
 
  for (int i = 1; i < (pages + 1); i++)
  {
    curr_addr = (uint32_t)addr - (FS_PAGE_SIZE*i);
    nrf_nvmc_page_erase(curr_addr);
  }
}