In our devices we use a custom PCB that has a slot for plugging in the Verdin AM62 module. Our devices dont have displays, hence there is no HDMI port on the board.
My goal is to achieve easy batch programming of several devices. I was planning to have the following steps:
Assemble device, slot the Verdin module in
Connect device to a local network that serves my custom TorizonOS image (with autoinstall option enabled) over ethernet
Boot device
Expect OS to install automatically.
But I see that on our custom PCBs tezi fails to start because there is no graphical backend i guess. Below is the tezi.log from a Verdin am62 module with only Torizon Easy Installer image installed
/ # cat /var/volatile/tezi.log
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimal, offscreen, vnc, wayland.
So, my question is, is tezi usable at all without the graphical backend? Does this behaviour mean that toradex boards are designed to be used with the display? Or do we need to do some HW hacks to trick the system into thinking that hdmi is connected?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
Thank you for reaching out with your question. The Toradex Easy Installer (Tezi) is indeed designed to operate with a graphical interface, typically requiring a display or a remote interface like VNC. Since your custom PCB lacks HDMI support, you can use VNC to access the Tezi GUI remotely over the network, which is a practical solution for your setup.
Here’s how you can proceed:
Network Configuration: Ensure your device is connected to a local network accessible from your host machine.
VNC Setup: When Tezi boots, it should automatically start a VNC server. You can connect to this server using a VNC client from your host machine. The default VNC port is usually 5900, so you would connect to device_ip:5900.
Autoinstall Configuration: To automate the installation process, ensure your custom TorizonOS image is configured with the autoinstall option enabled. This can be set in the image’s JSON configuration file.
Testing: Before deploying this setup in production, test the VNC connection and autoinstall process to ensure everything works as expected.
By using VNC, you can effectively manage the installation process without needing a physical display, allowing you to perform batch programming of your devices efficiently.
I hope this helps! If you have any more questions, feel free to ask.
Best regards,
Toradex AI Assistant.
Please, also check if these links can help you solve your problem:
The Toradex Easy Installer is expected to work even without a graphical output.
Which version of the Toradex Easy Installer are you using? Is it the same that is pre-installed to your modules?
Also, what is the serial number of the module you are using?
Serial number of my “test module” is 15361822, Verdin AM62 V1.1B
I was testing Toradex Easy Installer 6.8.1+build9 , the image that is available to install after going through the recovery procedure.
I have to admit, since I don’t have any fresh out of factory modules at the moment, I don’t know which version of Tezi is preinstalled.
In addition:
The method I have described in the original post i tested with the USB media. But i’m not sure it matters, since it seems that Tezi fails to startup.
And to clarify, when I plug in the same module into my Yavia board, Tezi starts up as expected, so most likely some required hardware pin is not in the right state.
Sorry for the delay in getting back to you. @bruno.tx is busy attending Embedded World at the moment together with most of our team. I am working on this topic now and will try to reproduce the issue. You can expect an answer from me later today.
I could not reproduce this issue using our Mallow carrier board. I had a Verdin AM62D 1GB WB IT V1.1B module installed with Toradex Easy Installer version 6.8.1 plugged into the board. I had no display connected to the board. I served a reference Torizon OS image configured with autoinstall true over my local network server. The module automatically started the installation of the image and I could then reboot the device into this Torizon OS image.
Do you have one of our evaluation or production carrier boards with you? If yes, could you try to reproduce the issue on it?
Apologies, perhaps my explanation wasn’t clear enough.
We have a Yavia development board, that works without any display connected. The steps that you have performed work here as well.
My issue is that these steps don’t work on our custom PCB that has no HDMI port at all. So it seems that there is some HW difference, that prevents Tezi from starting (see tezi.log output in my original post).
So the reason I even posted this question is to check whether there are any HW requirements related to running the torizon easy installer image.
It looks like something is holding up weston from starting or delaying it and therefore the application itself does not start. I would like you to try a couple of things:
Can you try to run tezi from the command line using tezictl commands (for example, tezictl image-list should show the available images.)
Could you please send me the output of # cat /var/volatile/weston.log ?
The last thing would be to look into the hardware aspect of the issue. As this only happens on your custom carrier board, I would be curious to understand the differences when compared to a Toradex design. It would be helpful if you could send us your schematics in a pdf file to support.eu@toradex.com.
