[参考译文] PROCESSOR-SDK-AM62P：编译 TI boot3 启动错误

尊敬的 Pu Jia：

您是否可以按照说明使用顶级 makefile 来构建 u-boot、并看看这样是否有助于创建 bootimage tiboot3.bin 映像。

https://software-dl.ti.com/processor-sdk-linux/esd/AM62PX/latest/exports/docs/linux/Overview/Top_Level_Makefile．html

下载 Processor SDK 安装程序二进制文件后、发出 make u-boot 应该能够在 output directory/r5 文件夹中创建 tiboot3.bin。

请告诉我该怎么做。

此致、

Suren

是的、我使用本指南构建 R5 引导加载程序。 全部制作&&制作 u-boot-R5。 现在我尝试将 defconfig 更改回默认值、img 正在工作、我尝试使用早期启动界面构建 uboot、您能提供指南吗？  

您好：  

明白了、 如果可以在 R5 SPL 中执行操作、早期启动画面是在 A53 SPL 中？

尊敬的 Pu Jia：

您使用 SPL 引导流程并希望在 R5 SPL 中执行启动操作的原因是什么？  在我们的 SBL 引导流程中、我们已经支持 R5 SPL 上的 DSS、这将允许提前启动。

请检查以下链接：

https://www.ti.com/lit/an/spradk8/spradk8.pdf

SBL 引导流程：

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/11_01_00_16/exports/docs/api_guide_am62px/index.html

https://www.ti.com/tool/download/MCU-PLUS-SDK AM62P/11.01.00.16

此致、

Suren

你好, Suren Porwar,

现在、我们计划先使用 Falcon 模式启动 EVM、然后是 MCU SDK、

我想在 MCU_R5_NORTOS 中添加 bmp 启动画面吗？

尊敬的 Pu Jia：

请按照 MCU+SDK 文档中提供的说明进行操作。

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/11_01_00_16/exports/docs/api_guide_am62px/EXAMPLES_DRIVERS_DSS_DISPLAY_SHARE.html

如果您有任何问题、请告诉我。

此致、

Suren

您好、Suren Porwar

演示运行正常、但我有一些问题：

1.演示应用程序是构建 stage2 SBL 加载器吗?

2、图标闪烁前仍有闪屏标志,何时以及如何加载闪屏?

3.闪存至 eMMC 时,无法加载操作系统内核。 有一些奇怪的是从 eMMC 加载在第 1 阶段、但加载第 2 阶段在 OSPI 中、然后我不知道它是如何运行的

### ERROR ### Please RESET the board ###
[BOOTLOADER_PROFILE] Boot Media       : eMMC
[BOOTLOADER_PROFILE] Boot Media Clock : 200.000 MHz
[BOOTLOADER_PROFILE] Boot Image Size  : 1310 KB
[BOOTLOADER_PROFILE] Cores present    :
wkup-r5f0-0
[BOOTLOADER PROFILE] System_init                      :      38786us
[BOOTLOADER PROFILE] Board_init                       :          0us
[BOOTLOADER PROFILE] Drivers_open                     :          0us
[BOOTLOADER PROFILE] SBL Drivers_open                 :      20410us
[BOOTLOADER PROFILE] Board_driversOpen                :          0us
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :      22789us
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      81987us

