Hi,
We are experiencing an issue trying to make the 7/10 inch DSI screen from Toradex work with the Aquila iMX95 SoM on the aquila development board via the DSI adapter.
We initially spotted the problem running our custom OS image on top of BSP 7.6.2, but the same thing happens when launching TEZI (7.6.1+build.12 build) with the DSI overlay enabled in overlays.txt:
fdt_overlays=aquila-imx95_panel-cap-touch-7inch-dsi_overlay.dtbo
There is clearly some activity going through the adapter with leds blinking on TEZI startup via recovery script and the screen backlight coming on, but nothing gets rendered.
The screen works ok on the similar verdin-imx95 setup (dahlia carrier board).
Is there anything that we’ve missed in the setup sequence specifically for aquila or is there a known issue?
Best regards,
Sergey @ AGI SDA
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
Hi Sergey,
Thank you for providing the detailed information about your setup. Let me help you troubleshoot the DSI display issue with your Aquila iMX95 SoM.
Overlay Configuration
For the Aquila iMX95 with DSI displays, there are actually two different overlays available depending on your hardware configuration(1):
- aquila-imx95_panel-cap-touch-7inch-dsi_overlay.dtbo - for native DSI interface
- aquila-imx95_adapter_panel-cap-touch-7inch-dsi_overlay.dtbo - specifically for use with the DSI Display Adapter(1)
Since you mentioned you’re using the Toradex DSI Display Adapter, you should try the adapter-specific overlay instead(2)(1).
Recommended Configuration
Update your overlays.txt to use:
fdt_overlays=aquila-imx95_adapter_panel-cap-touch-7inch-dsi_overlay.dtbo
(1)
The same dual-overlay approach exists for the 10.1" display as well:
- aquila-imx95_panel-cap-touch-10inch-dsi_overlay.dtbo (native)
- aquila-imx95_adapter_panel-cap-touch-10inch-dsi_overlay.dtbo (with adapter)(1)
Verification Steps
After applying the correct overlay:
- Reboot the device
- Check if the overlay was applied successfully by examining
/proc/device-tree/chosen/overlays/(3)
- Verify the display pipeline is correctly configured
The fact that you’re seeing backlight activity and LED blinking suggests the hardware connection is working, but the wrong device tree configuration may be routing the display pipeline incorrectly.
Please try the adapter-specific overlay and let me know if this resolves your issue.
Best regards,
Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
@ToradexAI With the aquila-imx95_adapter_panel-cap-touch-7inch-dsi_overlay.dtbo overlay, the screen does not react at all.
Hi Sergey,
Thank you for testing the adapter-specific overlay. Since neither overlay is producing the expected results, let me help you troubleshoot further.
Diagnostic Steps
First, let’s verify the overlay application status. You can check if the overlay was successfully applied by examining:(1)
ls /proc/device-tree/chosen/overlays/
cat /proc/device-tree/chosen/overlays/aquila-imx95_adapter_panel-cap-touch-7inch-dsi_overlay.dtbo
If the file exists and contains 0, the overlay was applied successfully.(1)
Hardware Connection Verification
According to the documentation, when using the DSI Display Adapter with the Aquila Development Board:(2)
- Connect the DSI Display Adapter to the DSI Connector (J44) on the Aquila Development Board
- Connect the flat ribbon cable from the display to the adapter, ensuring pin 1 alignment
Could you verify:
- The physical connection between the adapter and J44 on the Aquila Development Board
- The ribbon cable orientation (pin 1 to pin 1)
- Whether you’re testing with the 7" or 10.1" display specifically
Additional Information Needed
To help diagnose this further, could you provide:
- OS version details - Run
tdx-info to get complete system information (tdx-info documentation)
- Kernel messages - Check
dmesg | grep -i dsi for any display-related errors
- Overlay verification - Confirm which overlays are currently loaded
Known Considerations
The Aquila iMX95 has specific DSI routing configurations that may differ from Verdin iMX95.(3) The fact that the same display works on Verdin iMX95 + Dahlia but not on Aquila iMX95 + Development Board suggests there may be a carrier board-specific configuration issue.
Please share the diagnostic information above, and I’ll help you investigate further.
Best regards,
Toradex AI Assistant.
Did you like my answer?
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
Hello @sergefr,
The current configuration of the Aquila iMX95 does not expose a DSI interface.
The DSI interface is used internally on the SoM to provide the DP output.
A custom configuration of the SoM would be possible, where DSI is exposed, but then DP would not be available.
The overlay is exactly made for such custom configurations.
At some point we may even have a standard configuration with the DSI output, but that is not the case at the moment.
The remaining display output is via LVDS, which is routed to the SoM pins but is not exposed in the current version of the Aquila development board and Clover Carrier Board.
What is your use case, do you need DP and DSI at the same time?
Best Regards,
Bruno
@bruno.tx At the moment, we only really need the DSI, so that we can test our applications’ touch screen behaviour with those standard screens.
We will be designing a custom board at some stage, but it would be really useful for us to have it working on the development board.
Thanks!
Hello @sergefr,
Thanks for the clarification.
For now, I would suggest you to use the Verdin iMX95 board that I think you should have available to test the DSI display.
On the Verdin iMX95, we do expose the DSI interface, which is accessible directly via the flat connector on the Mallow carrier board.
If this is not an option, please let me know so we can discuss a solution.
Best Regards,
Bruno
