Using SDK 16.0.0 on an nRF 52840 board.
Managed to get a board into a state where it had only data pages and no swap pages, and therefore fds_init fails with the NO_SWAP code from pages_init. Saw some other similar tickets, but none of them exactly the same. I have three pages all of which start with DEADC0DE F11E01FE. Only one page has any data after those markers. See attached document for flashdump. /cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-6a8175cd5d964af9875cb467636629a7/flashdump.txt
I am using the peer manager as well as storing a few configuration values in the FDS, which has all been working fine up until this board started failing on startup. I call garbage collection just after initialization whenever the board is booted, and I believe the peer manager also calls it as needed?
My theory is that garbage collection was interrupted by a power off at some specific point (similar to this bug https://devzone.nordicsemi.com/f/nordic-q-a/53687/fds---missing-swap-page), but I can't replicate this. The fix for that bug was implemented inside the FDS_PAGE_SWAP case in pages_init, which my code never reaches since all of my pages are marked as data.
Even without knowing the exact cause, it would be great to be able to implement recovery when this error code is returned. I know that means erasing a page and then reinitializing, but I can't seem to figure out how to erase the correct "page number" using sd_flash_page_erase. I can't access the start_addr of the FDS pages from outside the module - is there any way to get this value without recalculating it?
