Where are you initing the tcpip adapter and WiFi?

No, it says the RTC I2C pins are 21-24 (gpio 0,2,4,15). The main I2C peripheral goes through the gpio matrix so has no default pins and you are free to choose. Don't confuse qfn package pin # with gpio #. ESP32 has so many features it gets confusing, but that's great!

Rev1 not really available yet, only hint is some products quoting mid may.

Hi To my understand on rev_0 hardware the APLL resolution is not good enough for generating a 2.8224 Mhz i2s clock due to bug on sdm1 and sdm0. Yes sounds right, my only question was in the meantime could you use APLL to get a better starting freq for I2S clock divider to achieve a marginal improve...

I2S_CLKA_ENA Set this bit to enable clk_apll. (R/W)

https://github.com/espressif/esp-idf/bl ... i2s.c#L161

To be more specific all the I2C references are related to the internal control bus, not i2c peripheral.

https://github.com/espressif/esp-idf/bl ... _clk.h#L29

It depends on what driver you are using. Maybe you want to check https://github.com/search?q=esp32+ili93 ... positories

That is because gpio_set_pull_mode sets the pull-ups and -downsa in the digital domain, which gets powered down when the CPU enters deep sleep, leaving your pin floating. If you do not pull it up or down externally, it'll just be flapping in the breeze, picking up charge from whatever stray EMF it ...

Gpio# are labeled. Once you have that you tell the spi driver what pins you want and it uses gpio MUX/matrix to move spi functions to those pins. Other considerations are input only pins 34-39, flash pins 6-11, and strapping pins. Check pin list document.