This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[参考译文] AM62A7:使用 uart_uniflash.py 时、闪存失败!

Guru**** 2535150 points
Other Parts Discussed in Thread: UNIFLASH

请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1371603/am62a7-when-using-uart_uniflash-py-flash-failed

器件型号:AM62A7
主题中讨论的其他器件:UNIFLASH

工具与软件:

尊敬的所有人:

在 UART 模式下、我运行 uart_uniflash.py 失败。  

(我在终端看到了"c"、然后将其关闭。)

错误是:

C:\ti\mcu_plus_sdk_am62ax_09_02_00_38\tools\boot>python uart_uniflash.py -p COM23 --cfg=default_sbl_emmc_hs_fs.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 6 command(s) !!!

Executing command 1 of 6 ...
Command arguments : --file=C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x0
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   1%|    | 2058/155995 [00:00<00:52, 2910.80bytes/s]send error: expected ACK; got b'\x18' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   2%|    | 3087/155995 [00:00<00:24, 6306.72bytes/s]send error: expected ACK; got b'\x18' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   3%|    | 4116/155995 [00:00<00:24, 6306.72bytes/s]send error: expected ACK; got b'0' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   3%|▏   | 5145/155995 [00:02<01:26, 1740.84bytes/s]send error: expected ACK; got b'2' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   4%|▏   | 6174/155995 [00:02<01:26, 1740.84bytes/s]send error: expected ACK; got b'0' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   5%|▏   | 7203/155995 [00:02<01:25, 1740.84bytes/s]send error: expected ACK; got b'0' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   5%|▏   | 8232/155995 [00:02<00:43, 3359.27bytes/s]send error: expected ACK; got b'0' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   6%|▏   | 9261/155995 [00:02<00:43, 3359.27bytes/s]send error: expected ACK; got b'0' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   7%|▏  | 10290/155995 [00:02<00:33, 4410.35bytes/s]send error: expected ACK; got b'0' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   7%|▏  | 11319/155995 [00:02<00:32, 4410.35bytes/s]send error: expected ACK; got b'0' for block 2
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   8%|▏  | 12348/155995 [00:03<00:25, 5529.60bytes/s]send error: expected ACK; got b'0' for block 2
send error: NAK received 11 times, aborting.
Sending C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs:   8%|▏  | 12350/155995 [00:03<00:25, 5529.60bytes/s]
[ERROR] XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

我的 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 A53 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/am62ax-sk/sbl_uart_uniflash_stage1.release.hs_fs.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=C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_uart_uniflash_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --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=C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_emmc_stage1.Release.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0

# 2nd stage bootloader is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file=C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/sbl_emmc_stage2_am62ax-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000

# DM image is flashed at 0xC0000 or to whatever offset your bootloader is configured for

####################################
####### here is dmr5 appimage ######
####################################
--file=C:/Users/mxj/workspace_v12/ddr_perf_app_am62ax-sk_r5fss0-0_freertos_ti-arm-clang/Debug/ddr_perf_app_am62ax-sk_r5fss0-0_freertos_ti-arm-clang.appimage.hs_fs --operation=flash-emmc --flash-offset=0xC0000

# HSM image is flashed at 0x240000 or to whatever offset your bootloader is configured for
--file=C:/Users/mxj/Desktop/TI_workspace_lgm/image_all/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

####################################
####### here is mcur5 appimage #####
####################################
--file=C:/Users/mxj/workspace_v12/ddr_ecc_test_main_esm_am62ax-sk_mcu-r5fss0-0_freertos_ti-arm-clang/Debug/ddr_ecc_test_main_esm_am62ax-sk_mcu-r5fss0-0_freertos_ti-arm-clang.appimage.hs_fs --operation=flash-emmc --flash-offset=0x800000

# C7x image is flashed at 0xA00000 or to whatever offset your bootloader is configured for
# --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am62ax-sk/c75ss0-0_freertos/ti-c7000/ipc_rpmsg_echo.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0xA00000

# A53 image is flashed at 0x1200000 or to whatever offset your bootloader is configured for
# --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am62ax-sk/a53ss0-0_nortos/gcc-aarch64/ipc_rpmsg_echo.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x1200000

亲爱的先生,我要怎么回应呢?