No available USB device found with matching PID/VID

#12

Hello Johannes,

I just received my Axoloti today, and unfortunately am getting connection issues on Windows 7. It appears that the drivers and software are installed correctly.

However I'm having a similar issue as this thread, and also tried the DFU mode and got the error:

No devices in DFU mode detected. To bring Axoloti Core in DFU mode, remove power from Axoloti Core, and then connect the micro-USB port to your computer while holding button S1. The LEDs will stay off when in DFU mode.

You mentioned it "is probably an unknown hardware error". Can you elaborate?

Here is the output I get when first starting the software:

Axoloti version : 1.0.12-0-g80370d2 build time : 02/02/2017 20:39:14 CET
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\fineberg\Documents\axoloti\axoloti-factory\objects
search path : C:\Users\fineberg\Documents\axoloti\objects
search path : C:\Users\fineberg\Documents\axoloti\axoloti-contrib\objects
finished loading objects

Any advice would be appreciated.

Thank you,
Jeff

#13

if this is a new Axoloti , that you have only just plugged in, its unlikely to be hardware issue.
(as Johannes has various tests he runs on the board, and I think this includes uploading the firmware - iirc)

first thing I would check is the usb cable, be aware many micro usb cables are power ONLY, used for charging , you need one with data... so try different cables.

also what is happening with the Axoloti leds when you power up,
both when you don't press S1, and when you do.

#14

Actually I tried the Axoloti on a Windows 8 and all is well - effortlessly! So the cable and the Axoloti are fine, and it appears to be a Windows 7 issue. So even though the drivers appeared installed after plugging it into my computer (this was after software installation as per instructions), I still get the error. It appears to be a Windows 7 compatibility issue?

#15

Hmm, with windows 7 , it appears you still have to run Zadig to install the winusb drivers.
If you search on this forum, you'll find references to it.
( for some reason I thought this was no longer the case, but alas still appears to be required for some users)

#16

I think I am experiencing some issues related to these previous comments. Just received my Axoloti and can not get the patcher software to work.

Problem : Axoloti board turns on when connected to computer. Leds flash. Windows installs driver and says it's ok. When I try to run software I get "No available USB device found with matching PID/VID".

Things I have tried:

  • tried 4 different usb cables, verified they are data cables.
  • tried on multiple usb ports, 4 on one computer 5 on another.
  • axoloti_runtime installed to C:\Program Files (x86)\axoloti_runtime
  • tried on 2 different Windows 7 computers.
  • in axoloti software under -> Board -> Axoloti Core shows up but says "not accessible, driver not installed"
  • Put board into Rescue mode by holding down s1 and plugging in. In Zadig application chose
    STM32 Bootloader -> "Replace Driver" - > error " The driver Installation failed"

Not sure what else to try. I will note that regardless of what combination of computers and cable same exact errors exist. Seems to be a board problem?

#17

have you installed winusbcompat drivers?
its worth reading through this thread, as it covers issues other windows 7 users have had in the past.

#18

Trying to install this winusbcompat drivers. I tried to update the driver(one found from the thread you provided) and it says I already have the latest version. I then uninstalled the current driver and reinstalled using winusbcompat drivers. still getting same error message in axoloti software.

#19

Hello,
it's been a while since I last used my Axoloti.
I installed anew (had it installed before on my system, which is Ubuntustudio, Ubuntu 16.04.3 LTS)
I get the infamous "No available USB device found with matching PID/VID".
this is what I tried so far:
* connect Axoloti holding S1 button, in dfu mode (no LEDs flashing) and then Board/Firmware/Flash (rescue) -> "No devices in DFU mode detected."
* connect Axoloti normally (LEDs flash, green stays on) and then Board/Select device, click "refresh" -> no device appears
Any suggestions what to try next?

#20

its probably sulking because you haven't been paying it enough attention :wink:

