HDMI display become blank after Torizon OS Easy Pairing installation and successful device pairing

My Setup:

Verdin iMX8MP Q 4GB IT (V1.1B, PN 00631101, SN 08777772)

Verdin Development Board (V1.1F, PN 01561105, SN 12610832)

10.1 inch HDMI Touchscreen Monitor

USB mouse and keyboard

The HDMI Monitor is connected to Toradex DSI to HDMI Adapter. After power on the hardware for the first time, I installed Toradex OS Easy Pairing(7.7.0+build.40.modified.container (2026-07-16)). After the installation, I used the pairing code shown on the HDMI monitor for pairing. After the successful pairing, “Paired“ was shown on the HDMI monitor. But then, the display become blank/black even though I can still see the backlight.

I have tried to modify the overlays.txt:

fdt_overlays=verdin-imx8mp_native-hdmi_overlay.dtbo verdin-imx8mp_dsi-to-hdmi_overlay.dtbo

The change does not help. When I power off then on the hardware again, the display will show the Toradex icon or start-up logo before it turns blank again.

As I am new to Toradex, please can you tell me if this is normal. If not, what can I do to recover the display.

Thank you!

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.


HDMI Display Blank After Torizon OS Easy Pairing Installation

Based on your setup description, I can help troubleshoot this issue. However, I need one clarification first:

Which exact version of Torizon OS are you running?

You mentioned installing “Toradex OS Easy Pairing (7.7.0+build.40.modified.container (2026-07-16))”, but I need to know the underlying Torizon OS version on your Verdin iMX8MP module.

You can get this information by:

  1. Connecting via SSH to your device
  2. Running the tdx-info command

For more details on using this tool, see: Getting Device Information with Tdx-Info | Toradex Developer Center


Initial Observations

Looking at your overlay configuration, I notice a potential issue:

fdt_overlays=verdin-imx8mp_native-hdmi_overlay.dtbo verdin-imx8mp_dsi-to-hdmi_overlay.dtbo

Important: The Verdin iMX8M Plus does not have native HDMI support. The overlay verdin-imx8mp_native-hdmi_overlay.dtbo appears incorrect for your hardware configuration.(1)

Since you’re using the Toradex DSI to HDMI Adapter, you should only enable the DSI-to-HDMI overlay. According to the documentation, for Verdin iMX8M Plus with the DSI to HDMI adapter, the correct overlay is:

  • verdin-imx8mp_dsi-to-hdmi_overlay.dtbo(2)(1)

Recommended Next Steps

Once you provide the Torizon OS version, I can give you specific instructions. In the meantime, try modifying your overlays.txt file to contain only:

fdt_overlays=verdin-imx8mp_dsi-to-hdmi_overlay.dtbo

Remove the verdin-imx8mp_native-hdmi_overlay.dtbo entry, as this may be causing conflicts with the display pipeline.(1)

After making this change, reboot your device and check if the display works correctly.

Please share your Torizon OS version so I can provide more targeted assistance.

Best regards,
Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

sudo tdx-info

Software summary

Bootloader: U-Boot

Kernel version: 6.6.142-7.7.0 #1-Torizon SMP PREEMPT Fri Jun 19 08:16: 23 UTC 2026
Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo v t.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ost ree=/ostree/boot.1/torizon/cd0068be61bae17b474f2cdf5de592055facd3a9c05dfcb31fffd dddd5fa4bd0/0 video=HDMI-A-1:1920x1080@60
Distro name: NAME=“Torizon OS”
Distro version: VERSION_ID=7.7.0-build.40
Distro variant: VARIANT=“Docker”
Hostname: verdin-imx8mp-08777772

Hardware info

HW model: Toradex Verdin iMX8M Plus on Verdin Development Board

Toradex version: 0063 V1.1B
Serial number: 08777772
Processor arch: aarch64

Thank you for providing the system information! Now I can give you more specific guidance.

Analysis

You’re running Torizon OS 7.7.0-build.40 on a Verdin iMX8M Plus with the Verdin Development Board.

I notice something important in your kernel command line:

video=HDMI-A-1:1920x1080@60

This video parameter is forcing a specific resolution on the HDMI output, which may be causing conflicts after the Easy Pairing process completes.

Solution

Based on the documentation for your hardware configuration, here’s what you need to do:

Step 1: Correct Your Device Tree Overlay Configuration

Your current overlays.txt contains an incorrect overlay. The Verdin iMX8M Plus does not have native HDMI — it uses DSI that must be converted to HDMI via the adapter.(1)

Remove the incorrect overlay and use only:

fdt_overlays=verdin-imx8mp_dsi-to-hdmi_overlay.dtbo

This is the correct overlay for using the Toradex DSI to HDMI Adapter with your Verdin iMX8M Plus module.(2)(1)

Step 2: Modify the overlays.txt File

Connect to your device via SSH and run:

# Get the current OSTree deployment hash
cat /proc/cmdline

Look for the hash in the ostree= parameter. Based on your output, it appears to be:
cd0068be61bae17b474f2cdf5de592055facd3a9c05dfcb31fffdddddd5fa4bd0

Then modify the overlays file:

# Navigate to the correct directory (replace the hash with yours)
cd /sysroot/boot/ostree/torizon-cd0068be61bae17b474f2cdf5de592055facd3a9c05dfcb31fffdddddd5fa4bd0/dtb/

