My touchgfx screen is glitched and project broke after touchgfx update (4.23.0 -> 4.24.2)

[Florian37]

Hi,

 

I'm currently developping an application that need a tactile screen to run, i'm using the STM32F746G-Discovery board, and the project was in a finished state by June 2023. I re-used it now, and I saw that when flashing my old code into new board, the screen was all glitchy (a complete pixel non-sense of all color without any special logic). From the debugger, the program is crashed and called a Hardfault callback. The stack trace indicate clearly that it comes from the touchgfx part.

I tried then to create a blank touchgfx project in the version of my old project (4.23.0) and to flash it, the bug occur. And when I create a project from the 4.24.2 version (the last one then) it work as intended. So I concluded that this was just an update problem, but when I do the full touchgfx update procedure according to the guides, the problem still persist. I do the following :

- Open my old project in TouchGFX Designer 4.24.2 to update it, generate code through it
- Go to STM32Cube ioc file, migrate to the newer version of touchgfx through the component selector
- Generate code
- Compile and run

And then nothing changes, someone may get an idea on what am i doing wrong ?

I would like to precise that this exact problem happens to all my old projects (I have 3 touchgfx exemples of that), the only thing that changed is the st-link firmware forced upgrade I guess, since I didn't touched anything else. The whole thing seems realy weird to me. I also already tried to upgrade to the 4.24.0 first just in case.

 

Thanks to you all in advance for your help,

Best regards !

[GaetanGodart]

Hello @Florian37 ,

 

I noticed that you mention using a new board. You also say that creating a new project from TouchGFX Designer 4.24.2 works fine.
Can you check which version is that board and which version was the previous one.
There was a major change in the board revision CU4 and later uses a new memory.

If that is your case, the simplest way to fix it is to create a new project and then clicking on "Edit" => "Import" => "GUI".

If you have a complex project where there is code outside of the TouchGFX scope, either you have to manually add it or I could maybe provide you with the git commit change that switch from the old memory to the new one.

 

Regards,

[Florian37]

Hello @GaetanGodart , 

I really appreciate your help; you are absolutely right: old boards used CU2 revision, while the actual ones are on CU4. Sadly, the code is mostly external, so I would be glad to see this Git commit change. The GUI part never had bothered me, I used to copy the components directly from a .touchgfx file to another.

I saw a post with someone that has the exact same screen problem as mine where you already responded, here (https://community.st.com/t5/stm32-mcus-touchgfx-and-gui/stm32f746g-discovery-what-is-the-difference-between-cu3-and-cu4/td-p/744612) and it seems correlated. 

 

I can totally re-migrate projects for the new CU4 manually; I just hope I won't have to do it every time in the future.

 

Thanks for your reactiveness!

Best regards,

Florian

[GaetanGodart]

Hello @Florian37 ,

 

Perhaps the attached patch file would allow you to fix the issue without having to re-migrate everything.
To apply it do "git apply patchName.patch" (you need to use git I guess).

 

Regards,