FDS delete multiple records

RE: FDS delete multiple records

Petter Myhre — Wed, 13 Sep 2017 10:20:00 GMT

Usually 4 is fine. The larger the number, the more RAM has to be reserved.

The limit is 2^32, and in practice this will never be reached.

RE: FDS delete multiple records

xhr0428 — Wed, 13 Sep 2017 05:48:06 GMT

I increased FDS_OP_QUEUE_SIZE and the error is gone now. Why is this number set to 4 by default? Is there any problem setting this a large number?

Could you also answer the other question of mine? I see record ID counts up every time I write a new one. The old ID is not reused even the record is deleted. Is there an up limit for the count? What will happen if it counts to the limit?

RE: FDS delete multiple records

Petter Myhre — Tue, 12 Sep 2017 07:45:03 GMT

If you look at the documentation for fds_record_delete() you can see that 0x00000008 is FDS_ERR_NO_SPACE_IN_QUEUES - If the operation queue is full.

You can try to call it at a later point in time (or wait for a FDS_EVT_DEL_RECORD event), or you can try to increase FDS_OP_QUEUE_SIZE and/or FDS_CHUNK_QUEUE_SIZE. See this for more information.

RE: FDS delete multiple records

xhr0428 — Tue, 12 Sep 2017 05:21:26 GMT

Changing fds_record_delete(&record_desc); to uint32_t err_code = fds_record_delete(&record_desc); APP_ERROR_CHECK(err_code); triggers app_error_fault_handler() now. Error code is 8.

Another thing I noticed is if there are more than 4 records, fatal error always appears after 4 records. The first 4 records return error code 0.

RE: FDS delete multiple records

Petter Myhre — Mon, 11 Sep 2017 09:22:27 GMT

You should check that the returned error code of fds_record_delete() is actually FDS_SUCCESS (0x00000000), to be sure that the call is actually accepted.

You cannot be sure that the record is deleted until the FDS_EVT_DEL_RECORD event is received.

Fatal must be printed from somewhere. Are you sure app_error_fault_handler() is not called? Try to define DEBUG, and put a breakpoint in app_error_handler()