dear freescale team.
I'm using "QorIQ-SDK-V1.7".
there are some ramdisk errors in booting kernel.
in case of use "fsl-image-core-ls1021aiot-20150707124654.rootfs.ext2.gz.u-boot" file
[ 41.592198] VFS: Mounted root (ext2 filesystem) on device 1:0.
Bad inittab entry at line 3
can't run '/etc/init.d/rcS': No such file or directory
in case of use "fsl-image-rds-ls1021aiot-20150709153500.rootfs.ext2.gz.u-boot" file
- can't open /dev/EHV0: 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/S1: No such file or directory
is it QorIQ-SDK-V1.7 errors?
bellow link is history of discussion.
please check and let me reply.
Thanks
Hello MyungJin Hwang,
Please check whether add bootargs as the following would be better.
=> setenv bootargs root=/dev/ram0 rw rootwait console=ttyS0,115200 coherent_pool=4M
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Dear yipingwang, I recently had a similar issue (lots of 'can't find /dev/foobar) following SDK 1.9 for a LS1021atwr and using your setenv bootargs line solved it. Could you explain the issue, or why this bootargs are better ?
Best,
Vincent
It's necessary to specify rootfs boot type(from RAM) with "root=/dev/ram0".
Thanks,
Yiping