No available USB device found with matching PID/VID

thetechnobear · 2018-02-04 18:43:16 UTC

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

reubenfinger · 2018-05-09 13:28:21 UTC

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

reubenfinger · 2018-05-09 13:41:10 UTC

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

thetechnobear · 2018-05-09 16:52:59 UTC

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 ... 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.

reubenfinger · 2018-05-10 21:12:12 UTC

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

burningflags · 2018-08-28 00:31:51 UTC

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

thetechnobear · 2018-08-29 14:45:23 UTC

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.

torotumbo · 2019-07-29 03:02:18 UTC

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.

orenpine · 2020-08-27 05:57:03 UTC

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.

tele_player · 2020-08-27 06:03:07 UTC

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

orenpine · 2020-08-27 06:38:14 UTC

Oh wow! Thanks so much!

Paltoquet · 2021-05-14 13:02:30 UTC

Hi,
First i'm sorry fro my bad english...
I'm trying to run my axoloti board but i've any problems.
When i try to connect and run the patch this error is displayed: No available USB device found with matching PID/VID

I've tried to run in DFU mode pressing the S1 button but this message is displayed:

No devices in DFU mode detected.

The fact is i've already test the USB cable with my phone to save any files and it's working... By the way i'm on Mac osx (hight sierra)
So i really can't know what is the problem and searching on this english forum is a little bit difficult for me cause of my english first and my bad informatic's knowing...

I would be gratefully if you can share a path to follow !

hitachii · 2021-05-14 16:32:50 UTC

Hi paitoquet,

When you plug in the board, do the two LEDs in the front blink? The two LEDs next to S1 and S2 should blink red and green when first plugged in.

Paltoquet · 2021-05-14 17:16:17 UTC

Yes, the two LEDs blink!

hitachii · 2021-05-14 23:36:19 UTC

If the LEDs come on, something is working. That is a good start.

Does the SD card have anything on it? If you plug the SD card into a card reader, try backing the card up, erasing it, putting it back in the Axoloti, and see if that works.

reubenfinger · 2021-05-15 08:48:08 UTC

Just to second what hitachii is saying, can you startup normally with the SD card removed, just troubleshooting but it could be that your SD startup patch is causing an issue, so just to rule that out.

Also how are you powering the axo, just by USB or external power?

Have you got anything soldered to the board/Gpio’s?

Also just having read about my own issues earlier in this thread, can you try using it on another computer, again that could help isolate where the issue is occurring, I was able to use another macbook with success.

Paltoquet · 2021-05-15 09:21:39 UTC

Thanks you both for your answers,
So, first i tried without SD card and the problem was already there. I've just tried with an SD card empty and it's the same problem.
My axoloti is alimented just by the usb cable and nothing is soldered to the board.
I'll try to connect with another computer as soon as i could!

reubenfinger · 2021-05-15 10:56:25 UTC

Good try on another machine, also forgot to mention have you tried holding s2 on startup?

Is the axoloticore new or have you bought it second hand?
Have you successfully used it in the past or is this the first time you are trying it?

Also just quoting Johannes, try another cable, at this point you're just trying to rule out potential areas of issue, because as from below if it's an unknown hardware issue, who knows what the cause will be....