Just figured out how to make this work with Propeller in Spin
One trick is that you send addresses in big-endian format, but data in little-endian...
Anyway, here's code and photo showing one of the first examples in the programming guide with 7" LCD.

Note: This is work in progress, see end of thread for the latest, like this alpha channel overlay test with rotation and scaling thrown in:

Comments

Wow! I watched FTDI's video. These TFT modules, with their reasonable price points and built-in frame buffers, would seem to obviate any need for a P1 or P2 to be used as a direct video driver. Forget NTSC, VGA, even HDMI. And the graphics are stunning.

-Phil

Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away. -Antoine de Saint-Exupery

Wow! I watched FTDI's video. These TFT modules, with their reasonable price points and built-in frame buffers, would seem to obviate any need for a P1 or P2 to be used as a direct video driver. Forget NTSC, VGA, even HDMI. And the graphics are stunning.

The P1 could struggle, but surely the P2 can compete head on with the FT813 etc ?
The FT813 is not cheap at $6.09/250 ?

Yes, modules have their place, but if the P2 can compete with FT813 series, someone will make modules using that, surely ?
320x240 looks comfortable, but 800x480 is more a challenge for P2, but it could use the display-list approach ?

Nice, I watched some YT videos about this chip as well. In a way, the idea kind of reminds me of 4DGL's Goldelox chips from years ago...like a much more modern/high end version.
J/C - Is that an eval board they make or are you working on something around it?

Ray I’m really glad to see you having good luck with EVE2. I build some boards for this for the NH 7” but haven’t had time to program the machine and test it. Looking forward to trying this out. You can see the EVE2 and FPC40. This was on a P1 + P1V Max10 combo board that mounts on the back of the NH7 cap. Prettyy much the same schematic for EVE2 as their eval.

kuroneko gave me code to fix SPI_ASM for 32-bits and now it flies.
I put the display update in a loop animate the gauge and it moves very fast now with SPI_ASM.
Maybe I don't have to make a custom driver after all...

Rayman,
Well done - keep it coming! I love your interface development commentary and code examples on this emerging hardware.
This display seems to have a lot of potential for Prop projects.
I wish there was more of these sort of threads on the forum!

thanks.
Looks like Eagle -> KiCad import has the nets all correctly tagged, but in some cases the tag-name is moved (sometimes jumps to another corner) or rotated from the original.
Small net tags are added, eg to Prop Xtal N$4 N$5 I think to preserve the net names (packages usually have varying auto/hidden net naming )
Some also look to be redundant.
Not sure I see any real bugs, and those labels may be insurance to ensure a netlist match - which is probably the more important design transfer priority. You want it right, before you want it pretty !
They are easy enough to move/spin to a better cosmetic location.

checking the messages on net-import, I do see one minor effect on the PCB.
On regulator IC5, there are two zones imported on copper layers, and not net tagged.
As a result, the fill is slightly different - to correctly connect to pin4, pin 4 should have a net name, and the traces/vias/zones all match that net name.

If I manually edit Pin4 to match the via's THERMAL net, and tag the fill zones as THERMAL net, set their priority to >GND, and add a trace IC5.4-Via, it all fills/connects as local-copper-cooling.