2021-07-13 06:18 AM
I have two codes running (on stm32mp157f-Dk2) successfully one is running on M4+freeRTOS another on A7+Linux, they are intercommunicating via RPMSGx. The problem is that after power-loss or reboot, I want both of my programs starting automatically and not the default UI (GNU desktop screen with icons of examples). Is there a chance to get either step-by-step guide or even better a video executing all the steps to change the kernel and launch customer's code?
4 Build the Linux® kernel source code for the first time:
(4.1.2 Remote processor 'auto' boot (not recommended by STMicroelectronics)↑:(
https://wiki.st.com/stm32mpu/wiki/Linux_remoteproc_framework_overview
3.3 Modifying the Linux kernel device tree↑:
https://wiki.st.com/stm32mpu/wiki/How_to_cross-compile_with_the_Distribution_Package
Because the url guide is a bit unclear it seems to be missing some information.
Solved! Go to Solution.
2021-07-13 06:48 AM
Hi,
Except if you need to recompile the kernel, for a simple DT update (e.g. from CubeMX to target), please see https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package
To start M4 FW automatically, I recommend to start from a Linux script executed during startup (there is may ways, depend on your application environment). This is done by simply including the few command lines present in https://wiki.st.com/stm32mpu/wiki/Linux_remoteproc_framework_overview#Remote_processor_boot_through_sysfs
To avoid the launch of the demo, you could for instance adapt the /usr/local/weston-start-at-startup/start_up_demo_launcher.sh file (assuming you still need Weston).
Some video link (not sure they are up to date with latest ecosystem v3)
https://www.youtube.com/c/stmicroelectronics/search?query=stm32mp1
Regards.
2021-07-13 06:48 AM
Hi,
Except if you need to recompile the kernel, for a simple DT update (e.g. from CubeMX to target), please see https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package
To start M4 FW automatically, I recommend to start from a Linux script executed during startup (there is may ways, depend on your application environment). This is done by simply including the few command lines present in https://wiki.st.com/stm32mpu/wiki/Linux_remoteproc_framework_overview#Remote_processor_boot_through_sysfs
To avoid the launch of the demo, you could for instance adapt the /usr/local/weston-start-at-startup/start_up_demo_launcher.sh file (assuming you still need Weston).
Some video link (not sure they are up to date with latest ecosystem v3)
https://www.youtube.com/c/stmicroelectronics/search?query=stm32mp1
Regards.