feat: enable traffic module enable all nrf52 and esp32 nodes#9902
feat: enable traffic module enable all nrf52 and esp32 nodes#9902h3lix1 wants to merge 8 commits into
Conversation
|
I'm going to have to build and check this, but the Lilygo T3S3 series have only 2048 PSRAM, see Are you aiming to max out the PSRAM on the T3S3 models with this traffic module? |
The module should only use 20 Kilobytes of PSRAM. There isn't a goal to use all the PSRAM, but to be as light as possible on DRAM. |
Documents our experimentation with ESP-IDF DFS and why it doesn't work well for Meshtastic (RTOS locks, BLE locks, USB issues). Proposes simpler alternative: manual setCpuFrequencyMhz() control with explicit triggers for when to go fast vs slow.
3fcfbac to
10208e7
Compare
Summary
Enable Traffic Management by default for all
ESP32andnRF52builds via shared compile-time defaults, and remove now-redundant per-variant definitions.What Changed
src/mesh/mesh-pb-constants.hto defaultHAS_TRAFFIC_MANAGEMENT=1onARCH_ESP32andARCH_NRF52.2048onESP32boards withBOARD_HAS_PSRAM1024onESP32boards without PSRAM1024onnRF520when Traffic Management is disabledHAS_TRAFFIC_MANAGEMENT/TRAFFIC_MANAGEMENT_CACHE_SIZEoverrides from:variants/esp32s3/heltec_v4/variant.hvariants/esp32s3/station-g2/variant.hvariants/nrf52840/tracker-t1000-e/variant.hvariants/native/portduino/variant.hunchanged, since the shared default logic does not apply to native builds.Why
ESP32andnRF52targets.ESP32-S3and similar boards from incorrectly inheriting the larger2048cache.🤝 Attestations
Heltec v4
Station G2