5 Commits

Include renames

Author	SHA1	Message	Date
tfaour	474b92a282	Add server-side support for a second panel (13.3in Spectra 6 / EE02) and scaffold its firmware target ... 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.	2026-08-04 20:08:22 +00:00
tfaour	c4cd9b73e8	Invalidate the tracked display CRC when a non-photo screen is drawn ... The QR onboarding and "CONNECTING..." status screens write to the panel through a separate path that never touched the last-displayed-photo CRC added in the previous commit. That left it stale relative to what's actually on screen after either one draws -- most visibly after a factory reset: reprovisioning and reconnecting could fetch a photo whose CRC happened to match the one from before the reset, skip the refresh, and leave the QR code frozen on screen indefinitely. Both screens now invalidate the tracked CRC right after drawing, so the next photo fetch is always guaranteed to actually refresh.	2026-07-18 23:59:48 -04:00
tfaour	55d4b28f37	Clarify setup screen step headings	2026-07-18 16:27:22 -04:00
tfaour	ecc42f23c0	Redesign setup screen: title + two-step layout with a config QR ... Adds a "2. CONFIGURATION" step alongside WiFi setup: a second QR code linking straight to the captive portal page (http://<ap-ip>/), for anyone who's joined the AP but wants a one-scan shortcut to the config form instead of relying on the captive-portal popup. The AP netif is now created (but not started) before the display renders, since the AP's IP is fixed at netif creation and needed for this QR before the network is actually up. Pulls the pixel/text drawing primitives (previously private to qr_onboarding.c) out into epd_draw.c/.h so the upcoming status screen can reuse them instead of duplicating.	2026-07-18 14:07:56 -04:00
tfaour	1dd02da70a	Add QR-code WiFi onboarding screen ... Vendors two small MIT/BSD-3-Clause libraries rather than hand-rolling either: Nayuki's qrcodegen (QR matrix generation) and Waveshare's Font24 bitmap table from their e-Paper repo (same repo the epd7in3e driver came from) for rendering readable text on the panel. qr_onboarding_show() builds a standard WIFI:T:WPA;S:...;P:...;; payload, rasterizes the QR module matrix plus the SSID and password as plaintext underneath (for anyone provisioning from a device that can't scan a QR) onto a malloc'd frame buffer, and pushes it to the panel via epd_display_buffer(). The buffer is heap-allocated on demand rather than statically reserved, since 192KB held permanently in BSS would eat into the RAM budget the HTTP fetch path (task 6) is specifically trying to keep free. Wired into wifi_provisioning_start() before the softAP comes up, so the join instructions are already on-screen by the time the network is joinable.	2026-07-18 11:20:43 -04:00