<?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>ColdFire/68K Microcontrollers and ProcessorsのトピックRe: MCF51QE high internal reference clock</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51QE-high-internal-reference-clock/m-p/603200#M12962</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Software or hardware debugger? When the hardware debugger is connected, it uses a default trim value of 0x80.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When running without the debugger, it loads from the Flash IFR which is documented as being at 0x3ff, but is also documented as being UNREADABLE from the debugger or from user code. The only way to find what value is written in there is to have the chip run standalone and then print what got loaded into ICSTRM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Search this forum for "IFT TRIM" and other keywords. This one might be useful as it details (amongst other things) how some programming tools have to be set up to change (or not change) the stored values:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-comment-small" href="https://community.nxp.com/thread/78612?commentID=78618#comment-78618"&gt;https://community.nxp.com/message/78618?commentID=78618#comment-78618&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can always reload ICSTRM with values from some other NV storage in your product if that is more convenient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Oct 2016 00:49:14 GMT</pubDate>
    <dc:creator>TomE</dc:creator>
    <dc:date>2016-10-04T00:49:14Z</dc:date>
    <item>
      <title>MCF51QE high internal reference clock</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51QE-high-internal-reference-clock/m-p/603199#M12961</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;I recently started working with a product incorporating the MCF51QE128. According to the data sheet the typical value for the internal reference clock is 32.768 kHz. However, when I try to verify this by measuring on GPIO toggled by a TPM interrupt the derived clock appears to be 38.4 kHz. The trim value is loaded from flash address 0x03FF (0x0061). Other settings are:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DRS = 00&lt;/P&gt;&lt;P&gt;DMX32 = 0&lt;/P&gt;&lt;P&gt;BDIV = 0&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The debugger outputs "Bus Freq = 9837KHz" which also points to 38.4 kHz reference clock.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is the trim value wrong? Or am I missing something else?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Johan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Oct 2016 20:00:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51QE-high-internal-reference-clock/m-p/603199#M12961</guid>
      <dc:creator>johanbolin</dc:creator>
      <dc:date>2016-10-03T20:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: MCF51QE high internal reference clock</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51QE-high-internal-reference-clock/m-p/603200#M12962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Software or hardware debugger? When the hardware debugger is connected, it uses a default trim value of 0x80.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When running without the debugger, it loads from the Flash IFR which is documented as being at 0x3ff, but is also documented as being UNREADABLE from the debugger or from user code. The only way to find what value is written in there is to have the chip run standalone and then print what got loaded into ICSTRM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Search this forum for "IFT TRIM" and other keywords. This one might be useful as it details (amongst other things) how some programming tools have to be set up to change (or not change) the stored values:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-comment-small" href="https://community.nxp.com/thread/78612?commentID=78618#comment-78618"&gt;https://community.nxp.com/message/78618?commentID=78618#comment-78618&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can always reload ICSTRM with values from some other NV storage in your product if that is more convenient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Oct 2016 00:49:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51QE-high-internal-reference-clock/m-p/603200#M12962</guid>
      <dc:creator>TomE</dc:creator>
      <dc:date>2016-10-04T00:49:14Z</dc:date>
    </item>
  </channel>
</rss>

