-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
epd_renderer_init failing on v7 board #300
Comments
Never seen this error before but I had an issue trying with 5.3, although very different since it does not build. I strongly recommend you to install 5.1 and maybe on first try just flash the dragon example with IDF. |
The crash is due to an assert. Maybe you can see what the assert is checking? That can be a clue to what is going on. Also check your sdkconfig that both cpu cores is enabled. |
Check line 1061 in this file: |
It looks like downgrading to 5.1 works- I was able to build and flash the demo on v6 and v7 boards without any issues after doing so. Thanks for the guidance! As another note- is there a recommended place to ask general questions about this project beyond Github issues? It looks like the Slack link is broken. |
Sure please try https://github.com/vroland/epdiy/discussions |
Hello! I recently got a v7 board from JLCPCB. I've been able to get things running on the v5 board before, but I'm running into issues with the dragon example project with this new board. I installed IDF version 5.2.1 through the VSCode extension, and was able to successfully build and flash the project to my board. The only change I made in the code was to adjusts the VCOM in
epd_set_vcom
. When monitoring after flashing, I see the following message repeatedly in the logs:The assertion here is failing when calling
epd_renderer_init
: https://github.com/vroland/epdiy/blob/main/src/render.c#L326. As a result, there's nothing displaying on the screen. Has this issue been seen before, and if so are there any recommended mitigations? Thank you!The text was updated successfully, but these errors were encountered: