Files
heltec-repeater/docs/DEVBOARD_REQUIREMENTS.md
T

3.5 KiB

Future Solenos/Gebos dev-board requirements

Derived from actual debugging needs during this experiment. Machine-readable pin list: devboard_signals.csv.

Debug access that proved necessary

  • SX1262 BUSY + DIO1 on test points: needed to reason about command timing, IRQ latency, and stuck-BUSY recovery without guessing. "I needed direct access to this signal because the only alternative was inferring radio state from SPI responses."
  • Full SPI bus (NSS/SCK/MOSI/MISO) on a header: logic-analyzer decode of the SX1262 command stream is the ground truth when firmware and radio disagree.
  • FEM control lines (PWR_EN, CSD, CTX): RX sensitivity and TX output both silently break if these are wrong; scoping them is the fastest check. CSD doubles as board-revision detect (pull level) — keep it probeable.
  • Native USB pins must remain dedicated to flash/console; the DUT USB identity changes between app and ROM bootloader, so the dev board should also expose UART0 TX as an always-on log output (the Heltec does not, which made early-boot debugging blind).

Wishlist beyond the current board

  • Always-available secondary UART for logs (independent of native USB).
  • Measurable radio power rail (current shunt) to correlate TX events with actual PA draw — would have settled "is the FEM PA active?" instantly.
  • RF test connector (u.FL tap or directional coupler) for conducted measurements instead of over-the-air-only verification.
  • ESP32 BOOT/RESET buttons brought to a header for automated strapping.

Added after the RF experiment

Signals and facilities that specifically proved their worth (or whose absence cost time) during this bring-up:

  • SX1262 sync-word register readback as a health probe. The single most valuable diagnostic added: a radio that lost its configuration still reports a plausible chip mode while being deaf. On the dev board, keep SPI accessible so this can also be verified externally with a logic analyzer. "I needed this because a silently unconfigured radio is indistinguishable from a quiet RF environment."
  • A second, independent RF observer that is not a cheap USB dongle. The RTL-SDR drifted ~17 dB, died mid-stream without exiting, and eventually de-enumerated. Most of the debugging time in this experiment went into distinguishing observer faults from DUT faults. The instrumented dev board should include either an on-board receive path that can be cross-checked, or a documented conducted-measurement port.
  • RF test/attenuation port (u.FL tap or directional coupler). Our transmission reached the observer up to ~36 dB stronger than real meter traffic and drove it into compression, which cannot be fixed in software. A conducted tap with a fixed attenuator would have removed an entire class of ambiguity. "I needed this because over-the-air-only verification conflates transmitter behaviour with receiver overload."
  • Radio power-rail current sense. Would have answered "is the PA actually active?" immediately instead of inferring it from decodes.
  • Always-on log UART independent of native USB. The ESP32-S3 USB identity changes between the application and the ROM bootloader, and the early-boot window is invisible; a dedicated UART would have shown the first radio_init result without a reboot-and-capture dance.
  • FEM CSD brought out to a header. It doubles as the board-revision detect (pull level) and is the single control that decides whether the receiver has ~41 dB of front-end gain or not.