Brian Team

I just confirmed that these changes do work properly to drive a screen. Tested with an ED060SC4 driven by my custom board using the changes linked in my commit above....

> It seems there issues only compiling in IDF latest release: > > ``` > In file included from /app/src/epd_driver/display_ops.c:1: > /app/src/epd_driver/display_ops.h: In function 'fast_gpio_set_hi': > /app/src/epd_driver/display_ops.h:12:3: error: 'GPIO' undeclared...

@jdoubleu there are two changes that need to happen to the code merged from the BSP PR: 1. In display_ops.h, we can't access the GPIO macro directly anymore. Add these...

Ah dang looks like the jpeg decoder is having some issues as well, I'll take a look later this week

The last issue seems to be a weird problem with esp-idf's new component manager. It can't decide the right libsodium to pull in from the component list when using the...

Just pushed a small tweak to the display_ops functions after testing on-device - it should have been using the GPIO port number, not the pin number, to get the LL...

Edit: It seems as though this doesn't fix the issue for v4.3, just 4.4. The error seems to point to no support for the `rules` directive in the yaml file,...

I also couldn't find anything on `rules:`. They might not have updated their new idf-component docs to include it yet 🤷 . Here is where it was mentioned: https://github.com/espressif/esp-idf/issues/9309#issuecomment-1182083341

Re-ran CI since espressif pushed a new release_v4.3 docker image 2 days ago and the 4.3 mpd_status build is now passing. There's somehow now a bunch of issues with v5...

tl;dr espressif deprecated the esp_adc_cal component in 5.X and has a new interface for instantiating and reading values (this is what happened with the RMT periph, it was just easier...