FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

Petter Myhre — Fri, 02 Feb 2018 15:34:11 GMT

You can check the start and end address used by Fstorage by putting breakpoint in flash_bounds_set() in fds.c. If you have a bootloader flash_end_addr() will account for that and use the flash pages below. The SDK examples typically reserves 3 flash pages.

DFU_APP_DATA_RESERVED determines how many flash pages below the bootloader that will be reserved (not erased when doing DFU). This should match the number of pages used by Fstorage, typically 3.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

edmond.yun — Fri, 02 Feb 2018 12:30:20 GMT

Hi, Petter,

sorry for any confusion, I confused this agenda with other...sorry...

for only this agenda, currently I am not using for delete_record function,

instead, I confirmed the size of memory by using DFU_APP_DATA_RESERVED, it can be defined by user in sdk_config.h... and it is related with the region of app data, when verifying by myself, the data can kept in the region of app data(maybe) after doing DFU... I tried to verify for many times by firstly writing some data with field value, after that, I tried to read the data with the same field data by using fds function(not fstorage function). so I learned that if can confirm the size of necessary data with DFU_APP_DATA_RESERVED in the region of app data (maybe, I am'not sure that the region of DFU_APP_DATA_RESERVED is the region of app data), I don't need to delete the record every time (when writing new data in the same field) because new data will be updated (not written) by update_fds function.. is it right ?

so currently I can't find the error related with find function because I am not using delete_record_fds function. how about my usage ? is it right for mass production ?

please help to let me have the confirmation about my code...

thankful for your support in advance,

thanks.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

edmond.yun — Fri, 02 Feb 2018 12:10:00 GMT

Hi, Petter,

I am very thankful for your care and concern, I need to really use fstorage with exact information,

I will explain what I know for the function, please refer below,

1. I searched for app data, I can keep user data in the region of memory map and I can allocate the size of the memory with DFU_APP_DATA_RESERVED in sdk_config.h...

you can find more information in site of nordic development description like api description so on....

I need to keep the user data with fstorage in the region of app data memory, it is a fundamental question for this agenda.... How can I confirm the usage of app data memory with fstorage ? how can define the address of start/end ?

the data should be kept after doing dfu...it is also important for mass-production, please refer it,

please help to provide the useful example of fstorage by modifying my code,

thankful for your support in advance,

thanks.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

Petter Myhre — Fri, 02 Feb 2018 11:19:38 GMT

I'm sorry, I don't understand. What does DFU_APP_DATA_RESERVED have to do with this? Do you still have a problem? If you do, could you try to clearly explain what it is?

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

edmond.yun — Fri, 02 Feb 2018 01:31:48 GMT

Hi, Petter Myhre,

I refer your guide, and understand the reason that the FDS_ERR_NOT_FOUND error is happened,

after deleting record repeatedly and if trying to read and write data, maybe the fds management system can have the timing issue... so I think that if only using to update data (not using deleting record), the issue is not happened, but need to confirm the necessary memory with DFU_APP_DATA_RESERVED in sdk_config.h... is it right ?

if the size of data is not over to the memory, most errors are not happened...is it right ?

if I have mis-understanding, please help to provide the perfect example to use for mass-production,

when I check the example of sdk 14.1.0, it is not enough to use for production,

ex) if failing to update or write data, the handler that received the result need to try the behavior again after checking result...

thankful for your support in advance, (can see the case with FDS_EVT_GC in the attached code).

thanks.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

Petter Myhre — Mon, 29 Jan 2018 11:39:23 GMT

You should always check the returned errors, but not all errors are unrecoverable. I'm not sure why you wouldn't check the error?

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

edmond.yun — Fri, 26 Jan 2018 02:57:47 GMT

Hi, Petter,

I refer your guide, when trying to do more test, if trying to read the data after some time (after writing data), I can read/write correctly, the error is not happened, so I think that if trying to read the data as soon as writing the data, this kind of error is not happened, if so, I don't need to check the error, how about your opinion as to this situation ? I would like know your opinion, if current situation is no problem, I will use above code, no modification,

thankful for your kindness in advance, thanks.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

Petter Myhre — Thu, 25 Jan 2018 08:56:14 GMT

You should always wait for the completion event before assuming that the operation is complete. Always.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

edmond.yun — Thu, 25 Jan 2018 00:38:44 GMT

according to your description, if the data is stored in the communication flow (by handler) of BLE, this kind of issue can't be happened in most cases, currently I test by instant writing and reading, so this issue can be happened, is it right ? I wonder whether I should check the completion of writing in normal usage(ble communication), thankful for your kindness in advance, thanks.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

Petter Myhre — Wed, 24 Jan 2018 13:22:38 GMT

Yes, you should wait for the FDS_EVT_WRITE event in the handler before assuming that the record is written. Before you get the event, you don't know if the record has been written or not.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

edmond.yun — Wed, 24 Jan 2018 13:06:43 GMT

Hi, Petter,

firstly, thankful for rapid response, I worried that the error is happened in the timing of read trial, even though fds_record_find function return the error, what I mean is that when I would like to read the stored data(by fds_record_write funtion), the stored data can't be normally print out by yps_storage_read function, you can see the log,

yps_storage_find not found 0x1111 0x3333

fds_record_write : 0 245

yps_storage_read not found 0xEvent: FDS_EVT_WRITE received (FDS_SUCCESS)

first line is different from third line, I wonder why the error is happened in yps_storage_read function, the timing is that fds_record_write was already done, anyway as a result, I can't read the stored data when I would like to check it, it is a problem,

please help to let me know whether it is really a problem or not kindly,

thankful for your support in advance,

ref) Should I check the completion as to writing in event handler ? and then I should try to read the stored data, is it right ? Please help to let me know good idea,

thanks.

RE: FDS_ERR_NOT_FOUND issue of yps_storage_find in sdk 14.0.1

Petter Myhre — Wed, 24 Jan 2018 11:33:59 GMT

I don't quite understand what the problem is. Do you not expect to get FDS_ERR_NOT_FOUND after you have deleted the record? Could you please clarify what the problem is?