sd_flash_write halts

[Dajgoro Labinac]

Hi,

On SDK12.3 when using sd_flash_write at any memory location causes the device to halt and restart.
On SDK11 I've been using flash_word_write and flash_page_erase using the NRF_NVMC registers, and it worked flawlessly.
But I can't seem to figure out what is the issue with SDK12.3.
I've read that using NRF_NVMC with the softdevice is not allowed.
I've been writing to NRF_FICR->CODEPAGESIZE * (NRF_FICR->CODESIZE - 1) previously and that always worked.
But is there a way to reserve a page of flash to which I can store my custom data structure and modify it in the firmware without using fds?
I've tried making a const char array of a size and then writing to its pointer, but that didn't work. If I know my application code is less than 32k, can't I just write anything after the 32k mark?
I also have a softdevice and bootloader.

Edit:
I'm currently using SDK12.3 and I can't migrate it to a newer version, but the question applies for newer SDK too.

[Turbo J]

Flash writes should be done with softdevice functions. NRF_NVMC is only available when not using softdevice (or softdevice is completely disabled).

Reason behind this limitation is timing. Flash write and erase is only possible during bluetooth "gaps" - i.e. in the idle time between radio activities.

Edit: You can store application specific data using FDS. Note that using NRF_FICR->CODEPAGESIZE * (NRF_FICR->CODESIZE - 1)  would not work properly with the NRF supplied bootloader.

[Edvin]

Hello,

It is correct as Turbo J says, the NRF_NVMC is only available when the softdevice isn't enabled.

However, it should be possible to use sd_flash_write() (and all other functions starting with sd_...().

The description halt and restart sounds like the error handler. You probably get an return from one of your calls (possible sd_flash_write()) which returns an err_code != 0, which is passed into an APP_ERROR_CHECK(err_code);

Try to define DEBUG in your preprocessor defines, and set a breakpoint on line 76 in app_error.c. Add error_info to watch, and see where the error comes from. What is the .err_code, and what is the function call that returned the err_code which was passed into APP_ERROR_CHECK(err_code) on line .line_num in file .p_file_name ?

Best regards,

Edvin

[Dajgoro Labinac]

Seems I can't use FDS, I'm out of space, so I will have to find an alternative solution.

[Edvin]

From the PM that you sent me, I assume that you found the solution to your problem.

BR,
Edvin

[Dajgoro Labinac]

Yes, trivial fix.
I'm now experimenting with fstorage.