garbage collection

[Bar]

I need to run gc because I get rc =FDS_ERR_NO_SPACE_IN_FLASH.

So I run gc simple as written in 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 

I just write this

rc = fds_record_update(&record_desc, &record);
if(rc == FDS_ERR_NO_SPACE_IN_FLASH) // no space in the FLASH
{
  ret_code_t rc = fds_gc();// try to do garbage collection
  if (rc != FDS_SUCCESS)
  {
   /* error handle */
}

}

But just when I do the fds_gc() I get hard fault.

What do I miss here?

Bar.

[Simonr]

Hi Bar

Are you using a development kit or a custom board? And would it be possible to recreate on a development kit? Also, what do you mean by virtual flash?

Best regards,

Simon

[Bar]

O.K.

I do today a lot of fine tuning and adapt to do the FDS_gc() exactly as run in ble_app_gatts_c example.

But the some result. It send the full FLASH event and trigger the FDS_gc() but on the queue handling it fail to hardfault. From my previous experience I know it concern to memory leakage because to small "room" for one of the operation. maybe the gc need more space (each file I made is 2K) to make the job. Which defines I can "play" with and there meaning?

[Bar]

I do all of this on the DK PCA10056.

FDS_VIRTUAL_PAGE_SIZE tand FDS_VIRTUAL_PAGES

I read it on this post https://devzone.nordicsemi.com/f/nordic-q-a/25923/fds-gc-seems-not-to-work

[Simonr]

Hello Bar

Then, what have you set FDS_VIRTUAL_PAGE_SIZE and FDS_VIRTUAL_PAGES as? Remember that these values should add up with the actual amount of needed flash pages and flash page size. 

If you'd like, you can send me your project so that I can try to debug it from my side, as I'm still unsure what exactly is causing this hard fault of yours. If you don't want to share your project publicly on DevZone I can set this case to private so that only Nordic engineers will be able to see it.

Best regards,

Simon

[Bar]

Hi 

I play with the FDS_VIRTUAL_PAGE_SIZE (1024/2048)and FDS_VIRTUAL_PAGES(3/6) but it just expend the write area before get to the gc. The gc crass when get to the execute.

I attach a link to the whole project

https://drive.google.com/open?id=1wMrGyR6BABrZEiQG8R0lDPVpJIehySsT

The fail get around written list 85. Then when go to fds_gc

Bar