<?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>timer that pwm opens can not be closed</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12789/timer-that-pwm-opens-can-not-be-closed</link><description>Hi,all~ 
 I got a question about pwm&amp;#39;s timer. Here is my working environment: SDK 10.0, SD8.0, IC VERSION: qfabc0. 
 I use timer1 as clock of pwm. APP_PWM_INSTANCE(PWM1,1); 
When I run app_pwm_enable() ,the current goes to 3.6 mA. And then I run app_pwm_disable</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Oct 2016 10:56:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12789/timer-that-pwm-opens-can-not-be-closed" /><item><title>RE: timer that pwm opens can not be closed</title><link>https://devzone.nordicsemi.com/thread/48603?ContentTypeID=1</link><pubDate>Mon, 17 Oct 2016 10:56:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ed0dd766-b872-4ddf-b367-96c45ed20820</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;4.2 mA is too much for timer alone, this current indicates that the CPU is not going to sleep. You need to figure out why. It sounds like you are manipulating the registers while using the pwm library (app_pwm), this is not recommended as it will lead to undetermined behavior. Why can&amp;#39;t you use app_pwm_disable() or app_pwm_uninit()?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: timer that pwm opens can not be closed</title><link>https://devzone.nordicsemi.com/thread/48602?ContentTypeID=1</link><pubDate>Fri, 14 Oct 2016 10:49:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:39d77cc6-f6f6-4c8e-9b9b-a44c4fda646c</guid><dc:creator>dhawal94</dc:creator><description>&lt;p&gt;Hi, I am using sdk10 with softdevice enabled. My CPU is going into low power ON mode (~300uA) but after running NRF_TIMER1 for PWM application, the HFCLK seems to be left ON as the current goes to ~4.2mA and remains there.&lt;/p&gt;
&lt;p&gt;I have done deinit of PWM and also shutdown the timer writing 1 to timer register-&amp;gt;SHUTDOWN.&lt;/p&gt;
&lt;p&gt;What my guess is that once a peripheral starts the NRF_TIMER1 (which mostly accesses the PCLK1M/PCLK16M), the HFCLK is not getting shutdown and hence it consumes this much current. Any solutions to this ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: timer that pwm opens can not be closed</title><link>https://devzone.nordicsemi.com/thread/48600?ContentTypeID=1</link><pubDate>Wed, 30 Mar 2016 08:58:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cce0c216-2df8-4fdb-9230-4a0773b65a3c</guid><dc:creator>kk</dc:creator><description>&lt;p&gt;Sorry for interrupting folks, the unsual current comes from some of illegal motify of nrf_timer.h, after renewing my sdk environment the current go back to normal.&lt;/p&gt;
&lt;p&gt;Thank you very much&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: timer that pwm opens can not be closed</title><link>https://devzone.nordicsemi.com/thread/48601?ContentTypeID=1</link><pubDate>Tue, 29 Mar 2016 15:17:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b682f20a-40e0-4d50-8b5b-b87aed157e81</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;app_pwm_disable() turns off the pwm, app_pwm_uninit() calls app_pwm_disable and deallocates the resources (timer, gpiote channels, ppi channels).&lt;/p&gt;
&lt;p&gt;3.6mA does not sound like the CPU is on since this will require 4.1mA (running from flash) + HFCLK current, and it is too high for any other peripheral (other than the radio, for that it is too low). Are you sure the code is working and not running into some error condition and constantly resetting? Could you try to define DEBUG and see if the code stops executing? See &lt;a href="https://devzone.nordicsemi.com/question/60125/my-device-is-freezing-and-restarting/"&gt;this post&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: timer that pwm opens can not be closed</title><link>https://devzone.nordicsemi.com/thread/48598?ContentTypeID=1</link><pubDate>Mon, 28 Mar 2016 01:04:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c68b4951-c966-4a47-bbc6-71f91919230a</guid><dc:creator>kk</dc:creator><description>&lt;p&gt;I use 51822, &lt;code&gt;app_pwm_disable()&lt;/code&gt; contains the function of stopping timer &lt;code&gt;nrf_drv_timer_disable(p_instance-&amp;gt;p_timer);&lt;/code&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: timer that pwm opens can not be closed</title><link>https://devzone.nordicsemi.com/thread/48599?ContentTypeID=1</link><pubDate>Sat, 26 Mar 2016 18:41:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c23041d-d765-4a8b-9829-7b28db5831cf</guid><dc:creator>wlgrd</dc:creator><description>&lt;p&gt;What chip (51/52)? What does the pwm_disable actually do? It should be some function to uninit the pwm, since it sounds like the pwm disable only stops generating the pwm but leaves the timer running for faster resume when pwm output is needed&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>