It was running fine, with midi in still working, but midi out on tyhe USB host port was n longer working. I tried to connect it to the patcher, and it did no longer want to connect.
I got this message, or a a very similar one in the Ksoloti patcher ( I copied this one from the axoloti patcher)
Axoloti Core found. Core not responding - it may be stuck running a problematic patch. Restart the Core and try again. Disconnected
I flashed the 1.1.0 firmware from the latest patcher in DFUrescue mode and I was able to connect again after some tries.
I also saw this in the kernel log
[23289.596407] usb 1-3: can’t set config #1, error -110
Now I was able to flash a patch, but…
the voltage monitor is reporting 0.00V 3.30V
The lights go on, the LED connected to the GPIO lights up, but
Failed to start patch
Is my axo gone? Can I put the 5V somewhere else on the board?
I tried powering it from the barrel plug, this works in the same way as powering it from USB. I powers on. If I connect the usb later and connect the patcher. It reports 0.00V 3.29V
interestingly, I’m measuring 4.99V with the multimeter on the 5V pin on the axo breakout board (on the DIN midi part of the board) when powering with the barrel power supply, only 4.87V when using the USB power…
Was this with a startup patch (possibly of a previous firmware version) previously set up? Wondering if the (invalid because of different version) startup patch would be messing with the boot
This sounds like a previous firmware bug maybe, especially because I do not test Axoloti boards as much as Ksoloti boards after each firmware change. If the board comes alive in any way, there has to be 5V present - as you measured later.
This seems quite common. Some USB ports are just weaker - also I measure lower voltage with certain cables, and stable 5.1V with others. The Core should run fine at a measured 4.87V.
That’s good to know, this is indeed the latest update, maybe some hidden bug or mistake I made got rectified.
It was a patch flashed to the startup flash, there is no SD card in the axo.
but:
I’m starting to think that the controller might be the problem. As I use different computers some would have the controller object enabled (for the big Genes)
When I switch to legacy mode, the controller object is still enabled (I checked)
I don’t know what the BigGenes controller object would do on the axo, but maybe that is the source of the “problematic patch "
The only ‘Genes specific object in the controller is the encoder. Looking at the pinout there should be no conflicts unless the Axoloti Core struggles with configuring pins that are available on Ksoloti but left unconnected on Axoloti (PG10-PG12)