<?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のトピックLS1028A. Read errors from eSDHC1 during preboot (PB2)</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010813#M5423</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello.&lt;BR /&gt;Out hardware loads RCW and PB2 correctly from I2C EEPROM, and continues fetching PB31 from SD card. This data is again copied to DDR4 RAM as it should. The problem is that the data copied to DDR4 RAM is corrupted (approximately every 20th byte or so is corrupted). We have ruled out DDR4 configuration. We log every 32-bits as fetched from the DATPORT register (DMA has been disabled), and this is where we see that some bytes are corrupted. We have tried running the SD card interface at different speeds. We have also tried turning on the schmitt triggers (hyst_ana_cntrl1), tried various brands and models of SD cards (including an eMMC card), and so forth but nothing seems to make a difference.&amp;nbsp; We are starting to run out of ideas.&amp;nbsp; Does anybody have any ideas as to what could be causing this, and what we could try? Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 22 Dec 2019 15:57:39 GMT</pubDate>
    <dc:creator>rpk</dc:creator>
    <dc:date>2019-12-22T15:57:39Z</dc:date>
    <item>
      <title>LS1028A. Read errors from eSDHC1 during preboot (PB2)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010813#M5423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello.&lt;BR /&gt;Out hardware loads RCW and PB2 correctly from I2C EEPROM, and continues fetching PB31 from SD card. This data is again copied to DDR4 RAM as it should. The problem is that the data copied to DDR4 RAM is corrupted (approximately every 20th byte or so is corrupted). We have ruled out DDR4 configuration. We log every 32-bits as fetched from the DATPORT register (DMA has been disabled), and this is where we see that some bytes are corrupted. We have tried running the SD card interface at different speeds. We have also tried turning on the schmitt triggers (hyst_ana_cntrl1), tried various brands and models of SD cards (including an eMMC card), and so forth but nothing seems to make a difference.&amp;nbsp; We are starting to run out of ideas.&amp;nbsp; Does anybody have any ideas as to what could be causing this, and what we could try? Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 22 Dec 2019 15:57:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010813#M5423</guid>
      <dc:creator>rpk</dc:creator>
      <dc:date>2019-12-22T15:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: LS1028A. Read errors from eSDHC1 during preboot (PB2)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010814#M5424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Perhaps your problem concerns to DDR4.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;Test your memory using a memory test.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Pavel Chubakov&lt;/P&gt;&lt;P style="min- padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Dec 2019 06:22:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010814#M5424</guid>
      <dc:creator>Pavel</dc:creator>
      <dc:date>2019-12-24T06:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: LS1028A. Read errors from eSDHC1 during preboot (PB2)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010815#M5425</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Pavel, &lt;/P&gt;&lt;P&gt;We have run memory tests and they show that DDR4 is fine.&lt;/P&gt;&lt;P&gt;In the firmware/atf/plat/nxp/drivers/sd/sd_mmc.c file, function&amp;nbsp;esdhc_read_data_nodma(), we log val here:&lt;/P&gt;&lt;P&gt;/* get data from data port */&lt;/P&gt;&lt;P&gt;val = mmio_read_32((uintptr_t)&amp;amp;mmc-&amp;gt;esdhc_regs-&amp;gt;datport);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This shows that val is corrupted now and then. This is not related to DDR4. &lt;/P&gt;&lt;P&gt;Any ideas what could be causing this and how to fix it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;/P&gt;&lt;P&gt;Rolf Peder Klemetsen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Dec 2019 22:04:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010815#M5425</guid>
      <dc:creator>rpk</dc:creator>
      <dc:date>2019-12-25T22:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: LS1028A. Read errors from eSDHC1 during preboot (PB2)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010816#M5426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi again,&lt;/P&gt;&lt;P&gt;Turns out it really was a DDR4 configuration issue. The memory tests were fooled by the cache, and a byte swapping issue caused a misinterpation of data read from the data port.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;/Rolf&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Jan 2020 16:19:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1028A-Read-errors-from-eSDHC1-during-preboot-PB2/m-p/1010816#M5426</guid>
      <dc:creator>rpk</dc:creator>
      <dc:date>2020-01-04T16:19:22Z</dc:date>
    </item>
  </channel>
</rss>

