Commit Graph
1423 Commits
Author SHA1 Message Date
tthandClaude Opus 5.5 46d33bd2b0 FwUpdate: chunk offset overflow, no heavy work in handlers, crc 0 refused
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 14:30:19 +01:00
tth a029863d66 FwUpdate binary: the chunk crc covers sid, offset and length too 2026-11-13 02:11:00 +01:00
tth 227edb9c63 FwUpdate: transfer counters in the ready status too 2026-11-13 02:05:31 +01:00
tth b8ce87c6ff FwUpdate binary: crc16 per chunk; a mangled chunk is dropped and asked for again 2026-11-13 02:03:16 +01:00
tth 0c06994d1f FwUpdate: diagnosis counters in 'failed' status (binary/dropped/text chunks, last manifest writer) 2026-11-13 01:57:56 +01:00
tth b4d2601c8f FwUpdate: transfer session id; binary chunks of another session are dropped 2026-11-13 01:49:55 +01:00
tth 3a7140fd51 FwUpdate: wrong base error names both sha prefixes 2026-11-13 01:33:28 +01:00
tth 232c2bb791 FwUpdate: fw bin -- the binary mesh protocol over the USB console (bench) 2026-11-13 01:30:14 +01:00
tth dc13c5b286 FwUpdate: check the manifest from a RAM copy; flag a flash readback mismatch 2026-11-13 01:26:10 +01:00
tth d1e893f692 FwUpdate binary: explicit chunk length (the node sees the payload padded to 16 B) 2026-11-13 01:18:27 +01:00
tth 637b0d78b7 FwUpdate: binary firmware chunks over the mesh (REQ_TYPE_FW_OTA 0xF0) 2026-11-13 00:55:06 +01:00
tth 5f8788c4b4 FwUpdate: fw base prints the full sha256 of the running image (cache vs fresh) 2026-11-13 00:37:12 +01:00
tth 228e7a129b FwUpdate: manifest check and verify run in loop(), not in the command handler 2026-11-13 00:23:05 +01:00
tth aaca10958e FwUpdate: format 2 delta packages (FwPatch in RAM), base checked with the manifest 2026-11-12 23:52:14 +01:00
tth 8d3e554ca3 FwPatch: in-place delta update (detools 0.53.0 vendored), dry run predicts the real run 2026-11-12 23:23:40 +01:00
tth 3cb3a458ce FwUpdate: battery gate skipped on USB power (VBUS) 2026-11-12 22:29:21 +01:00
tth daaf0c2267 FwUpdate: admin-pushed OTA without a bootloader change (bench stage) 2026-11-12 14:24:24 +01:00
tthandClaude Opus 5.5 ad4f53016c sensors: every continuously converting chip sleeps between reads; INA chips identified
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 13:38:13 +01:00
tthandClaude Opus 5.5 b1e4e65c52 sensors: INA219 sleeps between telemetry reads
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 12:51:40 +01:00
tthandClaude Opus 5.5 3c7d947887 gps duty: sync once a day, retry a failed window after 6 h
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 09:49:46 +01:00
tthandClaude Opus 5.5 84e4136a84 docs: gps duty vs upstream gps period; advert.loc, not "set loc"
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 09:27:26 +01:00
tthandClaude Opus 5.5 8d0b0dd164 Merge upstream/dev (80 commits) [upstream-sync]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 09:22:19 +01:00
nullrouten0andClaude Sonnet 5.5 d1be1cbef0 GPS: stop MicroNMEA reading past the NMEA buffer
Add a 16-byte zeroed tail behind the 100-byte NMEA buffer. MicroNMEA's
fixed-width field skips can read a few bytes past the end of a malformed
sentence; with the tail those reads land on NUL bytes.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-11 17:58:36 +00:00
Olexandr Tyshchenko ace5230ff0 GPS guard: drop leftovers of the alert telemetry channel
#3813 removed the telemetry channel for the GPS time alert. Remove the
docs sentence that still described it and the now unused
GpsGuard::getAlertOffset().
2026-11-11 16:18:58 +02:00
fdlamotte 0ed9ba5724 Merge pull request #3801 from AlexandrTyshchenko/feature/gps-guard-time-wait
GPS guard: show "time wait" instead of "rej nofix" between fixes
2026-11-11 10:13:11 -04:00
Florent 798b719caf CommonCLI: get/set loc to replace gps advert command 2026-11-11 09:52:03 -04:00
Florent 7de440c0d3 gps_guard: remove time alert telemetry 2026-11-11 07:58:39 -04:00
Florent cefd4c76cf Revert "Merge pull request #3784 from Maxwell456/feature/repeater-history"
This reverts commit 66d404eac8, reversing
changes made to 1c4b237d73.
2026-11-11 07:49:41 -04:00
Valentin Metz f02d9d9e47 Fix stack-buffer overflow in CLI reply buffers
The remote-CLI reply buffers in onPeerDataRecv() (repeater, room server,
sensor) and BaseChatMesh were sized temp[166] for a 5-byte datagram
header plus 161 bytes of reply. But MyMesh::handleCommand() first
reflects a 3-byte correlation prefix (e.g. 'aa|') into the reply, after
which CommonCLI commands may write up to 160 chars + NUL into the
remaining 158 bytes -- overflowing the buffer by 2 bytes (e.g. a full
'regions' listing via exportTo(reply, 160)).

