Problems using fstorage to write to flash (using it alongside mesh sdk)

Question

Hi, currently I am using fstorage alongside ble-mesh to store some data in flash. Currently however, writing with fstorage seems to be successful only about 50% of the time, with the other failing 50% giving me a timeout error (error code 13, NRF_TIMEOUT_ERROR). The memory areas between the mesh data and the fstorage do not overlap. Reading using fstorage so far works just fine. Are there any ideas to what might be causing this issue? 
 I suspect perhaps the fstorage operations might be competing with the mesh events in some sort of scheduler but I am not sure. 
 Thanks in advance 
 PS. I am aware that the mesh SDK offer its own thing for managing flash data (flash manager) but i used fstorage due to my greater familiarity with it plus the fact that there are no flash manager examples in the SDK, so I would prefer if i can stick with my current fstorage solution, however if this issue is unfixable I am open to trying out the mesh SDK's flash manager.

Hung Bui · Accepted Answer

Hi Jeffe, I suspect that the mesh stack timeslot scheduling may be the cause. So basically the way the mesh stack works is to request timeslot from the softdevice and continue to extend it until it reach the limit (128s) then it will request another timeslot. 
 If you are inside an timeslot and calling a softdevice flash API , it may get delayed until the timeslot next extending period. It's mentioned here in our documentation in the earlier nRF5 Mesh SDK documentation (look for fstorage). 
 The reason the ble_app_proximity works fine could be that flash operation only occurred when the chip is handling BLE activities (bonding), when it may not be the case with your application. 
 I think the best solution here would be to use the flash manager module from mesh. Or you would need to pause mesh before you execute flash operation in fstorage and then continue back on.

Problems using fstorage to write to flash (using it alongside mesh sdk)

Top Replies