AnsweredAssumed Answered

dont get kernel booted, boot process ends with 'Starting kernel ...'

Question asked by Juergen Vorbach on Nov 14, 2014
Latest reply on Nov 21, 2014 by Jaymin Dabhi

I have done the installation part on a SD-Card as described and shown below. But I just get until a Starting Kernel ... message, no further.


Does anyone know how to fix this?

Thanks in advance




my Hyperterminal Bootsequence is:


U-Boot 2013.04 (Sep 19 2014 - 17:56:15)


CPU:   Freescale i.MX6Q rev1.2 at 792 MHz

CPU:   Temperature 45 C, calibration data: 0x5a74db7d

Reset cause: POR

Board: MX6Q/SDL-SabreSD

I2C:   ready

DRAM:  1 GiB


No panel detected: default to Hannstar-XGA

Display: Hannstar-XGA (1024x768)

In:    serial

Out:   serial

Err:   serial

Found PFUZE100! deviceid=10,revid=11

mmc1 is current device

Net:   FEC [PRIME]

Normal Boot

Hit any key to stop autoboot:  0

mmc1 is current device


MMC read: dev # 1, block # 2048, count 12288 ... 12288 blocks read: OK


MMC read: dev # 1, block # 20480, count 2048 ... 2048 blocks read: OK

## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.10.17-1.0.2_ga+g33597e3

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    5260744 Bytes = 5 MiB

   Load Address: 10008000

   Entry Point:  10008000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 18000000

   Booting using the fdt blob at 0x18000000

   Loading Kernel Image ... OK


switch to ldo_bypass mode!

   Using Device Tree in place at 18000000, end 1800ebac


Starting kernel ...


and I don't get any further.

Everything is based on the package: fsl-L3.10.17_1.0.2_iMX6QDLS_Bundle.tar.gz

what I did before was:

U-Boot > setenv loadaddr 0x12000000
U-Boot > setenv fdt_addr 0x18000000
U-Boot > setenv fdt_high 0xffffffff
U-Boot > setenv bootargs_base 'setenv bootargs console=ttymxc0,115200'
U-Boot > setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk0p2 rootwait rw video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'
U-Boot > setenv bootcmd_mmc 'run bootargs_base bootargs_mmc;mmc dev 1;mmc read ${loadaddr} 0x800 0x3000;mmc read ${fdt_addr} 0x5000 0x800;bootm ${loadaddr} - ${fdt_addr}'
U-Boot > setenv bootcmd 'run bootcmd_mmc'
U-Boot > saveenv
U-Boot > run bootcmd


#Copying the Boot Loader Image, offset=1k

sudo dd if=$BOOTLOADER of=/dev/$DEV bs=512 seek=2 conv=fsync
#Copying the Kernel Image and DTB File, offset=1M
sudo dd if=$KERNEL of=/dev/$DEV bs=512 seek=2048 conv=fsync
#DTB, offset=10M
sudo dd if=$DTB of=/dev/$DEV bs=512 seek=20480 conv=fsync

also by hand:

#sudo fdisk /dev/$DEV
#sudo mkfs.ext4 /dev/${DEV}1
#sudo mount /dev/${DEV}1 /home/juergen/tmp/mnt
#sudo mount -o loop -t ext3 fsl-image-weston-imx6qdlsolo.ext3 /home/juergen/tmp/rootfs
#cd /home/juergen/tmp/rootfs
#sudo cp -a * /home/juergen/tmp/mnt


I received from command output:

733+1 Datensätze ein
733+1 Datensätze aus
375488 Bytes (375 kB) kopiert, 3,37769 s, 111 kB/s
10275+1 Datensätze ein
10275+1 Datensätze aus
5260808 Bytes (5,3 MB) kopiert, 35,8851 s, 147 kB/s
93+1 Datensätze ein
93+1 Datensätze aus
48045 Bytes (48 kB) kopiert, 1,03537 s, 46,4 kB/s

so everything seemed to be ok.