-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Compiling cale-idf in target esp32c3 #39
Comments
Next blocker: Is transferring too much for the C3. Using display.spi_optimized = false; will not sent all X lines together. Status: I still could not see the epaper refresh. Todo: hook analyzer with SPI and check what comes out |
Build and working. SPI speed does not seem to be lower. Pending to review consumption from C3 vs ESP32 Not sure when this is going to be merged in master since initially was though as an experimental test. The good thing is that works correctly. Working pins are in this file:
|
Implementation branch: 39-c3
We need to exclude epd_driver from build since it's ESP32's only:
idf.py set-target esp32c3
It seems EPDiy is using some includes that are not meant to work in C3. But of course using parallel is excluded from testing this since it does not even has enough PINs for something like this.
Building this with target esp32c3 gives issues with SPI:```
../components/CalEPD/models/plasticlogic/epdspi2cs.cpp:66:28: error: 'EPD_HOST' was not declared in this scope
ret=spi_bus_initialize(EPD_HOST, &buscfg, DMA_CHAN);
^~~~~~~~
../components/CalEPD/models/plasticlogic/epdspi2cs.cpp:66:28: note: suggested alternative: 'SPI_HOST'
ret=spi_bus_initialize(EPD_HOST, &buscfg, DMA_CHAN);
^~~~~~~~
SPI_HOST
../components/CalEPD/models/plasticlogic/epdspi2cs.cpp:66:47: error: 'DMA_CHAN' was not declared in this scope
ret=spi_bus_initialize(EPD_HOST, &buscfg, DMA_CHAN);
^~~~~~~~
../components/CalEPD/models/plasticlogic/epdspi2cs.cpp:66:47: note: suggested alternative: 'DMA_ATTR'
ret=spi_bus_initialize(EPD_HOST, &buscfg, DMA_CHAN);
^~~~~~~~
DMA_ATTR
The text was updated successfully, but these errors were encountered: