Cannot boot LS1088ARDB-PB from SD Card

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cannot boot LS1088ARDB-PB from SD Card

Jump to solution
1,200 Views
svanderleest
Contributor I


It looks like I might have scrogged my on-board boot image for the LS1088ARDB-PB. I was previously getting the bootup messages and could login on the serial channel, so I know my serial connection is set up correctly.

I tried programming an SD card using the instructions from the Layerscape Software Development Kit 18.09 Documentation. After inserting the SD Card and pressing power button, I do not get any output on my serial channel. Can you provide some debugging help?

I have set my dip switches to force boot from the SD Card, as follows:

Changed from default SW1:SW2 of 0011_0001 0100 to 0010_0000 0110


When I power up the board, the LED lights show the following, which seems to indicate it is not coming completely out of reset.

D41 PORST is blinking red.
D35 ASLEEP is solid yellow
D34 FAIL is off

D41, D40, 39, 38, 37 = PORST and STAT[3:0] are cycling through a pattern:

0 0000
1 1101
1 0101
1 0110
1 1110
1 0110

0 0000
1 0101
1 1101
1 1110
1 0110
1 1110
0 1100
1 0101
1 1110
1 0110

0 0000
1 1101
1 0101
1 0110
1 1110
0 0110
1 0101
1 1101
1 1110
1 0110
1 1110

0 0000
etc.


I programmed my SD Card as follows.

As the last step after building all the images using flex-builder,

$ flex-installer -b bootpartition_arm64_lts_4.14.tgz -r build/images/rootfs_lsdk1909_LS_arm64_main.tgz -f firmware_ls088ardb_uboot_sdboot.img -d /dev/sdc
bootpart = bootpartition_arm64_lts_4.14.tgz
rootfs = build/images/rootfs_lsdk1909_LS_arm64_main.tgz
firmware = firmware_ls088ardb_uboot_sdboot.img
Partitioning /dev/sdc ...
Formatting partitions ...


Model: Mass Storage Device (scsi)
Disk /dev/sdc: 31.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 71.3MB 176MB 105MB primary ext4
2 177MB 1251MB 1074MB primary ext4
3 1252MB 7694MB 6442MB primary ext4
4 7695MB 31.9GB 24.2GB primary ext4

partition and format /dev/sdc [Done]
Installing boot partition, please wait ...
boot partition installation [Done]
Installing system rootfs partition, please wait ...
rootfs partition installation [Done]
sync data, please wait ...
setting PARTUUID ...
chmod: cannot access '/run/media/sdc4/etc/fstab': Input/output error

I checked the result using:

$ sudo fdisk -l
Disk /dev/sdd: 29.7 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x49a8a6e2

Device Boot Start End Sectors Size Id Type
/dev/sdd1 139264 344063 204800 100M 83 Linux
/dev/sdd2 346112 2443263 2097152 1G 83 Linux
/dev/sdd3 2445312 15028223 12582912 6G 83 Linux
/dev/sdd4 15030272 62333951 47303680 22.6G 83 Linux

I also checked the result by mounting the device and listing the 4 resulting mount points:

$ mount |grep sdd
/dev/sdd1 on /media/steve/misc type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2)
/dev/sdd2 on /media/steve/boot type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2)
/dev/sdd3 on /media/steve/backup type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2)
/dev/sdd4 on /media/steve/system type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2)

When I list the contents of the mounted partitions, I see the programmed image contents:


