[参考译文] SK-AM62B-P1：从 eMMC 引导 SK-AM62B-P1

尊敬的 Mallika：

请按照 AM62 Academy 中提到的步骤进行操作。

https://dev.ti.com/tirex/explore/node?node=A__AdNWBqCVds4ZSqU9osT1tQ__AM62-ACADEMY__uiYMDcq__LATEST

AM62 Academy -> Linux-> Development Linux on TI EVM -> Flash Linux on eMMC 部分应提供所有详细信息。

希望这对您有所帮助

此致、

Suren

您好！  

我尝试过这些步骤、最终得到了以下结果：

root@am62xx-evm：/# dd if=tiboot3.bin of=/dev/mmcblk0boot0 seek=0
DD：无法打开"tiboot3.bin"：没有此类文件或目录


Im 使用 Debian 映像、用于在 SD 卡上进行刷写。

尊敬的 Mallika：

您在 EVM 上的何处复制了 tiboot3.bin 和其他 u-boot 映像？  

u-boot 映像必须首先位于 EVM 上、以便您可以使用 dd 命令。

此致、

Suren

我已将它们安装在这条路径中：

root@am62xx-EVM：~ ls -l /mnt/sdboot
共计3294.
drwxr-xr-x 2 root root 512 Jan 30 2025 'System Volume Information'(系统卷信息)
-rwxr-xr-x 1 root root 12285 12 6 2024 ti_logo_414x97_32bpp.bmp.gz
-rwxr-xr-x 1 root root 294441 DEC 6 2024 tiboot3-am62x-gp-evm.bin
-rwxr-xr-x 1 root root 297030 Dec 6 2024 tiboot3-am62x-hs-evm.bin
-rwxr-xr-x 1 root root 297030 Dec 6 2024 tiboot3-am62x-hs-fs-evm.bin
-rwxr-xr-x 1 root root 297030 Dec 6 2024 tiboot3.bin
-rwxr-xr-x 1根根1159835 12 6 2024 tispl.bin
-rwxr-xr-x 1根根1011971 DEC 6 2024 u-boot.img



我已完成以下步骤：
root@am62xx-evm：/mnt/sdboot dd if=tiboot3.bin of=/dev/mmcblk0boot0 seek=0
580+1记录
580+1记录
297030字节(297KB、290KiB)已复制、0.0229746s、12.9MB/s
root@am62xx-evm：/mnt/sdboot dd if=tispl.bin of=/dev/mmcblk0boot0 seek=1024
2265+1记录了
2265+1记录
1159835字节(1.2 MB、1.1 MIB)已复制、0.0703862 s、16.5 MB/s
root@am62xx-evm：/mnt/sdboot dd if=u-boot.img of=/dev/mmcblk0boot0 seek=5120
1976+1记录
1976+1记录在案
1011971字节(1.0 MB、988 KiB)已复制、0.0616285 s、16.4 Mb/s

现在您能够正确复制它们。

您是否能够继续？

此致、

Suren

我已经使用了指定的所有命令、但在 u-boot 提示符中使用以下命令后：

=> MMC partconf 0 1 1 1
=> MMC bootbus 0 2 0 0 

=> setenv mmcdv 0
=> setenv bootpart 0 

尊敬的 Mallika：

是、在较新的 SDK 中、默认情况下会禁用"saveenv"@u-boot、因为这有时会导致动态引导流程中出现不一致情况。

建议用户根据需要自定义"am62x.env"、并为用户的电路板设计重新编译 u-boot。

例如、"mmcdev/bootpart"

https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env?h=ti-u-boot-2024.04

此致、

当然

我们是否可以使用启动脚本以便作为解决方案自动启动？

尊敬的 Mallika：

您是指 uEnv.txt？

此致、

Suren

是的、我曾尝试创建 boot.txt 文件并创建 boot. src 文件、然后尝试自动运行。
但我遇到了这样的情况：
"源"命令的映像格式错误1脚本就绪 MMC 1 mmc@fa10000.bootdev.part /boot/boot.scr ** mc@fa10000.bootdev.part 使用脚本引导引导流程"源"命令的映像格式错误引导失败(err=1)


我尝试创建了/boot/boot.txt、如下所示：

