Using s332 with FSTORAGE

[bencbyers]

I have been modifying a project we have to use the s332 2.0.1 with SDK 12.1. Upfront, In the current project environment, I can't update the version of the SDK I'm using, so I need to stick with SDK 12.1. 

I was able to get the project building and the initialization of the softdevice and the ANT stack appear to all be successful, however, when I try to do an FSTORAGE write shortly after startup, I get the FS_ERR_OPERATION_TIMEOUT error. I followed the directions in the sdk_config.h to increase the max retries, set it to 10, still gives same error code. This was a working project with just BLE that I started to modify and add ANT+ profiles. Is there an issue with running the BLE, ANT+ and FSTORAGE together? Is there a configuration setup that does or doesn't work with all three?

[Einar Thorsrud]

Hi,

There should not be any problem running BLE, ANT+ and fstorage together. However, the SoftDevice need to be able to schedule flash operations (erase or write) between other events, as the CPU is blocked during that time. If you for example advertise with a high frequency, there SoftDevice may not be able to find time to do the flash operation.

[rc766437]

Hi, Einar Thorsrud, I have the same problem about FStorge.I use SDK13.1, S332-sd-V4.0.2.

my project is running BLE(central+peripheral),  ANT+ and fstorage together. 

If BLE(central+Peripheral) and ANT+ work together, storge data work normal, but when earse sector will occur the same problem,  even if the retries increase to 40, can't solve this problem；

If ANT+ closed, stroge and earse data will work normal.

Please tell me how to solve this problem.

[Einar Thorsrud]

Hi rc766437,

The problem is as I described in the original answer: If the SoftDevice is busy doing (too) many things, it may not be able to schedule any flash operations between the other events. If increasing the number of retries does not help, then the only way to fix this is do make sure there is less other SoftDevice activity so that it is possible for the SoftDevice to fit the flash operation in between the other events. To do this, use longer connection/advertising/scan events for BLE and/or ANT, or more extremely as you do: terminate a connection.