hmmm.. odd though, theres no reason it shouldn't at least turn up as a DFU device.
really you need to proceed as you would with any other usb device on linux...
- try a different usb cable (make sure its a data cable, not just power)
- dont use a usb hub, try to eliminate any other possible issues
- check logs and device mapping using dmesg and lsusb ,
- check udev rules. (though this wont stop it appearing)

when checking the logs, what you really want to see is if any device is being seen by linux.
even if a device is completely unrecognised by linux, it should still appear on the device tree and something come up in the console logs.
if its not, then that sounds like hardware/cables ... if something does appear sounds more like OS/firmware.

Id also connect it to a mac or windows machine and see if that can see it in either mode... to determine if its a hardware issue, or just your linux setup. (mac is preferable, as has less variables than windows :wink: )

you could also try holding down S2 whilst booting to see if it then appears to work in normal mode (this prevents any auto start patch loading) , but frankly it sounds like you have a USB connection issue... either due to OS configuration or bad cable/hardware

#21

Thank you thetechnobear,
In my rusty Axoloti skills, I forgot to think about one possibility you mentioned, this Axoloti had an auto start patch in internal flash. So the holding down S2 did the trick!

#22

excellent, happy your back to patching.... still a bit surprised S1 didn't get you into DFU more.
anyway, great news your up n running again :slight_smile:

#23

I am on a Mac too Axo had been working fine up until today,

I have gotten the No available USB device found error and followed the advice in this thread
and got this:

