I can confirm this exact issue on two of my own CrowPanel 4.2" E-Paper units. Same symptom: BUSY (GPIO48) never clears after reset, no matter what firmware I compile myself - only the precompiled factory image works. Happy to share detailed logs if useful.
Elecrow team, please respond with any workaround, thank you. I'm about to send my THIRD elecrow panel back for a return/replacement. This is super frustrating. The ESP-32 chip is alive and works fine, but nothing can be painted to the screen; that's the whole reason for an e-Paper display.
@bEngel79 said:
I can confirm this exact issue on two of my own CrowPanel 4.2" E-Paper units. Same symptom: BUSY (GPIO48) never clears after reset, no matter what firmware I compile myself - only the precompiled factory image works. Happy to share detailed logs if useful.
Can you post the link to the image that actually works?
In my case, only the firmware that came with worked, and then whatever else I flash, it does not.
Can confirm that I have the exact same issue as OP, and I created an account to ask about this. I will try the green dot firmware and report if that fixes my issues.
Comments
I can confirm this exact issue on two of my own CrowPanel 4.2" E-Paper units. Same symptom: BUSY (GPIO48) never clears after reset, no matter what firmware I compile myself - only the precompiled factory image works. Happy to share detailed logs if useful.
Elecrow team, please respond with any workaround, thank you. I'm about to send my THIRD elecrow panel back for a return/replacement. This is super frustrating. The ESP-32 chip is alive and works fine, but nothing can be painted to the screen; that's the whole reason for an e-Paper display.
I have the EXACT same issue... Only my panel says v1.2
Can you post the link to the image that actually works?
In my case, only the firmware that came with worked, and then whatever else I flash, it does not.
Why is no-one from Elecrow actively looking into this? It's been WEEKS!!
Brought it back to "life" with "green sticker" firmware.... But how do I compile the examples to get my own SW working...???
Solved mine with "green dot" firmware and examples. Also reverted ESP32 package in Arduino back to 2.0.14.
Can confirm that I have the exact same issue as OP, and I created an account to ask about this. I will try the green dot firmware and report if that fixes my issues.