回显"正在启动 eMMC 引导..."
setenv fdtfile ti/k3-am625-sk.dtb
setenv bootargs console=ttyS2115200n8 root=/dev/mmcblk0p1 rw rootwait
加载 MMC 0：1 $｛kernel_addr_r｝Boot/Image
加载 MMC 0：1 $｛fdtaddr｝boot/dtb/$｛fdtfile｝
booti $｛kernel_addr_r｝-$｛fdtaddr｝



并创建了以下内容：

mkimage -a ARM64 -o Linux -T 脚本-C none -a 0 -e 0 -n "Boot Script"-d /boot/boot.txt /boot/boot.scr



这种方法是否有效？
如果不能、您可以建议我采用新方法

请允许我向我的专家咨询有关上述方法的回复、

与此同时、您是否曾尝试过在 u-boot 中修改 am62x.env、看看它是否有用？

此致、

Suren

在引导提示符下、我可以看到以下内容：
按任意键以停止自动引导：0
切换到分区#0、好
mmc1是当前器件
器件1上的 SD/MMC
加载"uEnv.txt"失败
19849728字节在250毫秒内读取(75.7 MiB/s)
60579字节在31ms 内读取(1.9MiB/s)
工作 FDT 设置为88000000

使用 print env 时、我可以看到在我的控制台中找不到命令

尊敬的 Mallika：

Suren 之前说过、您需要更新 U-Boot board/ti/am62x/am62x.env 中的 env 来进行 eMMC U-Boot 构建是正确的解决方案。 无论使用何种脚本、即使不更新 am62x.env、U-Boot 也会始终尝试从 SD 卡加载脚本、因为为 SD 卡引导预编译的 SDK 中定义了"mmcdev=1"。

嗯、在我签核今天之前、我对它进行了快速测试、将 sin am62x.env 更改、但从 eMMC 引导在 tiboot3.bin 加载 tispl.bin 时失败。 我明天将继续讨论这一问题。

我正在我  的8GB SD 卡上使用此图像 dr-download.ti.com/.../tisdk-debian-trixie-am62xx-evm-10.01.10.04.wic.xz、其中仅列出以下文件：


tiboot3.bin、tispl.bin、u-boot.img、tiboot3-am62-gp、hs、hs-fs bin 文件。
当我以 SD 引导开关模式将 SD 卡插入 EVM 板时、它已引导。

我只想将 DDR abd eMMC 用于我的应用、其中、在 mmcblk0中创建子文件夹、将所有内核文件传输到/boot、并使用这些命令、系统只能从 eMMC 引导一次、从而使电路板必须从 eMMC 引导。

我的文件系统中的任何位置都没有 am62x.env。
感谢您的支持、期待您的回复。

如果我使用 SDK 或以其他方式出错、请在不含 SD 卡的情况下直接引导至 EVM、并从 Linux PC 将引导文件和映像文件直接刷写到 eMMC

现在、只有当我将引导开关保持在 eMMC 模式时、EVM 才会从 SD 卡引导。 我试图闪存另一个也是 Debian 的 SDK、但我遇到 SD 卡 只有在我将引导开关保持在 eMMC 模式下时才在引导、即8-15 (00000000)(0-7)(11010011)

Unknown 说：

在我的文件系统中、任何地方都没有 am62x.env。

am62x.env 位于定义 U-Boot 环境变量的 U-Boot 源代码中。 该文件不在 SD 卡 Debian 中。

我不认为我可以在 AM62x EVM 上重现此问题、我仍然可以更改 eMMC 引导或 SDCARD 引导之间的引导模式切换。

我下星期将不在办公室、但在我回到办公室后、我将继续研究这个问题。

以前,当我尝试在 mmcblk0中刷新所有内容以进行 eMMC 引导时,我更改了 eMMC 的引导开关,从那时起,系统仅在该模式下引导,即使系统是从 SD 卡引导。 总之、我们可以将此引导开关正常复位吗？如果 SD 卡从 eMMC 引导开关模式引导、如果我们希望电路板从 eMMC 引导、会怎样？

谢谢你

尊敬的 Mallika：

我不确定是否能充分理解您的消息、但您需要根据要使用的引导模式(eMMC 或 SDcard)调整 EVM 上的引导模式开关。

您好、Bin、

我已经下载了 SDK (即 ti-processor-sdk-linux-am62xx-EVM-10.01.10.04)、并安装了该 SDK、然后安装./setup.sh、并将以下文件更改为从 mmc0引导、进行以下更改：

