The Nano ESP32-S3 is generally faster at everything compared to the Pico2, but updating the display should take the same amount of time. The SPI bus of that display should handle at least 20MHz, but likely it can do 40MHz and beyond. Both MCUs can push the pixels at the same speed.
Interesting, have you taken a look what's going on on the wire?
The ESP32 has a slight theoretical edge (max 80MHz SPI rate) over the rp2350 (62ishMHz) but I'd have thought the display would be the bottleneck, as most have lower max transfer rates.
Can you point me to the display update code? Maybe it's doing something wasteful like setting the address window repeatedly and writing it one line at a time.
Yeah, I'm using that to keep the code simple for beginners. Would the performance difference between the ESP32 and RP2350 be large enough to account for the 20ms difference when dumping the frame buffer over SPI?
yup. noticed that a while back. I was using the esp32 for project with a custom driver. the esp32 SPI bus is way faster . I was getting about 15ms/frame on the esp but it was 25ms on the rp2040 using the exact same code. BTW. try setting the esp freq higher than spec and see what happens
Of course, I can speed drawing up by making a paddle sprite and a ball sprite, and selectively updating parts of the display, but that's a lot more work. 😂
Comments
The ESP32 has a slight theoretical edge (max 80MHz SPI rate) over the rp2350 (62ishMHz) but I'd have thought the display would be the bottleneck, as most have lower max transfer rates.
Anyway, I wonder what the source of the 20ms is?