<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:微软雅黑
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Federico,<div><br>I met the same problem few weeks ago.</div><div>For some reason, googleapis website is blocked in China.</div><div>So I update SPI flash manually, followed by <a href="http://eewiki.net/display/linuxonarm/i.MX6x+SABRE+Lite+SPI+FLash+Recovery">http://eewiki.net/display/linuxonarm/i.MX6x+SABRE+Lite+SPI+FLash+Recovery</a></div><div><br></div><div>The fix steps are the same as Eric said with more details.</div><div><br></div><div>Hope this can help you.</div><div><br></div><div>Regards,</div><div><br></div><div>Yuan Li</div><div><div><br><div>> Date: Thu, 6 Mar 2014 07:46:48 -0700<br>> From: eric.nelson@boundarydevices.com<br>> To: fede.vitali@gmail.com; meta-freescale@yoctoproject.org<br>> Subject: Re: [meta-freescale] Problem booting fsl-image-gui with imx6qsabrelite<br>> <br>> Hi Federico,<br>> <br>> On 03/06/2014 05:36 AM, Federico Vitali wrote:<br>> > Goodmorning,<br>> ><br>> > I have built a fsl-image-gui (poky dora) for imx6qsabrelite. I have<br>> > followed the instruction<br>> > to burn the sdcard image ona micro sd.<br>> ><br>> > On boot I get the following errors:<br>> ><br>> <br>> This is the problem:<br>> <br>> > U-Boot 2009.08 (Jul 05 2012 - 15:37:27)<br>> ><br>> > CPU: Freescale i.MX 6 family 0.0V at 792 MHz<br>> > Temperature: can't get valid data!<br>> > mx6q pll1: 792MHz<br>> > mx6q pll2: 528MHz<br>> > mx6q pll3: 480MHz<br>> > mx6q pll8: 50MHz<br>> > ipg clock : 66000000Hz<br>> > ipg per clock : 66000000Hz<br>> > uart clock : 80000000Hz<br>> > cspi clock : 60000000Hz<br>> > ahb clock : 132000000Hz<br>> > axi clock : 264000000Hz<br>> > emi_slow clock: 29333333Hz<br>> > ddr clock : 528000000Hz<br>> > usdhc1 clock : 200000000Hz<br>> > usdhc2 clock : 200000000Hz-<br>> > usdhc3 clock : 200000000Hz<br>> > usdhc4 clock : 200000000Hz<br>> > nfc clock : 24000000Hz<br>> > Board: MX6Q-SABRELITE:[ POR]<br>> > I2C: ready<br>> > DRAM: 1 GB<br>> > MMC: FSL_USDHC: 0,FSL_USDHC: 1<br>> > JEDEC ID: 0xbf:0x25:0x41<br>> > Reading SPI NOR flash 0xc0000 [0x2000 bytes] -> ram 0x276009b8<br>> > SUCCESS<br>> ><br>> > In: serial<br>> > Out: serial<br>> > Err: serial<br>> > Net: got MAC address from IIM: 00:19:b8:00:fd:74<br>> > FEC0 [PRIME]<br>> > Warning: FEC0 MAC addresses don't match:<br>> > Address in SROM is 00:19:b8:00:fd:74<br>> > Address in environment is 00:01:02:03:04:05<br>> ><br>> > Hit any key to stop autoboot: 0<br>> > Card did not respond to voltage select!<br>> > mmc0(part 0) is current device<br>> > MMC: block number 0x1 exceeds max(0x0)<br>> > ** Can't read from device 0 **<br>> ><br>> > ** Unable to use mmc 0:1 for fatload **<br>> > ** Bad partition 1 **<br>> > mmc1 is current device<br>> > reading /6q_bootscript<br>> ><br>> <br>> And this is the key symptom (6q_bootscript):<br>> <br>> > ** Unable to read "/6q_bootscript" from mmc 1:1 **<br>> > Loading file "/6q_bootscript" from mmc device 1:1 (xxb1)<br>> > Failed to mount ext2 filesystem...<br>> > ** Bad ext2 partition or disk - mmc 1:1 **<br>> ><br>> > What could be the problem? I've also tried with different images, but<br>> > without success.<br>> ><br>> <br>> Yocto includes a boot script that assumes you're using<br>> a main-line version of U-Boot. Because of the incompatibilities<br>> between the 2009.08 code base and main-line, the boot<br>> script was re-named from 6q_bootscript to 6x_bootscript in<br>> the process.<br>> <br>> It also generates a U-Boot binary for you, but doesn't<br>> upgrade it in SPI-NOR.<br>> <br>> See this post for details:<br>> http://boundarydevices.com/switching-u-boot-versions-on-i-mx6/<br>> <br>> So to get past this, you need to program the file 'u-boot.imx' from<br>> your SD card, and this is done through the 'upgradeu' command:<br>> <br>> U-Boot > run upgradeu<br>> <br>> Unfortunately, the command incompatibilities are in the 'upgradeu'<br>> process as well, so this will fail for you until you copy the<br>> script file '6q_upgrade' from this package:<br>> http://commondatastorage.googleapis.com/boundarydevices.com<br>> /6q_upgrade-20121109.zip<br>> <br>> Note that you only need to copy the one file '6q_upgrade' from that<br>> package into the Boot partition. You should already have a<br>> u-boot.imx file produced by Yocto that is relatively recent.<br>> <br>> Finally, the environment variables changed between the two<br>> code bases. To restore them to factory default, you can use<br>> the 'clearenv' command:<br>> U-Boot > run clearenv.<br>> <br>> So, to re-cap:<br>> <br>> 1. Copy 6q_upgrade from the 6q_upgrade-20121109.zip package<br>> into the boot partition of your SD card,<br>> 2. Boot the device and run these commands:<br>> U-Boot > run upgradeu<br>> U-Boot > run clearenv<br>> U-Boot > reset<br>> 3. Enjoy!<br>> <br>> Regards,<br>> <br>> <br>> Eric<br>> _______________________________________________<br>> meta-freescale mailing list<br>> meta-freescale@yoctoproject.org<br>> https://lists.yoctoproject.org/listinfo/meta-freescale<br></div></div></div> </div></body>
</html>