Max

Firmware Mx Architecture

Five boot phases, five FreeRTOS tasks, six transports on an ESP32-S3.

Firmware Mx Architecture (v2026-09-30T101433Z-5e473105f4) 2026-09-30 | Five boot phases, five FreeRTOS tasks, six transports on an ESP32-S3. 1 - BUILD - Firmware Compilation Developer Edit platformio.ini Add -D BENCH_MODE Save changes PlatformIO platformio run --environment heltec_v2_hub -w Builds firmware.elf Watches for changes Edit build con… 2 - TEST - Firmware Testing Firmware Initialize HAL Initialize transports Run tests Serial Monitor platformio device monitor --baud 115200 Monitors test output Displays results Start firmware 1. Edit build config 2. Start build process 3. Initialize HAL 4. Initialize transports 5. Run tests 6. Monitor test results platformio.ini snippet [env:heltec_v2_hub] platform = espressif32 board = heltec_wifi_lora_32 framework = arduino build_flags = -std=c++17 -fexceptions -Wall -Wextra -D FIRMWARE_VERSION="0.2.0" -D MAGIC_V2 -D ROLE_HUB -D RADIO_SX1276 -D ARDUINO_HELTEC_WIFI_LORA_32 -D BENCH_MODE 4 of 4 identifiers appear only in design docs, not in code — this shows SPECIFIED behaviour, not verified implementation. Ensure all tests pass before deploying to mesh. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal As of 2026-09-30 10:14 UTC, from commit 5e47310

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Max
Slug
firmware-mx-architecture
Rendered
2026-09-30T101433Z
From commit
5e473105f4
Updated
30 Sep 2026, 10:14 UTC
Sources at
5e47310
Watches
1 path
  • firmware/mx