Other Parts Discussed in Thread: SYSCONFIG, UNIFLASH, AM62P
请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。
部件号： AM62P
Thread 中讨论的其他器件： SYSCONFIG、 UNIFLASH
大家好、TI 专家。
我使用的是 TI 的 SK-AM62P5 EVK。 在此基础上、我尝试使用自定义显示共享应用（在 DM-R5F 上）和 IPC 应用（在 Cortex-R5F 上）内核。 要刷写此示例、请访问 default_sbl_ospi_linux_hs_fs.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 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
# 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
# Program the OSPI PHY tuning attack vector
--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
--file=sbl_prebuilt/am62px-sk/sbl_ospi_linux_stage1.release.hs_fs.tiimage --operation=flash --flash-offset=0x0
# 2nd stage bootloader with DM is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/dss/dss_display_share/am62px-sk/wkup-r5fss0-0_freertos/ti-arm-clang/dss_display_share.release.appimage.hs_fs --operation=flash --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/am62px-sk/mcu-r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash --flash-offset=0x800000
# HSM image is flashed at 0x800000 or to whatever offset your bootloader is configured for
--file=HSMAppimageGen/board/am62px-sk/hsm.appimage.hs_fs --operation=flash --flash-offset=0x240000
# Linux image is flashed at 0xC00000 or to whatever offset your bootloader is configured for
--file=linuxAppimageGen/board/am62px-sk/linux.appimage.hs_fs --operation=flash --flash-offset=0x1200000
# u-boot.img is flashed at 0x280000
--file=linuxAppimageGen/board/am62px-sk/u-boot.img --operation=flash --flash-offset=0x280000但在使用该文件时、我看到 DM-R5F 内核上的显示共享示例的大小为 2415862 字节、并且与此后刷写的 HSM.appimage.hs_fs 和 u-boot.img 文件的偏移地址重叠。
现在刷写已完成、但电路板未启动、导致出现以下错误。
WARNING: Bootloader_verifyMulticoreImage:375: Failed to authenticate and copy on the go, reading the image to DDR.
SBL stage 1 failed!!那么、我应该采取哪些步骤来处理这个示例？
请帮助我确定应该保留我的核心二进制文件的偏移量、以便它不会影响/与其他二进制文件的偏移量重叠。
此致、
Aditya T
