AnsweredAssumed Answered

SDK 2.0 inittab entries not found booting from /dev/mmcblk0p2

Question asked by pro-supportengineer Employee on Jun 10, 2016
Latest reply on Jan 25, 2017 by chris warth

Experiencing failure to read inittab file on kernel boot rootfs from /dev/mmcblk0p2

 

When using the following bootargs, inittab tab entries are not found.  Reproducible on two different boards. Was able to boot rootfs successfully from /dev/mmcblk0p2 on SDK 0.5.

 

Bootargs to reproduce the failure:

 

This boots successfully:

setenv bootargs "console=ttyS0,115200 root=/dev/ram0 rw rootdelay=5
earlycon=uart8250,0x21c0500,115200"

This fails to boot:
setenv bootargs "console=ttyS0,115200 root=/dev/mmcblk0p2 rw rootdelay=5 earlycon=uart8250,0x21c0500,115200"

Get the following output on the serial console on failure. The content of both filesystems are identical.

[    2.372835] fsl_generic:
FSL DPAA Generic Ethernet driver

[    2.373027] hctosys: unable to open rtc device (rtc0)
[    2.373139] fdt: not creating '/sys/firmware/fdt': CRC
check failed

[   2.403534] usb usb6-port1: over-current condition
[    2.408271] Waiting 5 sec before mounting root device...
[    2.426819] mmc0: new high speed SDXC card at address
aaaa

[    2.432439] mmcblk0: mmc0:aaaa SL64G 59.4 GiB
[    2.443559]  mmcblk0: p1 p2 p3 p4 < p5 p6 >
[    7.420969] RAMDISK: gzip image found at block 0
[    8.663559] VFS: Mounted root (ext2 filesystem) on device
1:0.

Bad inittab entry at line 5
can't open /dev/si: No such file or directory
can't open /dev/~~: No such file or directory
can't open /dev/l0: No such file or directory
can't open /dev/l1: No such file or directory
can't open /dev/l2: No such file or directory
can't open /dev/l3: No such file or directory
can't open /dev/l4: No such file or directory
can't open /dev/l5: No such file or directory
can't open /dev/l6: No such file or directory
can't open /dev/z6: No such file or directory
can't open /dev/S0: No such file or directory
can't open /dev/AMA0: No such file or directory
can't open /dev/z6: No such file or directory
can't open /dev/S0: No such file or directory
can't open /dev/AMA0: No such file or directory
can't open /dev/z6: No such file or directory
can't open /dev/S0: No such file or directory
can't open /dev/AMA0: No such file or directory
can't open /dev/z6: No such file or directory
can't open /dev/S0: No such file or directory
can't open /dev/AMA0: No such file or directory


Procedure to boot from SD:

$ cd ~/QorIQ-SDK-V2.0-20160527-yocto

$ ./install

$ ./sources/meta-freescale/scripts/host-prepare.sh

$ . ./fsl-setup-env -m ls1043ardb

$ bitbake fsl-image-core

$ bitbake fsl-image-kernelitb

$ sudo fdisk /dev/mmcblk0

Create a Fat32 partition ornpartition 1 and the default ext2 for partition 2.  Place kernel.itb on partition 1 and the rootfs on partition 2. Sectors are all aligned and work SD boot works fine on v0.5 SDK. For 64GB SD partition 1 start block 8192 and end block 1056863. Partition 2 1056864 and end block 124735487 (end of disk).

$ sudo dd if=/tmp/deploy/images/ls1043ardb/u-boot-sdcard.bin of=/dev/mmcblk0 seek=8 bs=512

$ sudo dd if=tmp/deploy/images/ls1043ardb/fsl_fman_ucode_t2080_r1.1_106_4_18.bin of=/dev/mmcblk0 seek=2080 bs=512

$ sudo mkfs.vfat /dev/mmcblk0p1

$ sudo mkfs.ext2 /dev/mmcblk0p2

mount mmcblk0p1 and copy the kernel.itb

$ sudo cp -L tmp/deploy/ls1043ardb/kernel-fsl-ls1043a-rdb.itb /mnt/mmcblk0p1/kernel.itb

mount mmcblk0p2 and copy the rootfs

$ sudo tar xvf tmp/deploy/images/ls1043ardb/fsl-image-core-ls1043ardb.tar.gz -C /mnt/mmcblk0p2


Then boot on LS 1043ARDB target.  Uboot boots successfully, but kernel boot fails.

Outcomes