STM32F429I-DISCO & TouchGFX Setup

It seems that some people are having trouble exporting a STM32F429I-DISCO project from TouchGFX and importing it into STM32CUBE-IDE. So in this video I will show you how to export the project from TouchGFX, rename the project to a useful name then import it into STM32CUBE-IDE. I will also show you how to link to the IOC file so you can open it up in STM32CUBE-IDE.
In this tutorial I am using
TouchGFX v4.20
STM32CUBE-IDE v1.10.1
STM32F429I-DISCO
Also works for the newer STM32F429I-DISC1 amzn.to/3VFjuL1
Note 1: I accidentally mentioned STM32F469I-DISCO in the video but it is the STM32F429I-DISCO I am working with.
Note 2: You'll also have to rename the text within the two files in TouchGFX folder with the extensions *.touchgfx. Otherwise the TouchGFX project will give an error when generating code.

[@casualnoises2808]

Great tutorial Karl!!! It got me started on my discovery board real fast, thank you!!!

[@EEbyKarl]

You're welcome! Glad the video helped you out.

[@TheKoba30]

Great have you back.

[@svvelanautica2374]

Hello, I like your STM videos! May you eventually do an updated one where you install some GFX example? Thanks

[@mursalaboobacker3593]

Good video sir

[@DjordjeKostic]

Hi, great video, by the way, in TouchGFX Designer, there are 3 buttons. Generate code, build (window pops up to test) and build & run. When you finish designing, you just need to click the build & run, and the code is automatically flashed to the board. No need for this complicated stuff. If I understanded this right, this is the same you did. Regards.

[@EEbyKarl]

Yes i know you can program the development directly from TouchGFX. But then how do you set up UART, PWM, ADC, I2C from TouchGFX? How do you run the debugger from TouchGFX?

[@Bob-Is-A-PotterNow]

I ran across a note in the STM community "rename STM32CubeIDE project". It seems the process is much simplified. All that needs be done is to open the .project file and on the first line correct the default name supplied by touchgfx designer (which is the board name). Then when importing the project into the STM32Cube-IDE it will be named appropriately AND there won't be a conflict with the board name attached to the ioc file.

[@EEbyKarl]

You're partly correct that you only need to rename the one line. But you can't add the IOC file to the project tree without renaming it to the same name as the project. CubeIDE won't open it because it's not the same name as the project. But I did stumble on an easier way to add the IOC file to the project tree and to rename it. Then I realized that it fixes the issue with TouchGFX not finding the board name unless you rename the text as the project name in the .gfx files. But with your insight it helped me find an easier solution😀. I will have to replace this video soon.

[@Bob-Is-A-PotterNow]

@@EEbyKarl Love your videos! For such a noob as myself, they are very useful and informative. As to the naming of the *.ioc file, yep, after posting my original comment I ran across that. It seems ST's product dev teams, as good as they obviously are, could do a bit better job of communicating how the various apps should communicate and interact. It feels like they are SOOO close to having a fairly seamless integration between the gfx design and the Cube-IDE code & compile aspects of development. Distantly related to all the preceeding: I ran across a new channel (STM32 Research) with only a single video so far (posted about 4 months ago). What I found very, very useful was his approach to using the F429i disc1 board and adding a new (2nd) OLED ssd1306 display by hand. First starting the project as if it's a bare mcu (not a board version), configuring the pins for spi, then adding touchgfx to the project and showing the manual edits to get the display up. I found his workflow very straightforward. I need to try his approach to see if it finally gets me to a nice, orderly and repeatable approach to developing some apps for my own use. Please keep publishing! Your information is so very useful!!!🤩

[@madGambol]

The very first operation is to select something from TouchGFX Designer -- how is that installed?

[@mohaarhly2950]

please help, i want to go back to the factory condition on this board. After i debug it with stm32cube i can only see a white screen. I used a binary factory but the touch screen not responsive ther was a game in factory condition and now nothing work. Please help

[@knightrousoxide]

The video is titled STM32F469I-DISCO but you go on to do everything on a STM32F429I-DISCO. Is this on purpose and the advise universal for the DISCO boards or an error?

[@EEbyKarl]

Sorry, I accidently titled it wrong and even said the wrong part # in the video.

[@Chang-cy1lp]

Hi Karl, I am using STM32F469I-DISCO (DK32F469I$AU1), TouchGFX is version 4.21.1. My app is just a box with a button on it. Code generation and flashing onto the board show no error in TouchGFX, so is building app in STM32CubeIDE (with firmware version FW_F4 V1.27.1) but it just gives blank screen. Tried a few examples and demos on the board too, none worked. I have another made in China board, i can created TouchGFX app and runs fine, but this STMF469I-DISCO just drives me nuts, just could not get it run even a simple app. Any clue ?

[@embedded_eng]

Almost 6 months later, I have exactly the same error and it seems Stm32Ide is resulting for this bug and it is buggy anyway.

[@mursalaboobacker3593]

Waiting for feature videos on touchgfx

[@maikengelbrecht8259]

Can you Debuging with VSCode? Can you MAKE A VIDEO 😊

[@randomtuber5358]

Nice video.I followed your video for stm32f469i disco but it doesn't work.I tried many times but the screen remain black.can you make a video for stm32f469i disco.thanks in advance

[@luisdc1855]

Did you manage to solve your problem? I've been looking for a solution for hours but can't find anything

[@randomtuber5358]

@@luisdc1855 I didn't find solution yet on Touchgfx .

[@EEbyKarl]

For anyone who are running into the black screen issue. The latest TouchGFX fixes the issue due to the different LCD with revision B-07 they are using. When starting a new project just select the correct development board.