THE Classic bug (No available USB device found with matching PID/VID)

[terenss]

Hello everybody !

I'm a axoloti newbie. The Axoloti software console always write No available USB device found with matching PID/VID. But the messages before have changed.

I'm on Win7 X64. My USB cable is working, I did rescue firmware, WinUSB install, Zadig, external powering, many unplugging re-plugging... but I still get infamous No available USB device found with matching PID/VID

Any suggestion ?

Axoloti version : 1.0.12-2-0-g60a2f99 build time : 08/04/2018 20:20:07 CEST
Link to firmware CRC E95BAC96
Status: factory (1.0.12,anon) : OK ( 1.0.12,clean )
Status : home : OK
Status: community (1.0.12,anon) : OK ( 1.0.12,clean )
No available USB device found with matching PID/VID
search path : C:\Users\Toyoto\Documents\axoloti\axoloti-factory\objects
search path : C:\Users\Toyoto\Documents\axoloti\objects
search path : C:\Users\Toyoto\Documents\axoloti\axoloti-contrib\objects
finished loading objects

[terenss]

And I'm not using any hub on this USB port

[UHF]

The USB cable IS a data cable and not a charging cable?

[terenss]

Hello UHF,

It is a data cable. I've been able to successfully upload firmware on my axoloti with it. I've tried again with another high quality Anker data cable without success.

[UHF]

There seems to be a number of issues that can cause this. Have you looked at this thread?:

Win 7 no usb found with matching PID/VID

Hoi. I recieved my axoloti yesterday. The software reports a problem with the driver and can not connect, DId the installation as told in the guide. Axoloti core is visible in Win 7 Device Manager, The software found no matching PID/VID., when i try to connect. (USB is connected off course and the lights on the board blink at start up) When i choose select device, it sees the axo core and the usb port, at CPU ID it reads: not available: driver not installed. Re-installing the driver did…

Someone even had a problem with antivirus software blocking it.

[terenss]

I installed Windows 10 because Win7 seems to have trouble with Axoloti. It worked like a charm... at the begining. When I plugged in an headphone, I got a java error and now I have the same message again ("No available USB device found with matching PID/VID")

Thanks for the link. I will use the Zadig.exe in order to reload firmware. The board isn't visible in normal mode so I boot in rescue mode (S1), unplug, plug again in normal mode and then windows loads the core. And NOW IT IS WORKING !!!! GREAT !!

[deadsy]

Another datapoint (this time on Linux/ubuntu 18.04):

[   83.507607] usb 1-14.4: new low-speed USB device number 18 using xhci_hcd
[   83.587618] usb 1-14.4: device descriptor read/64, error -32
[   83.775540] usb 1-14.4: device descriptor read/64, error -32
[   83.963448] usb 1-14.4: new low-speed USB device number 19 using xhci_hcd
[   84.043433] usb 1-14.4: device descriptor read/64, error -32
[   84.231360] usb 1-14.4: device descriptor read/64, error -32
[   84.339591] usb 1-14-port4: attempt power cycle
[   85.507169] usb 1-14-port4: Cannot enable. Maybe the USB cable is bad?
[   86.358866] usb 1-14-port4: Cannot enable. Maybe the USB cable is bad?
[   86.359176] usb 1-14-port4: unable to enumerate USB device

And indeed it was (one cable swap later)....

[  138.840224] usb 1-14.4: new full-speed USB device number 22 using xhci_hcd
[  138.942059] usb 1-14.4: New USB device found, idVendor=16c0, idProduct=0442
[  138.942065] usb 1-14.4: New USB device strings: Mfr=1, Product=5, SerialNumber=3
[  138.942069] usb 1-14.4: Product: Axoloti Core
[  138.942073] usb 1-14.4: Manufacturer: Axoloti
[  138.942077] usb 1-14.4: SerialNumber: 0045001E3237511832333637

[sebiiksbcs]

I've been getting this type of error trying to connect to Axoloti Core on Ubuntu 18.04 out of the blue for days now without previously having changed anything in my setup ("although not "error -32" but error -110" for me)...

I am able to connect to STM32 in DFU mode at all times and flash firmware with any USB cables I tried, but can't connect to the Axoloti Core after reboot...

Tried all of the possible solutions online I could find, still no luck. At one point the connection came back for about an hour, then back to the error... People in forums say it could be a hardware fault at the host USB port but any other USB devices connect without problems...

Anyone have a tip?

[jcgriggs]

USB 110 is an incomplete transfer error, usually caused when the device power dips during the transfer. Make sure the Axoloti is getting enough power - no other devices on hub, etc.

Hope this helps,
John

[sebiiksbcs]

Thank you jcgriggs, external power, faulty USB cable etc. was among the things I've tested, also curious is the fact that Axoloti in DFU mode connects and flashes fine but isn't recognized after reboot.

I've come to the temporary conclusion that the fault may have to do with the current linux kernel version, that or the USB ports on my computer somehow became faulty.

[jcgriggs]

Sorry - I don't have any real insight other than recognizing the USB error code from something else I worked on.

Best of luck,
John