Should I call the fds_init function if I want to use fds module to store data?

RE: Should I call the fds_init function if I want to use fds module to store data?

Einar Thorsrud — Wed, 30 May 2018 08:12:24 GMT

There is no direct way to separate the areas as there is no support for it in FDS, and FDS only support a single instance. You can set a side x number of flash pages and manage it manually via fstorage like you suggest, while keeping FDS for the peer manager only. The downside is that fstorage is only provide basic flash write and erase support, so you will have to provide any file system like features and wear leveling yourself if you need it.

RE: Should I call the fds_init function if I want to use fds module to store data?

cgha — Wed, 30 May 2018 01:57:02 GMT

Is there any way to separate the area the peer manager used and my data area, does the fstorage can solve this problem, since it will give my the start addr and end addr upon it is initialized.

RE: Should I call the fds_init function if I want to use fds module to store data?

Einar Thorsrud — Tue, 29 May 2018 10:54:19 GMT

Hi,

There is no need to call fds_init() again if you use the peer manager. It will not do any harm as it will not do anything other than generate another FDS_EVT_INIT event immediately to let you know that FDS is initialized. In any case you must remember to not make any other API calls to FDS before you get this event the first time.

The Peer manager use the same flash pages as the application, so you should set FDS_VIRTUAL_PAGES so that there is room for both the peer manager data and your other application data.