TouchGFX engineers chose not to show header files. You can just import them into their respective folder or your own created folder, as a file system, but link to them only. The Project file structure does not have to follow the Windows file structure. That's why the Core folder has 2 actual files and the rest of the files are linked files. They are 2 Core folders shown as 1.

@@EEbyKarl I appreciate the quick response. I am used to the file structure created when starting a project from Stm32CubeIDE so this really through me off.

Did u find prob with #include "PollingRoutine.h"

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?

With VHB?

use osSemaphoreRelease and osSemaphoreAcquire

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

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

Long press to do what?

@@EEbyKarl well, like shut down system, or when you're going to turn on/off the LED for the simple application

@@Red_Fang. well instead of debouncing for 20ms you can do 2000ms which is 2 seconds which will call your shut down function TimerCallbackTimerStart(&timerCallback, ShutDownFunction, 2000, TIMER_NO_REPEAT);// one shot

Try using snprintfloat. support.touchgfx.com/4.20/docs/api/classes/classtouchgfx_1_1_unicode

You're welcome!

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.

@@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!!!🤩

You're welcome!

I have no idea. I never had a situation where the touch screen didn't work so I've never had to troubleshoot something that's not broken

@@EEbyKarl ok,i will make a video and then share with you,can you also make a video in which after reset it will work ?

You're welcome!

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

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

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.

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

Haha! Good comeback. 😆

* HAL