[参考译文] J722SXH01EVM：使用 SPI 的 Falcon 引导

您好！

我还没有试过 J722S 上的猎鹰。

首先、如果您已移植：

diff --git a/board/ti/j721s2/evm.c b/board/ti/j721s2/evm.c
index eea2c256b3..ce3ff90c97 100644
--- a/board/ti/j721s2/evm.c
+++ b/board/ti/j721s2/evm.c
@@ -107,6 +107,8 @@ static void __maybe_unused detect_enable_spinand(void *blob)
 #if defined(CONFIG_SPL_BUILD)
 void spl_perform_fixups(struct spl_image_info *spl_image)
 {
+       return;
+

我在 j722s 中没有看到类似的函数： https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/j722s/evm.c?h=ti-u-boot-2023.04

因此、我认为、移植这些版本需要有所不同。

您是否可以确保已加载 tispl.bin？ 我想知道故障是在执行 tispl.bin 时还是在加载之前。

-基尔西

Keerthy、您好！

我已经找到并更改了此内容：

diff --git a/board/ti/j722s/evm.c b/board/ti/j722s/evm.c
index 0194873f..9eb28ecd 100644
--- a/board/ti/j722s/evm.c
+++ b/board/ti/j722s/evm.c
@@ -105,6 +105,7 @@ static void __maybe_unused detect_enable_spinand(void *blob)
 #if defined(CONFIG_SPL_BUILD)
 void spl_perform_fixups(struct spl_image_info *spl_image)
 {
+       return;
        detect_enable_spinand(spl_image->fdt_addr);
 }
 #endif

我应用了另一论坛帖子中随附的 SPI 补丁、因此这就是该代码存在的原因。 请参阅随附的。

我发现代码在调用中卡住：
SPL_LOAD_FIT_IMAGE (信息、扇区、&ctx、节点、spl_image)；

最终、它会调用挂起的以下命令：
info->read (info、sector + get_aligned_image_offset (info、offset)、nr_sectors、src_ptr)！= nr_sectors

我 从另一个论坛帖子中注意到 src_ptr 与来自 tispl.its_lin 的 bl31.bin 的值相同。 因此、可能无法访问将信息存储到0x70000000、或导致某种 CPU 异常。

将 load 和 entry 设置为 0x9e780000可使其进一步运行、但现在它仍然无法执行以下打印操作：

U-Boot SPL 2023.04-00006-g96c6cb64-dirty (Jun 19 2024 - 11:25:09 -0500)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--w2023.01-j722s (Kool Koa')
SPL initial stack usage: 17064 bytes
Trying to boot from SPI
External data: dst=9e780000, offset=564, size=cef0
Image OS is ARM Trusted Firmware
spl_load_simple_fit[760]:spl_fit_image_get_os=25
External data: dst=9e800000, offset=d454, size=74d48
External data: dst=89000000, offset=8219c, size=20f30
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
External data: dst=82000000, offset=131dacc, size=11712
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
External data: dst=80080000, offset=a30cc, size=127aa00
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
NOTICE:  Upgrade Firmwares for Power off functionality
ERROR:   Failed to get response (-19)
ERROR:   Transfer send failed (-19)
ERROR:   Unable to query firmware capabilities (-19)

/dts-v1/;

/ {
	description = "Configuration to load ATF and SPL";
	#address-cells = <1>;

	images {
		atf {
			description = "ARM Trusted Firmware";
			data = /incbin/("bl31.bin");
			type = "firmware";
			arch = "arm64";
			compression = "none";
			os = "arm-trusted-firmware";
			load = <0x9e780000>;
			entry = <0x9e780000>;
		};
		tee {
			description = "OPTEE";
			data = /incbin/("bl32.bin");
			type = "tee";
			arch = "arm64";
			compression = "none";
			os = "tee";
			load = <0x9e800000>;
			entry = <0x9e800000>;
		};
		dm {
			description = "DM binary";
			data = /incbin/("ti-dm/j722s/ipc_echo_testb_mcu1_0_release_strip.xer5f");
			type = "firmware";
			arch = "arm32";
			compression = "none";
			os = "DM";
			load = <0x89000000>;
			entry = <0x89000000>;
		};
		kernel {
			description = "Linux Kernel (64-bit)";
			data = /incbin/("Image");
			type = "standalone";
			os = "Linux";
			arch = "arm64";
			compression = "none";
			load = <0x80080000>;
			entry = <0x80080000>;
		};
		fdt {
			description = "k3-j722s-evm";
			data = /incbin/("k3-j722s-evm.dtb");
			type = "standalone";
			arch = "arm";
			compression = "none";
			load = <0x82000000>;
			entry = <0x82000000>;
		};
	};
	configurations {
		default = "k3-j722s-evm.dtb";

		k3-j722s-evm.dtb {
			description = "k3-j722s-evm";
			firmware = "atf";
			loadables = "tee", "dm", "fdt", "kernel";
		};
	};
};

diff --git a/configs/j722s_evm_r5_defconfig b/configs/j722s_evm_r5_defconfig
index 0f9828d2..85ce04cd 100644
--- a/configs/j722s_evm_r5_defconfig
+++ b/configs/j722s_evm_r5_defconfig
@@ -24,7 +24,7 @@ CONFIG_DA8XX_GPIO=y
 CONFIG_DM_PCA953X=y
 CONFIG_SPL_DM_PCA953X=y
 CONFIG_OF_BOARD_SETUP=y
-CONFIG_SPL_STACK_R_ADDR=0x82000000
+CONFIG_SPL_STACK_R_ADDR=0x89000000
 CONFIG_SPL_SYS_MALLOC_F_LEN=0x8000
 CONFIG_SPL_NAND_SPI_SUPPORT=y
 CONFIG_SPL_MTD_SUPPORT=y
@@ -36,7 +36,7 @@ CONFIG_SPL_LIBDISK_SUPPORT=y
 CONFIG_SPL_SPI_FLASH_SUPPORT=y
 CONFIG_SPL_SPI=y
 CONFIG_SPL_LOAD_FIT=y
-CONFIG_SPL_LOAD_FIT_ADDRESS=0x80080000
+CONFIG_SPL_LOAD_FIT_ADDRESS=0x84000000
 # CONFIG_DISPLAY_CPUINFO is not set
 CONFIG_SPL_SIZE_LIMIT_SUBTRACT_GD=y
 CONFIG_SPL_SIZE_LIMIT_SUBTRACT_MALLOC=y
@@ -52,7 +52,7 @@ CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x200000
 CONFIG_SPL_SEPARATE_BSS=y
 CONFIG_SYS_SPL_MALLOC=y
 CONFIG_HAS_CUSTOM_SPL_MALLOC_START=y
-CONFIG_CUSTOM_SYS_SPL_MALLOC_ADDR=0x84000000
+CONFIG_CUSTOM_SYS_SPL_MALLOC_ADDR=0x90000000
 CONFIG_SYS_SPL_MALLOC_SIZE=0x1000000
 CONFIG_SPL_EARLY_BSS=y
 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR=y
@@ -145,3 +145,5 @@ CONFIG_SPL_TIMER=y
 CONFIG_OMAP_TIMER=y
 CONFIG_LIB_RATIONAL=y
 CONFIG_SPL_LIB_RATIONAL=y
+CONFIG_TEXT_BASE=0x83000000
+CONFIG_SYS_LOAD_ADDR=0x84000000
\ No newline at end of file

我 从另一个论坛帖子中注意到 src_ptr 与来自 tispl.its_lin 的 bl31.bin 的值相同。 因此、可能无法访问将信息存储到0x70000000、或导致某种 CPU 异常。

将 load 和 entry 设置为 0x9e780000可使其进一步运行、但现在它仍然无法执行以下打印操作：

这很好！ 是的、J722S 的 ATF 加载地址是不同的。 因此、现在您能够加载 ATF。 ATF 正在执行。
您能否将日志与默认引导日志进行比较、并在 ATF 中检查故障位置？

-基尔西