cancel
Showing results for 
Search instead for 
Did you mean: 

TouchGFX App runs with debugger connected, won't run stand-alone?

KMill
Senior

I'm working on my first TouchGFX app on an STM32F746G-DISCOVERY board.

The app builds, loads and runs fine using STm32CubeIDE. I can test my app and all looks good.

However if I power-down and back up, the UI loads on the screen, but nothing is working. It does not respond to any touches.

Am I missing something?

13 REPLIES 13
WDunc.1
Associate

I also have the STM32F746-Discovery board, revision C. [DK32F746$CU2]. I am using TouchGFX v 4.21.0 and the STLink Firware is V2J40M27. I am having the same issue with the touch screen part. It would be great to have it fixed in future revisions of TouchGFX.

I have used the method of using the CubeMXProgrammer , pressing the RUN button on the CPU tab. (I don't seem to need the RESET button to get the touch portion to work, just the RUN button). I also tried rolling back the TouchGFX to 4.20.0, and got the same results. It was nice to find this work around. I spent about 4 hours fiddling with this prior.

The problem and temp solution is noted here: https://community.st.com/s/question/0D53W00001wnohnSAA/touchgfx-generated-project-is-not-worked-on-stm32f746gdiscoc01only-the-touch-screen-doesnt-work

and here:https://community.st.com/s/question/0D53W00001XM98mSAD/touchgfx-generated-project-is-not-worked-on-stm32f746gdiscoc01

KMill
Senior

Thanks @WDunc.1​ and @Osman SOYKURT​ 

Looks like we have enough evidence that this is an issue on some boards. ;)

I'm guessing it's just a minor thing, but it would be great if ST could analyze it and find the actual cause. I can live with adding the delay, but it is kinda just a workaround.

thank you so much for your response .i am also facing same issue and i have searched on youtube but noting found.your answer is my solution.now my code is working after reset .thank you so much

MPicc
Associate II

I am facing the same issue and now have resolution by adding the HAL_Delay(100); prior to MX_I2C3_Init(void);. Great work all saved me much frustration and effort!