hi,
one of my axoloti boards give's me this error when trying to connect it, the other one I have works fine. I tried searching but only found people with similar problems on windows. any idea what I should do?
Emil
hi,
one of my axoloti boards give's me this error when trying to connect it, the other one I have works fine. I tried searching but only found people with similar problems on windows. any idea what I should do?
Emil
do you have both boards plugged in?
if so you may need to use 'select device' to select the other board.
btw, I got my boards today, had some teething troubles using all the boards... I think partly user error (e.g. getting confused which boards Id plugged in etc )
but what I did to get going, and troubleshoot, was after testing the first board was working, I deleted the midi device (using audio midi setup) , and plugged in the new board, and restarted axoloti GUI. to test that board..
I don't think it was necessary but just helped me verify each board individually.
once that was working, I plugged in each board and then renamed them to Axo 1, Axo 2 etc, so I can see them independently, and select them as needed.
Note: Ive found a bug in Select Device, its always selecting the first device. Ive fixed, and submitted for next build.
I suspect, now I have a few boards, I will be looking at improving the 'multi board' experience
If there is no led action when you plug it in, your board was unfortunately shipping without firmware flashed into it. The method is described here in the chapter "Rescue mode (DFU)".
I refer to there to avoid duplication explanations, so if there appears a need to clarify things in this explanation, everyone finds the corrected version.
@janvantomme could you please delete your post? One point that your guide missed is that you need to hold S1... it is obvious if you have done it countless times, but missed if you're new.
I followed janvantomme's advice and it solved my problem! thanks a lot to everybody for their time and advice
have a nice friday!
edit: remember to hold down the s1 button! I forgot at first
Hi Johannes, i did what explained here but i get this error:
Link to firmware CRC A4AA9FE1
Start disconnect
Done disconnect
Start flashing firmware with DFU
/bin/sh: /Applications/axoloti_runtime/platform_osx/upload_fw_dfu.sh: No such file or directory
shell task failed, exit value: 127
Flashing firmware failed!
can you help me?
Thank you
Sounds like you do not have installed the runtime properly. Check the installation instructions.
I have same problem but my leds are blinking when the device is connected.
I tested connecting to different usb port of my iMac but no luck.
I wanted to test with another microusb cable ( I know this cable works well normally ) to but I do not have any other in may hand.
Any ideas or troubleshooting tips ?
I can report back that my problems occured due to usb cable that I used.
Now I replaced the cable.
All looks fine
getting this problem all of the sudden.. recently started using 2 more boards, maybe that has to do with it? but i wasn't able to flash / rescue as per here (https://sebiik.github.io/community.axoloti.com.backup/t/axoloti-hardware/59).. the lights flash while im restarting + holding S1. anything else i should try?
(also tried other cables and clean start with S1)
The LEDs do not blink at all when entering rescue ("dfu") mode, follow exactly these steps to enter rescue mode:
thanks for the reply. you're right; i was referring to clean mode. but also after holding S1 (no blinking lights) im not able to flash rescue or select it as a device from the board menu. any help would be appreciated.
So the LEDs do blink at startup (but do not keep blinking) if you're not holding S1? That means the processor is working fine.
Are you using PC, Mac or Linux?
Are you sure your micro-USB cable is not a charging-only cable? Some micro-USB cables have wires for power but not for data.
the lights do not start up S1 pressed. a reboot lets me hear the patch that i saved to internal flash after that. ive tried 3 usb cables - also ones that were working with other units. im on mac
Just wanted to report that I had this problem and replacing the cheap crappy cable did it for me too. (The cable I was using was baaaaaaad)