<?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>softdevice process timing</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11679/softdevice-process-timing</link><description>Hi, all. I use nrf52 and softdevice(S132). 
 I&amp;#39;d like to know SoftDevice process timing to hardware.
Can it be ? 
 
 I know, SoftDevice Specification in &amp;quot;Processor availability and interrupt latency&amp;quot; but fixd parametor only. 
 I want any parametor</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 03 Feb 2016 01:21:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11679/softdevice-process-timing" /><item><title>RE: softdevice process timing</title><link>https://devzone.nordicsemi.com/thread/44152?ContentTypeID=1</link><pubDate>Wed, 03 Feb 2016 01:21:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2e90b3ac-bd41-4c06-8606-95fbd5157e25</guid><dc:creator>chiba</dc:creator><description>&lt;p&gt;Hi Kenneth
Thanks, nice idea!&lt;/p&gt;
&lt;p&gt;Try it&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/pic_5F00_x2.png" alt="image description" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softdevice process timing</title><link>https://devzone.nordicsemi.com/thread/44151?ContentTypeID=1</link><pubDate>Tue, 02 Feb 2016 16:34:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:493c3edc-5203-46a2-a8ca-802dd358ba58</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi, I see no easy way to do this, as there might be stack interrupts caused by both radio, and pre- and post-processing. My suggestion is to make a simplified application that emulate the data throughput you are aiming for, and then in main () you have a while loop that continuously toggle an GPIO. That way you can monitor when the GPIO doesn&amp;#39;t toggle, and based on that asses the actual interrupt latency for your application by the softdevice stack.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>