LayerscapeのトピックRe: LX2160ARDB-Rev2 Bad Linux ARM64 Image Magic

LX2160ARDB-Rev2 Bad Linux ARM64 Image Magic

acmitch — Tue, 12 Dec 2023 20:28:05 GMT

I am trying to bring up an LX2160A-RDB-B that I just received (presuming that means rev2). I set up a Ubuntu 22.04 VM, installed the tools and used bitbake to make these images: boot_lx2160ardb-rev2_lts_6.1.tgz, ls-image-main-lx2160ardb-rev2.tar.gz, and lx2160ardb-rev2/firmware_lx2160ardb-rev2_uboot_sdboot.img in the build_lx2160ardb-rev2/tmp/deploy/images/ directory. I then used tinyLinux and flex_installer to format and download the images to both a SATA HD and when that didn't work, the supplied SD Card.

flex-installer -i pf -d /dev/sda

flex-installer -b boot_lx2160ardb-rev2_lts_6.1.tgz -r ls-image-main-lx2160ardb-rev2.tar.gz -f firmware_lx2160ardb-rev2_uboot_sdboot.img -d /dev/sda

flex-installer -i pf -d /dev/mmcblk0

flex-installer -b boot_lx2160ardb-rev2_lts_6.1.tgz -r ls-image-main-lx2160ardb-rev2.tar.gz -f firmware_lx2160ardb-rev2_uboot_sdboot.img -d /dev/mmcblk0

Neither image boots, the relevant console output is

Device 0: unknown device

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0:1…

Scanning mmc 0:2…

Found U-Boot script /lx2160ardb_boot.scr

980 bytes read in 12 ms (79.1 KiB/s)

## Executing script at 80000000

Bad Linux ARM64 Image magic!

SCRIPT FAILED: continuing…

Scanning mmc 0:3…

Scanning mmc 0:4…

switch to partitions #0, OK

mmc1(part 0) is current device

** No partition table - mmc 1 **

scanning bus for devices…

Target spinup took 0 ms.

AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode

flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst

Device 0: (0:0) Vendor: ATA Prod.: Samsung SSD 870 Rev: SVT0

Type: Hard Disk

Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

SATA link 0 timeout.

AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode

flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst

SATA link 0 timeout.

AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode

flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst

SATA link 0 timeout.

AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode

flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst

Device 0: (0:0) Vendor: ATA Prod.: Samsung SSD 870 Rev: SVT0

Type: Hard Disk

Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

… is now current device

Scanning scsi 0:1…

Scanning scsi 0:2…

Found U-Boot script /lx2160ardb_boot.scr

980 bytes read in 5 ms (191.4 KiB/s)

## Executing script at 80000000

Bad Linux ARM64 Image magic!

SCRIPT FAILED: continuing…

Re: LX2160ARDB-Rev2 Bad Linux ARM64 Image Magic

acmitch — Tue, 12 Dec 2023 20:36:29 GMT

The SATA partitions contain these files:

root@TinyLinux:~# ls -l /mnt/*

/mnt/sda1:

total 16

drwx——— 2 root root 16384 Aug 23 17:15 lost+found




/mnt/sda2:

total 59712

-rw-r———r——— 1 1000 1000 45070848 Dec 12  2023 Image

-rw-r———r——— 1 1000 1000 15898458 Dec 12  2023 Image.gz

-rw-r———r——— 1 1000 1000    33525 Dec 12  2023 fsl-lx2160a-qds-lx2160ardb-rev2.dtb

-rw-r———r——— 1 1000 1000    33525 Dec 12  2023 fsl-lx2160a-qds.dtb

-rw-r———r——— 1 1000 1000    34234 Dec 12  2023 fsl-lx2160a-rdb-lx2160ardb-rev2.dtb

-rw-r———r——— 1 1000 1000    34234 Dec 12  2023 fsl-lx2160a-rdb.dtb

drwx——— 2 root root    16384 Aug 23 17:15 lost+found

-rw-r———r——— 1 1000 1000      980 Dec 12  2023 lx2160ardb_boot.scr

