<?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>Setting up CC case using Timer 2</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96169/setting-up-cc-case-using-timer-2</link><description>Am I able to set up both a case where a GPIOTE event controls through PPI a Capture event on CC[2] of Timer 2&amp;#39;s value as well as when Timer 2 reaches its max value (overflows to = 0) it will activate a COMPARE event on CC[2] or will I need to use another</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 31 Jan 2023 08:37:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96169/setting-up-cc-case-using-timer-2" /><item><title>RE: Setting up CC case using Timer 2</title><link>https://devzone.nordicsemi.com/thread/407234?ContentTypeID=1</link><pubDate>Tue, 31 Jan 2023 08:37:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:73ed196a-a28b-4fb9-b334-fbaa263f3a46</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;The capture task triggered by the GPIOTE event via PPI will overwrite your initial CC[2] register value set on startup. So, if you want to keep getting the timer overflow event, you will have to assign&amp;nbsp;two separate capture/compare registers for this.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>