[参考译文] AM625：无法使用 MCU+SDK v9.02刷写 SBL

您好！

请使用未修改的 `default_sbl_emc_linux.cfg`、如下所示

~/ti/mcu_plus_sdk/am62x/09_02_00_38/tools/boot
❯ /usr/bin/cat sbl_prebuilt/am62x-sk/default_sbl_emmc_linux.cfg
#-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                                                                             #
#-----------------------------------------------------------------------------#
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this EVM
# - The application image points to relative path of the ipc rpmsg linux application image for this EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify-emmc if you just want to verify the flash contents and not flash the file.
#


# First point to sbl_uart_uniflash_stage1 binary, which initialises DDR and receives sbl_uart_uniflash_stage2 binary
--flash-writer=sbl_prebuilt/am62x-sk/sbl_uart_uniflash_stage1.release.tiimage

# When sending sbl_uart_uniflash_stage2 binary make sure to flash at SOC memory offset 0x0.
# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
--file=../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage --operation=flash --flash-offset=0x0

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0 of eMMC
--file=sbl_prebuilt/am62x-sk/sbl_emmc_linux_stage1.release.tiimage --operation=flash-emmc --flash-offset=0x0

# 2nd stage bootloader is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage --operation=flash-emmc --flash-offset=0x80000

# When sending application image, make sure to flash at offset 0x100000 (default) or to whatever offset your bootloader is configured for
--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/m4fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage --operation=flash-emmc --flash-offset=0x100000

# HSM image is flashed at 0x800000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/HSMAppimageGen/board/am62x-sk/hsm.appimage --operation=flash-emmc --flash-offset=0x800000

# DM image is flashed at 0xa00000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage --operation=flash-emmc --flash-offset=0xA00000

# Linux image is flashed at 0xC00000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/linux.appimage --operation=flash-emmc --flash-offset=0xC00000

# u-boot.img is flashed at 0x280000
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/u-boot.img --operation=flash-emmc --flash-offset=0x280000

此外、请注意、从 MCU+ SDK v9.0开始、我们不支持 GP 器件。 因此、如果即使在使用正确的配置文件后仍无法进行刷写、我们将无法支持它。

此致、

普拉桑特

您好！

请注意，从 MCU+SDK v9.0开始，我们不支持 GP 设备。 因此,如果在使用正确的配置文件后刷写失败,我们将无法支持它。[/报价]

1.在本例中、我需要首先迁移到 HS-SBL 或 HS-SE 器件、然后尝试运行 FS 闪存。 我对吗？

2.如果无法在 GP 设备中刷写 SBL，那么如何使用 Falcon 模式来优化引导时间？

谢谢。此致、
Aditya T

您好！

是。 请注意、GP 器件无法转换为 FS 或 HS-SE 器件。 HS 器件以 HS-SE FS 状态发货(由 TI)、稍后转换为 HS-SE (由客户)。

如果无法实现、则 TI 文档中提供了相关链接： 链接为 GP 到 HS-EVM FS 迁移指南。

我没有说你不能。 您可以尝试使用正确的配置文件进行刷写。 如果它成功闪烁,一切都启动良好,那么它是伟大的,否则我们将在支持限制。

那么、您能否为我的案例指导哪个是正确的配置文件？

谢谢。此致、
Aditya T