<?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: i.MX8M DDR3L register programming aid difference in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-DDR3L-register-programming-aid-difference/m-p/957173#M143013</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello M.C.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Some details on the changes between revisions can be found on the Revision History sheet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for your questions this is the information I received from our experts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. IP vendor ticket STAR 9001091272 dictates that we should set DRAMTMG8.t_xs_x32 = DRAMTMG8.t_xs_dll_x32 to avoid timing violations from SRX to PDE in DDR3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Disabled DDRC_DFIPHYMSTR.DFI_PHYMSTR_EN as it is not used for DDR3L PHY firmware. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a side note, it’s always recommended to use the latest version of the programming aid.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Jul 2019 15:24:54 GMT</pubDate>
    <dc:creator>gusarambula</dc:creator>
    <dc:date>2019-07-24T15:24:54Z</dc:date>
    <item>
      <title>i.MX8M DDR3L register programming aid difference</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-DDR3L-register-programming-aid-difference/m-p/957171#M143011</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are two&amp;nbsp;i.MX8M DDR3L register programming aid.&lt;/P&gt;&lt;P&gt;Old is MX8M_DDR3L_register_programming_aid_VAL_preliminiary_v1_2.xlsx from &amp;lt;&lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-340268"&gt;https://community.nxp.com/docs/DOC-340268&lt;/A&gt;&amp;gt;.&lt;/P&gt;&lt;P&gt;New is MX8M_DDR3L_RPA_v6.xlsx from &amp;lt;&lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-340179"&gt;https://community.nxp.com/docs/DOC-340179&lt;/A&gt;&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May we know more detail about below two modifications?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. New “K18”, it is related to “C175” &amp;amp; “D175” and the result will be changed for “0x3D400120”&lt;BR /&gt; &lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/82380i571E60BECC215EE9/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;2. Disable DDRC_DFIPHYMSTR in the latest version “6”, but in previous v1.2, the value is “1” that means the DDRC_DFIPHYMSTR is enabled. Should we set value to “0”?&lt;BR /&gt;&lt;BR /&gt; &lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/82415iFA193ACEAEEFB059/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jul 2019 10:33:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-DDR3L-register-programming-aid-difference/m-p/957171#M143011</guid>
      <dc:creator>m_c</dc:creator>
      <dc:date>2019-07-23T10:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M DDR3L register programming aid difference</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-DDR3L-register-programming-aid-difference/m-p/957172#M143012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello M.C.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I’m looking for more information on the changes between both versions. I will let you know as soon as I have an update.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jul 2019 19:26:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-DDR3L-register-programming-aid-difference/m-p/957172#M143012</guid>
      <dc:creator>gusarambula</dc:creator>
      <dc:date>2019-07-23T19:26:49Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8M DDR3L register programming aid difference</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-DDR3L-register-programming-aid-difference/m-p/957173#M143013</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello M.C.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Some details on the changes between revisions can be found on the Revision History sheet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for your questions this is the information I received from our experts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. IP vendor ticket STAR 9001091272 dictates that we should set DRAMTMG8.t_xs_x32 = DRAMTMG8.t_xs_dll_x32 to avoid timing violations from SRX to PDE in DDR3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Disabled DDRC_DFIPHYMSTR.DFI_PHYMSTR_EN as it is not used for DDR3L PHY firmware. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a side note, it’s always recommended to use the latest version of the programming aid.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jul 2019 15:24:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8M-DDR3L-register-programming-aid-difference/m-p/957173#M143013</guid>
      <dc:creator>gusarambula</dc:creator>
      <dc:date>2019-07-24T15:24:54Z</dc:date>
    </item>
  </channel>
</rss>

