Fixing radio notification and flash write/erase conficts.

[Jordan Archer]

Is there a plan to fix this errata limitation from errata limitations documented on softdevice?

• If Radio Notifications are enabled, flash write and flash erase operations initiated through the SoftDevice API will be notified to the application as Radio Events (FORT-809).

Because of this limitation, if you are doing a fair amount of flash write/erase operations (not excessive), you can't tell when you've been interrupted for BLE operation, in critical operations such as ADC samples, in a very quiet rf environment. It could be a flash operation completing that was reported as an RF toggle. And worse yet, reported as a radio toggle event when it was, or wasn't.

I've captured this with some testing. And seen the recommended "toggle" method of tracking radio activity get out of sync, because a flash operations completed in the middle. So a toggle for radio start and then a radio stop is only reported as one event.

[Ole Bauck]

I meant do you get two radio notifications when doing a flash operation. If flash operation gives two radio notifications and no radio radio notifications is happening in between, then there will be no problem, only less time to do critical tasks. For example: flash start -> flash end -> radio start -> radio end will work fine, but radio start -> flash start -> flash end -> radio end will lead to time between radio start and radio end where the application thinks the radio is off. I will check with the developers if this is the case. I don't think timeslots should be affected by the flash operations, but need to check this also.