Server: Frame.panel_type (new column + migration) is auto-derived from the device's reported board (X-Frame-Board), never user-set -- the panel is a property of the hardware, not a picker in the UI. image_pipeline's packing/render pipeline is parameterized by panel geometry instead of hardcoded 800x480 globals, with the real confirmed 13.3in geometry (1600x1200) registered alongside the original 7.3in panel. Existing 7.3in frames are unaffected (column default + board mapping both resolve to the original panel). Board identifiers are also renamed (devkit/xiao -> devkit_esp32c6/ xiao_esp32c6, plus new "ee02") since the EE02 board also carries a XIAO module -- "xiao" alone stopped disambiguating hardware. The server keeps accepting the legacy bare names indefinitely for already-flashed devices. Firmware: scaffolds a third build target (ee02, ESP32-S3 -- a real chip-target change, not just a same-chip Kconfig variant like xiao) and a new epd13in3e driver component skeleton. The actual panel init/LUT/ refresh register sequence isn't ported from vendor demo code yet (none was available), so that component deliberately fails to compile (#error) rather than risk sending unverified register values to real hardware -- devkit/xiao are unaffected and build identically to before. CI's ee02 build step is continue-on-error for the same reason.
743 B
743 B
| 1 | # Name, Type, SubType, Offset, Size, Flags |
|---|---|
| 2 | # Same OTA layout/offsets as partitions.csv (the 8MB dev-board table) -- |
| 3 | # the XIAO ESP32-S3 Plus's 16MB flash has plenty of room for the same |
| 4 | # 2MB app slots (current firmware runs ~1.2MB, per partitions_xiao.csv's |
| 5 | # own sizing note) without needing to trim anything the way the 4MB xiao |
| 6 | # table did. Leaves ~12MB of the 16MB unused/unpartitioned for now -- |
| 7 | # revisit sizing once a real build's actual footprint and any EE02- |
| 8 | # specific storage needs (if ever) are known. |
| 9 | nvs, data, nvs, 0x9000, 0x6000, |
| 10 | phy_init, data, phy, 0xf000, 0x1000, |
| 11 | ota_0, app, ota_0, 0x10000, 0x200000, |
| 12 | otadata, data, ota, 0x210000, 0x2000, |
| 13 | ota_1, app, ota_1, 0x220000, 0x200000, |