I rebooted my computer and power-cycled the VENTUNO Q, but it still isn't detected.
Tested the USB-C cable with one of my Uno Qs, and the cable is good.
Tried another cable; App Lab still doesn't detect it.
The VENTUNO Q boots, the fan spins momentarily, then it goes to a beating heart, then flashes the entire LED panel and the STM LEDs. The power LED is on, as well as both LEDs on the Ethernet jack. Nothing shows up in Device Manager.
Have you tried powering via barrel jack or screw terminals? I was unable to make a USB-C connection until I powered using the barrel connector. I initially tried the supplied cable and USB-C power supply, in conjunction with the Arduino USB-C Hub, and it would power up, but the USB connection to the computer would not function.
I'm using the barrel jack. Now it's intermittent whether it appears in Device Manager or not. When it does, and I try to flash via CLI, it exits with error code 1 immediately after asking me to connect the board in EDL mode.
Hi @CYED. That tutorial is written for a planned new version 0.5.4 of the Arduino Flasher CLI tool. The version 0.5.3 you currently get from the "Software" page doesn't have full support for the VENTUNO Q.
Please download the release candidate version 0.5.4-rc.2 from the arduino-flasher-cli-0.5.4-rc.2-darwin-arm64.tar.gz link you will see under the "Assets" section of the release page in our GitHub repository for the Arduino Flasher CLI codebase:
That version should work as described in the tutorial. Please let us know if you encounter any problems flashing the operating system image using Arduino Flasher CLI 0.5.4-rc.2.
I have notified the team responsible for Arduino Flasher CLI of the need to make the production 0.5.4 release. I apologize for any confusion caused by this oversight.
Thanks.
With the right version of the tool, I was able to reinstall the card successfully.
It restarted properly.
It is currently updating AppLab.
Originally, the problem occurred during the first boot: it performed the update but then failed to restart.
I hope everything will be fine now.
I resolved this but there were a few "learning opportunities" along the way.
Bridged the pins to enable EDL mode.
I had to unbind qcserial kernel module from grabbing the Qualcomm board when connected (Fedora)
-> echo -n "7-1.1.4:1.0" | sudo tee /sys/bus/usb/drivers/qcserial/unbind
sudo./arduino-flasher-cli flash ventunoq
even though I had set up udev rules, this still required root; I went through multiple attempts without sudo, and got communication warnings about unable to connect to the board
that happened several times, and each time, it had to redownload the whole OS package (it seemed to get cleaned up on quit, and I couldn't seem to cache it locally, very annoying)
the user guide section on reflashing says to flash latest but arduino-flasher complains that that is deprecated.
That got me back to a "clean" board which I then set up in PC mode instead of SBC mode.
Then I updated things via App Lab.
Then I updated the OS via ssh.
Along the way, adb also got wedged and reported things like
2026/09/28 14:47:56 ERROR unable to connect to ADB device error="exit status 1" output="error: device '68499932' not found\\n" serial=68499932
2026/09/28 14:47:56 WARN failed to get custom name serial=68499932 error="ADB device not found"
2026/09/28 14:47:56 ERROR unable to connect to ADB device error="exit status 1" output="error: device '68499932' not found\\n" serial=68499932
2026/09/28 14:47:56 WARN failed to get custom name serial=68499932 error="ADB device not found"
And I needed to kill adbd fully and restart App Lab.
In the meantime I'll also point out that the App Lab 0.10.0 package for Debian/Ubuntu is fine, but I have to fully start with a fresh workspace every time on Fedora, or the second launch shows a blank window. I don't know what is going on there.
Oh, and the link to the VENTUNO Q category in the forum from the user manual is wrong (it goes to UNO Q section) and there is no VENTUNO Q section in the App Lab in-app documentation at the moment.
NB I haven't yet re-tried this in SBC mode so I'm not sure if the HDMI black screen thing is resolved by this sequence, but I am able to explore the running Linux and run things on the VENTUNO Q via App Lab over wifi and USB-C now (albeit the wifi seems to aggressively power save? and only wakes up if I ping from another machine? not sure).
Hi @andypiper. I'm glad you were able to recover your board by flashing the operating system image!
Is this what you are referring to by "workspace"?:
The primary method for gathering troubleshooting information for the Arduino App Lab application is via the DevTools console. If you share the content here, we can take a look to see if it contains a "smoking gun":
Start Arduino App Lab in the manner that produces the "blank window" fault.
Press the Ctrl+Shift+F12 keyboard shortcut.
The "DevTools" window will open.
Select the "Console" tab in the "DevTools" window.
Right-click on the main panel of the "DevTools" window.
A context menu will open.
Select "Copy console" from the menu.
This will copy the logs recorded in the console panel to the clipboard.
Open a reply here on this forum topic by clicking the "Reply" button.
Click the <CODE/> icon on the post composer toolbar.
This will add the forum's code block markup (```) to your reply to make sure the error messages are correctly formatted.
Press the Ctrl+V keyboard shortcut (Command+V for macOS users).
This will paste the copied logs into the code block.
Move the cursor outside of the code block markup before you add any additional text to your reply.
Click the "Reply" button to publish the post.
It is also possible some relevant information would be output by the application if you start it from a shell terminal.
Please let us know what you find when you do try it again.
You can use the arduino-flasher-cli download ventunoq command to download the image archive. Then pass the path of that file as an argument to the arduino-flasher-cli flash ventunoq command.
Thanks for bringing this to our attention! I submitted a report on your behalf to the team at Arduino responsible for this content.
Hi @kd7eir, @CYED, and @andypiper. In order to facilitate the investigation of the problem you reported, I am requesting you to provide the serial number of your VENTUNO Q.
The serial number is shown on the box the VENTUNO Q came in, as you see here:
This is in the "Data Matrix" format. I believe it can be read with any QR code reader app. I use the free open source Binary Eye Android app for this purpose.
If you prefer, you can send me the serial number via a DM. Just click the "Message" button on my forum profile page here:
However, this seems (!) to be OK now, after a reboot and any other package updates that happened in the meantime. May have been a WebkitGTK package issue, I am not completely sure.
Thank you for the pointer on arduino-flasher-cli download - somehow I completely missed that no matter how many times I checked the --help flags that is obvious now I see it. May be useful to add somewhere more clear in the documentation as well
I've still not yet tried in SBC mode again, but the VENTUNO Q is happily sitting on my home network at the moment and I haven't yet seemed to break it again!
One question about SBC mode and boot - is there any way to get console output or other visible activity on a screen before the desktop / greeter appears? The blank screen can otherwise be disconcerting.
that is obvious now I see it. May be useful to add somewhere more clear in the documentation as well 