Issues with Aquila AM69 setup and HDMI monitor display

Hello,
I am testing an Aquila AM69 with the corresponding Carrier Board.

Initially, I tried to access the Easy Installer via a DSI to HDMI adapter, but it didn’t work. Later, I discovered that the adapter only works in DSI to DSI mode, as other users have encountered the same issue.

At that point, I connected the device using a Type-C cable via remote desktop (TightVNC) and installed Torizon OS 7. However, the monitor still didn’t display anything. After reading some comments, I realized that the overlay needed to be modified. However, I learned that this operation is not supported in the stable version, only in nightly builds.

After downloading the nightly version of Torizon OS 7, the kernel failed to boot properly, getting stuck halfway. I then installed the BSP 7 Downstream Linux Reference Multimedia for Aquila AM69, where the kernel boots correctly, and I can modify the overlays. I added the aquila-am69_dsi-to-hdmi_overlay.dtbo to the /boot/overlays.txt configuration file.

Unfortunately, the monitor still doesn’t display anything. I also ran the ps -A command, but I don’t see Wayland or Weston among the active processes.

I would like to ask whether it’s necessary to install and configure Wayland or Weston to get the monitor working, or if you have other suggestions to display something on the screen.

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

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


Hello! Thank you for your detailed description of your setup and the troubleshooting you’ve done so far.

Here’s how you can proceed to set up display output on your Aquila AM69 with a DSI to HDMI adapter:

1. Overlay Selection:

  • For the Aquila AM69 with the Toradex DSI to HDMI adapter, the correct device tree overlay to use is verdin-am62_dsi-to-hdmi_overlay.dtbo (not aquila-am69_dsi-to-hdmi_overlay.dtbo) as per the latest documentation:

Please update your /boot/overlays.txt to use:

verdin-am62_dsi-to-hdmi_overlay.dtbo

and then reboot your system.

2. Verifying Display Detection:

  • Boot the system and check if the EDID (Extended Display Identification Data) of your monitor is detected by running:
    find /sys/devices -name "edid"
    
  • If you see an EDID file, your display connection is recognized at the kernel level.

3. About Weston/Wayland:

  • On Torizon OS, the graphical environment (Wayland/Weston) runs inside a container by default. If it isn’t running, the display output will remain blank even if the hardware is detected.
  • On the Reference Multimedia Image (BSP Linux), a display compositor (like Weston/X11) does not run by default. You need to start your own graphical application or compositor.

Suggested Steps:

  • Try the correct overlay and verify EDID detection first as described above.
  • If using Torizon OS, ensure the “Weston” container is running. You can check running containers with:
    docker ps
    
  • For BSP Linux, consider starting a graphical application manually for testing, such as running kmscube or installing and running Weston/X11 as needed.

Additional Notes:

  • Ensure the DSI to HDMI adapter is properly and securely connected.
  • Double-check your monitor input settings and cables.

For detailed steps and more troubleshooting on displays:

Please try these steps and update me on your EDID detection and whether the correct overlay resolves your display issue.

Best regards,
Toradex AI Assistant.

Hi,
I managed to boot the Torizon OS Nightly version, but the overlay file I need to modify is not available.

So, I reinstalled the BSP 7 Downstream Linux Reference Multimedia and edited the /boot/overlays.txt file, adding:
verdin-am62_dsi-to-hdmi_overlay.dtbo

After rebooting the system, I get the following error related to Weston:

[FAILED] Failed to start Weston, a Wayland compositor, as a system service.
See ‘systemctl status weston.service’ for details.
[DEPEND] Dependency failed for Start a wayland application.

Also, when I run the command find /sys/devices -name “edid”, the output is:

root@aquila-am69-12593514:~# find /sys/devices -name “edid”
/sys/devices/platform/bus@100000/4a00000.dss/drm/card0/card0-DP-1/edid
root@aquila-am69-12593514:~#

Despite all this, I still don’t see anything displayed on the monitor connected via HDMI.

