Applying new firmware to your AudioMoth just became much easier with the release of the AudioMoth Flash App. With this application you can easily download and apply updates to the default AudioMoth firmware as we release them. If you've written your own firmware variant then you can apply it using this application too.
If you're applying new firmware to a device currently on 1.2.2 or older, then a paperclip will be required to manually put the device into flash mode (instructions for doing so are found in the app).
Post any support queries in the new forum section here.
If you've never updated the firmware on your AudioMoth, now's the best time for it! To get all the improvements and bug fixes implemented so far just download the app and download firmware version 1.3.0.
The Flash app doesn't work!
The app will find an AudioMoth in flash mode - either automatically if v1.3.0 is installed or following manual set up of flash mode with earlier firmware - and when a downloaded firmware is selected the "Flash AudioMoth" button is enabled.
Iniitially the "Flashing AudioMoth" pop-up is displayed and (if flashing from v1.3.0) the correct COM port opens. However this is followed by an error dialogue: "Failed to open port" and the AudioMoth is left in an unresponsive state. A firmware must then be installed manually, using the original Flash utility.
Could I get a bit more information about your setup? What operating system are you running, have you tried different USB ports/cables/AudioMoths and all gotten the same result?
Peter
@Peter Prince
Windows 10 Professional 64 bit
Two USB cables, both known to work with the AudioMoth
Several different USB 2 ports
Two AudioMoth 1.0.0 + two AudioMoth1.1.0 devices
Tried with all firmware versions from 1.0.0 to 1.3.0 pre-loaded on device and attempting to flash with each version.
Also tried flashing from "Local File" as well as "Standard Release".
The only option I haven't tried is "Overwrite bootloader".
Same failure results in every case.
All devices flash successfully when using the command line Flash utility, connected with exactly the same ports and cables and the same .bin files. (Although flashing always fails at the first attempt when a device is pre-programmed with v1.2.2 or v1.3.0)
Device is recognized by Flash app when connected to USB in USB/OFF mode
If existing firmware is pre-v1.30 the app prompts to configure flash mode manually.
When "Flash AudioMoth" clicked the app opens the correct COM port if the device is running v1.3.0 (confirmed by Device Manager), otherwise flash mode is entered manually and the device put back in USB/OFF mode.
Either way the "Flashing AudioMoth" dialogue is displayed briefly with message: "Applying firmware to attached device."
Shortly afterwards an error dialogue is displayed:
"Failed to open port.
Could not connect to AudioMoth
Reconnect device and Flash again."
At this point Device manager show that the COM port is still connected.
Device then appears to be "bricked" ie no LED activity in any mode and not recognized by Config utility. However it can be put into Flash mode by following normal procedure and firmware can be reinstalled using the command line utility.
EDIT:
I've tried connecting to ports COM2 through to COM7
Is it possible that the Flash utility has been hard-coded with some other port number?
@davidlee_malvern Strange. The app definitely isn't hardcoded with a port number. It searches the list of devices connected to your machine, finds an AudioMoth and uses that port number. I've set up a version of the flash app which saves a log file of all actions and errors it comes across. This will eventually be brought into the standard release, but it'll be useful for debugging this issue. Download the installer here:
LINK REMOVED
Once installed, attempt to flash a device as you have previously. Then navigate to "%USERPROFILE%\AppData\Roaming\AudioMoth-Flash\logs\" and grab the file named "audiomoth_flash.log". If you could then upload that file (it should be extremely small) I can have a look and work out how to fix the issue.
Peter
Peter - an info report - On Windows 10 Home 1909 - the flashapp bricked both my AudioMoths. Then I couldn't get flash to load the firmware either, after much pluggin unpluging and rebooting - Windows decided to reinstall the USB/COM driver as COM4 whereas flash had been reporting the AudioMoth as COM3. Using COM4 - flash did it's thing and now I have both AudioMoths back reporting the correct firmware.