[PCA10040][SDK11] FDS unable to read [closed]

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Fri, 10 Jun 2016 09:24:06 GMT

Excellent!

RE: [PCA10040][SDK11] FDS unable to read [closed]

Lalit Kumar — Fri, 10 Jun 2016 09:19:25 GMT

Found the solution. The problem was I was not initializing the fds_find_token_t ftok, which in this example has been marked as very important. Should have read the comments :/ Everything is working fine now.

Anyway thanks RichieJH for helping.

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Fri, 10 Jun 2016 08:44:54 GMT

Ah, ok I see. A couple of other things, are your flags working as you imagine? You are defining a global rec_count and manipulating that it a number of different places. Is it the value you imagine when trying to read a record? You are debugging almost identical sentences at different places, is there a chance you are misinterpreting?

RE: [PCA10040][SDK11] FDS unable to read [closed]

Lalit Kumar — Fri, 10 Jun 2016 08:19:14 GMT

I have commented peer_manager_init in the main as I'm not using any BLE functions. That's why I'm calling fds_init separately.

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Fri, 10 Jun 2016 07:38:14 GMT

I see you are calling fds_init when the peer manager does this. This can lead to strange behaviour, especially early on. Also most fds returns are call successes, not operational successes. So don't be fooled into believing something has happened because the return is nil.

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Wed, 08 Jun 2016 10:21:56 GMT

I'm a simple guy, so if I was you I would first check if I could find the record in main and then work up from there. Flash is asynchronous so to try and do things in an interrupt at the wrong priority is not going to be ideal.

RE: [PCA10040][SDK11] FDS unable to read [closed]

Lalit Kumar — Wed, 08 Jun 2016 10:15:15 GMT

I have checked it many times, the err_code is 10. In the fds_evt_handler I'm getting a valid record id on written event, so I guess it is safe to assume that the write is done successfully. I have also tried keeping the record.key same and searching with the same key, but with no success. One thing I'd lforgotten to mention is that I'm trying to read the data in a timer timeout handler. I've attached the main file as an edit to the question in case I might have missed something else that needs mentioning.

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Wed, 08 Jun 2016 08:59:29 GMT

Providing the err_code is 10 (i.e., not able to find record) and not some other error code then it is a mystery. Perhaps avoid the increment to the record number in the fds_record_find() call itself but providing you have written successfully then that is call that should yield success.

RE: [PCA10040][SDK11] FDS unable to read [closed]

Lalit Kumar — Wed, 08 Jun 2016 08:22:04 GMT

Yes, i have made sure that the fds is initialized only once. Also i think thewrite is done properly as in the FDS_EVT_WRITE I'm getting a valid record id. Is there any other method to check that the write is done properly? I have used the above code as a guide in writing my current code.

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Wed, 08 Jun 2016 07:42:40 GMT

I think the peer manager initialises FDS, so be careful you are not doing it twice as this can lead strange behaviour. More on that here https://devzone.nordicsemi.com/question/78487/fds-sample-code/

RE: [PCA10040][SDK11] FDS unable to read [closed]

Lalit Kumar — Wed, 08 Jun 2016 06:54:44 GMT

Yes i am. I have used app proximity example for pca10040 as starting point which uses peer manager and fds, the function has been called inside sys_evt_dispatch.

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Wed, 08 Jun 2016 06:48:05 GMT

Are you calling this void fs_sys_event_handler( uint32_t sys_evt ) anywhere in your code? Without this it may appear to be writing correct but it won't be.

RE: [PCA10040][SDK11] FDS unable to read [closed]

Lalit Kumar — Wed, 08 Jun 2016 04:35:41 GMT

I can see that writing is done successfully. Fds_record_find return fds_error_not_found meaning the record was not found. I am assuming that the key that is being given to fds_record_find is the record.key and not the record key returned by record_desc as they are different. Any suggestions on what should i look for in debug?

RE: [PCA10040][SDK11] FDS unable to read [closed]

RichieJH — Tue, 07 Jun 2016 21:34:48 GMT

You have plenty of debug messages and err_codes set - what are you seeing?