Hi,
once loaded a cortex M4 image at u-boot (bootaux) and checked it works by interacting on the M4 console, i boot linux (boot cmd) and suddenly M4 stops to work. Is this normal ? Is there a way to keep M4 running over Linux boot ?
Hi Igor,
sorry, should have been a typo, i tested with fdt_file=imx8qxp-mek-dsi-rm67191-rpmsg.dtb
Same issue, M4 app stops to work as soon as the kernel boots, as some clocks or power is cut.
Hi spectrum
what bsp used in the case, one can try with latest Linux 5.4.70_2.3.0, use below dts
linux documentation
Best regards
igor
Hi Igor,
thanks for the feedback, but issue is still the same: at the moment when linux boots, M4 application stops to run.
I tested a mainline kernel, and it does not stops M4 at boot.
I am using
imx_5.4.70_2.3.0
imx8qxp-mek-dsi-rm67191.dtb
On M4, i am keeping running power_mode_switch app, that allows to use an interactive menu on M4 console, and i can see if M4 is running.
From u-boot, i do :
fatload mmc 1:1 ${loadaddr} power_mode_switch.bin && dcache flush && bootaux ${loadaddr} 0
(M4 demo works just after fw loading)
command line: console=ttyLP0,115200 root=/dev/mmcblk1p2 rootwait rw
As defconfig using one based on imx_v8_defconfig.
If any help, welcome.
Angelo
Hi Angelo
could you try imx8qxp-mek-dsi-rm67191-rpmsg.dts as was suggested.
Best regards
igor
Hi Igor,
re-adding here, tested i tested imx_5.4.70_2.3.0 with fdt_file=imx8qxp-mek-dsi-rm67191-rpmsg.dtb , still M4 stops to run at kernel boot.
i tested now imx_4.19.35_1.1.0, it does not stop M4 at boot.
So issue is related to imx_5.4.70_2.3.0. Please let me know if this is an open issue on imx_5.4.70_2.3.0.
Hi,
seems something related my image built on dunfell and meta-freescale was causing the issue.
Probably something related to SCU fw.
Building using meta-nxp stuff (zeus, using 5.4.70_2.3.0)
MACHINE=imx8qxpmek source imx-setup-release.sh -b initial_build_dir
All seems to work.
Thanks
regards