AM62P: How to flash ipc_rpmsg_echo example provided in MCU-Plus SDK

Please refer https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/latest/exports/docs/api_guide_am62px/GETTING_STARTED_FLASH.html document on how to flash examples to ospi memory.

The above page show how to flash hello_world example which you can replace with ipc_rpmsg_echo example and follow the same steps.

Regards,

Tushar

When I replaced example with ipc_rpmsg_echo the below is my .cfg file.

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

#-----------------------------------------------------------------------------#
#                                                                             #
#      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/ipc/ipc_rpmsg_echo/am62px-sk/wkup-r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo.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/am62px-sk/mcu-r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo.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

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

But after this, when I flashed this example then on MCU-UART0 and WKUP-UART0 any logs didn't came on it.

Please make sure you are checking the right console. Refer https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/latest/exports/docs/api_guide_am62px/EVM_SETUP_PAGE.html#CCS_UART_TERMINAL for details.

Are you able to see any SBL logs? Are you seeing the logs from Linux?

Regards,

Tushar

I've opened all  3 consoles mentioned below,

ttyUSB0 -> For Linux
ttyUSB2 -> For DM R5F
ttyUSB3 -> For MCU R5F

And I see only

�Sciserver Testapp Built On: Mar  2 2026 10:42:34
Sciserver Version: v2025.12.0.0-REL.MCUSDK.K3.11.02.00.23+
RM_PM_HAL Version: v11.02.05

These logs on DM R5F console, After this neither MCU R5F console prints anything nor the Linux console. Also Linux isn't booting.

Regards,
Aditya T

Aditya Tandulwadkar said:

These logs on DM R5F console, After this neither MCU R5F console prints anything nor the Linux console. Also Linux isn't booting.

This means there is problem in your flashed binaries. Which UART instance are you using in your R5F and MCU_R5F application?

Regards,

Tushar

Hello,

Tushar Thakur said:

This means there is problem in your flashed binaries.

But I haven't modified any code in that example.

Tushar Thakur said:

Which UART instance are you using in your R5F and MCU_R5F application?

MCU_UART0 for for example in MCU R5F, and WKUP_UART0 for example in WKUP R5F.

Also I'm able to run ipc_rpmsg_echo_linux example in both MCU R5F and WKUP R5F cores of board.

Regards,
Aditya T

Please try with the default_sbl_null_hs_fs.cfg file instead of default_sbl_ospi_linux_hs_fs.cfg file.

Please change the DM appimage path with IPC binary in the cfg file and let us know the results.

Regards,

Tushar

Hi,

Tushar Thakur said:

Please try with the default_sbl_null_hs_fs.cfg file instead of default_sbl_ospi_linux_hs_fs.cfg file.

Please change the DM appimage path with IPC binary in the cfg file and let us know the results.

When tried this, got output as given below on WKUP-R5F terminal

��Sciserver Testapp Built On: Mar  2 2026 10:42:34
Sciserver Version: v2025.12.0.0-REL.MCUSDK.K3.11.02.00.23+
RM_PM_HAL Version: v11.02.05
Starting Sciserver..... PASSED

8540.default_sbl_null_hs_fs.cfg
Still this issue is not resolved, also sorry for replying this late.

Regards,
Aditya T

After flashing the SBL NULL binary you should get output similar to below.

Can you please open all the ports and check logs are coming or not?

Regards,

Tushar