topic 回复： When executing the CM7 firmware using the IMX8MP Linux system, the system blocked in i.MX Processors

When executing the CM7 firmware using the IMX8MP Linux system, the system blocked

Dzen — Tue, 28 Apr 2026 12:00:38 GMT

hi NXP Supports,

I am currently working on developing the firmware for the IMX8MP CM7, but have encountered some issues.

I compiled the hello_world example firmware using MCUpresso for VS Code. When performing the following operation, the system blocked and did not move. there were no logs printed from the debug serial port of A53 either. please point out where I haven't made the configuration correctly? TKS.

The device tree configuration is as follows:

memory@40000000 {

device_type = "memory";

reg = <0x0 0x40000000 0 0x40000000>; / * 1GB DDR */

};

reserved-memory {

#address-cells = <2>;

#size-cells = <2>;

ranges;

/* 128MB */

linux,cma {

compatible = "shared-dma-pool";

reusable;

size = <0 0x8000000>;

alloc-ranges = <0 0x40000000 0 0x40000000>;

linux,cma-default;

};

/* Reserve 16MB for RTOS running on CM7 */

m7_reserved: m7@7E000000 {

no-map;

reg = <0 0x7E000000 0 0x1000000>;

};

vdev0vring0: vdev0vring0@7D000000 {

reg = <0 0x7D000000 0 0x8000>;

no-map;

};

vdev0vring1: vdev0vring1@7D008000 {

reg = <0 0x7D008000 0 0x8000>;

no-map;

};

vdevbuffer: vdevbuffer@7D100000 {

compatible = "shared-dma-pool";

reg = <0 0x7D100000 0 0x100000>;

no-map;

};

rsc_table: rsc-table@7D0FF000 {

reg = <0 0x7D0FF000 0 0x1000>;

no-map;

};

imx8mp-cm7 {

compatible = "fsl,imx8mn-cm7";

rsc-da = <0x7D000000>;

clocks = <&clk IMX8MP_CLK_M7_DIV>;

clock-names = "core";

mbox-names = "tx", "rx", "rxdb";

mboxes = <&mu 0 1

&mu 1 1

&mu 3 1>;

memory-region = <&m7_reserved>,

<&vdevbuffer>,

<&vdev0vring0>,

<&vdev0vring1>,

<&rsc_table>;

status = "okay";

fsl,startup-delay-ms = <500>;

};

Re: When executing the CM7 firmware using the IMX8MP Linux system, the system blocked

dbaluta — Wed, 29 Apr 2026 06:38:40 GMT

Sending you some pointers until NXP support team will jump in.

Can you try using this tree https://github.com/nxp-imx/linux-imx/tree/lf-6.18.y and this dts?

https://github.com/nxp-imx/linux-imx/blob/lf-6.18.y/arch/arm64/boot/dts/freescale/imx8mp-evk-rpmsg.dts

Re: When executing the CM7 firmware using the IMX8MP Linux system, the system blocked

Manuel_Salas — Wed, 29 Apr 2026 18:36:16 GMT

Hello @Dzen

I hope you are doing very well.

You can try configuring your device tree as the chapter 9.1 i.MX Linux rproc support of the AN5317.

Same as suggested by @dbaluta .

Best regards,

Salas.

回复： When executing the CM7 firmware using the IMX8MP Linux system, the system blocked

Dzen — Sat, 09 May 2026 08:08:36 GMT

Thanks,

I have been able to run the firmware of CM7 using the sysfs method by sending the command "run prepare_mcore" in the boot process.

However, during the operation of the CM7 firmware, the following errors still occurred. I used the project "boards\evkmimx8mp\demo_apps\hello_world". From the log, it seems to be a problem with the SAI/audio configuration. But I have already deleted the contents related to audio in clock_config.c(attached file), yet the error still occurred. Please tell me if there is anything that was not properly modified?

[ 122.890817] Internal error: synchronous external abort: 0000000096000210 [#1] PREEMPT_RT SMP
[ 122.890822] Modules linked in: fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce snd_soc_imx_card polyval_ce polyval_generic snd_soc_fsl_micfil snd_soc_fsl_sai snd_soc_fsl_utils imx_pcm_dma snd_soc_tas5805m caam secvio error leds_serial_gpio fuse
[ 122.890866] CPU: 0 PID: 248 Comm: irq/221-sai Not tainted 6.6.36-rt35-lts-next #1
[ 122.890873] Hardware name: NXP i.MX8MPlus EVK board (DT)
[ 122.890875] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 122.890881] pc : regmap_mmio_read32le+0x8/0x60
[ 122.890891] lr : regmap_mmio_read+0x44/0x70
[ 122.890896] sp : ffff800082fcbcc0
[ 122.890898] x29: ffff800082fcbcc0 x28: 0000000000000000 x27: 0000000000000000
[ 122.890905] x26: ffff8000800f3e90 x25: ffff8000800f198c x24: ffff000005f3b500
[ 122.890913] x23: ffff000005b60000 x22: ffff000005bea400 x21: ffff800082fcbd84
[ 122.890920] x20: 0000000000000008 x19: ffff000005afecc0 x18: ffffffffffffffff
[ 122.890928] x17: 0000000100000100 x16: 000010003d000000 x15: ffff000036d5ac40
[ 122.890935] x14: 00000505d7fc02f4 x13: 00143f3c7cb53818 x12: 0000000000000055
[ 122.890942] x11: 0000000000000001 x10: 0000000000000a10 x9 : ffff800082fcbd30
[ 122.890951] x8 : ffff000008096170 x7 : ffff000036d5a440 x6 : 0000000000143f3c
[ 122.890957] x5 : ffff80008098ce58 x4 : 0000000000000008 x3 : 0000000000000008
[ 122.890964] x2 : ffff80008098d5d8 x1 : 0000000000000008 x0 : ffff800082fb0008
[ 122.890971] Call trace:
[ 122.890974] regmap_mmio_read32le+0x8/0x60
[ 122.890979] _regmap_bus_reg_read+0x70/0xb0
[ 122.890986] _regmap_read+0x60/0xd8
[ 122.890993] regmap_read+0x4c/0x78
[ 122.890998] fsl_sai_isr+0x48/0xec [snd_soc_fsl_sai]
[ 122.891012] irq_forced_thread_fn+0x3c/0xc8
[ 122.891021] irq_thread+0x174/0x23c
[ 122.891028] kthread+0x110/0x114
[ 122.891034] ret_from_fork+0x10/0x20
[ 122.891043] Code: b5000001 d65f03c0 f9400000 8b214000 (b9400000)
[ 122.891048] ---[ end trace 0000000000000000 ]---
[ 122.891051] Kernel panic - not syncing: synchronous external abort: Fatal exception in interrupt
[ 122.891055] SMP: stopping secondary CPUs
[ 122.891062] Kernel Offset: disabled
[ 122.891064] CPU features: 0x0,00000008,00020000,1000421b
[ 122.891068] Memory Limit: none
[ 123.748394] ---[ end Kernel panic - not syncing: synchronous external abort: Fatal exception in interrupt ]---