Add zigbee router support

[hlyi]

@jnilo1 Do you think you can add zigbee router firmware support? Thanks!

[d0np3p3]

It is already supported.
https://github.com/jnilo1/hacking-lidl-silvercrest-gateway/blob/main/2-Zigbee-Radio-Silabs-EFR32%2F27-Router%2FREADME.md

[hlyi]

Thanks @jnilo1. Sorry for not clear about the ask, i meant supporting sw flow control build. Thanks

[jnilo1]

Yes — router BOARD= support is planned

Thanks for clarifying — you want the standalone Zigbee router firmware built with software flow control for the G4, i.e. BOARD= support for 27-Router. Today the scope note in 2-Zigbee-Radio-Silabs-EFR32/boards/README.md is explicit: NCP and OT-RCP are board-parameterised, while RCP, Router and the Gecko bootloader remain lidl-only.

The good news is that the mechanism you validated for the NCP (#130) carries over directly: build_router.sh will source boards/<board>/board.env and apply lib_uart_config.sh to the router's VCOM header, exactly like build_ncp.sh does. For the G4 that means the MG13 part number (BOARD_TARGET_DEVICE) and BOARD_UART_FLOW=sw (XON/XOFF), producing -sengled-e39-g8c-suffixed artifacts (.gbl and .s37, as for the NCP). flash_efr32.sh will lift its router refusal for parameterised boards, so — since you flash the radio through it, meaning your G4 already runs a working Gecko bootloader — the router GBL will flash the same way as your NCP, with nothing else needed on your side. As with the NCP, the lidl build stays byte-for-byte unchanged, and I will rely on you for the hardware validation on a real G4.

Timing

Queued for v4.0.0. We will not publish any new release candidate until issue #99 is definitively closed (rc4 is under field validation), so this will ship with v4.0.0 directly.

[jnilo1]

Implemented — router BOARD= support

The Z3 Router build is now board-parameterised, using exactly the mechanism you validated on the NCP (#130): build_router.sh sources boards/<board>/board.env, re-points the project at BOARD_TARGET_DEVICE, and applies the board's UART routing and flow-control type to the VCOM header via lib_uart_config.sh. For the G4 that gives an MG13 build with software XON/XOFF flow. Non-lidl artefacts carry the -<board> suffix (.gbl and .s37), and flash_efr32.sh accepts router for non-lidl boards, with the same devicetree board-match guard as the NCP. On your side it is just:

BOARD=sengled-e39-g8c ./2-Zigbee-Radio-Silabs-EFR32/27-Router/build_router.sh
BOARD=sengled-e39-g8c ./flash_efr32.sh -y router

Two checks behind the change: the lidl router rebuilt through the new board mechanism is byte-for-byte identical to the committed prebuilt (md5 f2f830156c93a6c7df4ac87a6d889084), and the G4 build compiles end-to-end (MG13 target, uartFlowControlSoftware in the generated config). A side benefit from #141: flashing through flash_efr32.sh records FIRMWARE_FLOW_CTRL=sw in radio.conf automatically, so the kernel bridge configures its side of the UART to match — the mini-CLI over nc <gateway-ip> 8888 should just work.

What I'll rely on you for

No G4 prebuilt is committed — the G4 router build has never run on real hardware (same policy as OT-RCP). The validation that closes this one: build it, flash it, and confirm the router joins a network (network steering from your coordinator) and the mini-CLI responds. The router is the least demanding firmware on the UART side — text CLI at 115200 only — so the high-baud question from #142 doesn't apply here.

Also included: BOARD= for the Gecko bootloader and the RCP

While at it, the two remaining lidl-only builds were ported too, so every EFR32 firmware now takes BOARD=. Both are informational for you — neither has run on real G4 hardware, and you need neither:

• Gecko bootloader: BOARD=sengled-e39-g8c ./build_bootloader.sh produces an MG13 image with the correct xG13 first stage, placed in the MG13's dedicated bootloader flash region at 0x0FE10000 (verified against the SDK prebuilts; on the MG1B the bootloader lives in main flash instead). Your G4 already runs a working bootloader — the one you flash through — so there is no reason to replace it. If you ever do: the .gbl only updates stage 2, and recovery from a bad bootloader is SWD-only, so keep your debugger attached.
• RCP (multi-PAN): builds for the G4 with one caveat baked in — CPC supports only RTS/CTS or no flow control (no XON/XOFF), so the G4's sw flow is clamped to none. flash_efr32.sh records it as such in radio.conf, so the in-kernel UART bridge — which is what cpcd connects to, over TCP — arms its side of the link to match. Probably academic on a G4 anyway.

Timing

Same as the rest: this ships with v4.0.0 — no new release candidate until issue #99 is definitively closed.

[hlyi]

Thanks for adding router support in v4.0.0-rc5. Close this discusion