<?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>ppi and softdevice</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/79462/ppi-and-softdevice</link><description>I&amp;#39;m evaluating the nRF52840_DK with nRF5_SDK_17.0.2 
 After doing some tests with ppi to timestamp gpio events, I&amp;#39;m now enabling the softdevice. 
 This leads to two questions; 
 
 1. I&amp;#39;m using nrfx_ppi rather than nrf_ppi, because I like to allocate ppi</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 13 Sep 2021 05:03:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/79462/ppi-and-softdevice" /><item><title>RE: ppi and softdevice</title><link>https://devzone.nordicsemi.com/thread/329123?ContentTypeID=1</link><pubDate>Mon, 13 Sep 2021 05:03:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db6b0916-ad9d-4ef3-a1d4-2fc51067cb28</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The only reason would be to&amp;nbsp;get an error if you try using the higher channels (20 and up),&amp;nbsp;but if you use nrfx_ppi with dynamic channel allocation this shouldn&amp;#39;t really happen anyway.&amp;nbsp;&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><item><title>RE: ppi and softdevice</title><link>https://devzone.nordicsemi.com/thread/329056?ContentTypeID=1</link><pubDate>Fri, 10 Sep 2021 13:35:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:507dbb1e-a710-427b-808c-cc8fcd273652</guid><dc:creator>pieterg</dc:creator><description>&lt;p&gt;Thanks for clearing that up, so there is no reason to use the sd_ppi_channel_* calls?&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll keep using nrfx_ppi then.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ppi and softdevice</title><link>https://devzone.nordicsemi.com/thread/328925?ContentTypeID=1</link><pubDate>Fri, 10 Sep 2021 07:13:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd8feec3-167c-412d-83d2-868478643ca7</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;To be honest I always assumed the nrf_drv_ppi driver would use SoftDevice calls under the hood, but I realize now this is not the case.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;That being said, the PPI peripheral is not protected by the SoftDevice, so there is really no reason to avoid using the nrfx_ppi driver together with the SoftDevice.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The SoftDevice will only use the static PPI channels (channel 20 and up), while all the configurable channels are available to the application.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In other words I would recommend just using the driver, whether or not the SoftDevice is enabed.&amp;nbsp;&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>