No AudioMoth found: can upgrade with paperclip, but still not found afterwards

Can also get fancy spring loaded contacts which work better but aren't so easy to connect up with small jumper cables.

Alex,

Thanks for the prompt and fulsome response. I've downloaded the 'SetupSTM32CubeProgrammer-2.8.0' but it doesn't want to run on the Mac, so I'll try the W'doze version :(

Looking for an edge connector to avoid soldering pins on the Moth pads.

Cheers

Greg

PS: Interesting if it was such a simple thing, that it was trying to write to SD, but as no card, stuck, and then I compounded the problem. Might be worth adding to a FAQ.

Hi Greg, It sounds like this AudioMoth is stuck in DEFAULT and is trying to write to the SD card and then flashes red and green when it fails to find a card. We've added a few more steps in the 'overwrite bootloader' option to make this less likely to happen. Removing it from the main GUI unless explicitly enabled.

To put the bootloader back you need any programmer that supports the JTAG/serial wire debug (SWD) interface. We normally use EFM32 starter kits which work well: https://community.silabs.com/s/article/using-an-efm32-starter-kit-as-an-external-debugger-1?language=en_US

You need to write the binary file below to the start of the flash: https://www.dropbox.com/s/fcbc987j74fyv73/bl-usartusb-wonder-v2.05.bin?dl=0

https://www.dropbox.com/s/tn3q070lzenenmt/bl-usartusb-wonder-v2.05.hex?dl=0

The pinouts on the programming port are shown in the AudioMoth Dev data sheet - https://github.com/OpenAcousticDevices/Datasheets/blob/main/AudioMoth_Dev_Datasheet.pdf - and correpond to the six connections shown in the Silicon Labs instructions. Once the bootloader is back, you should be able to install the firmware using the Flash App.

Let me know if you'd prefer to post it to me to have a look at - alex@openacousticdevices.info.

Alex

Hi Team,

One of my Moths (1.0.0) had this 'No Audiomoth Found' by Config with 'red on & green flashing, no response to switch' problem. Numerous other Moths work fine on this OSX setup.

I've taken the clip & slider out of the switch, but still the same behaviour.

Paperclip at power on got it recognised, so installed 1.6.0, but it still disappears after reboot, although OSX could still 'see' it in System Report.

Next move was fatal - I ticked 'Overwrite bootloader'. Now nothing. Oops!

-

I see elsewhere in the forum, Alex generously offering to rewrite it if mailed back to him.

However, should the ST-Link V2 for STM32 be able to rewrite, it, I'm keen to try. I would need directions though; the file and the pinouts of the port.

Otherwise, Alex might be kind enough to email me the address to mail it to.

Sorry to have been impulsive... (but the warning might be made even more expliicit!)

Regards

Greg

Should I understand there is no warranty?

Should I try to repair as mentioned in https://www.openacousticdevices.info/support/device-support/simple-audiomoth-switch-repair ? (although nothing looks broken in my unit)

@Alex Rogers Correct, always the red light on and green one flashing. I bought this one within GroupGet for AudioMoth v1.1.0 (Round 7)

This sounds like this is a switch problem - the device stays in CUSTOM mode no matter what the actual switch position. When you launch into bootloader mode with the paperclip the switch state is ignored so this is why you could re-flash it okay. Does the switch movement feel different to the others?

For step 4 - what do the LEDs do when you switch between CUSTOM and DEFAULT?

Do your other units work okay?

The red LED on constant, and the green flashing, means that the time has not been set when you switched to CUSTOM and it is listening for the tone from the smartphone app to set the time. If you were to move the switch to USB/OFF while the USB is Connected to PC the green LED should light up and you can configure.