<?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>Changing on_ble_evt interrupt priority</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24854/changing-on_ble_evt-interrupt-priority</link><description>Working with: examples/ble_peripheral/ble_app_uart . I would like to change on_ble_evt priority level so that UART IRQ handler has lower priority then softdevice event dispatching routine. 
 So far I checked that there are following IRQ priority levels</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 06 Sep 2017 13:12:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24854/changing-on_ble_evt-interrupt-priority" /><item><title>RE: Changing on_ble_evt interrupt priority</title><link>https://devzone.nordicsemi.com/thread/97880?ContentTypeID=1</link><pubDate>Wed, 06 Sep 2017 13:12:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7569ab74-35d8-4db6-b9e6-f708092f9865</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;You don&amp;#39;t have to call app_uart_get(..) right away, even if you get the DATA_READY interrupt. You can simply ignore it, and wait for the NUS to finish before reading out the next byte. Assuming you have enough buffer space available to store the incoming data you will not lose any bytes.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Changing on_ble_evt interrupt priority</title><link>https://devzone.nordicsemi.com/thread/97879?ContentTypeID=1</link><pubDate>Mon, 04 Sep 2017 13:29:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1ec8dcaa-f492-4542-8e47-bd6a73428ba4</guid><dc:creator>pbn4</dc:creator><description>&lt;p&gt;It does not solve my problem anyway, how can I stall UART RX? Let&amp;#39;s assume I wait for &amp;#39;\n&amp;#39;. I want to stop receiving (but not start droping data) and wait for &lt;code&gt;on_ble_evt&lt;/code&gt; call to resume UART RX. Ideally UART would use flow control to stop the communication with some host and wait for softdevice event to enable it again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Changing on_ble_evt interrupt priority</title><link>https://devzone.nordicsemi.com/thread/97878?ContentTypeID=1</link><pubDate>Fri, 01 Sep 2017 14:17:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1aacae2b-2705-4ed2-99b8-1eb6e59dcf18</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;After you have enabled the stack it should be possible to change the priority of the BLE events like this:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;NVIC_SetPriority(SD_EVT_IRQn, 7);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Please be aware that you should only use interrupt priorities allocated to the application, and using an interrupt priority higher than the SVC handler doesn&amp;#39;t really make sense (since it means you can&amp;#39;t call SoftDevice functions inside the event handler), so the only recommended options are 6 and 7.&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;
Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>