<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FreeRTOS: Safe to block BLE task created in nrf_sdh_freertos.c?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/87470/freertos-safe-to-block-ble-task-created-in-nrf_sdh_freertos-c</link><description>Background: 
 
 Custom boards 
 SDK 15.2.0 
 SoftDevice: s140_nrf52_6.1.0 
 
 Hello, 
 We recently updated our project to use 2M PHY instead of the default 1M PHY. Our device implements over-the-air (OTA) firmware updates and writes the received firmware</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 May 2022 18:07:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/87470/freertos-safe-to-block-ble-task-created-in-nrf_sdh_freertos-c" /><item><title>RE: FreeRTOS: Safe to block BLE task created in nrf_sdh_freertos.c?</title><link>https://devzone.nordicsemi.com/thread/365841?ContentTypeID=1</link><pubDate>Mon, 02 May 2022 18:07:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e5f215f0-01c9-4d47-a3fb-8a0d26035832</guid><dc:creator>droberson</dc:creator><description>&lt;p&gt;Hey&amp;nbsp;&lt;span&gt;Torbj&amp;oslash;rn,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I have seen page erase take upwards of 150+ msec roughly, so I would be blocking for up to ~200 msec at a time. The alternative is to have a very large application RX queue but I am trying to avoid that if possible.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regarding:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;quot;At some point data throughput will suffer, as the SoftDevice will start NAKing new data once the internal buffers fill up, but it shouldn&amp;#39;t affect the reliability of the connection or the stack&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;This is the behavior I was hoping for as opposed to the SoftDevice / BLE task dropping packets.&amp;nbsp;NAK&amp;#39;ing packets&amp;nbsp;should be fine for my purposes for now so long as it only decreases throughput and doesn&amp;#39;t result in dropped packets.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FreeRTOS: Safe to block BLE task created in nrf_sdh_freertos.c?</title><link>https://devzone.nordicsemi.com/thread/365723?ContentTypeID=1</link><pubDate>Mon, 02 May 2022 10:30:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31f5bf8e-4e18-4737-a5aa-f931163cf941</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Derek&lt;/p&gt;
&lt;p&gt;How long of a block are you talking about here?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In general this should be fine. All the time critical SoftDevice operations are running from high priority interrupts, and it is OK for the application to delay the processing of SoftDevice events.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;At some point data throughput will suffer, as the SoftDevice will start NAKing new data once the internal buffers fill up, but it shouldn&amp;#39;t affect the reliability of the connection or the stack.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>