[参考译文] AM69、无法从 uboot 引导 Linux FS

问题可能在这里

加载"/boot/dtb/ti/k3-am69-sk.dtb "失败
libfdt FDT_check_header ()：FDT_ERR_BADMAGIC
未配置 FDT 存储器地址。 请配置
通过"FDT addr "添加 FDT 地址

此处是来自预构建映像的 env 配置，该映像由 TI 捆绑在 SD 卡中。 但与传统的略有不同、

=> printenv
addr_fit=0x90000000
arch=arm
args_all=setenv optargs earlycon=ns16550a,mmio32,0x02880000 ${mtdparts}
args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}
args_ufs=setenv devtype scsi;setenv bootpart 1:1;run ufs_finduuid;setenv bootargs console = ${console} ${optargs}root=PARTUUID=${uuid} rw rootfstype=${scsirootfstype};setenv devtype scsi;setenv bootpart 1:1
baudrate=115200
board=j784s4
board_name=am69-sk
board_rev=E3
board_serial=0151
board_software_revision=01
boot=mmc
boot_fdt=try
boot_fit=1
boot_rprocs=if test ${dorprocboot} -eq 1 && test ${boot} = mmc; then rproc init;run boot_rprocs_mmc;fi;
boot_rprocs_mmc=env set rproc_id;env set rproc_fw;env set secure_suffix;if test ${boot_fit} -eq 1; then env set secure_suffix -sec;fi;for i in ${rproc_fw_binaries}; do if test -z "${rproc_id}" ; then env set rproc_id $i;else env set rproc_fw $i${secure_suffix};run rproc_load_and_boot_one;env set rproc_id;env set rproc_fw;fi;done
bootcmd=run findfdt; run envboot; run init_${boot}; run main_cpsw0_qsgmii_phyinit; run boot_rprocs; if test ${boot_fit} -eq 1; then run get_fit_${boot}; run get_overlaystring; run run_fit; else; run get_kern_${boot}; run get_fdt_${boot}; run get_overlay_${boot}; run run_kern; fi;
bootdelay=2
bootdir=/boot
bootenvfile=uEnv.txt
bootm_size=0x10000000
bootpart=1:2
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
console=ttyS2,115200n8
cpu=armv8
default_device_tree=k3-j784s4-evm.dtb
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;tiboot3.bin.raw raw 0x0 0x400 mmcpart 1;tispl.bin.raw raw 0x400 0x1000 mmcpart 1;u-boot.img.raw raw 0x1400 0x2000 mmcpart 1;u-env.raw raw 0x3400 0x100 mmcpart 1;sysfw.itb.raw raw 0x3600 0x800 mmcpart 1
dfu_alt_info_mmc=boot part 1 1;rootfs part 1 2;tiboot3.bin fat 1 1;tispl.bin fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1;sysfw.itb fat 1 1
dfu_alt_info_ospi=tiboot3.bin raw 0x0 0x080000;tispl.bin raw 0x080000 0x200000;u-boot.img raw 0x280000 0x400000;u-boot-env raw 0x680000 0x020000;sysfw.itb raw 0x6c0000 0x100000;rootfs raw 0x800000 0x3800000
dfu_alt_info_ram=tispl.bin ram 0x80080000 0x200000;u-boot.img ram 0x81000000 0x400000
do_main_cpsw0_qsgmii_phyinit=1
dorprocboot=0
dtboaddr=0x89000000
envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootscript; then run bootscript;else if run loadbootenv; then echo Loaded env from ${bootenvfile};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;fi;fi;
ethaddr=08:04:b4:2e:8f:2f
fdt_addr_r=0x88000000
fdtaddr=0x88000000
fdtcontroladdr=fdeae070
fdtoverlay_addr_r=0x80200000
findfdt=setenv name_fdt ${default_device_tree};if test $board_name = am69-sk; then setenv name_fdt k3-am69-sk.dtb; fi;if test $board_name = j784s4; then setenv name_fdt k3-j784s4-evm.dtb; fi;setenv fdtfile ${name_fdt}
finduuid=part uuid ${boot} ${bootpart} uuid
get_fdt_mmc=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${name_fdt}
get_fdt_ufs=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
get_fit_mmc=load mmc ${bootpart} ${addr_fit} ${bootdir}/${name_fit}
get_kern_mmc=load mmc ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
get_kern_ufs=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
get_overlay_mmc=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $name_overlays;do;load mmc ${bootpart} ${dtboaddr} ${bootdir}/${overlay} && fdt apply ${dtboaddr};done;
get_overlay_ufs=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $name_overlays;do;load scsi ${bootpart} ${dtboaddr} ${bootdir}/${overlay} && fdt apply ${dtboaddr};done;
get_overlaystring=for overlay in $name_overlays;do;setenv overlaystring ${overlaystring}'#'${overlay};done;
importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${loadaddr} ${filesize}
init_main_cpsw0_qsgmii_phy=gpio set gpio@22_17;gpio clear gpio@22_16
init_mmc=run args_all args_mmc
init_ufs=ufs init; scsi scan; run args_ufs
kernel_addr_r=0x82000000
loadaddr=0x82000000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
loadbootscript=load mmc ${mmcdev} ${loadaddr} boot.scr
loadfdt=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
loadimage=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
main_cpsw0_qsgmii_phyinit=if test ${do_main_cpsw0_qsgmii_phyinit} -eq 1 && test ${dorprocboot} -eq 1 && test ${boot} = mmc; then run init_main_cpsw0_qsgmii_phy; run toggle_mux2_ethfw;fi;
mmcboot=mmc dev ${mmcdev}; devnum=${mmcdev}; devtype=mmc; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadimage; then run args_mmc; if test ${boot_fit} -eq 1; then run run_fit; else run mmcloados;fi;fi;fi;
mmcdev=1
mmcloados=if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdtaddr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcrootfstype=ext4 rootwait
mtdids=nor0=47040000.spi.0,nor0=47034000.hyperbus
mtdparts=mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),256k(ospi.env.backup),57088k@8m(ospi.rootfs),256k(ospi.phypattern);47034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env),-@8m(hbmc.rootfs)
name_fit=fitImage
name_kern=Image
partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=0,size=-,uuid=${uuid_gpt_rootfs}
pxefile_addr_r=0x80100000
ramdisk_addr_r=0x88080000
rd_spec=-
rdaddr=0x88080000
rproc_fw_binaries=2 /lib/firmware/j784s4-main-r5f0_0-fw 3 /lib/firmware/j784s4-main-r5f0_1-fw 4 /lib/firmware/j784s4-main-r5f1_0-fw 5 /lib/firmware/j784s4-main-r5f1_1-fw 6 /lib/firmware/j784s4-main-r5f2_0-fw 7 /lib/firmware/j784s4-main-r5f2_1-fw 8 /lib/firmware/j784s4-c71_0-fw 9 /lib/firmware/j784s4-c71_1-fw 10 /lib/firmware/j784s4-c71_2-fw 11 /lib/firmware/j784s4-c71_3-fw
rproc_load_and_boot_one=if load mmc ${bootpart} $loadaddr ${rproc_fw}; then if rproc load ${rproc_id} ${loadaddr} ${filesize}; then rproc start ${rproc_id};fi;fi
run_fit=bootm ${addr_fit}#${fdtfile}${overlaystring}
run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
scriptaddr=0x80000000
scsirootfstype=ext4 rootwait
serial#=0000000000000151
soc=k3
stderr=serial@2880000
stdin=serial@2880000
stdout=serial@2880000
toggle_mux2_ethfw=gpio set gpio@22_13; gpio set gpio@22_14;gpio set gpio@22_15
ufs_finduuid=part uuid scsi ${bootpart} uuid
update_to_fit=setenv loadaddr ${addr_fit}; setenv bootfile ${name_fit}
vendor=ti