# Edit or create the overlays.txt file
sudo sh -c "echo 'fdt_overlays=verdin-imx8mp_dsi-to-hdmi_overlay.dtbo' > overlays.txt"

# Sync to ensure changes are written
sync

(2)

Step 3: Reboot

sudo reboot

(2)

What’s Happening

The display shows correctly during boot (Toradex logo) but goes blank after the system fully boots because:

  1. Wrong overlay combination: Using both verdin-imx8mp_native-hdmi_overlay.dtbo (which doesn’t exist for your hardware) and verdin-imx8mp_dsi-to-hdmi_overlay.dtbo creates a conflict in the display pipeline(1)

  2. Video parameter conflict: The kernel command line parameter video=HDMI-A-1:1920x1080@60 may be conflicting with the actual display configuration after Easy Pairing modifies the system

Expected Result

After applying only the correct DSI-to-HDMI overlay and rebooting, your HDMI display should work properly throughout the entire boot process and remain active after Easy Pairing completes.(2)(1)

If the issue persists after this change, please let me know and we can investigate further.

Best regards,
Toradex AI Assistant.


Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

I followed suggestion by ToradexAI by executing the following steps, I still cannot see the display after these changes:-

a) Removed unrelated *.dbto. Now, my overlays.txt has the following line:-
fdt_overlays=verdin-imx8mp_dsi-to-hdmi_overlay.dtbo

b) Changed display resolution to 1020x600. After change:-

torizon@verdin-imx8mp-08777772:~$ sudo tdx-info
Password:

Software summary

Bootloader: U-Boot
Kernel version: 6.6.142-7.7.0 #1-Torizon SMP PREEMPT Fri Jun 19 08:16:23 UTC 2026
Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/cd0068be61bae17b474f2cdf5de592055facd3a9c05dfcb31fffddddd5fa4bd0/0 video=HDMI-A-1:1020x600@60
Distro name: NAME=“Torizon OS”
Distro version: VERSION_ID=7.7.0-build.40
Distro variant: VARIANT=“Docker”
Hostname: verdin-imx8mp-08777772

Hardware info

HW model: Toradex Verdin iMX8M Plus on Verdin Development Board
Toradex version: 0063 V1.1B
Serial number: 08777772
Processor arch: aarch64

For your information, my HDMI display has these specs:-

ROADOM 10.1-inch touchscreen monitor
Display Specs:-
Native Resolution:1024 x 600
Max Input Resolution: Up to 1920 x 1080 (FHD support)
Panel Type: IPS LCD with 178° viewing angles
Touch Support: 5-point capacitive touch

Please let me know what else I can try.

Thanks!

Hello @ctee,

After pairing the device, the easy-pairing container should no longer run.
Therefore, there will be nothing to show on the screen.
Torizon OS has no desktop, you can read a bit more about it here:


Without changing anything on the overlays, you should still be able to see the splash-screen when turning on and off the board.
Could you confirm this is the case?

What would be good if you plan to use the DSI to HDMI output specifically, is to only leave that display overlay enabled. You already did that, so that is good.


With that working as expected, you have the option to deploy different applications to the board.
The path will depend on what exactly you want to do.

To just see some application come up on the screen, you can follow the final step of the quickstart and use the Torizon Cloud to deploy pre-made applications:

To setup a development environment, you can follow the following steps on the quickstart:

From there, you will be able to select the desired GUI framework, develop an application and deploy it to the device.

Best Regards,
Bruno

Hi bruno.tx,

I can confirm that I am still able to see the splash-screen when turning on and off the board. Thank you for confirming that it is normal to see nothing(blank) on screen after the splash-screen. I am using DSI to HDMI output as I am following the online tutorial.

To see some applications come up on the screen, I will proceed to next step of the [quick start] and use the Torizon Cloud to deploy the pre-made applications.

Thank you for your feedback!

Hi Bruno,

I went to Torizon Cloud to initiate the installation for the Demo APP (chromium-verdin-imx8mp). After the successful installation, I can now see the display on screen after the splash-screen. My issue is resolved.

Thank you!

Best Regards,
ctee

Hello @ctee,

Thanks for the update.
It is good to know you were able to get it working.

Best Regards,
Bruno

Hello Bruno,

I have just found out that after installing the Demo App (chromium-verdin-imx8mp),
I will have to execute the following command manually to see the display:

# sudo systemctl start docker-compose.service

I have to run this command after every power reset.

Best Regards,
ctee

Hello @ctee,

This should not be necessary, as the update via the Torizon Cloud should have enabled this service.

It is possible that it was disabled if the board was connected to the VSCode extension.

To enable it for every subsequent boot, you can run the following command:

sudo systemctl enable docker-compose

Note that this is a reasonable way to test the board and configure a PoC.

For production, we recommend using TorizonCore Builder to bundle the initial containers into a customized Torizon OS image.
More information about this tool can be found here: TorizonCore Builder Overview | Toradex Developer Center

Best Regards,
Bruno

Hello Bruno,

I no longer has to start the docker-compose service manually after executing the command below to enable:
# sudo systemctl enable docker-compose.service

Thank you!

Best Regards,
ctee