Stm32f7 corrupted screen

[tejo]

Hi everyone,

I've been using TouchGFX v25 for almost a month and successfully flashing it to my STM32F7 board. I create projects in Designer, then open CubeIDE to edit the code, build, and flash. Everything was working fine.

Recently, I tried installing the STM32Cube extension for VSCode. I was able to build the project, but couldn't get it to run. After that, when I tried running it again using CubeIDE, the screen became corrupted. I can still flash old projects and create new ones, but the top part of the screen consistently shows the same issue.

As a first step, I deleted VSCode and erased the flash using STM32 Programmer.

Then I uninstalled and reinstalled all components: STM32CubeMX, STM32 Programmer, CubeIDE, and TouchGFX. I also updated TouchGFX to v26.
After that, I deleted the IDE workspace and removed the folders:

C:\Users\myuser\.stm32cubemx

and C:\Users\myuser\.stm32cubeide

Then I’ve compared ioc files before and after using my backup on GitHub. They show differences in terms of pin assignments. I’ve replaced ioc file by the backup file, I’ve observed that pins changed on ioc view inside CubeIDE but the situation remains.

Any idea what may be causing this? What steps should I take?

I share with you the old project that worked fine  and the new one with problems.

OLD

https://github.com/TejoTago/stm32-touchgfx-tutorials/tree/main/myBarCharts

https://www.youtube.com/watch?v=MS1xix1E5KU

NEW

https://github.com/TejoTago/corruptedScreen/tree/main/myBarCharts

https://youtu.be/Qp1TC60dG28?si=7JRHb8jhkbpN6pqQ

Thanks in advance for all you support.

Kind regards,

Jota

[tejo]

Just to add that I used generated configurations from TouchGFX Designer. Never edited ioc in the past.

Now I've tried to change from 24 bits to 16bits but the problem remains.

I also added a button in that part of the corrupted screen and it responds to touch.

https://www.youtube.com/watch?v=xtBsHELLcJ0

Thanks.

[mathiasmarkussen]

How are you flashing your board? The issue could be that you have flashed your background image to external flash previously, it has become corrupted later on, and you are only flashing the internal flash.

Using the run target button in TouchGFX designer will flash both internal and external memory:

You can also verify if the issue is with the screen or the asset by placing a box:

At the top of your display, and seeing if the area covered by the box is corrupted. You can make the box draggable in the panel on the right if you want to see what happens if you move it around.

[tejo]

Hi Mathias,

Thanks for taking the time.

I created a new project with two draggable boxes and ran it. The error persisted.

Then I updated the ST-Link via CubeIDE and STMProgrammer from version 32 to 33 without success. I forced the update by downloading the ST-Link package and running STLinkUpgrade. It updated to version 33. I ran the code again, and now the screen is even more corrupted — there's an additional lines across the middle of the display.

I don't understand what is happening.

[mathiasmarkussen]

Can you try to build one of the supplied demos or examples directly in Designer?

What is your framebuffer location strategy set to?