Environment size: 6518/131067 bytes

尊敬的 Marcin：

您是否可以通过将 tiboot3-j784s4-hs-fs-evm.bin 重命名为 tiboot3.bin 来尝试将 tiboot3.bin 替换为 tiboot3-j784s4-hs-fs-evm.bin？

谢谢！

法比亚纳

我已经这么做了、正如我在这里提到的 FS、"我有 HS-FS 板、所以我将 tiboot3-j784s4-hs-fs-evm.bin 和 tiboot3.bin 放置在 SD 卡的引导分区中、它与 hs-fs bin 链接"、因此、基本上我采用了  tiboot3-j784s4-hs-fs-evm.bin 复制它并将副本重命名为 tiboot3.bin、 两个文件都放在 SD 卡上、就像在随电路板提供的 SD 卡上一样。 这意味着它在这里不是解决方案、  

如您所见 、K3-AM69-SK.DTB 位于2个分区上  

ls mmc 1:2
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 bin
<DIR>       4096 boot
<DIR>       4096 dev
<DIR>       4096 etc
<DIR>       4096 home
<DIR>       4096 include
<SYM>         20 init
<DIR>       4096 lib
<SYM>         19 linuxrc
<DIR>       4096 media
<DIR>       4096 mnt
<DIR>       4096 opt
<DIR>       4096 proc
<DIR>       4096 run
<DIR>       4096 sbin
<DIR>       4096 sys
<DIR>       4096 tmp
<DIR>       4096 usr
<DIR>       4096 var
<DIR>       4096 .cache
<DIR>       4096 data
=> ls mmc 1:2 boot
<DIR>       4096 .
<DIR>       4096 ..
<SYM>         26 Image
        19079680 Image-5.10.162-g76b3e88d56