Triggering this remotely crashes the node (observed as an unresponsive
repeater after a prefixed 'regions' query); the 2 out-of-bounds bytes
are a printable region-name character and a NUL.

Size the buffers for the full worst case instead:
5 header + 3 prefix + 160 reply + 1 NUL = 169.

Verified with a host ASan harness reproducing the exact layout:
prefixed 'regions' with a 25-region listing overflowed temp[166]
(BufStream::write, RegionMap.cpp) and now passes clean with temp[169];
unprefixed (serial) path unaffected.
2026-11-11 05:30:54 +01:00
Olexandr Tyshchenko e1a445b967 GPS guard: show "time wait" instead of "rej nofix" between fixes
When the last GPS time check passed but there is no current trusted fix
(e.g. the GPS is asleep between periodic fixes), gps guard showed
"time rej nofix", which reads like a rejection although the clock is fine.
Show "time wait" instead. A real rejection without a trusted fix (GPS time
arriving while fixes are rejected) still shows "rej nofix".
2026-11-11 01:48:12 +02:00
Olexandr Tyshchenko 790f4d3f08 GPS: GPS_BAUD_PROBE_LIST as a build flag for any NmeaGpsDriver; enable on Station G2/G3
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.
2026-11-10 23:51:29 +02:00
fdlamotte 66d404eac8 Merge pull request #3784 from Maxwell456/feature/repeater-history
Add min/max/avg history queries to repeaters
2026-11-10 12:42:53 -04:00
fdlamotte 095bd8c311 Merge pull request #3793 from fdlamotte/eink_hibernate_when_off
eink: some updates (busy loop + hibernate when screen off)
2026-11-10 12:00:43 -04:00
Florent 474021f10a eink: some updates (busy loop + hibernate when screen off) 2026-11-10 11:52:38 -04:00
dahuib 6ce010fbfe Support RAK16000 (INA219 at 0x41) on dev 2026-11-10 15:57:32 +01:00
fdlamotte 41540f1642 Merge pull request #3664 from Martin-hub1/dev
Add DFRobot LoRaWAN ESP32-S3 Companion BLE firmware
2026-11-10 09:06:07 -04:00
fdlamotte be36c02d5b Merge pull request #3724 from akalinin-softvelum/feature/eink-busy-hook-v2
companion: keep mesh/BLE running during e-ink refresh
2026-11-10 08:40:43 -04:00
fdlamotte 8d56dcc877 Merge pull request #3725 from Blake-Latchford/fix/espnow-no-lora-build
Fix Generic_ESPNOW_* builds on boards without a LoRa radio
2026-11-10 08:25:37 -04:00
fdlamotte f40e13a425 Merge branch 'dev' into feature/lilygo-t3-stm32 2026-11-10 08:22:52 -04:00
fdlamotte 822bea7b7c Merge pull request #3753 from fdlamotte/gps_refactor
Big GPS refactor
2026-11-10 07:44:00 -04:00
fdlamotte 41eb344511 Merge pull request #4 from AlexandrTyshchenko/feature/gps-guard-refactor
GPS: optional anti-spoofing guard for position and time (GPS_GUARD)
2026-11-09 18:02:06 -04:00
Olexandr Tyshchenko 3da13dd91a GPS guard: gps guard on/off, saved in the GPS prefs 2026-11-09 23:50:48 +02:00
Olexandr Tyshchenko 6291f9156a GPS guard: save gps fence in the GPS prefs 2026-11-09 23:16:29 +02:00
Olexandr Tyshchenko ca5ccddc85 NmeaGpsDriver: baud rates to probe come from the board, not a build flag 2026-11-09 22:59:47 +02:00
Olexandr Tyshchenko faabf34950 GpsGuard: let GPS correct a clock outside the plausible window 2026-11-09 22:54:18 +02:00
Olexandr Tyshchenko f5cbc18b83 GPS guard: drop time force, it goes to a separate PR 2026-11-09 22:30:24 +02:00
Olexandr Tyshchenko 1c9adb46cb GpsGuard: do not show a stale time ok without a current trusted fix 2026-11-09 22:15:45 +02:00
Olexandr Tyshchenko 6b3da8a2b1 GPS: optional anti-spoofing guard for position and time (GPS_GUARD)
A spoofed GPS signal can move a fixed node anywhere and set its clock to
any time; the clock only moves forward, so a time pushed into the future
breaks timestamps and replay protection until fixed by hand.

