I have a Ventuno Q (16GB) with the UNO Media Carrier (ASX00083) and a Waveshare 8-DSI-TOUCH-A panel. Everything is physically connected and confirmed working electrically 5V is reaching the panel through J13, the DSI ribbon is seated in DSI0 with contacts facing down, and the carrier is fully seated on JMEDIA/JMISC.
The panel backlight doesn't come on, which I believe is expected, it's waiting for a DSI init sequence that never arrives because there's no device tree overlay loaded for this panel.
On the UNO Q, arduino-linux-config carrier enable media-carrier display=8-dsi-touch-a handles this. On the Ventuno Q (Ubuntu 24.04, kernel 6.8.0-1078-qcom), that tool doesn't exist. arduino-app-cli doesn't have a carrier or display subcommand either.
What I see in dmesg confirms the DSI controller is initialized but currently routed to the ADV7535 HDMI bridge:
msm_dsi ae94000.dsi: supply refgen not found, using dummy regulator
DRM only shows DP-1, HDMI-A-1, and Writeback-1 — no DSI connector.
The I2C expander on the Media Carrier (TCA9555) isn't showing up on any bus either, so it seems like the carrier needs an overlay to be fully recognized.
My questions:
Is there a display overlay or device tree configuration available for the Ventuno Q + Media Carrier + Waveshare 8-DSI-TOUCH-A combination?
Is carrier support for the Ventuno Q coming through a system update, or is there a manual step I'm missing?
If overlays aren't available yet, is there a timeline or a way I can help test?
Hi @penfold1. We currently only support the use of the UNO Media Carrier with the UNO Q. Unfortunately there are some significant technical challenges to supporting use with the VENTUNO Q.
Excellent observation. Access to the I2C bus is indeed the significant challenge that must be overcome in order to use the MIPI DSI interface exposed by the UNO Media Carrier.
I don't have any information regarding plans to provide official support for using the UNO Media Carrier with the VENTUNO Q. This is of course something we would like to do.
Fortunately the VENTUNO Q has an on-board HDMI socket, which allows use with HDMI monitors. Furthermore, it has three on-board MIPI CSI interfaces, which make it possible to use cameras without the need for a carrier board.
The community is of course welcome to work independently to find solutions. Perhaps other forum members will comment here with suggestions on how to proceed with that endeavor.
I am a bit befuddled though. The Arduino website specifically says that the media carrier is for the Ventuno and the Ventuno board itself has information on the board that corresponds to the media carrier being used.
This is taken from the arduino website:
“Extend the multimedia capabilities of UNO Q and VENTUNO Q by enabling advanced vision, display, and audio applications with plug-and-play simplicity. ”
Surely, the intent must be to use the media carrier with the ventuno board?
Thanks for bringing this to our attention. That statement is incorrect. I have notified the people at Arduino who manage the store of the error.
I apologize for any confusion caused by this statement. If you are not satisfied with the UNO Media Carrier, you are welcome to submit a return request to the seller you purchased from. If you purchased from Arduino Store, you can use this contact form for that purpose:
If you look at the spec sheet for the Ventuno you can see that there is an outline on the back of the board that aligns with the carrier and it had the text, “UNO Carrier” on it.
"UNO Carrier" is a general term for any supplemental board that connects to the "high-speed headers" (JMISC, JMEDIA) on the bottom of the VENTUNO Q or UNO Q boards.
So this does not refer to the UNO Media Carrier specifically, but rather to a general class of hardware.
We can anticipate the creation of various UNO Carrier products as time goes on. Community members have already independently created some. For example:
We also have another official UNO carrier product in the works:
Ideally all UNO Carriers would be compatible with all boards that have the standardized "high-speed headers". However, technical challenges may make this infeasible in some cases. So you should not assume such compatibility. Of course it is reasonable to assume that if the product listing states compatibility.