# Running firmware on Cortex M4 core

**URL:** <https://community.solid-run.com/t/running-firmware-on-cortex-m4-core/912>\
**Category:** NXP i.MX8M Plus\
**Created:** [October 11, 2024, 12:04pm UTC](https://community.solid-run.com/t/running-firmware-on-cortex-m4-core/912 "2024-10-11T12:04:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tanshihaj](https://avatars.discourse-cdn.com/v4/letter/t/eb8c5e/32.png) [@tanshihaj](https://community.solid-run.com/u/tanshihaj)\
**Post date:** [October 11, 2024, 12:04pm UTC](https://community.solid-run.com/t/running-firmware-on-cortex-m4-core/912/1 "2024-10-11T12:04:07Z")

</div>

I’m trying to run NXP’s sample applications (for example, [rpmsg\_lite\_str\_echo\_rtos](https://github.com/nxp-mcuxpresso/mcux-sdk-examples/tree/main/evkmimx8mm/multicore_examples/rpmsg_lite_str_echo_rtos)) on the Cortex M4 kernel using [Linux Remote Processor Framework](https://github.com/nxp-imx/linux-imx/blob/d23d64eea5111e1607efcce1d601834fceec92cb/Documentation/staging/remoteproc.rst). The issue is i do not see neither /dev/ttyRPMSG30 device after loading imx\_rpmsg\_tty module nor appropriate channel in /sys/bus/rpmsg. How can I debug where is the issue? Is there any working setup for Hummingboard Ripple + i.MX 8M Mini to launch simple application on Cortex M4?

My setup details:

- Board: HummingBoard Ripple
- SOM: i.MX 8M Mini
- OS: NixOS 24.05
- Linux kernel: [GitHub - nxp-imx/linux-imx at b586a521770e508d1d440ccb085c7696b9d6d387](https://github.com/nxp-imx/linux-imx/tree/b586a521770e508d1d440ccb085c7696b9d6d387) (v6.6.23)
- Device Tree: [dts for Solid-Run Humminboard Ripple with i.MX 8M Mini SOC · GitHub](https://gist.github.com/tanshihaj/dc7c413284e99fe3714241d328e5b9e0) (basically just [linux-stable/arch/arm64/boot/dts/freescale/imx8mm-hummingboard-pulse.dts at linux-5.4.y-imx8 · SolidRun/linux-stable · GitHub](https://github.com/SolidRun/linux-stable/blob/linux-5.4.y-imx8/arch/arm64/boot/dts/freescale/imx8mm-hummingboard-pulse.dts) with small fixes and new node for Cortex M4 remote processor)