Skip to content

Add iLabs Challenger RP2040 LoRa variant (RFM95W / SX1276) - #3767

Open
Ve2mrx wants to merge 2 commits into
meshcore-dev:devfrom
Ve2mrx:feature/ilabs-challenger-2040-lora
Open

Ve2mrx wants to merge 2 commits into
meshcore-dev:devfrom
Ve2mrx:feature/ilabs-challenger-2040-lora

Conversation

@Ve2mrx

@Ve2mrx Ve2mrx commented Nov 4, 2026

Copy link
Copy Markdown

Adds a variant for the iLabs Challenger RP2040 LoRa (1st generation): RP2040 + HopeRF RFM95W (SX1276), Feather form factor, U.FL antenna, LiPo charger.

Pins

RFM95W on SPI1: SCK 10, MOSI 11, MISO 12, NSS 9, RESET 13, DIO0 14, DIO1 15. LED 24. I²C SDA 0 / SCL 1.
Source: arduino-pico variants/challenger_2040_lora/pins_arduino.h, matching the iLabs datasheet. Uses the existing PlatformIO board challenger_2040_lora from the RP2040 platform MeshCore already uses.

Environments

ilabs_challenger_2040_lora_repeater, _companion_radio_usb, _terminal_chat.

Notes for review

  • -D SS=21: arduino-pico's challenger_2040_lora/pins_arduino.h does not include generic/common.h, so SS is undefined and the WiFi library (pulled in by the companion) fails to compile. 21 is PIN_SPI0_SS.
  • Default frequency: the RFM95W is sold per band, and this is the 915 MHz module. The variant unflags the EU default (869.618 MHz / SF8) and boots on 910.525 MHz / SF7 so a fresh repeater doesn't advertise off-band. Happy to drop this if you'd rather keep the global default.
  • Power saving: 50 MHz system clock, plus ChallengerBoard::sleep(), which uses WFI with interrupts masked around a DIO0 check (so a packet arriving just before WFI still wakes it) and a timer alarm for the periodic wake. One-line change in CommonCLI.cpp: powersaving on also accepts boards that define BOARD_LIGHT_SLEEP, instead of only ESP32/nRF52. I can split this into its own PR if preferred.
  • No battery-voltage divider on this board, so getBattMilliVolts() returns 0.

Tested (2 boards, firmware v1.18.0 based, 915 MHz)

  • Companion (USB) ↔ repeater over the air in both directions, auto-added contacts, trace round trips.
  • Repeater settings persist across reboot.
  • With powersaving on, running from battery only (USB unplugged): 6/6 traces from the companion answered immediately, so DIO0 wakes the core.
  • All three environments build on dev.

🤖 Generated with Claude Code

Ve2mrx and others added 2 commits October 26, 2026 17:37
1st-generation board: RFM95W on SPI1 (SCK 10, MOSI 11, MISO 12, NSS 9),
RESET 13, DIO0 14, DIO1 15, LED 24. Boots on the North American preset
(910.525 MHz, SF7) instead of the EU default, which is off-band for a
915 MHz-only module.

Battery (UPS) runtime: 50 MHz system clock, and a WFI light sleep woken by
DIO0, USB or a timer alarm. A BOARD_LIGHT_SLEEP flag lets 'powersaving on'
accept boards outside ESP32/nRF52.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Why 50 MHz is safe, why the EU frequency must be unflagged (and that the
unflag strings must match exactly), why std_init gets &SPI1 and NSS is
not given to setCS, and what BOARD_LIGHT_SLEEP gates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant