Hi @Chavira
In rpmsg_lite_pingpong_rtos/linux_remote , I see the description
The primary core releases the secondary core from the reset and then the inter-core communication is established
But I didn't see any like bring up a-corc linux code in
rpmsg_lite_pingpong_rtos/linux_remote/main_remote.c
Also in readme-Prepare the Demo
3. Boot Linux BSP to u-boot, and load M core image from SD card to run. (Put the image into SD card before.) => load mmc 1:1 0x80000000 /rpmsg_lite_pingpong_rtos_linux_remote.bin => cp.b 0x80000000 0x201e0000 0x20000 => bootaux 0x1ffe0000 0
4. Append "clk_ignore_unused" in u-boot "mmcargs" env, before booting linux
5 .Boot to linux. Run "echo '7 4 1 7' > /proc/sys/kernel/printk" to change the message level.
I think is a-core boot first and then use u-boot to enable m-core