<?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のトピックYocto U-boot problems</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-U-boot-problems/m-p/297959#M37199</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi There,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying out the new Yocto BSP 1.0.0 and so far it builds but I'm having some trouble getting mmc running in u-boot on our custom board. While troubleshooting this I ran into some trouble with GDB. If I build the full image (bitbake fsl-image-dfb) and dump that onto the SD card u-boot always comes up as follows &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt; font-family: courier new,courier;"&gt;CPU:&amp;nbsp;&amp;nbsp; Freescale i.MX6Q rev1.2 at 792 MHz&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;CPU:&amp;nbsp;&amp;nbsp; Temperature 45 C, calibration data: 0x58d4f269&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;Reset cause: POR&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;Board: MX6Q/SDL-SabreSD&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;I2C:&amp;nbsp;&amp;nbsp; ready&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;DRAM:&amp;nbsp; 1 GiB&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;MMC:&amp;nbsp;&amp;nbsp; FSL_SDHC: 0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;MMC Device 1 not found&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;No MMC card found&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;Using default environment&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, when I use my BDI3000 and GDB to load the image ("u-boot-imx/2013.04-r0/git/u-boot") I can single-step through just fine, as soon as I "continue" it jumps into the weeds and nothing ever prints to the console. GDB u-boot debugging works fine on the old LTIB 4.1.0 BSP.&amp;nbsp; I don't necessarily need gdb, but the problem is that the compile-test-repeat cycle is at a glacial pace when rebuilding the whole SD card image. Any ideas on what could be the culprit ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed there is a "&lt;STRONG&gt;u-boot-imx6qsabresd.imx&lt;/STRONG&gt;" file in the images directory. What is this file used for ? I'm hoping that can be copied directly to an SD card somehow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Otto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 May 2014 22:08:00 GMT</pubDate>
    <dc:creator>ottoblom</dc:creator>
    <dc:date>2014-05-14T22:08:00Z</dc:date>
    <item>
      <title>Yocto U-boot problems</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-U-boot-problems/m-p/297959#M37199</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi There,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying out the new Yocto BSP 1.0.0 and so far it builds but I'm having some trouble getting mmc running in u-boot on our custom board. While troubleshooting this I ran into some trouble with GDB. If I build the full image (bitbake fsl-image-dfb) and dump that onto the SD card u-boot always comes up as follows &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt; font-family: courier new,courier;"&gt;CPU:&amp;nbsp;&amp;nbsp; Freescale i.MX6Q rev1.2 at 792 MHz&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;CPU:&amp;nbsp;&amp;nbsp; Temperature 45 C, calibration data: 0x58d4f269&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;Reset cause: POR&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;Board: MX6Q/SDL-SabreSD&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;I2C:&amp;nbsp;&amp;nbsp; ready&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;DRAM:&amp;nbsp; 1 GiB&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;MMC:&amp;nbsp;&amp;nbsp; FSL_SDHC: 0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;MMC Device 1 not found&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;No MMC card found&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier; font-size: 8pt;"&gt;Using default environment&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, when I use my BDI3000 and GDB to load the image ("u-boot-imx/2013.04-r0/git/u-boot") I can single-step through just fine, as soon as I "continue" it jumps into the weeds and nothing ever prints to the console. GDB u-boot debugging works fine on the old LTIB 4.1.0 BSP.&amp;nbsp; I don't necessarily need gdb, but the problem is that the compile-test-repeat cycle is at a glacial pace when rebuilding the whole SD card image. Any ideas on what could be the culprit ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I noticed there is a "&lt;STRONG&gt;u-boot-imx6qsabresd.imx&lt;/STRONG&gt;" file in the images directory. What is this file used for ? I'm hoping that can be copied directly to an SD card somehow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Otto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 May 2014 22:08:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-U-boot-problems/m-p/297959#M37199</guid>
      <dc:creator>ottoblom</dc:creator>
      <dc:date>2014-05-14T22:08:00Z</dc:date>
    </item>
    <item>
      <title>Re: Yocto U-boot problems</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Yocto-U-boot-problems/m-p/297960#M37200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The problem had to do with changes we made the board. For anyone else interested in what the imx uboot file is - It can be written to a sdcard as follows&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sudo dd if=tmp/deploy/images/imx6qsabresd/u-boot.imx of=/dev/sdc bs=512 seek=2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 May 2014 02:36:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Yocto-U-boot-problems/m-p/297960#M37200</guid>
      <dc:creator>ottoblom</dc:creator>
      <dc:date>2014-05-15T02:36:09Z</dc:date>
    </item>
  </channel>
</rss>

