Device tree Error log

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

Device tree Error log

Jump to solution
2,385 Views
Ghouse
Contributor V

Hi, iam using a custom board based on LS1046ardb,

on boot iam getting following Device tree error log, please let me what to do.

scanning bus for devices...
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: unknown device
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk esdhc@1560000.blk...
Found 5 disks
No EFI system partition
ERROR: invalid device tree
Scanning mmc 0:2...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
ERROR: invalid device tree
Scanning mmc 0:3...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
ERROR: invalid device tree
Scanning mmc 0:4...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
ERROR: invalid device tree

 

Thank you.

Tags (1)
0 Kudos
1 Solution
2,362 Views
yipingwang
NXP TechSupport
NXP TechSupport

As you can see, the second partition of SD card is empty, so you will get the error when booting.

Please try to execute the following command on your PC to deploy image to SD card.

$ flex-installer -i pf -d <device>

$ flex-installer -b boot_LS_arm64_lts_5.10.tgz -r rootfs_lsdk2108_ubuntu_main_arm64.tgz -d /dev/sdx

In the above command, the SD storage drive in the Linux PC is detected as /dev/sdX, where X is a letter such as a, b, c. Make sure to choose the correct device name.

If your problem persists, would you please provide your console log running "flex-installer" command?

 

View solution in original post

3 Replies
2,373 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please run the following command to check whether then second partition of your MMC/SD card contains the following files.(Image, fsl-ls1046a-rdb-sdk.dtb and ls1046ardb_boot.scr)

=> ext2ls mmc 0:2
<DIR> 4096 .
<DIR> 4096 ..
36 buildinfo
251424 config-5.10.35
14660 fsl-ls1012a-2g5rdb.dtb
15983 fsl-ls1012a-frdm.dtb
16022 fsl-ls1012a-frwy.dtb
14598 fsl-ls1012a-oxalis.dtb
16669 fsl-ls1012a-qds.dtb
14690 fsl-ls1012a-rdb.dtb
35290 fsl-ls1028a-kontron-kbox-a-230-ls.dtb
33370 fsl-ls1028a-kontron-sl28.dtb
33563 fsl-ls1028a-kontron-sl28-var2.dtb
35267 fsl-ls1028a-kontron-sl28-var3-ads2.dtb
34129 fsl-ls1028a-kontron-sl28-var4.dtb
2354 fsl-ls1028a-qds-13bb.dtb
2198 fsl-ls1028a-qds-65bb.dtb
1711 fsl-ls1028a-qds-7777.dtb
2143 fsl-ls1028a-qds-85bb.dtb
1620 fsl-ls1028a-qds-899b.dtb
1640 fsl-ls1028a-qds-9999.dtb
34636 fsl-ls1028a-qds.dtb
31778 fsl-ls1028a-rdb-dpdk.dtb
32751 fsl-ls1028a-rdb.dtb
41902 fsl-ls1043a-qds.dtb
43617 fsl-ls1043a-qds-sdk.dtb
38066 fsl-ls1043a-rdb.dtb
39769 fsl-ls1043a-rdb-sdk.dtb
41415 fsl-ls1043a-rdb-usdpaa.dtb
37038 fsl-ls1046a-frwy.dtb
38901 fsl-ls1046a-frwy-sdk.dtb
40295 fsl-ls1046a-frwy-usdpaa.dtb
41356 fsl-ls1046a-qds.dtb
43103 fsl-ls1046a-qds-sdk.dtb
37414 fsl-ls1046a-rdb.dtb
39209 fsl-ls1046a-rdb-sdk.dtb
40771 fsl-ls1046a-rdb-usdpaa.dtb
41875 fsl-ls1046a-rdb-usdpaa-shared.dtb
24876 fsl-ls1088a-qds.dtb
25505 fsl-ls1088a-rdb.dtb
33652 fsl-ls2080a-qds.dtb
32971 fsl-ls2080a-rdb.dtb
30453 fsl-ls2080a-simu.dtb
31424 fsl-ls2081a-rdb.dtb
33556 fsl-ls2088a-qds.dtb
33155 fsl-ls2088a-rdb.dtb
40976 fsl-lx2160a-clearfog-cx.dtb
40972 fsl-lx2160a-honeycomb.dtb
42506 fsl-lx2160a-qds.dtb
41849 fsl-lx2160a-rdb.dtb
43582 fsl-lx2162a-qds.dtb
<DIR> 4096 grub
2176 hdr_ls1012afrwy_bs.out
2176 hdr_ls1012ardb_bs.out
2176 hdr_ls1028ardb_bs.out
2176 hdr_ls1043ardb_bs.out
2176 hdr_ls1046afrwy_bs.out
2176 hdr_ls1046ardb_bs.out
2176 hdr_ls1088ardb_bs.out
2176 hdr_ls2088ardb_bs.out
2176 hdr_lx2160ardb_bs.out
2176 hdr_lx2162aqds_bs.out
41159168 Image
15185058 Image.gz
964 ls1012afrwy_boot.scr
962 ls1012ardb_boot.scr
1038 ls1028ardb_boot.scr
965 ls1043ardb_boot.scr
968 ls1046afrwy_boot.scr
965 ls1046ardb_boot.scr
961 ls1088ardb_boot.scr
961 ls2088ardb_boot.scr
37724135 lsdk2108_yocto_tiny_LS_arm64.itb
980 lx2160ardb_boot.scr
980 lx2162aqds_boot.scr
<DIR> 4096 modules
<DIR> 4096 secboot_hdrs
992 srk_hash.txt
<DIR> 4096 tools
15185058 vmlinuz-5.10.35
=>

In flex-builder build environment, please execute the following command to generate  boot_LS_arm64_lts_5.10.tgz.

$ flex-builder -i mkboot

$ wget https://www.nxp.com/lgfiles/sdk/lsdk2108/rootfs_lsdk2108_ubuntu_main_arm64.tgz

Deploy images to images to eMMC/SD device.

$ flex-installer -b boot_LS_arm64_lts_5.10.tgz -r rootfs_lsdk2108_ubuntu_main_arm64.tgz -d /dev/sdx

 

0 Kudos
2,370 Views
Ghouse
Contributor V

Hi,

Thank for the reply,

Following is the result of the command u suggested

=> ext2ls mmc 0:2
<DIR> 4096 .
<DIR> 4096 ..
<DIR> 16384 lost+found
=> ext2ls mmc 0:2
<DIR> 4096 .
<DIR> 4096 ..
<DIR> 16384 lost+found

I have also tried the commands

$ flex-builder -i mkboot and

$ flex-installer -b boot_LS_arm64_lts_5.10.tgz -r rootfs_lsdk2108_ubuntu_main_arm64.tgz -d /dev/sdx

But iam getting the same error (Device tree error), please suggest what should be done.

Please note that iam trying to boot from an SD card

Thank u.

 

0 Kudos
2,363 Views
yipingwang
NXP TechSupport
NXP TechSupport

As you can see, the second partition of SD card is empty, so you will get the error when booting.

Please try to execute the following command on your PC to deploy image to SD card.

$ flex-installer -i pf -d <device>

$ flex-installer -b boot_LS_arm64_lts_5.10.tgz -r rootfs_lsdk2108_ubuntu_main_arm64.tgz -d /dev/sdx

In the above command, the SD storage drive in the Linux PC is detected as /dev/sdX, where X is a letter such as a, b, c. Make sure to choose the correct device name.

If your problem persists, would you please provide your console log running "flex-installer" command?