--debug shows no additional information

[dlarue]

I'm trying to debug why I can not flash the Arduino Uno-Q and keep getting "qdl: unable to open USB device" so I run:

qdl-2.22/qdl -d --allow-missing --storage emmc flasher-updater-1598470955/arduino-unoq-debian-image-20251024-412/flash/prog_firehose_ddr.elf flasher-updater-1598470955/arduino-unoq-debian-image-20251024-412/flash/rawprogram0.xml flasher-updater-1598470955/arduino-unoq-debian-image-20251024-412/flash/patch0.xml

and it shows no additional data except version number:

qdl version v2.2-dirty
qdl: unable to open USB device
Waiting for EDL device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device
qdl: unable to open USB device

[facchinm]

Hi @dlarue ,
you should be able to flash via sudo or by adding an udev rule for the board as in arduino/ArduinoCore-zephyr#240

[dlarue]

Hi @facchinm , I would think so too but so should my userID as part of dialout group, with /dev/ttyUSB with 666 privileges, dmesg does not show the device closed and I even stopped the ModemManager service. Does the Windows and Mac versions require admin privileges because if so, that should be documented.

I just tried on another 24.04 based system as root and it did succeed. What appears to happen is the arduino-flasher-cli process looks like it disconnects the /dev/ttyUSB0 device and then communicates with the USB device using something else.

[facchinm]

Ah, I think I know the issue then, it's the qcserial driver interfering with qdl. Blacklisting it should do the trick. If it does, I'll invoke the help of content team to update the documentation. Thanks for the extensive report!

[dlarue]

It's mentioned that qcserial should be blacklisted when it causes a disconnect message when you plug in the Uno-Q.
I did not see that disconnect so didn't blacklist it. But I had unloaded the driver at one point to see what's up. I will try that on this system which just worked as root.

[dlarue]

I went back and verified the doc( https://docs.arduino.cc/tutorials/uno-q/update-image/ ) shows if there is a qcserial device disconnect then blacklist. I believe they should have stated if the device created is associated with the qcserial module...

But regardless, I blacklisted it and rebooted and still my userID can't flash it. Is there a version of qdl which has more verbose debugging output?

[per1234]

--debug shows no additional information

This project only produces builds of the upstream project:

https://github.com/linux-msm/qdl

A paucity of debug output when the --debug flag is used would be something to take up with the developers of the upstream project, as it is out of scope for this repository.

keep getting "qdl: unable to open USB device"

I see you already opened an issue about that at arduino/arduino-flasher-cli#26. That issue will be used for any further discussion of the failure.