Problems with white screen for the STM32H745I-DISCO Board

[Fausto_SIlva]

Hello ST members
I've been having a problem with my STM32H745I-DISCO Board after my co-worker was trying to learn how to use and create projects with it.
It was a simple project of using a digital button conected to the board via jumper and a potentiometer. it used sampling from gui to make the conection between the information that came from the model to the view.
He used the option of solve clock issues in cubeMX to configure the analog ports.

After that, the screen was blank, I tried to upload my previously working projects to the board but nothing changed. I tried erasing the flash and external memory via cube programmer, nothing changed.
There were no build problems, and when flashing the project via touchgfx, no problems were announced in the monitor too.
Then, I tried uploading the exemple project from ST called LTDC_Display_2Layers, and it worked perfectly.
After that, I tried uploading the full demo for my board STM32Cube_Demo-STM32H745I-DISCO-V1.0.0_FULL.hex, it also worked perfectly.
After that, I tried flashing again my old projects, but they still wouldnt work.
I am a begginer, so I am not very knowledgeable about this boards. What could the error be?
From what I read, it could be a clock issue or a sdram issue of some kind.
Is there any way I can reset my board to its previous state, so it can work again?

[TDK]

There's not too many nonvolatile settings. Check values of option bytes. If other programs work, hardware is likely fine. Debug your program to see what is going wrong.

[Fausto_SIlva]

I agree that hardware is not the problem. However my projects were not altered, yet they stopped working. So does it still make sense to debug? How can a project become problematic without me altering it?
Even when I generate automatically a project in touchgfx, and I add absolutly nothing, the same problem still happens.
Some of the option bytes were wrong aparently. so maybe it is these nonvolatile settings right?
How many of those are there and where can Iearn more about it?
Also I will try to debug anyway just to see if i can gather more information 

[TDK]

I suggest debugging the program as-is rather than trying to rationalize that it should be working but isn't. Stay objective. You can load other programs so the hardware is fine. The chip doesn't know or care what was loading last week, it only knows what is going on now, so focus on that. Something changed.