Hi @rolando5005 !
Actually, by using Torizon OS, you can leverage Torizon Cloud to update your devices (OS and/or application) on field using online or offline approach:
By using Torizon Cloud it is quite easy to deploy new version of OS and/or your application on the field with security and robustness.
If you have interest, you can try it for free. Just check the torizon.io website
Regarding the HDMI display, since you are using the native HDMI, isn’t it possible that you should control the card0-HDMI-A-2
instead of card0-HDMI-A-1
?
You can actually check which HDMI output you are using before manipulating its status:
torizon@verdin-imx8mp-15247228:~$ cat /sys/class/drm/card0-HDMI-A-1/status
disconnected
torizon@verdin-imx8mp-15247228:~$ cat /sys/class/drm/card0-HDMI-A-2/status
connected
When connecting the HDMI monitor to the native HDMI of Verdin iMX8MP on Dahlia, card0-HDMI-A-2
became connected instead of card0-HDMI-A-1
. So echoing off
to card0-HDMI-A-2
’s status disabled the display. I could wait several minutes and the HDMI monitor never activated itself. It only became active after echoing on
to card0-HDMI-A-2
’s status.
So I could not reproduce the behavior your are facing.
Here are the details of my setup:
- module Verdin iMX8MP Q 4GB WB IT V1.1A
- Toradex carrier board Dahlia V1.1C
- Torizon OS 6.7.0-build.18 (quarterly)
- HDMI monitor LG FLATRON 32UL750-W
Best regards,