4 ms·
If it was possible to drive a touch interface and SPI display of that size from an MCU of that size/speed and still be responsive. I have only driven them from
by jrexilius 4y ago
If it was possible to drive a touch interface and SPI display of that size from an MCU of that size/speed and still be responsive. I have only driven them from Pi Zeros, PocketBeagles and other much larger/faster systems, and still noticed some drag. Up to now, I've stuck to smaller displays without a touch layer for projects where I'm using the RP2040. [caveat: I am _not_ an embedded systems SWE so still figuring out where limitations are hardware vs. my knowledge]
- dmitrygr 4y agoNow you can use that display too :) As the driver uses no CPU, CPU speed doesn’t matter
- djmips 4y agoImpressive work. I hope the original designers of the RP2040 PIO system are well pleased.
- ta988 4y agoI hope they are. I also hope their next generation will have more PIOs and ideally a bit more instructions.
- dmitrygr 4y agoI only have one wish for PIOv2 in future chips: wire it up to the AHBlite bus as a target, behind a small cache, so i can make my own QSPI iface (or 8xSPI, or 16xSPI, or SDRAM, etc)
- HeyLaughingBoy 4y agoI mentioned upthread that I bought an ESP32-based DLC-32 3D printer/laser controller board. It uses a 2.4" TFT SPI display. Admittedly, I didn't use it for very long before reflashing it with my own test code, but the display seemed pretty responsive. I've been doing a lot of work with TFT_eSPI recently, but only on the display side (not using touch input) using the LVGL framework and it is very nice and smooth.