<?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: flash clock causes hard fault in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/flash-clock-causes-hard-fault/m-p/297441#M12293</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Venkata&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the Flash clock is too high Flash reads are unreliable and the code will tend to fail (immediately).&lt;/P&gt;&lt;P&gt;Are you sure of the clock speed that you are setting since it should work reliably up to 25MHz - &lt;EM&gt;the bus clock speed should however not be set lower than the Flash clock speed&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;I recommend setting the Flash clock to a lower speed that works and then let the SW verify the system clock speed (eg. switch a clock to the CLOCKOUT pin so that it ca be measured, or use a timer interrupt that is running from a defined clock to verify that it is as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen similar problems where the system clock was mistakenly set up too high (thinking that it was 100MHz for example when it was really 200MHz) and so the Flash clock rate was also too high. It tends to be the Flash that fails first in this case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 May 2014 12:50:37 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2014-05-14T12:50:37Z</dc:date>
    <item>
      <title>flash clock causes hard fault</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/flash-clock-causes-hard-fault/m-p/297439#M12291</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;120MHz, K21 controller causes hard fault if I set flash clock between 20 to 24MHz, it is fine for Below 20MHz, I am using external (12MHz) crystal with PEE mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I could not corner the issue, please help!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;tvc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2014 10:58:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/flash-clock-causes-hard-fault/m-p/297439#M12291</guid>
      <dc:creator>venkatachalapat</dc:creator>
      <dc:date>2014-05-14T10:58:50Z</dc:date>
    </item>
    <item>
      <title>Re: flash clock causes hard fault</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/flash-clock-causes-hard-fault/m-p/297440#M12292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your post, however please consider moving it to the right community place (e.g. &lt;A _jive_internal="true" class="jivecontainerTT-hover-container jive-link-community-small" data-containerid="1" data-containertype="14" data-objectid="2019" data-objecttype="14" href="https://community.nxp.com/community/kinetis"&gt; Kinetis Microcontrollers&lt;/A&gt;) to get it visible for active members.&lt;/P&gt;&lt;P&gt;For details please see general advice &lt;A _jive_internal="true" data-containerid="2001" data-containertype="14" data-objectid="99909" data-objecttype="102" href="https://community.nxp.com/docs/DOC-99909"&gt;Where to post a Discussion?&lt;/A&gt; ( &lt;A _jive_internal="true" data-containerid="2001" data-containertype="14" data-objectid="99909" data-objecttype="102" href="https://community.nxp.com/docs/DOC-99909"&gt;https://community.freescale.com/docs/DOC-99909&lt;/A&gt;&amp;nbsp;&amp;nbsp; )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for using Freescale Community.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2014 11:46:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/flash-clock-causes-hard-fault/m-p/297440#M12292</guid>
      <dc:creator>Wlodek_D_</dc:creator>
      <dc:date>2014-05-14T11:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: flash clock causes hard fault</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/flash-clock-causes-hard-fault/m-p/297441#M12293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Venkata&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the Flash clock is too high Flash reads are unreliable and the code will tend to fail (immediately).&lt;/P&gt;&lt;P&gt;Are you sure of the clock speed that you are setting since it should work reliably up to 25MHz - &lt;EM&gt;the bus clock speed should however not be set lower than the Flash clock speed&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;I recommend setting the Flash clock to a lower speed that works and then let the SW verify the system clock speed (eg. switch a clock to the CLOCKOUT pin so that it ca be measured, or use a timer interrupt that is running from a defined clock to verify that it is as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen similar problems where the system clock was mistakenly set up too high (thinking that it was 100MHz for example when it was really 200MHz) and so the Flash clock rate was also too high. It tends to be the Flash that fails first in this case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2014 12:50:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/flash-clock-causes-hard-fault/m-p/297441#M12293</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2014-05-14T12:50:37Z</dc:date>
    </item>
  </channel>
</rss>

