2022-03-23 05:27 AM - last edited on 2023-07-21 01:46 AM by Amel NASRI
Hi everyone.
I'm facing some issues when trying to define STM32CodeMonitor v1.3.0 or v1.4.0 as service on boot on Ubuntu 20.04 Desktop version.
I'm used to Node-RED and there is a procedure to set it as service on boot quite easy and stable to implement here.
I have already seached on STM32CubeMonitor wiki and here at forum for some procedure but won't found any solution. There is a way to define STM32CubeMonitor as service on boot already documented by ST?
Solved! Go to Solution.
2022-03-31 08:15 AM
Hello @_acv_atr
STM32cubeMonitor is an executable that is packaged through electron framework. Therefore procedure used to set it as a boot service may differ from Node-RED one.
On Ubuntu you can add it in the startup applications preferences to launch it at boot.
2022-03-31 08:15 AM
Hello @_acv_atr
STM32cubeMonitor is an executable that is packaged through electron framework. Therefore procedure used to set it as a boot service may differ from Node-RED one.
On Ubuntu you can add it in the startup applications preferences to launch it at boot.
2022-03-31 08:28 AM
Hello @Richard.Chvr
Thank you for your answer and workaround.
That approach works assuming automatically login by the user on power-up.
To ensure a better security approach, I want/need to start the STM32CubeMonitor before use login.
Tipically I can do this using a service.
If you have other idea or workaroud to implement this, please, let me know.
Thank you