meshtastic/firmware

Assert and watchdog behaviour on RP2xx0 is unusual compared to other architectures, and might be a suitable subject for a deep dive into the hardware. Possible related issues: #11632 #11234 #10430 #11235 (DRAFT) #11220 #11630 #11641

Platform other Description The RAK WisMesh Tag uses an AT6558R GNSS receiver. When gps_update_interval > 10s, Meshtastic uses GPS_HARDSLEEP, but waking behaves like a cold start: 18:27:16 GPS power state move from HARDSLEEP to ACTIVE 18:28:00 New GPS pos ... Sats=10 GPSlock=1 18:28:00 Took 43s to get lock 18:28:27 GPS power state move from HARDSLEEP to ACTIVE 18:29:18 New GPS pos ... Sats=9 GPSlock=1 18:29:18 Took 51s to get lock For comparison, without cutting power: 18:28:05 GPS power state move from IDLE to ACTIVE 18:28:11 New GPS pos ... Sats=12 GPSlock=1 18:28:11 Took 6s to get lock Positions after hard sleep also jump considerably before stabilizing. The AT6558R supports UART timed standby: $PCAS12,<seconds>*<checksum> Meshtastic could use this instead of hard power-off, retaining navigation data and waking with a hot start. Using the datasheet values of 23 mA active and 20 µA sleep, assuming 4 seconds for hot reacquisition and the observed average of 47 seconds for cold sta

Description Implement the signed plaintext licensed-mode remote-administration design from meshtastic/design#123 as a separate follow-up stacked on #10967 and #10969. This must reuse existing Router-verified XEdDSA, security.admin_key[], and the AdminModule session challenge. It must not add an authentication version, signature format, certificate scheme, encrypted ham traffic, or normal-mode signed-admin fallback. Required behavior Accept a licensed remote Admin request/mutation only when it is directed to this node, has a successfully verified XEdDSA signature, and the exact verified signer key matches a populated admin_key slot. Carry the exact verified signer key from Router to AdminModule as transient authenticated state; clear and ignore serialized auth flags/keys at ingress. Require prior verified signed NodeInfo discovery or warm-store key retention; admin_key is authorization, not discovery. Retain the existing session-passkey requirement for mutations. Add explicit session-i

Category Other Hardware T-Echo Is this bug report about any UI (https://meshtastic.org/docs/configuration/device-uis/) component firmware? Meshtastic UI aka MUI InkHUD BaseUI Firmware Version 2.7.23.b246bcd Description After upgrading from firmware version 2.7.23.2.7.22.96dd647 (working) to 2.7.23.b246bcd (broken), the LilyGo T-Echo device no longer stays powered off when shut down. Instead, it powers off briefly and then automatically restarts. Hardware Model: LilyGo T-Echo Firmware versions tested ✅ Working: 2.7.23.2.7.22.96dd647 (commit 96dd647, dated 2026-04-13) ❌ Broken: 2.7.23.b246bcd (commit b246bcd, dated 2026-05-06) Root cause analysis The issue appears to be related to commit c038cfe ("Move device code from main.cpp to earlyInitVariant", 2026-01-26), which was merged between these two versions. This commit refactored the shutdown logic for T-Echo: Before (working): The T-Echo shutdown code was embedded directly in src/platform/nrf52/main-nrf52.cpp within cpuDeepS

Summary meshtasticd (Linux/portduino build) grows its virtual address space without bound on long-uptime hosts. On two boxes in a 5-box fleet I observed VmPeak ~915 GB and VmSwap ~1.78 GB after 9–10 days of uptime, while VmRSS stayed at ~45 MB. The 1.78 GB of touched-then-swapped pages pegged one Pi 5's swap at 100% and starved the rest of the stack. A clean restart drops VmPeak back to ~280 MB and VmSwap to 0. I'm filing this from the perspective of an operator running a small permanent NOC fleet — happy to instrument further if it helps narrow it down. Environment Version: meshtasticd 2.7.15 (all five fleet boxes are on the same build) OS: Debian / Raspberry Pi OS bookworm (trixie on one) Arch: aarch64 Hardware: mix of Pi 4B (Cortex-A72), Pi 5 (Cortex-A76), and a Pi Zero 2 W (Cortex-A53) Service: meshtasticd.service running long-lived as a systemd unit HATs: Various Meshtastic SX1262 HATs via SPI Fleet snapshot at the time of investigation Box Hardware Preset User Uptime VmP