fds invalid page tag

RE: fds invalid page tag

Matej — Thu, 03 May 2018 13:37:44 GMT

Yes, on peer manager event PM_EVT_STORAGE_FULL....

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

RE: fds invalid page tag

haakonsh — Thu, 03 May 2018 12:51:48 GMT

I don't think the RAM settings is an issue. The SoftDevice Handler would notify you if there's a collision with the app ram region and SoftDevice ram region.

Do you perform garbage collection at any point?

RE: fds invalid page tag

Matej — Thu, 03 May 2018 09:46:42 GMT

Hi Håkon,

We set FDS_VIRTUAL_PAGES to 3 and flash is not used by any other module so from that we conclude that memory space is valid.

With define FDS_MAX_PAGES(FDS_VIRTUAL_PAGES - 1) fds module itself takes care that two pages are used for data and one is used for swapping data. Or did we miss something?

We have readout flash after each pairing and swapping works fine – except once… when all 3 pages were marked as they contains data (0xF11E01FE), unfortunately we are not able to reproduce it.

Removing all propriety code from project will take quite a long time that will be buildable…

What is your opinion about RAM settings (please check previous post)?

Thank you for response!

BR,
Matej

RE: fds invalid page tag

haakonsh — Fri, 27 Apr 2018 11:06:40 GMT

Hey Matej,

My first guess is that you have set an invalid memory space for the FDS library(used by other libraries or S130).

My second guess is that you have not allocated an additional page for the SWAP, f.ex. 3 pages for user data + 1 page SWAP.

Do you mind sharing your code in a project that compiles with SDK12.3?

Cheers,
Håkon