NRF FDS Issue:

RE: NRF FDS Issue:

Einar Thorsrud — Fri, 21 Oct 2022 06:45:39 GMT

Hi,

[quote user="ChinmayDixit97"]1. I am using 3 fstorage locations as 0x3e000, 0x3e004 and 0x3e008. What is the width of the data in fstorage? Can I store uin32_t data in 0x3e000,0x3e001 and 0x3e002? [/quote]

Fstorage just provide direct access to the flash, so there are no headers etc. It simply gives you a API for writing to flash and erasing flash pages that is the same regardless of if you are using a SoftDevice or not, and ensures that you stay within the region you have defined. As you only write to a small part of the page at 0x3e000, you should reserve that page for fstorage, but not anything more. And nothing else should use that page. So in this case it would make sense to set the end address to 0x3ffff. Moreover, you need to have full control over your memory layout. What does your flash cosists of, and where is every part located? Many things need to be placed at exact locations, and some (like your fstorage page) could be anywhere, as long as it does not overlap with anything else. If you see unpredictable behaviour, this is the first thing I would check (perhaps you are overwriting parts of the application or similar?).

[quote user="ChinmayDixit97"]2. Is fds pages starts automatically from where the fstorage ends? I can see, The fds has the last address as 0x80000 which is the last location in flash.
[/quote]

No. The FDS pages are located either at the very end of the flash, or right below the bootloader (if you are using that). The number of pages being used is defined by the FDS_VIRTUAL_PAGES define in sdk_config.h (the default in most examples is 3). Have a look at the memory layout figure in the bootloader documentation to get an overview.

RE: NRF FDS Issue:

ChinmayDixit97 — Thu, 20 Oct 2022 16:07:05 GMT

I have two question.
1. I am using 3 fstorage locations as 0x3e000, 0x3e004 and 0x3e008. What is the width of the data in fstorage? Can I store uin32_t data in 0x3e000,0x3e001 and 0x3e002?
2. Is fds pages starts automatically from where the fstorage ends? I can see, The fds has the last address as 0x80000 which is the last location in flash.

Thanks for your support.

RE: NRF FDS Issue:

ChinmayDixit97 — Thu, 20 Oct 2022 16:00:33 GMT

Got your point Einar Thorsrud . Will do some debugging and get back to you.!! Thank you so much!!

RE: NRF FDS Issue:

ChinmayDixit97 — Thu, 20 Oct 2022 15:58:07 GMT

Sorry Einar. Could not see your reply. Will read and get back to you.

Thanks.

RE: NRF FDS Issue:

ChinmayDixit97 — Thu, 20 Oct 2022 15:48:31 GMT

Waiting for the reply as deadlines are tight. Really Appreciated if anyone can reply and suggest me for this problem!!!

Thanks. 🙂

RE: NRF FDS Issue:

Einar Thorsrud — Wed, 19 Oct 2022 08:33:01 GMT

Hi,

I do not immediately see the link between your direct use of fstorage and FDS, other than that your fstorage region is very large and overlaps with the pages used by FDS. It would probably make sense to reduce this region to what you actually intend to read/write to, to ensure that you do not accidentally touch the FDS pages.

Regarding the reading, the code looks sensible. You write "it just hangs", but the PC will be somewhere, and you should be able to learn more by debugging. Where does it "hang"? What else do you find from debugging?

[quote user=""]is there any efficient way to read the whole data at once?[/quote]

If this data is in a single FDS record, it is consecutive in flash, so you can use memcpy just like I see you do. But separate records needs to be read separately (both because they could be scattered around the FDS pages, and because you have the headers in addition to the data, so you cannot simply copy data from more than one record in one go).