AM625: Failed in flashing SBL using MCU+SDK V9.02

Hello,

Please use the unmodified `default_sbl_emmc_linux.cfg` as shown below

~/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

Also, please note we don't support the GP devices from MCU+ SDK v9.0 onwards. So, in case the flashing fails even after using the correct config file, we won't be able to support it.

Regards,

Prashant

Hello,

Prashant Shivhare said:

please note we don't support the GP devices from MCU+ SDK v9.0 onwards. So, in case the flashing fails even after using the correct config file, we won't be able to support it.

1. In this case, I need to migrate to HS-FS or HS-SE device first, then try to run the SBL flashing. Am I right?

2. If can't flash the SBL in GP devices, then how to optimize the boot time using Falcon mode?

Thanks & Regards,
Aditya T

Hello,

Aditya Tandulwadkar said:

1. In this case, I need to migrate to HS-FS or HS-SE device first, then try to run the SBL flashing. Am I right?

Yes. Please note the GP devices cannot be converted into HS-FS or HS-SE devices. The HS device is shipped in HS-FS state (by TI) and later converted into HS-SE (by the customer).

The TI AM62x HS-FS board can be found here: https://www.ti.com/tool/SK-AM62B

Aditya Tandulwadkar said:

2. If can't flash the SBL in GP devices, then how to optimize the boot time using Falcon mode?

I did not say you can't. You can try flashing with the correct config file. If it flashes successfully and everything boots fine then it's great otherwise we will be limited in the support.

Regards,

Prashant

Hello,

Prashant Shivhare said:

Yes. Please note the GP devices cannot be converted into HS-FS or HS-SE devices. The HS device is shipped in HS-FS state (by TI) and later converted into HS-SE (by the customer).

If this is not possible, then there's link given in Ti's document for it: the link, which says "GP to HS-FS Migration Guide"

Prashant Shivhare said:

I did not say you can't. You can try flashing with the correct config file. If it flashes successfully and everything boots fine then it's great otherwise we will be limited in the support.

Can you guide which is correct config file for my case then?

Thanks & Regards,
Aditya T