HDMI Screen blank after Torizon Os installation

Technical Support
, , ,
1

Hello,

I am using the Verdin iMX8M Plus Quad 4GB WB IT (V1.1B) module on the Mallow V1.1C carrier board. My setup includes a 10.1-inch HDMI display, which works fine with the preinstalled Tezi software.

I tried installing Torizon OS 7.1.0 and Torizon Core using the Tezi tool. After completing the installation and restarting the module as recommended, the Torizon logo with a loading bar appears briefly. However, after a few seconds, the screen goes blank, and nothing is displayed.

Regards,
Anurag

2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello Anurag,

Thank you for reaching out. It sounds like the issue with your HDMI display after installing Torizon OS might be related to configuration settings. Here are some steps you can take to troubleshoot and resolve this:

  1. Device Tree Overlays: Ensure the correct device tree overlays are applied for your HDMI display. Torizon OS may require specific overlays for different display interfaces. You can apply these using the Toradex Easy Installer or by manually modifying the device tree settings.

  2. Display Resolution and Timings: Verify that the display resolution and timings are set correctly. Check your display’s datasheet to ensure the horizontal and vertical periods are configured properly in the device tree.

  3. Weston Compositor: Torizon uses the Weston compositor for display management. Make sure the Weston container is running correctly. You can start it with the following command:

    docker run -d --rm --name=weston --net=host --cap-add=CAP_SYS_TTY_CONFIG torizon/weston

    This should bring up the GUI on your display if everything is configured correctly.

  4. Debugging: Use the modetest utility from the libdrm-tests package to test and debug the display output. This can help identify if the issue is with the display settings or the hardware connection.

  5. Check Connections: Ensure all physical connections between the module, carrier board, and HDMI display are secure and properly seated.

By following these steps, you should be able to identify and resolve the issue with your HDMI display. If the problem persists, reviewing the display’s documentation for specific configuration requirements might be helpful.

Best regards,

Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Cog container unstable on Torizon OS 7.

3

torizon@verdin-imx8mp-15502128:~$ dmesg | grep hdmi
[ 1.229862] samsung-hdmi-phy 32fdff00.hdmiphy: failed to get phy apb clk: -51 7
[ 1.284852] imx-hdmi-pavi 32fc4000.hdmi-pai-pvi: No pvi clock get
[ 1.929471] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2)
[ 1.930494] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driv er
[ 1.931541] imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw_hdmi_imx_o ps)
[ 5.837429] debugfs: Directory ‘30cb0000.aud2htx’ with parent ‘audio-hdmi’ al ready present!
[ 5.847230] imx-cdnhdmi sound-hdmi: i2s-hifi ↔ 30cb0000.aud2htx mapping ok
[ 5.858292] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound /card0/input2
torizon@verdin-imx8mp-15502128:~$

4

Hi @AnuragBluAI !

Welcome to Toradex Community! Feel free to browse around! :smiley: :tada:

Are you using

Since you are on Mallow, you are using the X14 HDMI connector, which is the native HDMI. Currently, on Torizon OS 7, a bug on Weston container was found and it is being worked on.

A current workaround is to set WESTON_DISABLE_ATOMIC=1. For instance:

docker container run -d --name=weston --net=host     --cap-add CAP_SYS_TTY_CONFIG     -v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/     --device-cgroup-rule="c 4:* rmw" --device-cgroup-rule="c 253:* rmw"     --device-cgroup-rule="c 13:* rmw" --device-cgroup-rule="c 226:* rmw"     --device-cgroup-rule="c 10:223 rmw" --device-cgroup-rule="c 199:0 rmw" -e WESTON_DISABLE_ATOMIC=1 torizon/weston-imx8:4     --developer

Please note that this currently is just a workaround.

EDIT: There is another workaround, which involves removing the --current-mode from the entry.sh script of the weston container (torizon-containers/support-files/weston/entry.sh at stable · torizon/torizon-containers · GitHub) and rebuilding it. Although it is more work, I was informed that this a better approach from the technical point of view.

Best regards,

5

Hello @henrique.tx ,
Thank you for the reply.

This helped me get the display running. Create a systemd service file to start the Weston container automatically at boot.

Best Regards,
Anurag

6

Hi @AnuragBluAI !

Thank you for the feedback. I am glad that the workaround worked for you :slight_smile:

By default Torizon OS has already a systemd service to start your containers automatically at boot: docker-compose.service.

It launches the containers at /var/sota/storage/docker-compose/docker-compose.yml. During development, you can simply modify this file to have your containers launched automatically.

For production, you should use TorizonCore Builder to Bundle your containers into your customer Torizon OS image. You can check this documentation for more information: TorizonCore Builder Tool - Customizing Torizon OS Images | Toradex Developer Center

Best regards,