With GPS_GUARD, MicroNMEALocationProvider asks a GpsGuard before a fix is
stored as the last fix (satellites, HDOP, optional region box, fence
around the configured position, jump speed, N stable fixes) and before
GPS time is written to the clock (trusted fix current, not before the
build date, small steps once the clock is valid, drift-sized after the
first sync). Without a trusted fix no live position is reported.

CLI in CommonGpsPrefs: 'gps guard', 'gps guard accept', 'gps fence',
'gps ref'; CommonCLI keeps the reference on set lat/lon and gps setloc,
resets the time anchor on manual clock sets and adds 'time force'.

Ported from #3736 onto the GpsDriver/LocationProvider refactor.
2026-11-09 20:43:09 +02:00
Olexandr Tyshchenko 978f2662c6 NmeaGpsDriver: optional UART baud rate autodetection (GPS_BAUD_AUTODETECT)
Bytes arriving on the UART does not mean the baud rate is right: at the
wrong rate the parser only sees garbage and never gets a fix. Modules
such as the M5Stack GROVE GPS now default to 115200, while boards
configure 9600.

With GPS_BAUD_AUTODETECT, detect() probes common GNSS rates, starting
with the configured one, and keeps the first one that yields an NMEA
sentence with a valid checksum. The rate is stored in the driver, so
later power cycles reopen the UART with it. Without the flag nothing
changes.

Ported from #3729 onto the GpsDriver refactor.
2026-11-08 23:24:29 +02:00
Maxwell 64f75005b5 Add min/max/avg history queries to repeaters
Move TimeSeriesData from simple_sensor into src/helpers and drive it with
monotonic uptime, so RTC changes cannot stall recording or break queries.
Keep the old RTCClock* overloads as deprecated for custom sensor sketches.

Record 24h of battery, noise floor, TX/RX airtime % and MCU temperature on
repeaters and answer the existing 0x04 min/max/avg request using the same
format as sensor nodes. No packets are sent by this feature.
REPEATER_HISTORY_SLOTS=0 removes it; default off on STM32/RP2040.

Add native tests for TimeSeriesData and document the request and channels.
2026-11-08 16:34:54 +02:00