$ ls /media/steve
backup boot misc system
steve@steve-VirtualBox$ ls -l /media/steve
total 16
drwxr-xr-x 3 root root 4096 Apr 1 08:59 backup
drwxr-xr-x 6 root root 4096 Apr 1 09:02 boot
drwxr-xr-x 3 root root 4096 Apr 1 08:59 misc
drwxr-xr-x 23 root root 4096 Apr 1 09:02 system
steve@steve-VirtualBox$ ls -l /media/steve/*
/media/steve/backup:
total 16
drwx------ 2 root root 16384 Apr 1 08:59 lost+found

/media/steve/boot:
total 112956
-rw-rw-r-- 1 1001 1001 155981 Sep 19 2018 config-4.14.67
-rw-rw-r-- 1 1001 1001 1601744 Sep 19 2018 firmware_ls1012afrwy_uboot_qspiboot.img
-rw-rw-r-- 1 1001 1001 12582912 Sep 19 2018 firmware_ls1012ardb_uboot_qspiboot.img
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 firmware_ls1043ardb_uboot_norboot.img
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 firmware_ls1046ardb_uboot_qspiboot.img
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 firmware_ls1088ardb_pb_uboot_qspiboot.img
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 firmware_ls1088ardb_uboot_qspiboot.img
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 firmware_ls2088ardb_uboot_norboot.img
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 firmware_ls2088ardb_uboot_qspiboot.img
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 firmware_ls2088ardb_uefi_norboot.img
drwxrwxr-x 9 1001 1001 4096 Sep 19 2018 flash_images
-rw-rw-r-- 1 1001 1001 20782 Sep 19 2018 flash_images.scr
-rw-rw-r-- 1 1001 1001 11937 Sep 19 2018 fsl-ls1012a-2g5rdb.dtb
-rw-rw-r-- 1 1001 1001 13095 Sep 19 2018 fsl-ls1012a-frdm.dtb
-rw-rw-r-- 1 1001 1001 13072 Sep 19 2018 fsl-ls1012a-frwy.dtb
-rw-rw-r-- 1 1001 1001 13681 Sep 19 2018 fsl-ls1012a-qds.dtb
-rw-rw-r-- 1 1001 1001 12064 Sep 19 2018 fsl-ls1012a-rdb.dtb
-rw-rw-r-- 1 1001 1001 29885 Sep 19 2018 fsl-ls1043a-qds.dtb
-rw-rw-r-- 1 1001 1001 32052 Sep 19 2018 fsl-ls1043a-qds-sdk.dtb
-rw-rw-r-- 1 1001 1001 27684 Sep 19 2018 fsl-ls1043a-rdb.dtb
-rw-rw-r-- 1 1001 1001 29851 Sep 19 2018 fsl-ls1043a-rdb-sdk.dtb
-rw-rw-r-- 1 1001 1001 31366 Sep 19 2018 fsl-ls1043a-rdb-usdpaa.dtb
-rw-rw-r-- 1 1001 1001 29269 Sep 19 2018 fsl-ls1046a-qds.dtb
-rw-rw-r-- 1 1001 1001 31548 Sep 19 2018 fsl-ls1046a-qds-sdk.dtb
-rw-rw-r-- 1 1001 1001 26493 Sep 19 2018 fsl-ls1046a-rdb.dtb
-rw-rw-r-- 1 1001 1001 29096 Sep 19 2018 fsl-ls1046a-rdb-sdk.dtb
-rw-rw-r-- 1 1001 1001 30527 Sep 19 2018 fsl-ls1046a-rdb-usdpaa.dtb
-rw-rw-r-- 1 1001 1001 16246 Sep 19 2018 fsl-ls1088a-qds.dtb
-rw-rw-r-- 1 1001 1001 16649 Sep 19 2018 fsl-ls1088a-rdb.dtb
-rw-rw-r-- 1 1001 1001 20760 Sep 19 2018 fsl-ls2080a-qds.dtb
-rw-rw-r-- 1 1001 1001 20310 Sep 19 2018 fsl-ls2080a-rdb.dtb
-rw-rw-r-- 1 1001 1001 19125 Sep 19 2018 fsl-ls2081a-rdb.dtb
-rw-rw-r-- 1 1001 1001 21300 Sep 19 2018 fsl-ls2088a-qds.dtb
-rw-rw-r-- 1 1001 1001 20214 Sep 19 2018 fsl-ls2088a-rdb.dtb
drwxrwxr-x 2 1001 1001 4096 Sep 19 2018 grub
-rw-rw-r-- 1 1001 1001 2176 Sep 19 2018 hdr_ls1012afrwy_bs.out
-rw-rw-r-- 1 1001 1001 2176 Sep 19 2018 hdr_ls1012ardb_bs.out
-rw-rw-r-- 1 1001 1001 2176 Sep 19 2018 hdr_ls1043ardb_bs.out
-rw-rw-r-- 1 1001 1001 2176 Sep 19 2018 hdr_ls1046ardb_bs.out
-rw-rw-r-- 1 1001 1001 2176 Sep 19 2018 hdr_ls1088ardb_bs.out
-rw-rw-r-- 1 1001 1001 2176 Sep 19 2018 hdr_ls1088ardb_pb_bs.out
-rw-rw-r-- 1 1001 1001 2176 Sep 19 2018 hdr_ls2088ardb_bs.out
-rwxrwxr-x 1 1001 1001 8388608 Sep 19 2018 Image
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 Image.gz
drwx------ 2 root root 16384 Apr 1 08:59 lost+found
-rw-rw-r-- 1 1001 1001 964 Sep 19 2018 ls1012afrwy_boot.scr
-rw-rw-r-- 1 1001 1001 962 Sep 19 2018 ls1012ardb_boot.scr
-rw-rw-r-- 1 1001 1001 965 Sep 19 2018 ls1043ardb_boot.scr
-rw-rw-r-- 1 1001 1001 965 Sep 19 2018 ls1046ardb_boot.scr
-rw-rw-r-- 1 1001 1001 1031 Sep 19 2018 ls1088ardb_boot.scr
-rw-rw-r-- 1 1001 1001 1037 Sep 19 2018 ls1088ardb_pb_boot.scr
-rw-rw-r-- 1 1001 1001 1031 Sep 19 2018 ls2088ardb_boot.scr
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 lsdk_linux_arm64_tiny.itb
-rw-r--r-- 1 1001 1001 8388608 Sep 19 2018 ramdisk_rootfs_arm64.ext4.gz
drwxrwxr-x 10 1001 1001 4096 Sep 19 2018 secboot_hdrs
-rw-rw-r-- 1 1001 1001 997 Sep 19 2018 srk_hash.txt
-rw-rw-r-- 1 1001 1001 8388608 Sep 19 2018 vmlinuz-4.14.67

/media/steve/misc:
total 16
drwx------ 2 root root 16384 Apr 1 08:59 lost+found

/media/steve/system:
total 96
drwxr-xr-x 2 root root 4096 Oct 17 06:24 bin
drwxr-xr-x 2 root root 4096 Apr 24 2018 boot
drwxr-xr-x 4 root root 4096 Oct 17 06:20 dev
drwxr-xr-x 87 root root 4096 Mar 31 10:34 etc
drwxr-xr-x 3 root root 4096 Oct 17 05:45 home
drwxr-xr-x 3 root root 4096 Oct 17 09:23 include
drwxr-xr-x 16 root root 4096 Mar 31 10:34 lib
drwx------ 2 root root 16384 Apr 1 09:00 lost+found
drwxr-xr-x 2 root root 4096 Oct 17 05:35 media
drwxr-xr-x 2 root root 4096 Oct 17 05:35 mnt
drwxr-xr-x 7 root root 4096 Oct 17 09:23 opt
drwxr-xr-x 2 root root 4096 Apr 24 2018 proc
drwx------ 2 root root 4096 Oct 17 05:35 root
drwxr-xr-x 6 root root 4096 Oct 17 05:57 run
drwxr-xr-x 2 root root 4096 Oct 17 09:23 sbin
drwxr-xr-x 3 root root 4096 Oct 17 09:23 share
drwxr-xr-x 3 root root 4096 Oct 17 06:20 srv
drwxr-xr-x 2 root root 4096 Apr 24 2018 sys
drwxrwxrwt 2 root root 4096 Oct 17 08:16 tmp
drwxr-xr-x 11 root root 4096 Oct 17 05:35 usr
drwxr-xr-x 11 root root 4096 Oct 17 05:35 var

0 Kudos
1 Solution
1,138 Views
ufedor
NXP Employee
NXP Employee

Use pre-built firmware image "firmware_ls1088ardb_pb_uboot_sdboot.img" available for download from:

LSDK Open Source 

section LSDK IMAGES

Create bootable SD card on a Linux PC:

# dd if=firmware_ls1088ardb_pb_uboot_sdboot.img of=/dev/sdb bs=512 seek=8

View solution in original post

2 Replies
1,139 Views
ufedor
NXP Employee
NXP Employee

Use pre-built firmware image "firmware_ls1088ardb_pb_uboot_sdboot.img" available for download from:

LSDK Open Source 

section LSDK IMAGES

Create bootable SD card on a Linux PC:

# dd if=firmware_ls1088ardb_pb_uboot_sdboot.img of=/dev/sdb bs=512 seek=8

1,138 Views
svanderleest
Contributor I

Thank you, that worked and I get the uboot output to serial, up to the BOOTP repeated message. I then tried the flex-installer again, using the firmware image you noted.This time, I see uboot start, and then the Linux kernel starts booting (showing the version 4.14.67, as I expected).  However, it then gets stuck when it tries to mount the root file system:

[ 4.841560] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[ 4.849665] VFS: Mounted root (ext4 filesystem) on device 179:3.
[ 4.856425] devtmpfs: error mounting -2
[ 4.860588] Freeing unused kernel memory: 1344K
[ 4.865180] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

When I put the card in my Linux host machine, it sees multiple partitions, not only the boot partition, but also a system partition (ext4 filesystem), which I can mount and see the standard filesystem I expect, including system/sbin/init.  Any suggestions for why it cannot mount it?

0 Kudos