#include
#include
#include
#include
#if CONFIG_CMD_REMOTEPROC
#include
#endif

name_kern=图像
console=ttyS2115200n8
args_all=setenv optargs $｛optargs｝earlycon=ns16550a、mmio32、0x02800000
$｛mtdparts｝
run_kern=booti $｛loadaddr｝$｛rd_spec｝$｛fdtaddr｝

boot_targets=mmc1 mmc0 USB PXE DHCP
引导=MMC
mmcdev=0
bootpart=0：2
bootdir=/boot
RD_SPEC=-

splashfile=ti_logo_414x97_32bpp.bmp.gz
splashimage=0x80200000
splashpos=m、m
splashsource=MMC
rproc_fw_binaries = 0 /lib/firmware/am62-mcu-m4f0_0-fw

#if CONFIG_BOOTMETH_Android
#include
FORCE_AVB=0
adtb_idx=0
get_adtb_idx=
如果测试$｛board_name｝= am62x_lp_skevm；那么
setenv adtb_idx 1；
设计
setenv adtb_idx 0；
FI；
bootcmd=运行 get_adtb_idx；引导流程扫描-lb
#endif



将 mmcdev 更改为0后、我已经运行以下指定的命令、用于生成引导加载程序文件：


https://dev.ti.com/tirex/explore/content/am62x_academy_10_00_00_01/am62x_academy_10_00_00_01/source/linux/ch-develop/dev-build-uboot.html

我设置了工具链路径、一切正常：
编译 R5映像成功、但在尝试编译 ARM64映像时、Im 出现以下错误：

CC lib/strto.o
CC lib/abuf.o
CC lib/date.o
CC lib/rtc-lib.o
CC lib/elf.o
ar lib/built-in．o
LD u-boot
/home/optilink/ti-processor-sdk-linux-am62xx-evm-10.01.10.04/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-oe-linux/aarch64-oe-linux-ld.bfd：找不到-lgcc：没有此类文件或目录
make[1]:***[git/Makefile:1766:/home/optilink/ti-processor-sdk-linux-am62xx-evm-10.01.10.04/board-support/ti-u-boot-2024.04 u-boot]错误1.
make[1]：正在离开目录/home/optilink/ti-processor-sdk-linux-am62xx-evm-10.01.10.04/board-support/u-boot-build/a53
make：***[Makefiles:177: sub-make]错误2.

如何继续、进行为 eMMC 引导创建默认引导选项所做的修改是否正确？

这周,他的表现很好。 敬请期待下周的答复。

有人可以协助吗？

尊敬的 Mallika：

在上周糟糕的时候、我曾尝试修改 am62x.env 以直接从 MMC0启动、因此启动会出现问题。 我会研究一下、然后回复给您。

您好、Bin、

我现在可以看到系统可以从 eMMC 引导、但一旦我发出重新引导命令、控制台上就会出现以下提示、提示失败：

