This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

S140/S132 flash operation scheduling timeout

Hello!

I'm working with both the s132 and s140 softdevices on their dedicated hardwares. We are heavily utilising the radio timeslot API to run our propriatery stack and are having issues with our flash operations interfering unpredictably with our timeslots (and the other way around).

In the S140 documentation it's written that the priority of a flash operation is increased (form 4th to 3rd) after being blocked consecutively for a few times. I would like to know more precisely when this happens.

The flash operation will also generate the event NRF_EVT_FLASH_OPERATION_ERROR if it can't schedule the operation at all after a given timeout. I would like to know how long this timeout is.

I would also know how long time we have left until the timeout after the flash operation priority is increased, since it won't preempt an already granted radio timeslot.

Our fear is that if we run radio timeslots with the 3rd priority (with roughly 95-99% duty cycle) it will block the scheduling of a flash operation until the escalation of it's priority. If our radio timeslots are longer than the time we have left until flash timeout the operation will fail. So I'd like to know how long I can make our radio timeslots to garantuee that this doens't happen.

Best regards,

Johannes

Parents Reply Children
Related