Hi all, I have recently compiled kernel (https://github.com/patrykk/linux-udoo) on my udoo and everything is working great apart from the uboot script: my uboot script - /boot/boot.cmd: setenv bootargs root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=ttymxc1,115200 ext2load mmc 0 0x18000000 /boot/dtb/imx6q-udoo.dtb ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000 then: /boot# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Image Name: Created: Mon Aug 3 18:39:35 2015 Image Type: ARM Linux Script (uncompressed) Data Size: 211 Bytes = 0.21 kB = 0.00 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 203 Bytes = 0.20 kB = 0.00 MB when I restart my board all I get is this: U-Boot 2015.04-dirty (Jul 13 2015 - 12:27:45) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: Udoo DRAM: 1 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device 275 bytes read in 104 ms (2 KiB/s) Running bootscript from mmc ... ## Executing script at 12000000 35681 bytes read in 145 ms (240.2 KiB/s) 6491688 bytes read in 376 ms (16.5 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x630e28 ] However when I abort the autoboot and manually enter the script lines: ................. > ext2load mmc 0 0x12000000 /boot/zImage 6491688 bytes read in 376 ms (16.5 MiB/s) => bootz 0x12000000 - 0x18000000 Kernel image @ 0x12000000 [ 0x000000 - 0x630e28 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800bb60 Starting kernel ... It boots fine. Any suggestions what am I doing wrong? Thanks
