imx8qm auto scfw and bootup

cancel
Showing results for 
Search instead for 
Did you mean: 

imx8qm auto scfw and bootup

163 Views
roger_luo
Contributor I

Dear NXP, 

We use p9.0.0_2.1.0-auto-ga to build mek_8q_car_userdebug, and modify vendor/nxp/fsl-proprietary/uboot-firmware/imx8q_car/board-imx8qm.c  to build scfw_tcm.bin, but only m41 can bootup, there is no any log on arm. How to do to make both arm and m41 work?

The mek_8q_car_userdebug using "flash_b0_spl_container_m4_1_trusty" FLASH_TARGET to make imx image, while mek_8q_userdebug using "flash_linux_m4".  Using the same scfw_tcm.bin, "flash_linux_m4" could bootup arm, m40 and m41.  I have checked the scfw resource asign, can't find where is wrong.

By the way,  I have  referenced "System-Controller-Firmware-101" series docs.

 

The attachment is mek_8q_car_userdebug scfw partition.

 

0 Kudos
1 Reply

137 Views
nxf46838
NXP TechSupport
NXP TechSupport

Hello,

This may be caused due to the memory region the Flash target you're using selects for the Cortex-M:
 

flash_b0_spl_container_m4_1_trusty
Cortex-M code will run in DDR which if not having the correct setting may cause problems if Cortex-A boots.
https://source.codeaurora.org/external/imx/imx-mkimage/tree/iMX8QM/scripts/android.mak?h=imx_5.4.70_...

 

flash_linux_m4
In here memory region for Cortex-M is default
https://source.codeaurora.org/external/imx/imx-mkimage/tree/iMX8QM/soc.mak?h=imx_5.4.70_2.3.0#n96

I'll suggest trying building your Cortex-M application for DDR and try again.

Best regards,
Aldo.

0 Kudos