AnsweredAssumed Answered

ls1021atwr boot issue

Question asked by Matthew Clifford on Aug 24, 2017

Hi

 

I am trying to load a new OS image onto the LS1021ATWR development board and having a few problems.

 

I have downloaded and installed the QorIQ SDK V2.0-1703 including the "image" iso. I have built the core and minimal OS images and attempted to boot from the SDcard by loading the images to a ramdisk and booting from this. However i get a few errors once the filesystem is mounted which include:

Bad inittab entry at line 5

 

and

 

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

 

I have tried the same test using the pre-built images from the SDK Images iso and get the same errors.

 

I have also compared the inittab file to that pre-installed in the NOR flash on the development card and line 5 appears to be identical.

 

My uboot environment for testing against the pre-built images is

baudrate=115200
bootargs=‘root=/dev/ram0 rw rootdelay=5 ramdisk_size=40000000 console=ttyS0,115200’
bootcmd=mmcinfo;ext2load mmc 0:2 $loadaddr /boot/$bootfile;ext2load mmc 0:2 $fdtaddr /boot/$fdtfile;ext2load mmc 0:2 $fsaddr /$filesystemfile;bootm $loadaddr $fsaddr $fdtaddr
bootdelay=3
bootfile=uImage-ls1021atwr_image.bin
dnsip=10.192.130.201
eth1addr=00:04:9f:04:e1:f9
eth2addr=00:04:9f:04:e1:fa
ethact=eTSEC3
ethaddr=00:04:9f:04:e1:f8
ethprime=eTSEC3
fdt_high=0xffffffff
fdtaddr=8f000000
fdtcontroladdr=bef0ed34
fdtfile=uImage-ls1021a-twr_image.dtb
filesystemfile=fsl-image-core-ls1021atwr-20160514210716.rootfs.ext2.gz.u-boot
fsaddr=88000000
gatewayip=10.193.20.254
initrd_high=0xffffffff
ipaddr=10.193.20.191
loadaddr=83000000
netmask=255.255.255.0
scsidevs=0
serverip=10.192.208.233
stderr=serial
stdin=serial
stdout=serial

and i have attached a log of the boot sequence.

 

Any ideas?

 

Thanks

Matt

Original Attachment has been moved to: boot.txt.zip

Outcomes