<?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>Issues with using Timer1 in counter mode after SDK migration.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/11417/issues-with-using-timer1-in-counter-mode-after-sdk-migration</link><description>Hi! 
 I have inherited a large codebase that I&amp;#39;m trying to migrate to SDKv10 from SDKv6. 
 The project also uses an A4960 BLDC motor controller. To bring the motor up to speed, we count the number of rising edges on the TACHO pin of the controller,</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 22 Jan 2016 14:23:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/11417/issues-with-using-timer1-in-counter-mode-after-sdk-migration" /><item><title>RE: Issues with using Timer1 in counter mode after SDK migration.</title><link>https://devzone.nordicsemi.com/thread/43056?ContentTypeID=1</link><pubDate>Fri, 22 Jan 2016 14:23:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3cd89700-008d-4793-a80b-732728cd4c5d</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi,
TIMER1 does not support 32 bit mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issues with using Timer1 in counter mode after SDK migration.</title><link>https://devzone.nordicsemi.com/thread/43054?ContentTypeID=1</link><pubDate>Wed, 20 Jan 2016 15:40:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:99e1d8cf-1540-41ad-bb8e-7caafc8edab9</guid><dc:creator>Sebastian Claici</dc:creator><description>&lt;p&gt;Thanks. I&amp;#39;ll check the PPI registers, and maybe hook up a oscilloscope to the pin to see if it&amp;#39;s actually toggling.&lt;/p&gt;
&lt;p&gt;Good to know that the code still looks sane.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issues with using Timer1 in counter mode after SDK migration.</title><link>https://devzone.nordicsemi.com/thread/43055?ContentTypeID=1</link><pubDate>Wed, 20 Jan 2016 00:23:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5fcc737a-82f5-46b8-b9eb-4a63fe22558c</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Don&amp;#39;t see anything which wouldn&amp;#39;t work. Couple of general points, TIMER1 isn&amp;#39;t 32 bit, it&amp;#39;s max 16 bit, but it should still count.
If you&amp;#39;re moving to a more recent softdevice, the PPI peripheral is no-longer restricted, so no need for the sd_enabled check, you can just set up the PPI directly saving the softdevice overhead.&lt;/p&gt;
&lt;p&gt;I&amp;#39;d enable the GPIOTE interrupt and ensure that event is being correctly triggered by breaking in the handler and check the PPI registers at that point to make sure the channel you&amp;#39;re using is still set up and enabled.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>