New VOXL2 not connecting to Windows machine that connects to Older VOXL2
-
I was previously able to connect to an older VOXL2 with my windows machine with both CMD and WSL. Just got a new VOXL2 yesterday and it is not recognized by the same windows machine.
USB-C to USB-A
QUSB_BULK_SN:A37F2E68
This is the device in device manager. Is there a driver for this device?
-
**
Does anyone have a driver for this? -
@rdjarvis , please make sure you are using a proper USB3.0 cable (USB-C to USB-A) or try another cable.
How are you testing if the device is recognized? Are you using
adbto test this? On some machines you need runsudo adbin order to access VOXL2. (may need to runadb kill-serverbefore tryingsudo adb) -
@Alex-Kushleyev Thank you the reply.
Yes I have the VOXL and multiple VOXL2s. I have used the same cables (USB-A-USB-C).
Device Manager sees the QBULK (Qualcomm) device, but cant install any drivers.
Both VOXL1 and previous VOXL2 connects without an issue.
I have tried ADB kill-server/start-server. then adb devices. Nothing appears.
I had the same issue with the VOXL in October and received help from the DEV team. No Luck. CHAT GPT helped and I was able to get the device recognized by adjusting the environmental variables on the Windows machine with success on VOXL and VOXL 2.
The new VOXL2 I just received isnt popping up under adb devices, and I cant find the driver for the QBULK device.
RDJ
-
I believe that if the device is showing up as QBULK, it boots into recovery mode. It is strange that this is happening to a brand new VOXL2. I will check about this. Have you ever tried the unbricking procedure for VOXL2? https://docs.modalai.com/voxl2-unbricking/ ?
Before you do try it on this board, let us get back to you.
-
@Alex-Kushleyev Thank you for the response. I have not tried unbricking.
-
The board is in eDL mode (emergency download). Can you please check that SW2 is off and if the issue is persists, provide serial number of voxl2 board, we will check test records.
