Over size of FLASH when using fs_stotage ex

RE: Over size of FLASH when using fs_stotage ex

Bar — Tue, 21 May 2019 14:46:50 GMT

If you just mention the garbage collection I didn't aware about it. So I read it can be call when there is no free space to write.

But I see if you use fds_gc "This function is asynchronous. Completion is reported through an event that is sent to the registered event handler function."

But I can't find which event it is and what handler it use. I assume the handler is configure on init at start. DOes it part of the FDS_init or there and init for the gc alon?

Is there an example I can see how it run because in the FDS storage it is not clear?

RE: Over size of FLASH when using fs_stotage ex

Kenneth — Tue, 21 May 2019 11:59:35 GMT

There is no "management table no", the only addition I can think of is the page tags:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_fds_format.html?cp=5_1_3_55_2_1#lib_fds_format_page

If you are updating records you should run garbage collection to free up space:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_fds_functionality.html?cp=5_1_3_55_1_2#lib_fds_functionality_gc

RE: Over size of FLASH when using fs_stotage ex

Bar — Tue, 21 May 2019 11:32:02 GMT

Yes I use the FDS.

I know about the header. But I believe there is also menagment Table that hold reference to each file. How big is this table, and does it fix or increase as file added?

RE: Over size of FLASH when using fs_stotage ex

Kenneth — Tue, 21 May 2019 08:59:55 GMT

The fstorage module doesn't have any overhead (it will write whatever you specify to an address), but if you use FDS then there is some overhead as described here:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_fds_format.html?cp=5_1_3_55_2