Layer: L7 Application ยท Build flags: PC_ENABLE_PARTITION_MONITOR
What this example teaches
The ESP32's flash is carved into partitions (factory app, OTA slots, NVS, LittleFS, ...). pc_partition_monitor_begin() serves that table as JSON at /partitions: each entry's label, kind, type/subtype, flash offset, and size, plus which app slot is currently running. It is a one-call diagnostics endpoint that pairs well with OTA dashboards, and it needs no special hardware.
One call mounts the endpoint:
pc_partition_monitor_begin(server, "/partitions");
The handler reads the partition table from the ESP-IDF API and serializes it directly into the response (no heap).
Build and run
pio ci --board=esp32dev --project-option="framework=arduino" \
--project-option="build_flags=-DPC_ENABLE_PARTITION_MONITOR=1" \
--lib="." examples/L7-Application/PartitionMonitor/PartitionMonitor.ino
curl http://<ip>/partitions # JSON: labels, offsets, sizes, running slot
Annotated source
The complete sketch (PartitionMonitor.ino), reproduced verbatim with added explanatory comments:
#define PC_ENABLE_PARTITION_MONITOR 1
static const char *SSID = "YOUR_SSID";
static const char *PASSWORD = "YOUR_PASSWORD";
void setup()
{
Serial.print("Connecting to WiFi");
{
delay(250);
Serial.print('.');
}
Serial.printf("IP: %u.%u.%u.%u\n", (unsigned)(ip & 0xFF), (unsigned)((ip >> 8) & 0xFF),
(unsigned)((ip >> 16) & 0xFF), (unsigned)((ip >> 24) & 0xFF));
pc_partition_monitor_begin(server, "/partitions");
}
void loop()
{
}
Single-port HTTP server with deterministic, zero-allocation execution.
int32_t begin(const WebServerConfig *cfg=nullptr)
Initialize all connection slots and open all registered listeners.
void handle()
Drive the server - call every Arduino loop() iteration.
Flash partition-map monitor (PC_ENABLE_PARTITION_MONITOR).
bool init_wifi_physical(const char *, const char *)
Connect to a WiFi access point.
uint32_t pc_net_egress_ip(void)
IPv4 (network byte order) of the current egress interface, or 0 if none.
bool wifi_ready()
True if the WiFi station link is up (associated + an IP is assigned).
Layer 1 (Physical) - link bring-up and live egress-interface reporting.
Layer 7 (Application) - public HTTP routing API.