Hi @AldoG ,
We are tplanning to do i.MX93 low power boot on Yocto 6.12.
After boot to cm33, is there any way to boot Linux from cm33?
Hi @WolsYang!
Thank you for contacting NXP Support!
It is not possible to run Linux on the M core, as it is designed for real-time, low-power tasks and does not have the resources required to support a full Linux operating system.
Best regards,
Chavira
Hi @Chavira ,
Sorry for unclear description.
I means when I enable .bin in only m-core at u-boot, after bring up .bin content, u-boot will close (If is not correct, please let me know)
So, after bring up .bin content in only m-core, how can I bring up Linux in a-core?
Hi @WolsYang!
In the i.MX93, it is possible and even intended for both cores to work together.
Once the M core has booted, you can proceed to boot Linux on the A core. However, you may need to make some adjustments to the device tree, depending on your configuration.
As you know, both cores can access most of the peripherals. Therefore, it’s important to ensure that any peripherals used by the M core are disabled in the device tree for the A core. This prevents resource conflicts and ensures stable operation for both cores.
Best Regards!
Chavira
Hi @Chavira ,
Do we have example about this?
In my understood, after brigng up m-core, u-boot job is done, and will close.
Then for example after 10 minute, now only m-core is running, how to bring up a-core linux now?
Hi @WolsYang!
You can find the complete procedure for working with multiple cores in our i.MX93-EVK examples at the link below:
https://github.com/nxp-mcuxpresso/mcux-sdk-examples/tree/main/mcimx93evk/multicore_examples
Best regards,
Chavira
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