This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

fds_record_write doesn't trigger a FDS_EVT_WRITE event

Hello,

My problem is pretty much identical to this one:

devzone.nordicsemi.com/.../

My functions look exactly like the ones posted in the original question and I was indeed making the same mistake that was being made in that case. But after I applied the fix, and added the fs_sys_evt_handler to my softdevice callback, I still did not receive any flash events. I have even tried copy pasting most of the code from the original question, but that hasn't worked either.

I am using an nRF51 board with the s130 softdevice and the v12.1.0 SDK. Any help would be appreciated!

Thank you.

Regards, Sid

Parents
  • If I just load the hex file from the example you provided, it looks like everything works. I am able to connect to the board and view the services, etc. So looks like my board is fine. I stripped everything down again and added just the fds functions to my code, and now I am getting the error FDS_ERR_NO_PAGES. I feel like there is something wrong with my memory allocation, but I checked my linker scripts and the memory numbers there match the ones in the linker script from your example. I am quite stumped as to what could be going wrong. Here is a link to the test code that I was using: www.dropbox.com/.../fds_test.c

    Edit 1: As bizzare as it sounds, this code now seems to be working without me having to change anything, albeit on an nRF51 and not nRF52. On the 52, I get FDS_ERR_BUSY with the FDS_INIT event...

    Thanks your help, I really appreciate it! -Sid

Reply
  • If I just load the hex file from the example you provided, it looks like everything works. I am able to connect to the board and view the services, etc. So looks like my board is fine. I stripped everything down again and added just the fds functions to my code, and now I am getting the error FDS_ERR_NO_PAGES. I feel like there is something wrong with my memory allocation, but I checked my linker scripts and the memory numbers there match the ones in the linker script from your example. I am quite stumped as to what could be going wrong. Here is a link to the test code that I was using: www.dropbox.com/.../fds_test.c

    Edit 1: As bizzare as it sounds, this code now seems to be working without me having to change anything, albeit on an nRF51 and not nRF52. On the 52, I get FDS_ERR_BUSY with the FDS_INIT event...

    Thanks your help, I really appreciate it! -Sid

Children
No Data
Related