Hello @Stefano,

We recommend using the latest 7.3.0 quarterly releases at this point as they have been released.

Currently, the DSI to HDMI adapter is not working with the Aquila AM69 module.
For now, I recommend that you use the DisplayPort output on the Aquila Development board.
Is that sufficient for your current use case?

Best Regards,
Bruno

Hi,
since the adapter is a Verdin DSI to HDMI , does that mean it cannot be used to connect a monitor to the Aquila SoM?

Is the only working option to connect the DisplayPort (J27) directly to a monitor that has a native DisplayPort input, without using any adapters?

Is there any other possible solution, considering that my monitor does not have a DisplayPort input?

Hello @Stefano,

This is actually not a problem with the adapter itself.
Previously there was a software issue with the DSI output of the Aquila AM69, but that has been resolved.
However, the issue now is that there is an issue with the Aquila Development Board V1.2 which causes the adapter not to work.
This will be solved in a new revision of the board and we will publish an errata explaining the issue.


Some DisplayPort to HDMI adapters have worked in the past.
From our testing, it depends on the monitor and the adapter, but such configuration could be possible.
If this does not work in your setup, at the moment the way to go would be to use a native DisplayPort monitor.

Best Regards,
Bruno

Hi,
I have another question.
When I purchased the Carrier Board V1.2B and the Aquila AM69 SoM, I also bought a Verdin DSI to LVDS Adapter Rev 1.1.
Does this adapter also not work with this type of board

Hi @Stefano,

The issue on the DSI to HDMI adapter is related to the DDC signals on HDMI.
This is not a problem when using an LVDS display.

Therefore, the DSI to LVDS adapter will work with the Aquila Development Board V1.2B, as long as you connect a compatible LVDS display to it.

We provide a compatible display for evaluation: Capacitive Touch Display 10.1" LVDS | Toradex Developer Center
Most LVDS displays are expected to be compatible with the LVDS signal itself, however some adapter for the connector or voltages provided may be needed if using other displays.

Best Regards,
Bruno

Ok, perfect.

Unfortunately, I don’t have the Capacitive Touch Display 10.1" LVDS. I would like to connect a 15" LVDS display that i already use with the IXORA V1.1B board together with the Apalis iMX8 SoM, which can be directly connected to the Verdin DSI to LVDS Adapter Rev 1.1.

On the IXORA V1.1B board, a small modification is made: the display’s VDD uses 5V. The other voltage and signal details are shown in the image below.

Can I safely connect this display to the Aquila board for testing purposes, without risking any damage to the hardware?
If needed, I can also provide additional details from the display’s datasheet.

Hi,
while reviewing the displays available in our warehouse, I noticed we have an older 15-inch display which might have voltage values more aligned with those of the 10.1" Capacitive Touch Display LVDS. This could make it more suitable for testing with the Aquila SoM.

Below, I’ve included images showing the datasheet values for the 15" display.
Best Regards,
Stefano


Hello @Stefano,

If you have used these displays with the Ixora Carrier Board in the past, you should be viable to be used with the DSI to LVDS adapter.

It provides both 5V and 12V power, on different pins.
The 5V is only provided on a single pin, so the current is somewhat limited.

I recommend that you check the datasheet for the DSI to LVDS converter to be sure that your connections are correct: Toradex DSI to LVDS Adapter | Toradex Developer Center

Also, it is very likely that you will need a custom device tree overlay for your display.
This would be mainly for adjusting timings and configuring the correct touch controller if using a touchscreen.
To create your custom overlay and apply it to Torizon OS, I recommend that you use the following guide: Device Tree Overlays on Torizon | Toradex Developer Center
Please use the latest Torizon OS 7.3.0 as a starting point: Download Links | Toradex Developer Center
As per the overlay itself, the following is a good starting point: aquila-am69_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dts « overlays - device-tree-overlays.git - Sources for Device Tree Overlays

Best Regards,
Bruno