Getting started with Riverdi EVE FT813 & STM32H755 with TouchGFX

[bramble]

Hi Community,

I have a project on STM32H755 Nucleo using a simple small LCD. Now I want to add a Riverdi display, RVT50AQFFWC00, which uses the FT813 EVE.

I'm not very clear how best to start. From what I've found it seems that there's no driver for this display in the BSP for H755 and the best-looking driver that I've come across is Rudolph Riedel's (https://github.com/RudolphRiedel/FT800-FT813).

Should I start by adding TouchGFX to my project via Middleware config in CubeIDE, drop Rudoph's driver into the project, then go to TouchGFX?  But then how to proceed, since I only see options in TouchGFX to use some pre-defined configurations that include H755 and similar displays, but there isn't one matching my exact configuration? If I use the simulator that's OK, but then how do I run on my target?

Maybe I should instead start in TouchGFX and perhaps that allows me to pull the required driver in to my project and update my project with it?

These probably seem like silly questions but any advice would be great.

If anyone has a project using TouchGFX and FT813 on H755 Nucleo that they can share that would also be a big help.

Thanks!

[GaetanGodart]

Hello @bramble ,

 

You can follow this guide to see how to set up a new project with a specific hardware.

I do not know much about the FT813 but you will indeed need the drivers/library for your specific display.

 

Regards,

[bramble]

Hi @GaetanGodart , thank you very much indeed.

[bramble]

Just to update that, after a little code bashing at the weekend I have the Riverdi EVE display running on my F429 Nucleo, and migrating to the H7 Nucleo will now be easy. I used the official FT813 driver from them and adapted one of their existing demos. Bridgetek also have a pretty nice looking drag-and-drop screen designer tool.

As @GaetanGodart has advised, my choice of lcd and taget STM MCU is not suited to Touch GFX, however I can proceed with what I have.

[GaetanGodart]

Hello @bramble ,

 

TouchGFX supports SPI displays:
https://support.touchgfx.com/docs/development/touchgfx-hal-development/scenarios/scenarios-spihttps://support.touchgfx.com/docs/basic-concepts/framebuffer#framebuffer-strategies

 

TouchGFX support displays with built in frame buffer (aka GRAM):
https://support.touchgfx.com/docs/basic-concepts/framebuffer#framebuffer-strategies
However, you also need an accessible framebuffer to render to, this could be a partial framebuffer if you need to save memory:
https://support.touchgfx.com/docs/development/touchgfx-hal-development/scenarios/scenarios-spi

 

What I think TouchGFX doesn't support is the smart displays (EVE displays) in the sense that TouchGFX manages the rendering and do not want to offload it to the screen (and probably can't).
This is because we have our own graphics hardware enable as NeoChrom and ChromArt which are both graphics accelerators.

Perhaps a better approach would be to get one of the new and affordable chip such as the STM32H7S7 or the STM32U5G9, they both have graphics acceleration which would make up for the "lack" of EVE graphics.

 

Regards,

[bramble]

Hi @GaetanGodart ,

Ah thank you for correcting my misunderstanding. I have edited my previous post on this thread to avoid spreading mis-information that may confuse others.

We should really mark your last post as the answer to my original question, so if you can edit it do that please do. I don't know how to change the accepted answer.