feat: support PROVES Flight Control Board v5e (SX1262 radio)

[Mikefly123]

Summary

Adds a board port so the GRC firmware runs on the PROVES Flight Control Board v5e in addition to the ground_radio_controller and v5 boards.

• New board boards/proves/proves_flight_control_board_v5e/ — mirrors the v5 port (upstream Pico 2 base + project hardware dtsi with dual CDC ACM, fstab, ramdisk). The only substantive difference is the radio: the v5e carries an SX1262-based E22-400M30S module instead of the v5's SX1276. Wiring follows the v5e board definition in proves-core-reference: reset P6, busy P13, dio1 P14, TX/RX antenna-switch enables P21/P22, DIO3-controlled 1.8V TCXO with 10ms startup delay, rx-boosted. SPI1 pins are identical to v5.
• prj.conf no longer hard-sets CONFIG_LORA_SX127X. Both SX12xx drivers are default y gated on their devicetree compatible, so the board DT selects the driver. Hard-setting either is a fatal unmet-dependency Kconfig warning for boards carrying the other radio.
• No app changes: Main.cpp binds the radio via DT_NODELABEL(lora0), which the v5e port defines.
• README/settings.ini: v5e documented as a BOARD= alternative; ground_radio_controller remains the default.

Testing

• Built for proves_flight_control_board_v5e/rp2350a/m33; verified CONFIG_LORA_SX126X=y and the full sx1262 node in the merged devicetree.
• Flashed a bench v5e (UF2 via BOOTSEL) — all 6 one-board main tests pass, including SET_FREQ at 437.4 MHz, which performs a live lora_config() on the SX1262 and would return EXECUTION_ERROR on failure.
• Regression: rebuilt for ground_radio_controller — builds green with CONFIG_LORA_SX127X=y still selected from its devicetree.

Notes

• Stock LoRaConfig::TX_POWER = 23 exceeds the SX1262 driver's +22 dBm limit; worth revisiting before running a v5e at full power (not changed here).
• The two-board (bft2) flow flashes one ELF to both boards, so mixed GRC↔v5e RF link testing needs a follow-up workflow change.

🤖 Generated with Claude Code

Quick builds for manual testing

For manual testing convenience, the branch v5e-portable-builds combines this PR with the portable-builds tooling. Check it out and run make build for a self-bootstrapping build (uv, venv, west workspace, and Zephyr SDK are set up automatically) — no manual environment setup needed. Switch boards by toggling BOARD= in settings.ini, then make generate followed by make build. Both ground_radio_controller and proves_flight_control_board_v5e targets build green on that branch.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new PROVES flight controller board target, proves_flight_control_board_v5e, with Kconfig, board.yml, devicetree, and defconfig files defining an SX1262-based hardware layout. Updates prj.conf to select LoRa driver via devicetree instead of hard-coding, and updates settings.ini and README accordingly.

Changes

v5e board support

Layer / File(s)	Summary
Board identity and Kconfig entry boards/proves/proves_flight_control_board_v5e/Kconfig, boards/proves/proves_flight_control_board_v5e/board.yml, boards/proves/proves_flight_control_board_v5e/proves_flight_control_board_v5e_rp2350a_m33.yaml	Defines new board Kconfig symbol with conditional SOC select, board metadata (name, vendor, SoC), and board YAML with identifier, MCU/arch, memory sizes, toolchains, and supported peripherals.
Devicetree hardware description boards/proves/proves_flight_control_board_v5e/proves_flight_control_board_v5e_rp2350a_m33.dts, boards/proves/proves_flight_control_board_v5e/proves_flight_control_board_v5e_hardware.dtsi	Top-level DTS includes upstream RP2350A/M33 and Pico dtsi files plus the new hardware dtsi, which enables CDC ACM UARTs, configures SPI1 pinctrl, instantiates an SX1262 LoRa node, sets console chosen node, and defines fstab/ramdisk entries.
Build defaults and driver selection boards/proves/proves_flight_control_board_v5e/proves_flight_control_board_v5e_rp2350a_m33_defconfig, prj.conf, settings.ini, README.md	Adds defconfig defaults (HEX/UF2 output, clock, console, GPIO, UART), updates prj.conf to select LoRa driver via devicetree instead of hard-coded SX127X, comments out active board line in settings.ini for both v5/v5e, and documents v5e flashing steps in README.

Estimated code review effort: 2 (Simple) | ~15 minutes

Sequence Diagram(s)

Not applicable — this PR adds static board configuration files and documentation without new multi-component runtime control flow.

Poem

A new board hops into the nest,
v5e with SX1262, dressed its best,
Devicetree picks the radio right,
No more hard-coded LoRa fight! 🐇
make generate-force, then away we bound —
Another board, another sound! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly names the new PROVES Flight Control Board v5e support and the SX1262 radio change.
Description check	✅ Passed	The description matches the board-port, LoRa driver, and documentation changes in the PR.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[jrpear]

I am a bit confused about this patch. We're not sleeping the radio as far as I know. And in any case the datasheet doesn't say "wait after wake" to send commands, it says "wait after sleep".

It is possible the delay just changed the timing of things so as to disguise a race condition causing the intermittent SET_FREQ failures the new README mentions.