Heyo, not sure if this is a meshtastic issue, WisBlock one, and/or a user issue.
Just got a RAK4631 and a RAK19003 as well as a RAK18001 buzzer. When in slot C with the GPIO pin set to 21 the board enters a boot loop the first time it receives a message, I’m assuming when it tries to do a buzzer thing. Removing the buzzer stops the boot loop so the GPIO can be turned off again. Any ideas??
Running metastatic, happens on both 2.6.11 and 2.7.12
Slot D has an known incompatibility and I have a RAK1901 in D which is working just fine.
Welcome to the forum @cardboard
Works fine for me with Slot C and a “none” Meshtastic test firmware.
Video of the test ==> https://drive.google.com/file/d/1ndK175lXIsk0Y32mVoNmz3rt6SV_MYEx/view?usp=sharing
Can you flash the UF2 file from the attached ZIP file to the RAK4631 and check if you can hear a sound?
firmware.uf2.zip (87.8 KB)
Hello an thank you @beegee
Flashed firmware and it still runs into a power cycle loop.
I can hear a very faint start of a beep before it reboots.
Tried a couple of different USB cables and USB ports, no change.
Your video was useful though, my buzzer does look like a different model, more components in a different layout if that would make any difference.
This is the link I purchased from, product picture matches your buzzer also for what that is worth.
https://a.aliexpress.com/_mK6mI3r
Found a solution. Buzzer works on battery power.
From an engineering approach it would seem as if something is browning out when trying to buzz when only powered by USB.