https://devzone.nordicsemi.com/f/nordic-q-a/48491/s140-s132-flash-operation-scheduling-timeoutHello! I&#39;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 ouren-USTelligent Community 13Thu, 13 Jun 2019 08:45:21 GMThttps://devzone.nordicsemi.com/thread/192588?ContentTypeID=1Thu, 13 Jun 2019 08:45:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e8235ce3-6d54-4836-82d4-144bc0eb7bf5Johannes<p>Thank you very much!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/192586?ContentTypeID=1Thu, 13 Jun 2019 08:44:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b9d974d7-7801-46a3-8fd2-0085484ad937Amanda Hsieh<p>Hi,&nbsp;</p> <p></p> <p>It&#39;s time-based, the priority increases after 30 ms.</p> <p></p> <p>-Amanda</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/192550?ContentTypeID=1Thu, 13 Jun 2019 06:47:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:191f9a73-c087-48fd-9cae-54bc0d56737eJohannes<p>Great! Thank you.<br /><br />How about when the flash operation priority increases? Is it based on numbers of scheduling attempts or is it time based?</p> <p>Best regards,</p> <p>Johannes</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/192538?ContentTypeID=1Thu, 13 Jun 2019 05:48:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4da4a2cc-e813-4ac2-a015-2b393b91b26dAmanda Hsieh<p>Hi,&nbsp;</p> <p></p> <p>It refers to the fact that high duty cycle directed advertising shall not last more than 1.28 s (it&#39;s defined in the spec).</p> <p>I have checked with the softdevice team that the Flash API timeout is 810ms.</p> <p></p> <p>-Amanda</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/192391?ContentTypeID=1Wed, 12 Jun 2019 13:02:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:35195c27-cd5d-40de-94de-2125c8ebaeb7Johannes<p>Hello Amanda and thank you for your answer.<br /><br />I&#39;ve read that section and it only mentions the existence of the timeout, and probability of success when running BLE. We aren&#39;t running BLE at all, only our own stack.<br /><br />If I would guess I&#39;d say that the timeout is 1.28s given the first row in the table. Is this correct?</p> <p>Best regards,</p> <p>Johannes</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/192380?ContentTypeID=1Wed, 12 Jun 2019 12:52:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:61a62d8d-baea-4eeb-bc9e-b2403a359155Amanda Hsieh<p>Hi,&nbsp;</p> <p></p> <p><span>Please refer to the&nbsp;</span><a href="https://infocenter.nordicsemi.com/topic/sds_s140/SDS/s1xx/flash_mem_api/flash_mem_api.html#flash_mem_api__table_mtd_h2t_cs">Behavior with Bluetooth Low Energy traffic and concurrent flash write/erase</a><span>&nbsp;for the time-out.&nbsp;</span></p> <p><span></span></p> <p><span>Best regards,</span></p> <p><span>Amanda</span></p><div style="clear:both;"></div>