# M4 Cortex firmware stops working after Mender integration on Apalis iMX8QM

**URL:** <https://hub.mender.io/t/m4-cortex-firmware-stops-working-after-mender-integration-on-apalis-imx8qm/8143>\
**Category:** Board Integrations\
**Tags:** nxp, mender-client\
**Created:** [December 16, 2025, 12:58pm UTC](https://hub.mender.io/t/m4-cortex-firmware-stops-working-after-mender-integration-on-apalis-imx8qm/8143 "2025-12-16T12:58:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rania](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/rania/32/2723_2.png) [@rania](https://hub.mender.io/u/rania)\
**Post date:** [December 16, 2025, 12:58pm UTC](https://hub.mender.io/t/m4-cortex-firmware-stops-working-after-mender-integration-on-apalis-imx8qm/8143/1 "2025-12-16T12:58:00Z")

</div>

hello community i’ ve already posted the same problem in toradex community

> **[M4 Cortex firmware stops working after Mender integration on Apalis iMX8QM](https://community.toradex.com/t/m4-cortex-firmware-stops-working-after-mender-integration-on-apalis-imx8qm/29643?u=rania)**
>
> Hardware & Software Setup Board: Toradex Apalis iMX8QM V1.1 BSP Version: toradex-bsp-6.7.0 (trying to integrate with toradex-bsp-6.2.0 for Mender) Mender Setup: Using meta-mender-community/meta-mender-toradex Kernel: Linux...

i need your help to understand mender changes made on u-boot so i can i know where ‘s the conflict is coming from and why integrating this latter cause the corruption of the cortex m4 binary

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [December 16, 2025, 2:21pm UTC](https://hub.mender.io/t/m4-cortex-firmware-stops-working-after-mender-integration-on-apalis-imx8qm/8143/2 "2025-12-16T14:21:35Z")

</div>

Hi @rania,

Thanks for reaching out! The Mender integration definitely should not interfere with the M4 at all. From the linked post I gather that it works on BSP 6.7 (without Mender) and fails on BSP 6.2 (with Mender), correct?

So the two things to check:

- does it work on vanilla BSP 6.2, without Mender? If no, then the BSP revision breaks/fixes something. If yes, then it is Mender :-/
- after that, try bumping the Mender integration to BSP 6.7. That should be very straightforward, please ping here if you hit any problems. Then, repeat test.

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![rania](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/rania/32/2723_2.png) [@rania](https://hub.mender.io/u/rania)\
**Post date:** [December 18, 2025, 8:50am UTC](https://hub.mender.io/t/m4-cortex-firmware-stops-working-after-mender-integration-on-apalis-imx8qm/8143/3 "2025-12-18T08:50:38Z")

</div>

Hi Josef,

To clarify the setup:  
My board is actually running Toradex BSP 6.7 (Yocto Kirkstone).  
However, since meta-mender-community only seemed to have configurations for BSP 6.0 and 6.2, I attempted to use the 6.2 integration logic on my 6.7 build.

This version mismatch might be why I am seeing these conflicts.

The specific behavior I am fighting is:

1. Memory Collision: The default Toradex 6.7 setup loads M4 to 0x95400000. Mender loads the Linux Kernel to the same address. I tried moving M4 to 0x88000000 manually.
2. Silent Failures: Even when I adjust the addresses manually in the U-Boot console, I struggle to get the M4 to boot reliably alongside Linux. I can see rpmsg communication , but mostly it fails silently .

Since I am on BSP 6.7, should I be using a different branch or specific configuration? Is there a known “safe” way to adapt the 6.2 configs to 6.7?

u have both cortex M4 and mender configurations can u help me find the u-boot conflicts whether address allocation or bootcmd