<?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: K70 Lockup Issue in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K70-Lockup-Issue/m-p/1238174#M59755</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Please check the community post below where a colleague states some lockup event causes.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/Kinetis-Microcontrollers/Please-let-me-know-when-Lockup-event-occurs/m-p/815371" target="_blank"&gt;Solved: Please let me know when Lockup event occurs - NXP Community&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Additionally, a colleague has a blog that explains how to debug hard faults so you can find the root cause easier.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://mcuoneclipse.com/2012/11/24/debugging-hard-faults-on-arm-cortex-m/" target="_blank"&gt; Debugging Hard Faults on ARM Cortex-M | MCU on Eclipse &lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Felipe&lt;/P&gt;</description>
    <pubDate>Mon, 01 Mar 2021 19:53:26 GMT</pubDate>
    <dc:creator>FelipeGarcia</dc:creator>
    <dc:date>2021-03-01T19:53:26Z</dc:date>
    <item>
      <title>K70 Lockup Issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K70-Lockup-Issue/m-p/1236094#M59739</link>
      <description>&lt;P&gt;We have a high percentage of systems in our production that are sporadically locking up during operation.&amp;nbsp;&amp;nbsp;Each system has a MK70FX512 &amp;nbsp;with DDR2 RAM&amp;nbsp;&amp;nbsp;communicating to an TFT-LCD screen with resistive touch capability. &amp;nbsp;&amp;nbsp;Some systems are utilizing the Micron&amp;nbsp;MT47H64M16:H/:M -25&amp;nbsp; or -25E &amp;nbsp;DDR2 RAM chip and others are using the Alliance&amp;nbsp;AS4C64M16D2A-25BCN &amp;nbsp;component.&amp;nbsp; &amp;nbsp;&amp;nbsp;We are using MQX 4.0, CodeWarrior 10.6.4,&amp;nbsp;Freescale eGUI/D4D 2.30,&amp;nbsp;and a PEmicro MultiLink Universal debug probe.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;We are seeing various lockup symptoms from the devices that fail.&amp;nbsp;&amp;nbsp; Some produce hard faults almost immediately after power up.&amp;nbsp; Some lockup and become unresponsive to touch or serial data and have LCD Screens that turn to a greenish hue, and others receive core lockup resets. &amp;nbsp;&amp;nbsp;&amp;nbsp;One of the units that has the LCD screen turn to a greenish hue quite often has gone through some additional testing and it has also been found that the lower 8 bits of 16 bit accesses to the DDR memory always return 00 when this occurs. Note, that lockup can occur after 2 and upto 12 minutes after power on.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;We have monitored the task stacks and interrupt stack and neither exceed 40% of their allotted space. When the system Locks up nothing is ever reported. We occasionally will get a BUS Fault that is&amp;nbsp;reported. We are unsure as to the cause of this too, but repowering the unit fixes this issue.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;We suspect a possible issue with the DDR2 Ram because we keep the LCD Frame buffer in this area.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;We have used the K70Memctrl program to create the ddr_setup routine.&lt;BR /&gt;Fixes have been applied to the DDR_CR values so that the values are now correct and/or in the correct location, as per K70P256M150SF3RM (Reference Manual) Rev. 4, 10/2015.&lt;BR /&gt;&amp;nbsp; &amp;nbsp;Corrected tCPD in DDR_CR10 (value was missing)&lt;BR /&gt;&amp;nbsp; &amp;nbsp;Corrected tREF in DDR_CR12 (value was smaller than entered)&lt;BR /&gt;&amp;nbsp; &amp;nbsp;Moved p2typ to DDR_CR44, moved qfull/fstwr/wrlatr to DDR_CR29.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any thoughts on this situation would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 20:28:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K70-Lockup-Issue/m-p/1236094#M59739</guid>
      <dc:creator>markdoxbeck</dc:creator>
      <dc:date>2021-02-24T20:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: K70 Lockup Issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/K70-Lockup-Issue/m-p/1238174#M59755</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Please check the community post below where a colleague states some lockup event causes.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/Kinetis-Microcontrollers/Please-let-me-know-when-Lockup-event-occurs/m-p/815371" target="_blank"&gt;Solved: Please let me know when Lockup event occurs - NXP Community&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Additionally, a colleague has a blog that explains how to debug hard faults so you can find the root cause easier.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://mcuoneclipse.com/2012/11/24/debugging-hard-faults-on-arm-cortex-m/" target="_blank"&gt; Debugging Hard Faults on ARM Cortex-M | MCU on Eclipse &lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Felipe&lt;/P&gt;</description>
      <pubDate>Mon, 01 Mar 2021 19:53:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/K70-Lockup-Issue/m-p/1238174#M59755</guid>
      <dc:creator>FelipeGarcia</dc:creator>
      <dc:date>2021-03-01T19:53:26Z</dc:date>
    </item>
  </channel>
</rss>

