This example shows usage of RP Message APIs to exchange messages between RTOS/NORTOS CPUs as well as exchange message with QNX on Cortex-A CPU.
The example integrates bootloading funtionality with SBL on OSPI bootmedia. It also integrates Device manager functionality. The SBL stage 2 thread boots all the cores along with HLOS like Linux. Refer SBL Booting Linux From OSPI for boot flow sequence.
Parameter | Value |
---|---|
CPU + OS | mcu-r5fss0-0 freertos |
wkup-r5fss0-0 freertos | |
Toolchain | ti-arm-clang |
Board | am62px-sk |
Example folder | examples/drivers/ipc/ipc_rpmsg_echo_qnx |
C:/ti/mcu_plus_sdk
and this example and IPC application is built using makefiles, and Linux Appimage is already created, in Windows, cd C:/ti/mcu_plus_sdk/tools/boot python uart_uniflash.py -p COM13 --cfg=C:/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/am62px-sk/default_sbl_ospi_qnx_hs_fs.cfg
~/ti/mcu_plus_sdk
cd ~/ti/mcu_plus_sdk python uart_uniflash.py -p /dev/ttyUSB0 --cfg=~/ti/mcu_plus_sdk/tools/boot/sbl_prebuilt/am62px-sk/default_sbl_ospi_qnx_hs_fs.cfg
There is no direct output from the RTOS/NORTOS CPUs on the UART or CCS console. The output is seen on the QNX console on Cortex-A CPU.