mirror of
https://github.com/MarekZegare4/MeshCore-Solo.git
synced 2026-10-11 16:12:01 +00:00
JakubandClaude Opus 5.5
7826360d13
The phone app's offline queue took 256 x 177 B = 45 KB, which with the on-device UI left the L1 ~5 KB of heap from boot (the sign buffer of #38 never fit). The UI keeps its own message history, and a full queue drops the oldest channel messages first, so 128 is plenty: the L1 heap now has ~27 KB free. L1 OLED / e-ink, ProMicro, T-Echo Lite, both GAT562; the upstream variants/ are unchanged (build_unflags in solo/). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
25 lines
1.3 KiB
INI
25 lines
1.3 KiB
INI
; Solo build for Seeed Wio Tracker L1 (OLED) -- extends WioTrackerL1CompanionDual,
|
|
; defined in variants/wio-tracker-l1/platformio.ini. Solo configs live in their
|
|
; own top-level solo/ folder, separate from the shared upstream board variants
|
|
; in variants/, so this repo's Solo-specific additions don't get mixed in with
|
|
; configs other MeshCore forks/upstream also carry.
|
|
;
|
|
[env:WioTrackerL1_companion_solo_dual]
|
|
extends = WioTrackerL1CompanionDual
|
|
; Optimise for size, not speed: the nRF52 Arduino core defaults to -Ofast
|
|
; (≈ -O3 + -ffast-math), which bloats flash by ~200 KB on this feature-rich
|
|
; solo build. -Os keeps every feature, fits comfortably, and is actually safer
|
|
; for float (no fast-math reassociation). Speed is irrelevant for the UI/mesh.
|
|
; The offline queue (messages held for the phone app while it's away) at 128,
|
|
; not the board's 256: on the nRF52 the 256 x 177 B left ~5 KB of heap next to
|
|
; the on-device UI (which keeps its own history), too little for a sign buffer.
|
|
build_unflags = -Ofast -D OFFLINE_QUEUE_SIZE=256
|
|
build_flags = ${WioTrackerL1CompanionDual.build_flags}
|
|
-D OFFLINE_QUEUE_SIZE=128
|
|
-D UI_HAS_JOYSTICK_UPDOWN=1
|
|
-D ENABLE_SCREENSHOT
|
|
-D DUAL_SERIAL=1
|
|
-D GPS_SKYVIEW ; Tools > Satellites (helpers/sensors/GpsSky.h)
|
|
-Os
|
|
extra_scripts = post:create-uf2.py
|