> there any underlying firmware changes in the v7 firmware that wouldn't work on a WROVER chip with the same memory specs?
The v7 Firmware uses LCD Module internally instead of I2S as it did in the ESP32 WRover version. So you definitely can’t mix one with the other.
But this is resolved and there are precompiler conditionals that will adapt to one target or the other.
There are many things that change if you take a deep dive. Sending the pixels is different, the hor. sync and vsync is different, they are two different ways to send the framebuffer. Depending on the target you need to use one method or the other.
V7 using S3 is also faster than ESP32 WRover
The v7 Firmware uses LCD Module internally instead of I2S as it did in the ESP32 WRover version. So you definitely can’t mix one with the other. But this is resolved and there are precompiler conditionals that will adapt to one target or the other. There are many things that change if you take a deep dive. Sending the pixels is different, the hor. sync and vsync is different, they are two different ways to send the framebuffer. Depending on the target you need to use one method or the other. V7 using S3 is also faster than ESP32 WRover
Originally posted by @martinberlin in https://github.com/vroland/epdiy/issues/274#issuecomment-1878163877