Image loading done, switching to application ...
Starting 2nd stage bootloader
erver..... PASSED
Configure DSS region firewall... DONE !!!
Configure DSS framebuffer region firewall... DONE !!!
[BOOTLOADER_PROFILE] Boot Media       : FLASH
[BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz
[BOOTLOADER_PROFILE] Boot Image Size  : 903 KB
[BOOTLOADER_PROFILE] Cores present    :
hsm-m4f0-0
mcu-r5f0-0
a530-0
[BOOTLOADER PROFILE] System_init                      :       7101us
[BOOTLOADER PROFILE] Board_init                       :          6us
[BOOTLOADER PROFILE] FreeRtosTask Create              :        269us
[BOOTLOADER PROFILE] SBL Drivers_open                 :       1369us
[BOOTLOADER PROFILE] SBL Board_driversOpen            :       7853us
[BOOTLOADER PROFILE] HSM Image Load                   :       3849us
[BOOTLOADER PROFILE] MCU R5 Image Load                :       4251us
[BOOTLOADER PROFILE] A53 Image Load                   :      12148us
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      36849us

Image loading done, switching to application ...
Starting linux and RTOS/Baremetal applications
NOTICE:  BL31: v2.12.0(release):11.00.08-1-gb11beb2b6-dirty
NOTICE:  BL31: Built : 12:35:58, Mar 24 2025

这里是闪存配置：

#-----------------------------------------------------------------------------#
#                                                                             #
#      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 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/am62px-sk/sbl_uart_uniflash_stage1.release.hs_fs.tiimage

# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
# Please note this binary is copied to DDR by sbl_uart_uniflash_stage1 and not written to any boot media like flash or eMMC
--file=../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62px-sk/wkup-r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage.hs_fs --operation=flash --flash-offset=0x0

#--operation=flash-phy-tuning-data
# 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=../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage1/am62px-sk/wkup-r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage1.release.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0


# 2nd stage bootloader with DM is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file="C:/Users/uidk9830/workspace_ccstheia/dss_display_share_am62px-sk_wkup-r5fss0-0_freertos_ti-arm-clang/Debug/dss_display_share_am62px-sk_wkup-r5fss0-0_freertos_ti-arm-clang.appimage.hs_fs" --operation=flash-emmc --flash-offset=0x80000

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

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

# QNX image is flashed at 0x1200000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/qnxAppimageGen/board/am62px-sk/qnx.appimage.hs_fs --operation=flash-emmc --flash-offset=0x280000

您好、

您是否尝试使用双引导介质 (OSPI 和 eMMC) 运行？ 或仅 eMMC。

此致、

Suren

您好团队

否、现在我尝试更改了 SysConfig 中的 demo dss_display_share 设置、以将所有启动设置为 eMMC：

和闪存配置文件：

#-----------------------------------------------------------------------------#
#                                                                             #
#      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 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/am62px-sk/sbl_uart_uniflash_stage1.release.hs_fs.tiimage

# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
# Please note this binary is copied to DDR by sbl_uart_uniflash_stage1 and not written to any boot media like flash or eMMC
--file=../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62px-sk/wkup-r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage.hs_fs --operation=flash --flash-offset=0x0

#--operation=flash-phy-tuning-data
# 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=../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage1/am62px-sk/wkup-r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage1.release.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0


# 2nd stage bootloader with DM is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file="C:/Users/uidk9830/workspace_ccstheia/dss_display_share_am62px-sk_wkup-r5fss0-0_freertos_ti-arm-clang/Debug/dss_display_share_am62px-sk_wkup-r5fss0-0_freertos_ti-arm-clang.appimage.hs_fs" --operation=flash-emmc --flash-offset=0x80000
####Demo for screen test
#--file="C:\Users\uidk9830\workspace_ccstheia\dss_display_test_am62px-sk_wkup-r5fss0-0_freertos_ti-arm-clang\Debug\dss_display_test_am62px-sk_wkup-r5fss0-0_freertos_ti-arm-clang.appimage.hs_fs" --operation=flash-emmc --flash-offset=0x80000




# HSM image is flashed at 0x240000 or to whatever offset your bootloader is configured for
--file=HSMAppimageGen/board/am62px-sk/hsm.appimage.hs_fs --operation=flash-emmc --flash-offset=0x740000

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

# QNX image is flashed at 0x1200000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/qnxAppimageGen/board/am62px-sk/qnx.appimage.hs_fs --operation=flash-emmc --flash-offset=0x1200000

但当我尝试启动时、收到以下消息：

[BOOTLOADER_PROFILE] Boot Media       : eMMC 
[BOOTLOADER_PROFILE] Boot Media Clock : 200.000 MHz 
[BOOTLOADER_PROFILE] Boot Image Size  : 6568 KB 
[BOOTLOADER_PROFILE] Cores present    : 
wkup-r5f0-0
[BOOTLOADER PROFILE] System_init                      :      38831us 
[BOOTLOADER PROFILE] Board_init                       :          0us 
[BOOTLOADER PROFILE] Drivers_open                     :          0us 
[BOOTLOADER PROFILE] SBL Drivers_open                 :      20415us 
[BOOTLOADER PROFILE] Board_driversOpen                :          0us 
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :      85816us 
[BOOTLOADER_PROFILE] SBL Total Time Taken             :     145064us 

Image loading done, switching to application ...
Starting 2nd stage bootloader

然后启动等待

您好、

您运行的是 Linux 还是 QNX？

此致、

Suren

尊敬的 TI 团队

QNX、  

我已经解决了这个问题、我将启动时的代码更改为初始化 EMMC、然后引导就可以了。

很高兴它能正常工作。

我将关闭此主题。 如需进一步的帮助、请随时联系我们。

谨致问候、

Suren