<?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>LayerscapeのトピックRe: DRAM ODT configruration value</title>
    <link>https://community.nxp.com/t5/Layerscape/DRAM-ODT-configruration-value/m-p/2112220#M15818</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/227048"&gt;@pb3&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this email finds you well,&lt;/P&gt;
&lt;P&gt;Please note that the&lt;SPAN&gt;&amp;nbsp;DDR Validation tool determine the results the ODT Validation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;The QCVS Tool is programmed to select a central value from among the passing cells.&lt;BR /&gt;This means that if all combinations pass validation,&lt;BR /&gt;QCVS will choose a value that lies at the center of the range of all passing cells.&lt;/P&gt;
&lt;P&gt;Have a great day.&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Hector V&lt;/P&gt;</description>
    <pubDate>Fri, 06 Jun 2025 16:53:39 GMT</pubDate>
    <dc:creator>Hector_Villarruel</dc:creator>
    <dc:date>2025-06-06T16:53:39Z</dc:date>
    <item>
      <title>DRAM ODT configruration value</title>
      <link>https://community.nxp.com/t5/Layerscape/DRAM-ODT-configruration-value/m-p/2110347#M15813</link>
      <description>&lt;P&gt;Hi, we've been working on our custom board based on LS1028A, the memory that we're using is&amp;nbsp;IS43QR85120B-083RBLI in 512Mb x8 config - 2GB total.&lt;/P&gt;&lt;P&gt;We've managed to perform validation and so on, DDR seems to be working fine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've performed some other tests like:&lt;/P&gt;&lt;P&gt;- enabled built self test in TF-A&lt;/P&gt;&lt;P&gt;- mtest in u-boot&lt;/P&gt;&lt;P&gt;- overnight tests on couple boards using memtester in Linux&lt;/P&gt;&lt;P&gt;Every test passed without any problems, however our electronic team is a bit worried about hardware level tests - from what they told me, the signal integrity does not match the requirements enforced by JEDEC. It's not a big gap between what JEDEC expects and what we have but still - it exists.&lt;/P&gt;&lt;P&gt;So my question is - what value in DDR controller determines the value that is being set in DRAM MR1 RTT_NOM?&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've been using STATIC_DDR configuration you can see below:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;+const struct ddr_cfg_regs static_1600 = {
+	.cs[0].bnds = 0x7F,
+	.cs[0].config = 0x80010322,
+	.timing_cfg[0] = 0x80550018,
+	.timing_cfg[1] = 0xBDB48F42,
+	.timing_cfg[2] = 0x0048D114,
+	.timing_cfg[3] = 0x010C1000,
+	.timing_cfg[4] = 0x01,
+	.timing_cfg[5] = 0x03401400,
+	.timing_cfg[7] = 0x13300000,
+	.timing_cfg[8] = 0x02115600,
+	.sdram_cfg[0] = 0x650C0004,
+	.sdram_cfg[1] = 0x00401010,
+	.dq_map[0] = 0x56C5AC2C,
+	.dq_map[1] = 0xAD6B0000,
+	.dq_map[2] = 0x00,
+	.dq_map[3] = 0x01600000,
+	.sdram_mode[0] = 0x01010610,
+	.sdram_mode[1] = 0x00,
+	.sdram_mode[2] = 0x00,
+	.sdram_mode[3] = 0x00,
+	.sdram_mode[4] = 0x00,
+	.sdram_mode[5] = 0x00,
+	.sdram_mode[6] = 0x00,
+	.sdram_mode[7] = 0x00,
+	.sdram_mode[8] = 0x0400,
+	.sdram_mode[9] = 0x04A40000,
+	.sdram_mode[10] = 0x00,
+	.sdram_mode[11] = 0x00,
+	.sdram_mode[12] = 0x00,
+	.sdram_mode[13] = 0x00,
+	.sdram_mode[14] = 0x00,
+	.sdram_mode[15] = 0x00,
+	.md_cntl = 0x00,
+	.interval = 0x18600618,
+	.data_init = 0xDEADBEEF,
+	.clk_cntl = 0x01C00000,
+	.init_addr = 0x00,
+	.ddr_sr_cntr = 0x0,
+	.init_ext_addr = 0x00,
+	.zq_cntl = 0x8A090705,
+	.wrlvl_cntl[0] = 0x86750604,
+	.wrlvl_cntl[1] = 0x05060700,
+	.wrlvl_cntl[2] = 0x08,
+	.cdr[0] = 0x80080000,
+	.cdr[1] = 0xA180,
+	.debug[28] = 0x01080F70
+};&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The validation steps selects the following:&lt;/P&gt;&lt;P&gt;1) Read ODT and driver:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; - ODT 60ohm / DRAM driver strength 34 ohm - full&lt;/P&gt;&lt;P&gt;2) Write ODT and driver&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Controller DRV Strength - full strength / DRAM ODT - 60 ohm&lt;/P&gt;&lt;P&gt;As far as I understand, in the context of DRAM's MR1 RTT_NOM we're talking about 2) "Write ODT and driver" which was set during validation to 60 ohm, but I'm having difficulties understanding how the SDRAM_MODE register content reflects the RTT_NOM setting.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I mean - how can I be sure that DRAM ODT 60ohm selected by validation was in fact programmed in DRAM?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:13:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/DRAM-ODT-configruration-value/m-p/2110347#M15813</guid>
      <dc:creator>pb3</dc:creator>
      <dc:date>2025-06-04T10:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: DRAM ODT configruration value</title>
      <link>https://community.nxp.com/t5/Layerscape/DRAM-ODT-configruration-value/m-p/2112220#M15818</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/227048"&gt;@pb3&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this email finds you well,&lt;/P&gt;
&lt;P&gt;Please note that the&lt;SPAN&gt;&amp;nbsp;DDR Validation tool determine the results the ODT Validation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;The QCVS Tool is programmed to select a central value from among the passing cells.&lt;BR /&gt;This means that if all combinations pass validation,&lt;BR /&gt;QCVS will choose a value that lies at the center of the range of all passing cells.&lt;/P&gt;
&lt;P&gt;Have a great day.&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;Hector V&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jun 2025 16:53:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/DRAM-ODT-configruration-value/m-p/2112220#M15818</guid>
      <dc:creator>Hector_Villarruel</dc:creator>
      <dc:date>2025-06-06T16:53:39Z</dc:date>
    </item>
  </channel>
</rss>

