tfaour
474b92a282
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.
16 lines
621 B
CMake
16 lines
621 B
CMake
# SRCS is conditional on which board's panel this build targets (see
|
|
# main/CMakeLists.txt's comment on why REQUIRES/PRIV_REQUIRES itself
|
|
# can't be) -- an ee02 build still always requires this component (so
|
|
# its Kconfig menu/include dir exist), but contributes zero object
|
|
# files/symbols to it, since epd13in3e.c provides the real epd_init()
|
|
# etc. for that board instead.
|
|
if(CONFIG_FRAME_PANEL_EE02_13IN3)
|
|
set(srcs "")
|
|
else()
|
|
set(srcs "epd7in3e.c")
|
|
endif()
|
|
|
|
idf_component_register(SRCS ${srcs}
|
|
INCLUDE_DIRS "include"
|
|
PRIV_REQUIRES esp_driver_spi esp_driver_gpio)
|