CrowPanel 4.2" E-Paper (DIE07300S, V1.0) — panel frozen, won't update even with official factory fw
Hi everyone,
I have a CrowPanel ESP32 4.2" E-Paper HMI (SKU: DIE07300S, hardware V1.0 — no green sticker on the back). The panel worked perfectly out of the box (factory demo displayed). After flashing my own code, the panel stopped updating and now stays frozen on the last image. I've spent many hours troubleshooting and I'm stuck — hoping someone can help.
Current symptom: The e-paper never refreshes (no visible flicker/refresh at all) regardless of what I flash. The last factory demo image is still frozen on screen. The ESP32-S3 itself is clearly alive and healthy.
Evidence the chip/board is fine:
Detected every time in ESP Tool: Connected to ESP32-S3 (QFN56) revision v0.2
Uploads always succeed (100%, "Hash of data verified")
Clean boot in serial monitor: rst:0x1 (POWERON), mode:DIO
What I've tried (all with no change on the panel):
Correct board settings per the wiki: ESP32S3 Dev Module, Flash Mode QIO 80MHz, Flash Size 8MB, PSRAM OPI, Partition Scheme "Huge APP (3MB No OTA/1MB SPIFFS)", USB CDC On Boot Enabled, Upload Speed 115200.
Official Elecrow Demos.zip (4.2_WIFI_refresh) — uploads fine, panel doesn't change.
Official Elecrow Examples.zip (basic display example) — same, no change.
A minimal sketch using the official EPD driver (EPD.cpp / EPD_SPI.cpp) doing only EPD_GPIOInit() → EPD_Clear() → full-screen fill — no change.
Both pin sets found in EPD_SPI.h: the active set (RES 47, DC 46, CS 45, BUSY 48, SCK 12, MOSI 11) and the commented-out alternate set (RES 21, DC 9, CS 10) — no change with either.
Re-flashed the official factory firmware from the GitHub repo (factory_firmware: bootloader @0x0, partitions @0x8000, boot_app0 @0xe000, main.ino @0x100000) using esptool-js — flash succeeded, but the panel still does not display anything.
Reseated the orange FPC ribbon connector several times (clip fully closed, ribbon straight and fully inserted).
My conclusion / question:
Since the ESP32-S3 flashes and boots fine, but even the official factory firmware can't drive the panel, it seems the issue is with the e-paper panel or the FPC connection — not software. The driver appears to hang waiting on the BUSY signal (which never returns).
Is this a known failure mode for the FPC connector / panel on the 4.2" V1.0?
Is there any recovery procedure or hardware check I might have missed?
Thanks in advance!
Comments
Dear surdilamak,
We sincerely apologize for the inconvenience. We need some time to analyze your video and will get back to you as soon as possible. Please wait patiently.
Yeah, I tried for days with various examples to get this thing to display ANYTHING [I][app:151]: ESPHome version 2026.6.4 compiled on 2026-07-09 20:15:36 +0200
[20:19:11.596][I][app:158]: ESP32 Chip: ESP32-S3 rev0.2, 2 core(s)
Dear surdilamak,
Please record a video of the firmware flashing process. Also, please take a picture of the firmware flashing software interface so we can check if the download address is accurate. It should be usable normally.
Thanks!
Warm regards,
I tried for days with various examples (also from this site) to get this thing to display anything running ESPHome, the screen just does not change at all. I'm using ESPHome from Home Assistant to update it. Can you please provide one working YAML example for this specific screen (for the latest ESPHome)? The logs indicate the ESP32 board works and responds, it's the screen that does not react!
I have exactly the same issue for 2 pieces Of 4.2”eink ESP32 dev board I got from Amazon, need a solution for them too.
the ESP32S3 functions well on communicating with Arduino serial monitor, but the epaper screen don't show any change.
Dear TTT,
We apologize for the inconvenience.
Could you please provide the SKU of your device?
Please first flash the factory firmware (available via the GitHub link on the wiki(https://www.elecrow.com/wiki/)). Then, after flashing, connect the USB cable and press the button to see if the interface switches.
Dear Peter,
We apologize for the inconvenience.
Please first flash the factory firmware (available via the GitHub link on the wiki(https://www.elecrow.com/wiki/)). Then, after flashing, connect the USB cable and press the button to see if the interface switches.
SKU: DIE07300S v1.2
The back of my board has this printed on it:
I048 => LCD_BUSY
I047 => LCD_RES
I046 => LCD_D/C
I045 => LCD_SPI_CS
I012 => LCD_SPI_CLK
I011 => LCD_SPI_MOSI
Snippet from one of my tries:
ESP_LOGI("diag", "GPIO1 (EXIT) : %s", gpio1 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO2 (MENU) : %s", gpio2 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO4 (Rotary DOWN): %s", gpio4 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO5 (Rotary OK) : %s", gpio5 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO6 (Rotary UP) : %s", gpio6 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO7 (Power) : %s", gpio7 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO12 (CLK) : %s", gpio12 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO11 (MOSI) : %s", gpio11 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO45 (CS) : %s", gpio45 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO46 (DC) : %s", gpio46 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO47 (RESET) : %s", gpio47 ? "HIGH" : "LOW");
ESP_LOGI("diag", "GPIO48 (BUSY) : %s", gpio48 ? "HIGH (busy)" : "LOW (ready)");
[01:24:54.991][I][diag:144]: GPIO1 (EXIT) : HIGH
[01:24:54.994][I][diag:145]: GPIO2 (MENU) : HIGH
[01:24:54.995][I][diag:146]: GPIO4 (Rotary DOWN): HIGH
[01:24:54.996][I][diag:147]: GPIO5 (Rotary OK) : LOW
[01:24:54.997][I][diag:148]: GPIO6 (Rotary UP) : HIGH
[01:24:55.001][I][diag:149]: GPIO7 (Power) : LOW
[01:24:55.002][I][diag:150]: GPIO12 (CLK) : LOW
[01:24:55.005][I][diag:151]: GPIO11 (MOSI) : LOW
[01:24:55.006][I][diag:152]: GPIO45 (CS) : LOW
[01:24:55.007][I][diag:153]: GPIO46 (DC) : LOW
[01:24:55.008][I][diag:154]: GPIO47 (RESET) : LOW
Exact same issue, and this is my THIRD Elecrow E-Paper display that I've attempted.