<?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 QCVS-DDRV passed but Linux kernel crash ? in P-Series</title>
    <link>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714958#M4298</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;My board has P2020 with 1GByte&amp;nbsp;discrete ddr3 (4 sdrams* 128Mx16). We now have 30 boards of which 3 show unstable behaviour: uboot ok&amp;nbsp;but&amp;nbsp;linux&amp;nbsp;crashes due to kernel oops (bus-, paging-, segmentation- errors) indicating unstable instruction fetches from ddr3.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;With&amp;nbsp;Codewarrior-tap&amp;nbsp;I ran DDRValidation tool on these 3 boards and all 3 are&amp;nbsp;validated ok:&amp;nbsp; ddr operational testing of full 1GByte does not show errors.&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp; However, running linux from ddr3&amp;nbsp;is unstable ? &amp;nbsp;&lt;BR /&gt;P2020 DDR data rate = 666.66 Mbps (ddrclkin=66,666 Mhz*10)&amp;nbsp; &amp;gt;&amp;gt; ddr_mck = 333.33 Mhz&lt;BR /&gt;On one board I changed this to&amp;nbsp; 600 Mbps datarate (ddrclkin=100M*6) &amp;gt;&amp;gt; ddr_mck = 300 Mhz but stays unstable.&lt;/P&gt;&lt;P&gt;Could it be that some ddr3-sdram configuration parameter is causing trouble if&amp;nbsp;fast consecutive burst accesses (linux, dual core) ,&amp;nbsp;while cw-tap-ddrv access is less stringent ?&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Sep 2017 12:43:19 GMT</pubDate>
    <dc:creator>stefanvranken</dc:creator>
    <dc:date>2017-09-04T12:43:19Z</dc:date>
    <item>
      <title>QCVS-DDRV passed but Linux kernel crash ?</title>
      <link>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714958#M4298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;My board has P2020 with 1GByte&amp;nbsp;discrete ddr3 (4 sdrams* 128Mx16). We now have 30 boards of which 3 show unstable behaviour: uboot ok&amp;nbsp;but&amp;nbsp;linux&amp;nbsp;crashes due to kernel oops (bus-, paging-, segmentation- errors) indicating unstable instruction fetches from ddr3.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;With&amp;nbsp;Codewarrior-tap&amp;nbsp;I ran DDRValidation tool on these 3 boards and all 3 are&amp;nbsp;validated ok:&amp;nbsp; ddr operational testing of full 1GByte does not show errors.&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp; However, running linux from ddr3&amp;nbsp;is unstable ? &amp;nbsp;&lt;BR /&gt;P2020 DDR data rate = 666.66 Mbps (ddrclkin=66,666 Mhz*10)&amp;nbsp; &amp;gt;&amp;gt; ddr_mck = 333.33 Mhz&lt;BR /&gt;On one board I changed this to&amp;nbsp; 600 Mbps datarate (ddrclkin=100M*6) &amp;gt;&amp;gt; ddr_mck = 300 Mhz but stays unstable.&lt;/P&gt;&lt;P&gt;Could it be that some ddr3-sdram configuration parameter is causing trouble if&amp;nbsp;fast consecutive burst accesses (linux, dual core) ,&amp;nbsp;while cw-tap-ddrv access is less stringent ?&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Sep 2017 12:43:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714958#M4298</guid>
      <dc:creator>stefanvranken</dc:creator>
      <dc:date>2017-09-04T12:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: QCVS-DDRV passed but Linux kernel crash ?</title>
      <link>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714959#M4299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It will be more convenient if you create a Technical Case to investigate the issue:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://community.freescale.com/thread/381898" title="https://community.freescale.com/thread/381898"&gt;https://community.freescale.com/thread/381898&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Oct 2017 14:28:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714959#M4299</guid>
      <dc:creator>ufedor</dc:creator>
      <dc:date>2017-10-12T14:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: QCVS-DDRV passed but Linux kernel crash ?</title>
      <link>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714960#M4300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Case 00139557&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Nov 2017 10:18:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714960#M4300</guid>
      <dc:creator>stefanvranken</dc:creator>
      <dc:date>2017-11-03T10:18:56Z</dc:date>
    </item>
    <item>
      <title>Re: QCVS-DDRV passed but Linux kernel crash ?</title>
      <link>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714961#M4301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;In the mean time I have discovered one ddr-controller-parameter that can make my unstable protos good.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;This new setting is now under test on all prototypes but this is definitely a better ddr-controller setting for my boards. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;You can add next info to the ticket. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;parameter “timing_cfg1[29:31 wrtord]”&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: black; font-size: 11pt;"&gt;tWTR min = greater of 4CK or 7.5ns (Micron datasheet &amp;amp; CK=333Mhz_3.0ns)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11pt;"&gt;WRTORD = 4CK &amp;nbsp;min &amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11pt;"&gt;WRTORD = (tWTR+2cycles) if ddr_sdram_cfg2[OBC_CFG]=1 &amp;gt;&amp;gt; tWTR min = 4+2=6 &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11pt;"&gt;“OBC: On_the_fly_Burst_chop” is not used &amp;gt;&amp;gt; parameter WRTORD = 4 &amp;nbsp;(in my old reg-settings).&amp;nbsp;&amp;nbsp; &amp;lt;&amp;lt;&amp;lt;&amp;nbsp;Correction 4jan18: OBC=on,&amp;nbsp;explaining unstability&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #c00000; font-size: 11pt;"&gt;As soon as I make WRTORD &amp;gt; 4 ,&amp;nbsp; the unstable protos become stable.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #c00000; font-size: 11pt;"&gt;To create max margin max setting 7 ck is used.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;#define CONFIG_SYS_DDR_TIMING_1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0xBCBBE74&lt;/SPAN&gt;&lt;SPAN style="color: #c00000; font-size: 11pt;"&gt;&lt;STRONG&gt;7&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* caslat=6,wrrec=7,&lt;/SPAN&gt;&lt;SPAN style="color: #c00000; font-size: 11pt;"&gt;&lt;STRONG&gt;wtr=7&lt;/STRONG&gt;&lt;/SPAN&gt; &lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;*/&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d; font-size: 11pt;"&gt;#define CONFIG_SYS_DDR_MODE_1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x00041621&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;/* sdram:caslat=6,wrrec=7,Rtt=60,ods=half */&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Dec 2017 09:00:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/QCVS-DDRV-passed-but-Linux-kernel-crash/m-p/714961#M4301</guid>
      <dc:creator>stefanvranken</dc:creator>
      <dc:date>2017-12-07T09:00:32Z</dc:date>
    </item>
  </channel>
</rss>