<SYM>         29 fitImage
         8307211 fitImage-5.10.162-g76b3e88d56
            3639 k3-am69-sk-csi2-ov5640.dtbo
           13811 k3-am69-sk-ddr-mem-carveout.dtbo
            3596 k3-am69-sk-fpdlink-fusion.dtbo
            3149 k3-am69-sk-rpi-cam-imx219.dtbo
            1936 k3-am69-sk-rpi-hdr-ehrpwm.dtbo
           90726 k3-am69-sk.dtb
            2471 k3-j721e-fpdlink-imx390-cm-0-0.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-0-1.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-0-2.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-0-3.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-0.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-1.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-2.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-3.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-0.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-1.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-2.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-3.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-0.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-1.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-2.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-3.dtbo
           13306 k3-j784s4-edgeai-apps.dtbo
            1614 k3-j784s4-evm-csi2-ov5640.dtbo
           99385 k3-j784s4-evm.dtb
            3155 k3-j784s4-fpdlink-fusion.dtbo
           14313 k3-j784s4-vision-apps.dtbo 

尊敬的 Marcin：

您使用的是 SK-AM69还是 AM69 EVM？

谢谢！

法比亚纳

SK-AM69、我使用的是 SDK  

TI-PROCESSOR-SDK-LINUX-EDGEAI-J784s4-EVM-09_01_00_06-Linux-x86

我已经决定重新构建内核以便能够访问 dtb 目录，它的问题消失了，但显示了新的  

Working FDT set to 88000000
11348 bytes read in 5 ms (2.2 MiB/s)
10290 bytes read in 5 ms (2 MiB/s)
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
switch to partitions #0, OK
mmc0(part 0) is current device
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
No EFI system partition
No EFI system partition
Failed to persist EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
starting USB...
Bus usb@6000000: cdns-usb3-host usb@6000000: Unable to get USB2 phy (ret -61)
cdns-usb3-host usb@6000000: DRD version v1 (ID: 0004024e, rev: 00000200)
Register 2000840 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus usb@6000000 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:328
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled