<?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>How different is timeslot management in nrf52840 than in nrf51422?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22691/how-different-is-timeslot-management-in-nrf52840-than-in-nrf51422</link><description>Hello, I understand this may be a very broad question, but I still need to find as much information as I can. 
 Give a general answer if you&amp;#39;d like to, or a very specific one if you are so inclined. 
 To help narrow down this topic a bit and give you</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Jun 2017 08:55:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22691/how-different-is-timeslot-management-in-nrf52840-than-in-nrf51422" /><item><title>RE: How different is timeslot management in nrf52840 than in nrf51422?</title><link>https://devzone.nordicsemi.com/thread/89211?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 08:55:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f27cb9c7-fe3c-4237-a1c9-33c7fe67787f</guid><dc:creator>J&amp;#248;rn</dc:creator><description>&lt;p&gt;Hello Mitch996&lt;/p&gt;
&lt;p&gt;As endnode stated the overall API should be the same for S130 and S132. There might have been some changes to the inner workings of how the Softdevice handles the scheduling but it should not be visible from a user perspective.&lt;/p&gt;
&lt;p&gt;As for the chip-side of things, the nRF52 has a faster HFCLK than the nRF51, meaning you can potentially get more work done with the same timeslot duration. The duration of interrupts leading into and out from timeslots are a bit faster on the nRF52 than on the nRF51, see &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.sds%2Fdita%2Fsoftdevices%2Fs130%2Fprocessor_avail_interrupt_latency%2Ftsl_usage_patterns.html&amp;amp;cp=2_4_0_0_15_2_1"&gt;here&lt;/a&gt; and &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s130.sds%2Fdita%2Fsoftdevices%2Fs130%2Fprocessor_avail_interrupt_latency%2Ftsl_usage_patterns.html&amp;amp;cp=3_7_2_0_15_2_1"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Not strictly related to timeslots but the nRF52 has more interrupt priority levels than the nRF51. Priority level 0, 1 and 4 in the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/processor_avail_interrupt_latency/exception_mgmt_sd.html?cp=2_4_0_0_15_1"&gt;nRF52&lt;/a&gt; is reserved by the Softdevice, while for the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.sds/dita/softdevices/s130/processor_avail_interrupt_latency/exception_mgmt_sd.html?cp=3_7_2_0_15_1"&gt;nRF51&lt;/a&gt; only 0 and 2 are reserved. This could be worth considering when porting from the nRF51 to 52.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Jørn Frøysa&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How different is timeslot management in nrf52840 than in nrf51422?</title><link>https://devzone.nordicsemi.com/thread/89210?ContentTypeID=1</link><pubDate>Sun, 11 Jun 2017 09:48:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47d3c4b3-bb2d-4223-8da1-72820e4b8bff</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Isn&amp;#39;t this more matter of Soft Device then chip family? Considering S140 being pretty much straight port of S132 and that being based on S130 I believe there shouldn&amp;#39;t be many differences. API looks the same in both SDKs (by looking to SDK v12.3.0 and SDK v13.0.0), doesn&amp;#39;t it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>