Hardware / Systems · PRJ-2430

Rook RF Field Monitor · Rev C

Rev C turns a complex handheld concept into an explicit set of power, safety, interconnect, firmware, PCB, and verification contracts—while keeping prototype status visible.

C6BLE OBSWIFI OBSSTOREINTERFACESYSTEM PLATE / PRJ-2430STATUS / WORK IN PROGRESS · Rev C
14review findings closed
04processor domains
06bring-up phases defined
Problem

Problem and constraints

The previous revision contained failures that would have appeared only after fabrication: undersized buck converters, an impossible ESP32-S3 SDIO-slave link, shared access to the charger safety bus, incomplete USB-C protection, and package-level pin conflicts. A credible prototype required closing those findings at schematic and integration level before tape-out.

Engineering approach

Architecture and implementation

The review preserves four separated processing domains but corrects the implementation around them. ESP-Hosted SPI replaces the invalid SDIO path, the STM32G0 owns a physically private charger and fuel-gauge bus, the radio and application loads receive properly sized rails, and every link has a defined degraded mode. A measured six-phase bring-up plan gates progress from unloaded rails through thermal and RF coexistence testing.

Partitioning

ESP32-P4 application, ESP32-S3 Wi-Fi and LoRa coordination, ESP32-C6 BLE processing, and an always-on STM32G0 safety island each have explicit responsibilities.

Power + safety

Protected 1S charging, hard load gating, private safety I²C, independent rail enables, and layered cell, charger, safety-MCU, and application cutoffs make shutdown behavior structural.

Verification

The current plan defines rail transient limits, link throughput gates, RF desense windows, factory test points, and thermal soak criteria; these remain to be executed on hardware.

Development record

Work in progress.

Design and implementation records remain private while this work is in development.

Work in progressPrivate record

Private development record

Design notes and implementation records are not public while this work is in development.

Current development
Related work

Have a similar system to define, build, or recover?

Discuss the project