Comment

bvoigtlaender@feddit.org ⁨9⁩ ⁨hours⁩ ago

Thank you for your input. That does sound reasonable, currently i am closing and opening for each pixel i am setting. However the example code mine is based on also implemented away to set the cursor on an area. And i can then probably just provide more bytes than just two here. I will try this out later!

I don’t think mine is AVR based. It is the architecture of the CPU right? The datasheet says it has two Harvard Architecture Xtensa LX7 CPUs

source

Sort:hotnew top

nickwitha_k@lemmy.sdf.org ⁨1⁩ ⁨hour⁩ ago
You’re welcome!

However the example code mine is based on also implemented away to set the cursor on an area. And i can then probably just provide more bytes than just two here. I will try this out later!

That sounds like it could help.

I don’t think mine is AVR based. It is the architecture of the CPU right? The datasheet says it has two Harvard Architecture Xtensa LX7 CPUs

Ok. That means that you definitely should be able to get more performance out of an SPI display. If you’re able to access both cores, you could likely improve performance by dedicating one to communicating with the display, which, if the display supports it, may be able to effectively eliminate the connection setup/teardown as a factor.

source