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