Help: bricked my axoloti :(

#1

I've been very stupid and bricked my axoloti. I had a button connected to a patch/load that I didn't managed to remove even with no sd card uploading the patch to flash it still was connected somewhat, so I decided to upload the firmware but pressed the button before it finished... so now I have a dead axoloti. I tried the rescue upload (I'm on debian stable) but I get this message:

Link to firmware CRC E95BAC96
Start disconnect
Done disconnect
Start flashing firmware with DFU
dfu-util 0.8

dfu-util: Invalid DFU suffix signature
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
dfu-util: No DFU capable USB device available
shell task failed, exit value: 74
Flashing firmware failed!

can I rescue it ?

#2

@emillo to be clear...
you have followed the instructions as we "Rescue mode (DFU)", described here

and you can confirm that when you boot up axo, you held down S1, and that when you go to 'select device' it shows the axoloti as a DFU device.
only if its shown as a DFU device, will Rescue mode work.

(the error you describe, is what you would get if you weren't in DFU mode , as far as i remember)

#3

@thetechnobear
Yes I did power up by holding S1... the error if I don't to that is

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.

Yes I see it in select device it says "Device: STM DFU Bootloader", "Location: :2:1" and "CPU ID: Driver:ok, CPU ID Indeterminate"

#4

a quick bit of googlefu, indicates its possible some linux distros have an issue with dfu-util e.g. here

dont know if this is your problem, it would be worth trying on a macOS or Windows, if you have access to a machine.

later, when Ive got time, I'll try with the linux distro I have BUT it could be it works on some but not others, so wont help much.

#5

The following applies to Linux only:

Check if you have the device access permissions installed, if the file /etc/udev/rules.d/49-axoloti.rules file is not present, execute the script in platform_linux/add_udev_rules.sh.

#6

@johannes yes thanks I already had that file. @thetechnobear, I solved using your suggestion of using windows. Thanks very much I'm a bit relieved now :slight_smile:

However, I still have my original problem.. when I press PB9 it disconnects and tries to load probably a non existent patch, even if I have no sd card inserted and the patch uploaded to flash doesn't contain anything tied to PB9.. maybe has to do with the controller patch? How do I access that?