Other Parts Discussed in Thread: UNIFLASH
Tool/software:
Hello Ti teams,
I used the file default_sbl_emmc_linux_hs.cfg to flash my simple app in R5F0_0 no RTOS and start Linux after. I used am64x-evm hardware kit to do that.
On uart Terminal, i get that below . My R5F application not works and I don't understand why Boot Media is undefined and boot image size : 0KB. Only Cores present is M4F. If I used OSPI config, Boot media is ok, R5F is detected and application on R5F works very good.
Is someone have an idea why the emmc is not recognized when i used default_sbl_emmc_linux_hs.cfg ?
# First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files to eMMC --flash-writer=sbl_prebuilt/am64x-evm/sbl_uart_uniflash.debug.hs_fs.tiimage # 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/am64x-evm/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux.debug.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0 # 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_linux/am64x-evm/system_freertos/ipc_rpmsg_echo_linux_system.debug.appimage.hs_fs --operation=flash-emmc --flash-offset=0x800000 # Linux image is flashed at 0xA00000 or to whatever offset your bootloader is configured for --file=../../tools/boot/linuxAppimageGen/linux.appimage.hs_fs --operation=flash-emmc --flash-offset=0xA00000
