<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Can not get KL27 current draw down to expected values (in VLPS mode). in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349094#M17096</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;At this point I should probably add that I have tomb-stoned the zero ohm resistors R23 and R22 on my FRDM-KL27Z board.&amp;nbsp; Apparently the complete FRDM-KL27Z schematic is hard to come by.&amp;nbsp; But according to what I am seeing these needed to be disconnected to prevent the accelerometer chip and the KL27 processor pin PTC3 (CLKOUTA) from back driving each other.&amp;nbsp; Who knows, maybe there's still something hanging off pin 46 of the KL27 processor that we don't know about.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Mar 2015 21:21:36 GMT</pubDate>
    <dc:creator>rickstuart</dc:creator>
    <dc:date>2015-03-25T21:21:36Z</dc:date>
    <item>
      <title>Can not get KL27 current draw down to expected values (in VLPS mode).</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349091#M17093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am messing with various KL27 low current modes on the Freescale FRDM-KL27Z development board.&amp;nbsp; Right now I want to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Turn off the 48MHz clock.&lt;/P&gt;&lt;P&gt;2. Turn on the 2MHz clock.&lt;/P&gt;&lt;P&gt;3. Route the 2MHz clock to TPM0 timer.&lt;/P&gt;&lt;P&gt;4. Enter VLPS mode.&lt;/P&gt;&lt;P&gt;5. Draw 100uA or less (really was expecting less than half that).&lt;/P&gt;&lt;P&gt;6. Get woken up by the TPM0 timer interrupt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, step 5 is drawing 187uA!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Note, the processor is waking up about every 3 seconds, flashes the RGB LED on the FRDM-KL27Z development board then goes back to VLPS mode.&amp;nbsp; So the program is doing what I want.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The current value for the 2MHz clock can be found in Freescale document KL27P64M48SF2.pdf.&amp;nbsp; There in table 10 it states the typical value is 25uA for turning on the 2MHz clock.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now here is what I don't understand:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I turn off the 2MHz internal reference clock the current drops by about 181uA!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To do this, I change this line of code:&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;MCG-&amp;gt;C1 |= MCG_C1_IRCLKEN_MASK;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;// LIRC is enabled.&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To this:&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;///&lt;/TD&gt;&lt;TD&gt;MCG-&amp;gt;C1 |= MCG_C1_IRCLKEN_MASK;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;TD&gt;// LIRC is enabled.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now the TPM0 interrupt does not occur (no surprise there) and the current draw while in VLPS mode is down from 181uA to 5.2uA!&amp;nbsp; Way more than what I expected based on the 25uA allotment in the Freescale KL27P64M48SF2.pdf document.&amp;nbsp; I suspect there is something else running off the LIRC (8MHz/2MHz) clock that I don't see or need.&amp;nbsp; But I haven't found the culprit - if there is one.&amp;nbsp; Does anyone have any candidates I could chase down?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2015 15:12:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349091#M17093</guid>
      <dc:creator>rickstuart</dc:creator>
      <dc:date>2015-03-25T15:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: Can not get KL27 current draw down to expected values (in VLPS mode).</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349092#M17094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is interesting.&amp;nbsp; During testing at a different clock rate (48MHz) involving no low power mode, I noticed that the processor current demand had nearly doubled from previous tests.&amp;nbsp; The only code difference added the ability to monitor the processor clock on an external pin.&amp;nbsp; Essentially, adding this clock monitoring pin cost us about 4mA taking us from about 4 to about 8mA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the thinking was to remove the clock monitoring pin and re-test processor current demand for the VLPS mode with a 2MHz clock connected to TPM0 to create timed wake up interrupts.&amp;nbsp; That fix it!&amp;nbsp; The processor current demand while in VLPS w/the above configuration dropped from 187uA to 19.2uA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Driving the clock monitoring pin took an unexpected amount of current.&amp;nbsp; If anyone can explain why it would be a great way to sum up this thread.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2015 19:05:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349092#M17094</guid>
      <dc:creator>rickstuart</dc:creator>
      <dc:date>2015-03-25T19:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Can not get KL27 current draw down to expected values (in VLPS mode).</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349093#M17095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Sounds abnormally high, I will look into this and see what comes up, thanks for the heads up!!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2015 19:44:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349093#M17095</guid>
      <dc:creator>apanecatl</dc:creator>
      <dc:date>2015-03-25T19:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: Can not get KL27 current draw down to expected values (in VLPS mode).</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349094#M17096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;At this point I should probably add that I have tomb-stoned the zero ohm resistors R23 and R22 on my FRDM-KL27Z board.&amp;nbsp; Apparently the complete FRDM-KL27Z schematic is hard to come by.&amp;nbsp; But according to what I am seeing these needed to be disconnected to prevent the accelerometer chip and the KL27 processor pin PTC3 (CLKOUTA) from back driving each other.&amp;nbsp; Who knows, maybe there's still something hanging off pin 46 of the KL27 processor that we don't know about.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2015 21:21:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349094#M17096</guid>
      <dc:creator>rickstuart</dc:creator>
      <dc:date>2015-03-25T21:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: Re: Can not get KL27 current draw down to expected values (in VLPS mode).</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349095#M17097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We found that the scope probes were (significantly) contributing to the processor current demand.&amp;nbsp; The new values are not as dramatic as before:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="0" jive-data-cell="{&amp;quot;color&amp;quot;:&amp;quot;#575757&amp;quot;,&amp;quot;textAlign&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;padding&amp;quot;:&amp;quot;NaN&amp;quot;,&amp;quot;backgroundColor&amp;quot;:&amp;quot;transparent&amp;quot;,&amp;quot;fontFamily&amp;quot;:&amp;quot;arial,helvetica,sans-serif&amp;quot;,&amp;quot;verticalAlign&amp;quot;:&amp;quot;baseline&amp;quot;}" jive-data-header="{&amp;quot;color&amp;quot;:&amp;quot;#FFFFFF&amp;quot;,&amp;quot;backgroundColor&amp;quot;:&amp;quot;#6690BC&amp;quot;,&amp;quot;textAlign&amp;quot;:&amp;quot;center&amp;quot;,&amp;quot;padding&amp;quot;:&amp;quot;2&amp;quot;}" style="width: 384px;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="3" height="20" width="192"&gt;Processor Current Demands:&lt;/TD&gt;&lt;TD width="64"&gt;&lt;/TD&gt;&lt;TD width="64"&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;&lt;/TD&gt;&lt;TD colspan="2"&gt;w/scope probe&lt;/TD&gt;&lt;TD colspan="2"&gt;w/o scope probe&lt;/TD&gt;&lt;TD&gt;clock switch off from inside KL27 processor&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;48MHz&lt;/TD&gt;&lt;TD&gt;8.2mA&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;5.88mA&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;3.85mA&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;8MHz&lt;/TD&gt;&lt;TD&gt;698uA&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;394uA&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;107.1uA&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;2MHz&lt;/TD&gt;&lt;TD&gt;187uA&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;108uA&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;18uA&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data collected across different frequencies used different low power modes.&amp;nbsp; So going up and down the table is not suggested.&amp;nbsp; However, the power modes were consistent when moving across the table.&amp;nbsp; So the relation of processor current demand verses test configuration should be (is assumed to be) good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, while the values are a bit more palatable, the question remains if the change in processor current demand is with in the expected limits for driving an external pin with the processor clock?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2015 14:58:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Can-not-get-KL27-current-draw-down-to-expected-values-in-VLPS/m-p/349095#M17097</guid>
      <dc:creator>rickstuart</dc:creator>
      <dc:date>2015-03-26T14:58:44Z</dc:date>
    </item>
  </channel>
</rss>

