Handling Fds_write event before reading from flash.

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Tue, 22 Nov 2016 16:15:30 GMT

It is difficult to understand what you are doing with the record keys, I don't understand why you are changing them. Anyways, could you zip your complete project, edit the question and attach it there? So I can test it here? Also, what SDK and SoftDevice version are you using?

RE: Handling Fds_write event before reading from flash.

saiteja — Tue, 22 Nov 2016 13:29:12 GMT

arguments given to fds_write() are a 2 dimensional array,record_write parameter which will add to 0x2222 to get record key.size of model this is actually number of rows in model_array which will be multiplied by 3 to give the length_words.

i am testing this when I am reading from flash. i verified at every point that the data is not corrupted till the function fds_write() is called. means i am getting proper values of array before giving to fds_write().

in the last 5 rows i am getting back zero,but there should be some value.

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Tue, 22 Nov 2016 13:16:07 GMT

And how are you testing this? How are you using fds_write()? What arguments do you give to the function?

RE: Handling Fds_write event before reading from flash.

saiteja — Tue, 22 Nov 2016 12:26:47 GMT

I have found that during fds_record_update i was not providing the record_desc.record_id. that is why it was giving record not found.Now i am able to update. But the issue of last few bytes not been written is still there. I am attaching updated fds_write code

static ret_code_t fds_write(float  model_array[][3],uint16_t record_write,uint16_t size_of_model)

{

	fds_record_t        record;

	fds_record_desc_t   record_desc;

	fds_record_chunk_t  record_chunk;

	record_chunk.p_data         =  model_array;

	record_chunk.length_words   =  size_of_model*3;

	record.file_id              =  FILE_ID;

	record.key                  =  REC_KEY+record_write;

	record.data.p_chunks        =  &record_chunk;

	record.data.num_chunks      =  1;

	record_desc.record_id       =  record_write+1;//imp line when you are using fds_record_update.

	ret_code_t ret;

	ret = fds_record_update(&record_desc,&record);

	return ret;
}

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Tue, 22 Nov 2016 10:13:49 GMT

Ok. Maybe you can include some code that shows how you are doing this? I'm guessing it has changed from the code in the question?

RE: Handling Fds_write event before reading from flash.

saiteja — Tue, 22 Nov 2016 08:40:16 GMT

Here I tried to add larger and smaller array than previously stored data,and I am using fds_record_delete() followed by fds_record_write() , I found that the last 60 bytes are not updating.

I am not using fds_record_update because it provide me with error of FDS_ERR_NO_SPACE_IN_FLASH and also FDS_ERR_NOT_FOUND.

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Mon, 21 Nov 2016 14:03:22 GMT

It seems you can put more data into the record, have you experienced anything else?

RE: Handling Fds_write event before reading from flash.

saiteja — Mon, 21 Nov 2016 12:54:31 GMT

one more thing data length should be same for update? means can i give array of larger or smaller length than previously stored data,while calling fds_record_update().

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Mon, 21 Nov 2016 11:05:42 GMT

The record key will be whatever you give to fds_record_update().

RE: Handling Fds_write event before reading from flash.

saiteja — Fri, 18 Nov 2016 12:25:16 GMT

When fds_record_update() is called it will create a new record and delete the older one.So the question is that the REC_KEY is changed during this process,or it will update the record with the same REC_KEY.

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Fri, 18 Nov 2016 10:09:17 GMT

I don't understand, please clarify.

RE: Handling Fds_write event before reading from flash.

saiteja — Thu, 17 Nov 2016 13:38:48 GMT

i have commented that delete part already and then checked it.Is that possible that fds_record_update() when create a new record change the REC_KEY.

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Thu, 17 Nov 2016 11:23:53 GMT

I think fds_record_update() can't find the record because it is deleted. Why are you deleting the record before you update?

RE: Handling Fds_write event before reading from flash.

saiteja — Thu, 17 Nov 2016 07:23:15 GMT

Hi Petter, I debbuged the error and found fds_record_update is returning FDS_ERR_NOT_FOUND. how to solve this problem while if i am using fds_delete_record and then fds_record_write i am able to write few values not all.

RE: Handling Fds_write event before reading from flash.

saiteja — Wed, 16 Nov 2016 14:41:56 GMT

Thanks Petter for clearing things.

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Wed, 16 Nov 2016 14:35:41 GMT

Yes. If you call fds_record_write() you will get a FDS_EVT_WRITE event. If the result is FDS_SUCCESS the write operation is complete.

RE: Handling Fds_write event before reading from flash.

saiteja — Wed, 16 Nov 2016 14:33:25 GMT

In the case FDS_EVT_WRITE in fds_event_handler(),if result is FDS_SUCSESS this just means that the write event is completed ?

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Wed, 16 Nov 2016 14:23:57 GMT

Put in a case for FDS_EVT_UPDATE in fds_event_handler(). When you get this event and the result is FDS_SUCCESS, an update operation is complete.

RE: Handling Fds_write event before reading from flash.

saiteja — Wed, 16 Nov 2016 12:56:14 GMT

Hi Petter, Thanks for response,I was thinking if you could point me in direction that how to wait for the fds_evt_update to complete.should i put delay or any other suggestion.

RE: Handling Fds_write event before reading from flash.

Petter Myhre — Wed, 16 Nov 2016 12:44:47 GMT

I don't understand what the problem is, or what you are seeing, but:

Why are you deleting the record before you update it? fds_record_update will write the new record to flash and then delete the old record.

Why are you not checking the returned error of the functions? If they don't return FDS_SUCCESS you will not know if the operation was queued successfully.

Why are you not waiting for the events that tell you that the operation completed successfully? FDS_EVT_UPDATE, FDS_EVT_DEL_RECORD and FDS_EVT_GC?