Skip to Content
Memory and flash

Memory and flash

Flash layout

Flash (32 MB)

OffsetContentWritten by
0x0bootloaderflash.sh
0x8000partition table (partitions/v2/32m.csv)flash.sh
0x9000nvsfactory, 200 KB: Seeed device EUI and keysnever
0x3B000nvs, 840 KB: settings, notes, memories, alarmsthe firmware
0x10D000otadataflash.sh, OTA
0x200000ota_0, 4 MB: the appflash.sh, flash_app.sh, OTA
0x600000ota_1, 4 MB: the other OTA slotOTA
0xA00000assets, 16 MB: fonts, faces, wake word modelflash.sh, flash_assets.sh

nvsfactory holds the keys Seeed put on your device. No Bắp script writes it, so you can always go back to the official firmware.

RAM

The ESP32-S3 has about 512 KB of internal SRAM and the Watcher adds 8 MB of PSRAM. Internal RAM is the scarce one: Wi-Fi, TLS (hardware AES DMA buffers), audio and LVGL all want it.

IdleLowest seen
Free internal RAM55–60 KB~33 KB
Free PSRAM~3.2 MB

How Bắp keeps it that way:

  • cJSON and small allocations go to PSRAM; requests up to 256 bytes stay internal.
  • Task stacks that never touch flash run in PSRAM (xTaskCreateWithCaps): the Opus codec, the notification player and the Zing player.
  • Wi-Fi and lwIP buffers live in PSRAM, which leaves room for a 16 KB TCP window so Gemini audio arrives smoothly.
  • The LVGL task has a 12 KB stack (it used to overflow), and /api/perf reports each task’s minimum free stack so regressions show up early.
  • The web server is limited to 4 open sockets and lwIP to 16 in total.