<?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>No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/1933/no-interrupts-on-nrf51822-w-s110</link><description>Hi, 
 Can I stop interrupts for 2ms in an orderly manner without crashing the S110? 
 Thanks,</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 03 Mar 2015 02:46:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/1933/no-interrupts-on-nrf51822-w-s110" /><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8298?ContentTypeID=1</link><pubDate>Tue, 03 Mar 2015 02:46:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7069c715-ffbf-413f-adc2-5be1dd0d1fbe</guid><dc:creator>Yokoyama, Atsushi</dc:creator><description>&lt;p&gt;Hello everyone.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m very new to nRF51 and S110, but I was facing to the same problem for a couple of days.  Do we have some progress in this topic?  Does any new version of S110 have workaround to this?&lt;/p&gt;
&lt;p&gt;FYI, the reason I needed a time critical control is a UART peer device requires odd-parity even though nRF51 supports only even-parity so I needed bit-banging.&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Atsushi&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8305?ContentTypeID=1</link><pubDate>Thu, 20 Mar 2014 15:33:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f8f8a959-b64b-46ba-8e7a-c4993676fce5</guid><dc:creator>Antonio</dc:creator><description>&lt;p&gt;Thank you Alex, thats a great workaround. And thank you Torbjørn for the information.&lt;/p&gt;
&lt;p&gt;I am testing Alex tip and it seems like a good workaround while you get the new SoftDevice out. If there is a way to test the beta of that version I am in :).&lt;/p&gt;
&lt;p&gt;Thanks again for the workaround and the later solution.&lt;/p&gt;
&lt;p&gt;Antonio.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8303?ContentTypeID=1</link><pubDate>Thu, 20 Mar 2014 09:36:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76251fc3-154f-46f6-bbfb-522c6da3fb9c</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;It should be ready in about a month or so. If you need something sooner you can try the good tip from Alex, and use the radio notification feature.&lt;/p&gt;
&lt;p&gt;Typically the SPI master can live with interrupts, as the master is in control of the data transfer. Will your slave time out if the delay between bytes is too large?&lt;/p&gt;
&lt;p&gt;We have many different plans for the future, unfortunately I can&amp;#39;t reveal specifics yet...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8304?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2014 22:15:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:08350b02-f190-4826-974e-63f24d5fc659</guid><dc:creator>Alex Shepherd</dc:creator><description>&lt;p&gt;Hi Antonio,&lt;/p&gt;
&lt;p&gt;Have a look here: &lt;a href="https://github.com/lavallc/nrf51-neopixel"&gt;github.com/.../nrf51-neopixel&lt;/a&gt; and look for &amp;quot;ble_radio_notification_init&amp;quot; as we had the same type of issue driving the WS2812B LEDs with some timing critical software.&lt;/p&gt;
&lt;p&gt;The solution in this case was to configure the BLE stack to notify the main loop every time it becomes not-active and then you&amp;#39;ve got several ms to quickly do your own processing before you need to hand processing time back to the BLE stack.&lt;/p&gt;
&lt;p&gt;HTH&lt;/p&gt;
&lt;p&gt;Alex Shepherd&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8302?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2014 18:55:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f883e6c-5843-4d4c-9156-5fdaeccaea1b</guid><dc:creator>Antonio</dc:creator><description>&lt;p&gt;Awesome, Torbjørn!!! :-)&lt;/p&gt;
&lt;p&gt;Do you have a time frame for this new version? Do you have an alpha or beta that I could test?&lt;/p&gt;
&lt;p&gt;btw, I have to do this because the Master SPI does not have DMA. Any plans in the future?&lt;/p&gt;
&lt;p&gt;Thanks, Antonio.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8301?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2014 15:44:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c463c23-eb0c-4290-908d-c29dc5f02e2e</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Antonio&lt;/p&gt;
&lt;p&gt;Yes, you can close down the S110 stack and do some processing before enabling it again, but any running connection with the master will be disconnected. In other words you will have to reconnect after you wake up again.&lt;/p&gt;
&lt;p&gt;How long it takes to enable the stack is a bit application specific (depending on how many services you configure and so forth), but we did some testing on the heart rate example showing the start up delay to be around 5ms.&lt;/p&gt;
&lt;p&gt;The good news is that we are working on a new SoftDevice API that would allow you to request time slots in which you are guaranteed not to be interrupted by the stack. With this feature you could simply ask for a time slot from the stack, and the stack would find a free time slot in between any scheduled BLE events. Then you could run 2ms of blocking code without having to worry about issues, and without having to disable the stack and break existing connections.&lt;/p&gt;
&lt;p&gt;Regards
Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8300?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2014 14:16:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50ab48c7-5270-445c-8db8-d3d0fa762fc2</guid><dc:creator>Antonio</dc:creator><description>&lt;p&gt;Hi Torbjørn,&lt;/p&gt;
&lt;p&gt;Thank you for your prompt response.&lt;/p&gt;
&lt;p&gt;Maybe I would be twisting things by trying this out but, if it is a slave, could I quickly close the S110, or any other state that would be safe,  and init it again after those 2ms?
If this is posible, how long would this stop/start procedure take?&lt;/p&gt;
&lt;p&gt;Thanks again,&lt;/p&gt;
&lt;p&gt;Antonio.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: No Interrupts on nRF51822 w/S110</title><link>https://devzone.nordicsemi.com/thread/8299?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2014 13:59:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:faf73c66-225d-48eb-a7a8-7353fdfb2e26</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Antonio&lt;/p&gt;
&lt;p&gt;Unfortunately the SoftDevice was designed under the assumption that it would always have the highest interrupt priority, which means that critical SoftDevice events should never be interrupted.&lt;/p&gt;
&lt;p&gt;I can tell you with 100% certainty that if the SoftDevice was interrupted for as much as 2ms it would break sooner or later..&lt;/p&gt;
&lt;p&gt;Regards
Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>