The probe list was wired only in variants/promicro/target.cpp. It is now the
default list of NmeaGpsDriver when GPS_BAUD_PROBE_LIST is set, so a variant
enables baud autodetection with a build flag alone.
Station G2 and G3 enable it: their Grove UART connector is used with M5Stack
Unit GPS modules, which default to 115200.
On a RAK19007 the RAK12501's supply is 3V3_S, switched by WB_IO2, so
gps off, periodic mode and shutdown left it powered. Pass WB_IO2 to the
NMEA driver as peripheralPower under GPS_RAIL_POWER_CONTROL, set by the
new RAK_4631_repeater_gps_power env. It is opt-in because the rail feeds
every slot module, and refused with ETHERNET_ENABLED (RAK13800).
The RAK12500 (I2C) driver keeps switching its own power pin, so this
only applies on the NMEA path.
RefCountedDigitalPin now sets OUTPUT on claim and release: WB_IO2 left
as an input (as probeRak12500() leaves it after a failed probe) keeps
3V3_S in its last state, so writing the latch alone did not cut it.
Measured with a KM003C, battery and panel out: gps off 40.5 -> 12.4 mA,
shutdown 29.7 -> 1.30 mA.
The refactor no longer calls Serial1.setPins() on nRF52, so Serial1 uses
PIN_SERIAL1_RX/TX directly. Those were swapped (the GPS transmits on
P0.20), so no data was received. Fix them and define PIN_GPS_TX/RX by the
gps module's side, as other variants do.
The ATGM336H keeps its NMEA output config across power cycles, and other
firmware may leave every sentence disabled. Re-enable GGA + RMC after each
power-up.
Adds repeater, room_server, companion_radio_usb and kiss_modem
environments for the NUCLEO-WL55JC1 (STM32WL55JC, integrated SubGHz radio).
Notes on the board setup:
- Uses the upstream nucleo_wl55jc board. PlatformIO's boards_remap maps it
to the core's NUCLEO_WL55JC1 variant, so the LEDs, user buttons and the
LPUART1 -> ST-LINK VCP serial mapping all come from the core rather than
being redefined here.
- The RF switch table is built from the core's LORAWAN_RFSWITCH_* macros
(SP3T front end on PC3/PC4/PC5) so it tracks upstream if those are ever
revised. Both RFO_LP and RFO_HP are registered, so RadioLib selects HP
above 14 dBm and LP below it.
- board_build.extra_flags pins the device to STM32WL55xx. The stock board
manifest declares product_line STM32WL55xx but extra_flags -DSTM32WLE5xx;
that only works because every #elif chain happens to test WL55xx first.
- The Nucleo's LD1..LD3 are driven active HIGH, so the TX LED hooks are
inverted relative to STM32Board's active-LOW default.
- 32 KB reserved at the top of flash for LittleFS, as on the other
STM32WL variants.
Verified on hardware: all four environments build; repeater and room_server
flash and run over ST-LINK; identity and prefs persist across reboot and
across a firmware swap; and GPIOC reads back the documented RX levels at
idle, confirming the front-end switch is driven correctly.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Add a dimmed heartbeat for the SenseCAP Solar (P1 Pro) white LED in the
repeater firmware, implemented entirely as a SenseCapSolarBoard::loop()
override so no example main.cpp needs to be touched:
- 100 ms pulse every 5 s, dimmed to 10% brightness via hardware PWM
(NRF_PWM0 / HwPWM0, 1 kHz, COUNTERTOP 16000, compare 1600)
- during the 4.9 s off phase the PWM peripheral is stopped (ENABLE=0),
the pin is released (PSEL disconnect) and GPIO 11 is held LOW, so no
HFCLK is demanded between pulses
- on successful application-level "start ota" the PWM is stopped and the
white LED goes steady full-brightness while BLE OTA is advertised;
on failed start the heartbeat keeps blinking
- powerOff() stops/releases the heartbeat PWM before shutting the LED off
- non-blocking millis() timing with wrap-safe unsigned arithmetic
- gated by SENSECAP_SOLAR_WHITE_LED, defined only in the
SenseCap_Solar_repeater PlatformIO env, so the room-server and
companion firmwares sharing this board class are unaffected
No changes to LoRa/repeater forwarding, the blue TX LED, charging LEDs,
GPS, power management, config storage or the bootloader.
Add a board variant for the DFRobot DFR1195 (ESP32-S3-WROOM-1-N4, SX1262, 80x160 ST7735S) and a Companion BLE environment. The display and radio use separate SPI controllers: the SX1262 is on FSPI and the ST7735 is on HSPI. ST7735Display selects that HSPI bus and the 160x80 init sequence only when DFROBOT_LORAWAN_ESP32S3 is defined.
What changes
- variants/meshtracker_x1/platformio.ini moves stevemarple/MicroNMEA from the
four environments that listed it into the [MeshTracker_X1] base section, the
way nano_g2_ultra already keeps it, and drops the four copies.
Why
- MeshTracker_X1_kiss_modem was the one environment of this variant that did not
list the library, so it did not build:
src/helpers/sensors/MicroNMEALocationProvider.h:4: fatal error: MicroNMEA.h: No such file or directory
variants/meshtracker_x1/target.cpp includes the location provider
unconditionally and every environment of this variant compiles target.cpp, so
every one of them needs the library. Putting it in the base section makes that
true by construction rather than by repeating the line and hoping none is
forgotten, which is exactly what happened here.
Compatibility
- All five environments of the variant were built, which is the whole reach of this
change. MeshTracker_X1_kiss_modem now builds (text 240180, bss 18236; on unchanged
dev it does not build at all). For the four that already built, text and bss are
byte for byte identical to a build from unchanged dev 428a95c6 with the same
toolchain, so inheriting the library instead of listing it changes nothing for
them: MeshTracker_X1_repeater text 299524 bss 32024, _room_server 292020 / 35740,
_companion_radio_usb 316356 / 141000, _companion_radio_ble 322036 / 145432, each
text +0 and bss +0 against dev.
Move the onboard radio probe into RAK3401Board::begin() so a low-voltage
SYSTEMOFF at boot no longer leaves the RAK4631's onboard SX1262 in
standby. Add board startup tests and run them in CI.