FDS writes while performing garbage collection.

RE: FDS writes while performing garbage collection.

Jared — Mon, 08 Apr 2019 06:44:12 GMT

I understand. I'll forward your suggestion to the developing team.

RE: FDS writes while performing garbage collection.

bart — Fri, 05 Apr 2019 13:10:31 GMT

Indeed, it returns success, while it should not, since you have to wait for GC to be done. So my suggestion is that it should return FDS_ERR_BUSY when GC is running.

RE: FDS writes while performing garbage collection.

Jared — Fri, 05 Apr 2019 11:22:19 GMT

Hi,

No, FDS_ERR_BUSY is not returned by fds_record_write(), but is returned by record_write_data(). The latter is an internally function used by the module which is not meant to be used directly by the application. The documentation for fds_record_write() specifies the return types as follows:

Return values

FDS_SUCCESS	If the operation was queued successfully.
FDS_ERR_NOT_INITIALIZED	If the module is not initialized.
FDS_ERR_NULL_ARG	If `p_record` is NULL.
FDS_ERR_INVALID_ARG	If the file ID or the record key is invalid.
FDS_ERR_UNALIGNED_ADDR	If the record data is not aligned to a 4 byte boundary.
FDS_ERR_RECORD_TOO_LARGE	If the record data exceeds the maximum length.
FDS_ERR_NO_SPACE_IN_QUEUES	If the operation queue is full or there are more record chunks than can be buffered.
FDS_ERR_NO_SPACE_IN_FLASH	If there is not enough free space in flash to store the record.

Note: that the return of FDS_SUCCESS does not mean that the write operation is done, but that the operation has been staged.

Best regards

Jared

RE: FDS writes while performing garbage collection.

bart — Thu, 04 Apr 2019 11:31:34 GMT

Right, so shouldn't fds_record_write() return FDS_ERR_BUSY? I only have 1 FDS user, but when you have multiple, the other users don't even know GC started.

RE: FDS writes while performing garbage collection.

Jared — Wed, 03 Apr 2019 13:37:31 GMT

Hi,

The reason that you should wait for the asynchronous function to return is because it guarantees that the garbage collection has released the memory. A program that doesn't wait for the function to return could result in unexpected behavior.

Best regards

Jared