Hello,
I work on passive acoustic monitoring projects at a bat conservation charity, and we are struggling with some older AudioMoths that we are trying to flash and configure for this season. The AMs are version 1.0.0 and have previously been flashed with an old custom firmware. When I plug in the AudioMoths they appear in the firmware app with the name of the old firmware, but are not able to be automatically or manually flashed (I have tried all of the usual manual flashing techniques!). When I open the configuration app I get the error message "The firmware installed on your AudioMoth may not be supported by this version of the AudioMoth Configuration App." and when I try and add a config to the AM, I get the error message "The connected AudioMoth did not respond correctly and the configuration may not have been applied. Please try again.".
This is the case for about 10 of our devices, which makes me think that it is some fundamental issue with the custom firmware. I have attempted downpatching the flashing app and running things through the command line but that didn't seem to solve it. I was wondering if anyone has found a way to hard reset their AMs or go in and manually edit the firmware scripts or something to get them back into a usuable state.
Best,
Rowan
Hi Rowan, Can you confirm which firmware is currently installed on these devices? Also what operating system are you using?
The AudioMoth should still have the bootloader installed. You can start directly in the bootloader flash mode by removing the batteries, shorting out the PROG pins with a paper clip, and then plugging in the USB cable so that the AudioMoth powers up and immediately finds the PROG pins connected together so runs the bootloader rather than the installed firmware. This is quite fiddly to do. It is easier with two people so that one person plugs in the USB cable. You can then use a small jumper cable to connect the PROG pins together. It will always work in the end if the bootloader is still installed. Alex