drwxr-xr-x 3 1000 1000     4096 Sep  4  2023 modules




/mnt/sda3:

total 16

drwx——— 2 root root 16384 Aug 23 17:16 lost+found




/mnt/sda4:

total 878956

lrwxrwxrwx  1 root root         7 Aug 27 18:37 bin -> usr/bin

drwxr-xr-x  2 root root      4096 Aug 27 18:37 boot

-rw-r———r———  1 root root  79345412 Aug 27 16:50 boot_lx2160ardb-rev2_lts_6.1.tgz

drwxr-xr-x  2 root root      4096 Mar  9  2018 dev

drwxr-xr-x 97 root root      4096 Aug 27 18:37 etc

-rw-r———r———  1 root root  57551852 Aug 27 18:18 firmware_lx2160ardb-rev2_uboot_sdboot.img

drwxr-xr-x  3 root root      4096 Aug 27 18:37 home

lrwxrwxrwx  1 root root         7 Aug 27 18:37 lib -> usr/lib

drwx———  2 root root     16384 Aug 23 17:16 lost+found

-rw-r———r———  1 root root 763064905 Aug 27 16:49 ls-image-main-lx2160ardb-rev2.tar.gz

drwxr-xr-x  2 root root      4096 Mar  9  2018 media

drwxr-xr-x  2 root root      4096 Mar  9  2018 mnt

drwxr-xr-x  2 root root      4096 Mar  9  2018 opt

drwxr-xr-x  2 root root      4096 Mar  9  2018 proc

drwx———  2 root root      4096 Aug 27 18:37 root

drwxr-xr-x  7 root root      4096 Aug 27 18:37 run

lrwxrwxrwx  1 root root         8 Aug 27 18:37 sbin -> usr/sbin

drwxr-xr-x  2 root root      4096 Mar  9  2018 srv

drwxr-xr-x  2 root root      4096 Mar  9  2018 sys

drwxrwxrwt  4 root root      4096 Aug 27 18:37 tmp

drwxr-xr-x 12 root root      4096 Aug 27 18:37 usr

drwxr-xr-x 12 root root      4096 Aug 27 18:37 var




root@TinyLinux:/mnt/sda2# cat /mnt/sda2/lx2160ardb_boot.scr 

‘VN aM›žð”
ôŒ

env exists dtb || setenv dtb fsl-lx2160a-rdb.dtb;env exists kernel_image || setenv kernel_image Image;env exists devpart_boot || setenv devpart_boot 1;env exists devpart_root || setenv devpart_root 4;part uuid $devtype $devnum:$devpart_root partuuidr;setenv bootargs console=ttyAMA0,115200 earlycon=pl011,mmio32,0x21c0000 root=PARTUUID=$partuuidr rw rootwait pci=pcie_bus_perf $othbootargs;load $devtype $devnum:$devpart_boot $kernel_addr_r $kernel_image;load $devtype $devnum:$devpart_boot $fdt_addr_r $dtb;env exists secureboot && echo validating secureboot && run secureboot_validate;booti $kernel_addr_r - $fdt_addr_r

Re: LX2160ARDB-Rev2 Bad Linux ARM64 Image Magic

yipingwang — Fri, 15 Dec 2023 10:19:13 GMT

Please make sure that you are using the correct flex-installer script.

$ git clone https://github.com/nxp-imx/meta-nxp-desktop.git -b
lf-6.1.36-2.1.0-mickledore
$ cp meta-nxp-desktop/scripts/flex-installer_1.14.2110.lf /usr/bin/flexinstaller
$ sudo chmod a+x /usr/bin/flex-installer
$ which flex-installer

Re: LX2160ARDB-Rev2 Bad Linux ARM64 Image Magic

acmitch — Sat, 16 Dec 2023 13:03:23 GMT

I was running on the tinyLinux from the on-board flash and could not easily run flex-installer on the host. I copied the latest flex-installer and the previously build images to the tinyLinux ramdisk in the root home directory and ran flex-installer from there. Both the SD-card and SATA disk are booting.