Hi,
I found guidance as follows.
(reference link : https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_03_00_07/exports/docs/pdk_jacinto_07_03_00_29/docs/userguide/jacinto/boot/boot_k3.html)
Using the combined_appimage tooling to boot a HLOS+RTOS appimage
Creating a combined.appimage file including all images necessary to boot U-boot or HLOS on the SoC’s Cortex-A cores, as well as booting RTOS images on the other remote cores can be done with the following 4 steps:
- Modify the sbl/tools/combined_appimage/config.mk file HLOS_BIN_PATH var to point to the desired HLOS images to be booted
- Modify the HLOS_BOOT var in the same file to select “development” option (boots to SPL/U-boot) or “optimized” option (boots ATF/OPTEE/Linux)
- Modify the RTOS_BIN_PATH var there to point to your RTOS binaries and then list the cores & binaries to be loaded in the vars: IMG1, IMG2, ...
- Make the combined.appimage output app using the following make command:
But make was failed.
make BOARD=j721e_evm GCC_LINUX_ARM_PATH=/home/yongsig/workspace/TDA4x/psdk7.3/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/gcc-arm-9.2-2019.12-x86_64-aarch64-none-elf make: *** No rule to make target '/home/yongsig/workspace/TDA4x/psdk7.3/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/binary/ipc_echo_testb/bin/j721e_evm/ipc_echo_testb_mcu1_0_release_strip.rprc', needed by '/home/yongsig/workspace/TDA4x/psdk7.3_hirain/ti-processor-sdk-rtos-j721e-evm-07_03_00_07/pdk_jacinto_07_03_00_29/packages/ti/boot/sbl/tools/combined_appimage/bin/j721e_evm/combined.appimage'. Stop.
I don't understand what HLOS_BIN_PATH and RTOS_BIN_PATH mean.
I mentioned the generated app file using multicoreImageGen tool in the previous question.
Does RTOS_BIN_PATH mean the generated app file?
Ultimately, I'm trying to run my vision_app and the generated MCSPI_MCU1_0 app on Linux.
Best regards
Yongsig