Good Morning... I have not tried the T4 with the display for awhile... When I last did it, I did not have it in Paul's breakout board as I don't think the SPI pins all came out in normal places. So I did it using breadboard. The current stuff with the Pacman I have running with the T3.6 beta board and you might have noticed in the picture.
At some point I am thinking of hacking up a version of ili9341_t3? that works on T4 with or without hardware CS pin on DC... Not sure yet if to build it into my own _t3n or a version of _t3?
More a discussion for the T4 thread, but thinking of making it always have a frame buffer. Then have it maybe run in three different ways:
a) Explicit say update screen now
b) Always update - Once started it just keeps on running...
c) like b) but maybe only when the user calls some graphic primitive.... That is for example you call fillRect, it will set a dirty bit and when the fill rect is done in memory it will if necessary start the DMA operation. When the DMA completes, if nothing dirty it turns off... (maybe it runs an extra screen refresh?)
I see positive things for all three methods. a) gives the app developer the most control over things, b) probably gives you the fastest screen refreshes (most frames per second), c) may be an interesting compromise, for apps that don't have things on the screen constantly updating... Note: maybe have compile option (#define) to allow apps who need the fastest stuff to compile out the c) stuff.
What I sometimes wonder about DMA operations is, suppose I am constantly outputting DMA at something like 30mhz, what does it do to the performance of other things. (Yes I know that DMA runs by itself, but what does it do to memory access for other things, like maybe manipulating other images in memory or doing output UARTS or ...
But sorry I know that this is off topic. Right now in between playing with Annie, I thought I would update the keyPadLoop code in Packman to maybe know which Joystick we have and be able to process the actual buttons.
Example currently in the code for Start it is looking at:
Code:
if (buttons == 168 ) {
ClearKeys(); //else but_START=false;
but_START = true;
delay(300);
}
I have no idea what joystick would give you that? 0xA8 (3 bits on) for start button? I might either have tables for PS3/PS4... or ?