<?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>i.MX Processors中的主题 Re: Yocto i.mx28 eMMC Problem</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407574#M60741</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have you try only put bootloader in EMMC? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 Jun 2015 04:05:39 GMT</pubDate>
    <dc:creator>jimmychan</dc:creator>
    <dc:date>2015-06-09T04:05:39Z</dc:date>
    <item>
      <title>Yocto i.mx28 eMMC Problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407572#M60739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a board which is based on the i.MX28 EVK design but with eMMC on SSP1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using Yocto dora and have built the qte-in-use-image. The image works when programmed to SD card and booted from SSP0. When I program the eMMC with the same image (qte-in-use-image-imx28evk.sdcard) the result from the debug port at power on is 'HTLFLCM0x80206008'. The links are set correctly to boot from SSP1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We previously used LTIB and this worked booted with no source changes except the kernel boot string. Can anyone help to understand the problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2015 15:23:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407572#M60739</guid>
      <dc:creator>contra</dc:creator>
      <dc:date>2015-05-28T15:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: Yocto i.mx28 eMMC Problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407573#M60740</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error code is the next:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P data-canvas-width="237.78033437663987" style="font-size: 14.4px; font-family: sans-serif;"&gt;#define &lt;STRONG&gt;ERROR_SSP_DRIVER_DMA_TIMEOUT&lt;/STRONG&gt; (ERROR_DDI_GROUP | ERROR_DDI_SSP_DRIVER_GROUP | 0x8)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN class="highlight selected"&gt;0x80206008&lt;/SPAN&gt; &lt;/STRONG&gt;DMA Timed out&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After checking the documentation I believe this error corresponds to this description.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Data Time-Out Error—The SSP TIMEOUT counter is used to detect a time-out&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;condition during data write or read operations. The time-out counts any time that the&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SSP is waiting on a busy DAT bus. For read operations, the DAT line(s) indicate&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;busy before the card sends the start bit. For write operations, the DAT line(s) may&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;indicate busy after the block has been sent to the card. If the time-out counter expires&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;before the DAT line(s) become ready, the SSP stops any DMA requests, sets the&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;DATA_TIMEOUT status flag, and asserts a CPU IRQ. The ISR should check the&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;status register to see that a data time-out has occurred. It can then reset the DMA&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;channel and the SSP to re-try the operation.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen previous problems with different SD card brands. Each SD card or eMMC needs a different amount of time to access w/r its internal memory. And it seems that depending on the memory, the BootROM code may rise that error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wonder if you have tried with a different eMMC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Alejandro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jun 2015 17:17:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407573#M60740</guid>
      <dc:creator>alejandrolozan1</dc:creator>
      <dc:date>2015-06-08T17:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: Yocto i.mx28 eMMC Problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407574#M60741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have you try only put bootloader in EMMC? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jun 2015 04:05:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407574#M60741</guid>
      <dc:creator>jimmychan</dc:creator>
      <dc:date>2015-06-09T04:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Yocto i.mx28 eMMC Problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407575#M60742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes I have tried running only the bootloader in EMMC. At the moment I am using only the u-boot from Yocto. It will boot from MMC0 but not MMC1. At the moment I don't think EMMC is the problem, I think that MMC1 is not being set up. Is there a patch to get MMC1 to work?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2015 09:02:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-i-mx28-eMMC-Problem/m-p/407575#M60742</guid>
      <dc:creator>contra</dc:creator>
      <dc:date>2015-06-11T09:02:08Z</dc:date>
    </item>
  </channel>
</rss>

