Files
heltec-repeater/docs/DEVBOARD_REQUIREMENTS.md
T

1.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.