I think you'll be better off troubleshooting QSPI issues elsewhere in the forum.I can say that my experience is that dummy cycles do matter quite a lot, but you will usually lose the first pixels, not the last ones. In you case the buttons are quite ...

That was indeed what I meant regarding the __DSB() statement.Looking at the picture in your original post, it seems that the errors span the text in the cancel button, but the error is not present in the pixels that belong to the text. To me, that in...

This was indeed what I meant.I dno't know what to chase here. You write in your original post that you have verified the errors are in the frame buffer. Have you verified this by dumping memory, or what do you mean by that statement?In that case, loo...

Hello,I have a new suggestion, that I think you should try first.At the time that void TouchGFXHAL::flushFrameBuffer is called, the rendering is done, but DMA2D may still be transferring asset data from external flash to the frame buffer. To handle t...

How do you access the qspi in your application? If it's memory mapped which i guess based on your touchGFXHAL.cpp, I can only think of configuration being on the edge or something like dummy cycles being wrong, although I would think that would be co...