Error trying to flash firmware #149
Replies: 2 comments
What your log saysTwo things stand out. First, your gateway's config expects the radio at 460800 baud ( Second — and this is the actual blocker — after detecting the app, the flasher commands it to reboot into the Gecko bootloader (Spinel Two things to confirm
Meanwhile: get Thread working again without reflashingRight now ssh root@10.42.0.64
# set (or add) FIRMWARE_BAUD in /userdata/etc/radio.conf
sed -i '/^FIRMWARE_BAUD=/d' /userdata/etc/radio.conf
echo 'FIRMWARE_BAUD=115200' >> /userdata/etc/radio.conf
/etc/init.d/S70otbr restartYour Thread network will run fine at 115200 — 460800 is a performance improvement, not a requirement. The definitive fixIf the diagnosis is confirmed, the only way to replace a pre-v1.2 OT-RCP is over SWD (J1 header). The good news: with an SWD probe and Simplicity Commander you can flash the commander flash 2-Zigbee-Radio-Silabs-EFR32/26-OT-RCP/firmware/ot-rcp-460800.gbl --device EFR32MG1B232F256GM48After that, all future updates work in-band again (that build enters the bootloader on command). If you have (or can borrow) a probe and want help with the J1 wiring, say so. If not, the 115200 workaround above keeps you fully functional in the meantime. |
Reproduced on the bench — diagnosis confirmedI reproduced your exact failure on a bench gateway: I SWD-flashed the February 2026 OT-RCP build (the one shipped with v1.0/v1.1, 115200 baud) onto a Lidl gateway running 3.10.0, then ran the same Both remedies are now bench-validated end-to-end:
No J-Link? A Raspberry Pi, a Pico, or an ESP32 works tooThe J1 header already exposes everything you need — pin 1: 3.3V, pin 2: GND, pin 5: SWDIO, pin 6: SWCLK (see
With any of these, OpenOCD's openocd -f interface/cmsis-dap.cfg -c "transport select swd" -f target/efm32.cfg -c "program ot-rcp.s37 verify reset exit"(adjust the A quicker check than my earlier questionOnce the 115200 workaround is applied, run this on the gateway: ot-ctl rcp versionIf it prints |
Uh oh!
There was an error while loading. Please reload this page.
After successfull upgrading my gateway to 3.10.0 i tried to reflash the radio firmware. This fails with:
If I dont interrupt this, it will just repeat the detection cycle for a lot of different baudrates without detecting anything.
Between the
INFO Detected ApplicationType.SPINELand theTraceback (most recent call last):- line is ~ 5 second pause.Any directions?
All reactions