Start flashing firmware with DFU
java.io.IOException: Cannot run program "/bin/sh" (in directory "/private/var/folders/kj/8g_lmfkx28g7zspwj2rqh09m0000gn/T/AppTranslocation/3990F641-B50B-421C-B131-A03CA57E745F/d/Axoloti.app/Contents/Java/firmware"): error=2, No such file or directory
java.io.IOException: Cannot run program "/bin/sh" (in directory "/private/var/folders/kj/8g_lmfkx28g7zspwj2rqh09m0000gn/T/AppTranslocation/3990F641-B50B-421C-B131-A03CA57E745F/d/Axoloti.app/Contents/Java/firmware"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at java.lang.Runtime.exec(Runtime.java:620)
at java.lang.Runtime.exec(Runtime.java:450)
at qcmds.QCmdShellTask.Do(QCmdShellTask.java:114)
at qcmds.QCmdProcessor.run(QCmdProcessor.java:190)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 5 more

Flashing firmware failed!

Then I hit compile by mistake and pressed s2 and got this:

Flashing firmware failed!
USB device found
connected
Authentic Axoloti Core
Firmware version: 1.0.0.1, crc=0xE95BAC96, entrypoint=0x20011000
Firmware CRC mismatch! Please flash the firmware first! Hardware firmware CRC = E95BAC96 <> Software CRC = Please compile the firmware first
Link to firmware CRC Please compile the firmware first
can't read flasher, please compile firmware! (file: /private/var/folders/kj/8g_lmfkx28g7zspwj2rqh09m0000gn/T/AppTranslocation/3990F641-B50B-421C-B131-A03CA57E745F/d/Axoloti.app/Contents/Java/firmware/flasher/flasher_build/flasher.bin )
Start compiling firmware
java.io.IOException: Cannot run program "/bin/sh" (in directory "/private/var/folders/kj/8g_lmfkx28g7zspwj2rqh09m0000gn/T/AppTranslocation/3990F641-B50B-421C-B131-A03CA57E745F/d/Axoloti.app/Contents/Java/firmware"): error=2, No such file or directory
java.io.IOException: Cannot run program "/bin/sh" (in directory "/private/var/folders/kj/8g_lmfkx28g7zspwj2rqh09m0000gn/T/AppTranslocation/3990F641-B50B-421C-B131-A03CA57E745F/d/Axoloti.app/Contents/Java/firmware"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at java.lang.Runtime.exec(Runtime.java:620)
at java.lang.Runtime.exec(Runtime.java:450)
at qcmds.QCmdShellTask.Do(QCmdShellTask.java:114)
at qcmds.QCmdProcessor.run(QCmdProcessor.java:190)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 5 more

Link to firmware CRC Please compile the firmware first
Done compiling firmware
No devices in DFU mode detected. To bring Axoloti Core in DFU mode, remove power from Axoloti Core, and then connect the micro-USB port to your computer while holding button S1. The LEDs will stay off when in DFU mode.
Disconnect request
USB device found
connected
Authentic Axoloti Core
Firmware version: 1.0.0.1, crc=0xE95BAC96, entrypoint=0x20011000
Firmware CRC mismatch! Please flash the firmware first! Hardware firmware CRC = E95BAC96 <> Software CRC = Please compile the firmware first
Link to firmware CRC Please compile the firmware first
can't read flasher, please compile firmware! (file: /private/var/folders/kj/8g_lmfkx28g7zspwj2rqh09m0000gn/T/AppTranslocation/3990F641-B50B-421C-B131-A03CA57E745F/d/Axoloti.app/Contents/Java/firmware/flasher/flasher_build/flasher.bin )

I don't know what I have done, please help

#24

Update, I have plugged it into another mac and it connected, but now seems to have very low audio output, will keep investigating, but if anyone can shed some light on what is going on I would be very thankful

#25

the issue you are having is it cannot find /Applications/Axoloti.app, though Ive never see it expressed this way before...

Id check your install on that mac..

what cables have you connected , is this a v1.0 board? if so you need to use a stereo cable.
see, https://sebiik.github.io/community.axoloti.com.backup/t/axoloti-hardware/59

also be careful you don't put it into a balanced input.. otherwise L&R might cancel each other out (almost) on some patches. thats IIRC correctly... I remember doing something like this when I first got axoloti, but it was a long time ago now... so perhaps im mis-remembering :slight_smile: ... there are now 'audio config options' to resolve this , but id recommend initially just checking your cabling, so you identify the source of the issue.

otherwise perhaps its something with the particular patch your using?
perhaps check the headphone output, see if its the same.

#26

Thank You TB, Everything seems to be above board now, I had a dodgy stereo cable, and have replaced it, the volume output does seem lower but, I think that may just be paranoia. I have a version 1.2 board and have checked multiple patches they are all the same volume, so its possibly just my perception.

I will try reinstalling on my mac. Thank you again for your ever present and useful help

#28

Hi everyone,

After having the same problem mentioned above with the inability to do the "flash(rescue)" thing I opened the enclosure to find that some components are really hot, specially IC2 and IC1.
The LEDs are working like other users in this thread so I assume my Axo its not bricked already.

Also, I've tried 3 different USB cables with no luck as well as reinstalling the software.

Any tip would be great.

Thank you all in advance

#29

check the various threads, ive details many times what to try and check...
you should try the S1 during power cycle, and see if the board appears in DFU mode.
if it doesn't appear at all in your USB list , then either
a) your cable is no good
b) you have bricked your axoloti

if the later PM Johannes.

#30

hi everyone, i had some of the issues that you are talking about. Im on windows 7 (64) besides of the "matching PID/VID" bug, if i update the Axoloti Core driver with zadig then gives me the java bug (that i thougth that have been solved by updating java) anyway, if someone have any other recomendation besides unplug/plug - update drivers with zadig - go to dfu and flash (Recover). Cheers.

#31

Hi, I am on Ubuntu and getting the same PID/VID error. I would like to try deleting the startup patch using S2 and/or going to rescue mode using S1, the only problem is, I have no idea where these buttons are and have been scratching my head trying find them with no information online which seems to explain. Can someone tell me where I can locate these buttons on the keyboard? Thanks. :smile:

#32

The tiny buttons are next to the MIDI jacks, and marked on the bottom of the board.