<?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: K10 temperature sensor delay in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K10-temperature-sensor-delay/m-p/559739#M33808</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We could certainly look at your firmware for this function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've not known of any cause for 'delay in operability'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume you have read my treatise on the subject:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/390524"&gt;On-chip temperature Calculations&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You say 'other values given by ADC are correct', then I can assume there are 'some other' absolute-voltages coming in that give the 'right answer' from the get-go?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Aug 2016 17:00:55 GMT</pubDate>
    <dc:creator>egoodii</dc:creator>
    <dc:date>2016-08-25T17:00:55Z</dc:date>
    <item>
      <title>K10 temperature sensor delay</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K10-temperature-sensor-delay/m-p/559738#M33807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have designed somes boards including Kinetis K10 72MHz MCUs (64 &amp;amp; 100 pins).&lt;/P&gt;&lt;P&gt;ADCs are referenced with an external 0.1% 2.5V.&lt;/P&gt;&lt;P&gt;We are using the embedded temperature sensor by applying the conversion equation given in the reference manual.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is, if in "steady state" the calculated temperature is correct (we don't need a high accuracy on this measure), the time required after the boot before having a valid value is almost 20 to 25 seconds. During this period, the equivalent temperature given by the microcontroller is about 12°C (for an ambiant of 20-30°C), and all other values given by ADCs are correct. &lt;/P&gt;&lt;P&gt;We certainly missed something in our software configuration, but we can't find the error. Can somebody help us on this point?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance for your help,&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2016 13:26:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K10-temperature-sensor-delay/m-p/559738#M33807</guid>
      <dc:creator>bgra</dc:creator>
      <dc:date>2016-08-25T13:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: K10 temperature sensor delay</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K10-temperature-sensor-delay/m-p/559739#M33808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We could certainly look at your firmware for this function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've not known of any cause for 'delay in operability'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume you have read my treatise on the subject:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/390524"&gt;On-chip temperature Calculations&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You say 'other values given by ADC are correct', then I can assume there are 'some other' absolute-voltages coming in that give the 'right answer' from the get-go?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2016 17:00:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K10-temperature-sensor-delay/m-p/559739#M33808</guid>
      <dc:creator>egoodii</dc:creator>
      <dc:date>2016-08-25T17:00:55Z</dc:date>
    </item>
  </channel>
</rss>

