sd_flash_write HardFault when softdevice is enbled

Question

Hi,

I'm currently in trouble with the sd_flash_write function. I've already a library using this function running on the nRF52832 with the S132 softdevice. But when a tries to run the same code compiled for the S140 softdevice on the nRF52840, the function call get stuck in the hardfault handler.

I use the SDK version 15.2.0

If the softdevice is enabled, the hardfault always occurs at the address 0x24ADC and with the PC = 0x14a3a. But if the softdevice was never enbled, the function is perfectly working.

Do you have an idea why the function break the softdevice ?

I know the there are some other smart functons to manage the memory but I aready have an optimized library for the memory managment using the sd_flash_write function and sd_flash_page_erase.I don't want to redo all my library.

Regards

Øyvind · Accepted Answer

Hello again, We were able to find the source of the assertion. The code is writing too big chunks to the flash at one time, causing the error. This is explained in the SoftDevice Flash memory API documentation 
 However, this is a bug with the SoftDevice and is reported internally. A suggestion for a workaround is to write two times 512 bytes instead of 1024 bytes. 
 The best workaround is to use the Flash Storage (fstorage) , which is written to handle bigger data and divide into smaller chunks, and handle bigger queues with data, without disturbing radio events / SoftDevice. There is an example here . Hope this solves the issue. -Øyvind

sd_flash_write HardFault when softdevice is enbled

Top Replies