root@am62xx-evm:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mtdblock0 31:0 0 512K 0 disk
mtdblock1 31:1 0 2M 0 disk
mtdblock2 31:2 0 4M 0 disk
mtdblock3 31:3 0 256K 0 disk
mtdblock4 31:4 0 256K 0 disk
mtdblock5 31:5 0 55.8M 0 disk
mtdblock6 31:6 0 256K 0 disk
mmcblk0 179:0 0 14.8G 0 disk
`-mmcblk0p1 179:1 0 14.8G 0 part /
mmcblk0boot0 179:32 0 31.5M 1 disk
mmcblk0boot1 179:64 0 31.5M 1 disk
root@am62xx-evm:~# reboot
root@am62xx-evm:~# Stopping Session c6 of User root...
[ OK ] Removed slice Slice /system/modprobe.
[ OK ] Removed slice Slice /system/systemd-coredump.
[ OK ] Stopped target Graphical Interface.
[ OK ] Stopped target Multi-User System.
[ OK ] Stopped target Login Prompts.
[ OK ] Stopped target Host and Network Name Lookups.
[ OK ] Stopped target RPC Port Mapper.
[ OK ] Stopped target Sound Card.
[ OK ] Stopped target Timer Units.
[ OK ] Stopped Daily rotation of log files.
[ OK ] Stopped Daily Cleanup of Temporary Directories.
[ OK ] Stopped target System Time Set.
[ OK ] Stopped target Hardware activated USB gadget.
[ OK ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Stopping Job spooling tools...
Stopping Avahi mDNS/DNS-SD Stack...
Stopping containerd container runtime...
Stopping Periodic Command Scheduler...
Stopping Getty on tty1...
Stopping irqbalance daemon...
Stopping Reboot and dump vmcore via kexec...
Stopping LLDP daemon...
Stopping Netperf Benchmark Server...
Stopping Telephony service...
Stopping PulseAudio Sound System...
[ OK ] Stopped Expand the rootfs partition to full size of the boot device..
Stopping Serial Getty on ttyS2...
Stopping Seva Launcher Service...
Stopping Simple Network Management Protocol (SNMP) Daemon....
Stopping strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf...
Stopping Load/Save OS Random Seed...
Stopping TEE Supplicant on teepriv0...
Stopping Telnet Server...
[ OK ] Stopped Job spooling tools.
[ OK ] Stopped Avahi mDNS/DNS-SD Stack.
[ OK ] Stopped Periodic Command Scheduler.
[ OK ] Stopped irqbalance daemon.
[ OK ] Stopped Telephony service.
[ OK ] Stopped PulseAudio Sound System.
[ OK ] Stopped Seva Launcher Service.
[ OK ] Stopped strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.
[ OK ] Stopped LLDP daemon.
[ OK ] Stopped Netperf Benchmark Server.
[ OK ] Stopped Simple Network Management Protocol (SNMP) Daemon..
[ OK ] Stopped containerd container runtime.
[ OK ] Stopped Getty on tty1.
[ OK ] Stopped Serial Getty on ttyS2.
[ OK ] Stopped TEE Supplicant on teepriv0.
[ OK ] Stopped Reboot and dump vmcore via kexec.
[ OK ] Stopped Load/Save OS Random Seed.
[ OK ] Stopped Telnet Server.
[ OK ] Stopped Session c6 of User root.
[ OK ] Removed slice Slice /system/getty.
[ OK ] Removed slice Slice /system/serial-getty.
[ OK ] Removed slice Slice /system/tee-supplicant.
Stopping Save/Restore Sound Card State...
Stopping User Login Management...
Stopping Permit User Sessions...
Stopping User Manager for UID 0...
[ OK ] Stopped User Manager for UID 0.
[ OK ] Stopped Save/Restore Sound Card State.
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped target Network.
[ OK ] Stopped target Remote File Systems.
Stopping Network Configuration...
Stopping User Runtime Directory /run/user/0...
[ OK ] Stopped User Login Management.
[ OK ] Unmounted /run/user/0.
[ OK ] Stopped Network Configuration.
[ OK ] Stopped User Runtime Directory /run/user/0.
[50600.807552] kauditd_printk_skb: 8 callbacks suppressed
[50600.807574] audit: type=1334 audit(50622.760:39): prog-id=14 op=UNLOAD
[50600.819404] audit: type=1334 audit(50622.760:40): prog-id=17 op=UNLOAD
[ OK ] Removed slice User Slice of UID 0.
[ OK ] Stopped target Preparation for Network.
[ OK ] Stopped IPv6 Packet Filtering Framework.
[ OK ] Stopped IPv4 Packet Filtering Framework.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Path Units.
[ OK ] Stopped Dispatch Password Requests to Console Directory Watch.
[ OK ] Stopped Forward Password Requests to Wall Directory Watch.
[ OK ] Stopped target Slice Units.
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Socket Units.
[ OK ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Closed Docker Socket for the API.
[ OK ] Closed dropbear.socket.
[ OK ] Closed PC/SC Smart Card Daemon Activation Socket.
[ OK ] Closed Network Service Netlink Socket.
Stopping D-Bus System Message Bus...
[ OK ] Stopped Generate network units from Kernel command line.
[ OK ] Stopped D-Bus System Message Bus.
[50601.148738] audit: type=1334 audit(50623.100:41): prog-id=13 op=UNLOAD
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped target System Initialization.
Stopping Network Name Resolution...
Stopping Network Time Synchronization...
Stopping Record System Boot/Shutdown in UTMP...
[ OK ] Stopped Network Name Resolution.
[ OK ] Stopped Network Time Synchronization.
[50601.313615] audit: type=1334 audit(50623.264:42): prog-id=9 op=UNLOAD
[50601.320296] audit: type=1334 audit(50623.264:43): prog-id=8 op=UNLOAD
[ OK ] Stopped Apply Kernel Variables.
[ OK ] Closed Process Core Dump Socket.
[ OK ] Stopped Load Kernel Modules.
[ OK ] Stopped Record System Boot/Shutdown in UTMP.
[ OK ] Stopped Create System Files and Directories.
[ OK ] Stopped target Local File Systems.
Unmounting Temporary Directory /tmp...
Unmounting /var/volatile...
[ OK ] Unmounted Temporary Directory /tmp.
[ OK ] Unmounted /var/volatile.
[ OK ] Stopped target Preparation for Local File Systems.
[ OK ] Stopped target Swaps.
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped Create Static Device Nodes in /dev gracefully.
[ OK ] Reached target System Shutdown.
[ OK ] Reached target Late Shutdown Services.
[ OK ] Finished System Reboot.
[ OK ] Reached target System Reboot.
[50601.745509] audit: type=1334 audit(50623.696:44): prog-id=5 op=UNLOAD
[50601.752049] audit: type=1334 audit(50623.696:45): prog-id=4 op=UNLOAD
[50601.758544] audit: type=1334 audit(50623.696:46): prog-id=3 op=UNLOAD
[50601.765012] audit: type=1334 audit(50623.700:47): prog-id=16 op=UNLOAD
[50601.771551] audit: type=1334 audit(50623.700:48): prog-id=15 op=UNLOAD
[50601.779360] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[50601.786348] watchdog: watchdog0: watchdog did not stop!
[50601.812971] systemd-shutdown[1]: Using hardware watchdog 'K3 RTI Watchdog', version 0, device /dev/watchdog0
[50601.822868] systemd-shutdown[1]: Modifying watchdog hardware timeout is not supported, reusing the programmed timeout.
[50601.833587] systemd-shutdown[1]: Watchdog running with a hardware timeout of 1min.
[50601.858775] systemd-shutdown[1]: Syncing filesystems and block devices.
[50601.883003] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[50601.910375] systemd-journald[125]: Received SIGTERM from PID 1 (systemd-shutdow).
[50601.923360] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[50601.946978] systemd-shutdown[1]: Unmounting file systems.
[50601.955775] (sd-remount)[1710]: Remounting '/' read-only with options ''.
[50602.031370] EXT4-fs (mmcblk0p1): re-mounted ef7d57e6-588a-4385-9429-4fd97d50aa22 ro. Quota mode: none.
[50602.058656] systemd-shutdown[1]: All filesystems unmounted.
[50602.064403] systemd-shutdown[1]: Deactivating swaps.
[50602.069769] systemd-shutdown[1]: All swaps deactivated.
[50602.075020] systemd-shutdown[1]: Detaching loop devices.
[50602.085997] systemd-shutdown[1]: All loop devices detached.
[50602.091715] systemd-shutdown[1]: Stopping MD devices.
[50602.097177] systemd-shutdown[1]: All MD devices stopped.
[50602.102693] systemd-shutdown[1]: Detaching DM devices.
[50602.108332] systemd-shutdown[1]: All DM devices detached.
[50602.113748] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[50602.123405] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[50602.130292] systemd-shutdown[1]: Failed to disable hardware watchdog, ignoring: Device or resource busy
[50602.139683] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[50602.146546] watchdog: watchdog0: watchdog did not stop!
[50602.157922] systemd-shutdown[1]: Syncing filesystems and block devices.
[50602.164826] systemd-shutdown[1]: Rebooting.
[50602.197659] reboot: Restarting system

尊敬的 Mallika：

Unknown 说：

我现在可以看到系统可以从 eMMC 引导

您的意思是您现在可以直接引导至 Linux 而无需在 U-Boot 提示符中键入以下两个命令吗？

=> setenv mmcdv 0
=> setenv bootpart 0 

如果是、您为消除此手动步骤做出了哪些更改？

我在 U-Boot 提示符下给出了以下命令：
=> MMC partconf 0 1 1 1
=> MMC bootbus 0 2 0 0

已将引导开关运行至 eMMC 并移除 SD 卡。
系统已从 eMMC 引导、并使用的命令(lsblk)验证了此情况。

我尝试从命令行重新启动系统、但没有发生、并且冻结、 附带了上述提示。