2026-04-13 12:30 PM - last edited on 2026-04-22 3:02 AM by KDJEM.1
My STM32H745I-DISCO touch screen stopped working after a HardFault/debugger crash while running a test app generated by STM32CubeMX ("Create project from board"). The display works perfectly but touch is completely unresponsive.
Steps already taken:
Display works, buttons visible, but no touch response at all.
2026-04-15 1:44 AM
Hello,
@lmmv_ml wrote:
My STM32H745I-DISCO touch screen stopped working after a HardFault/debugger crash
What does that mean? do you suspect the Hardfault broke the touchscreen module?
2026-04-15 2:26 AM
I am too new to this (embedded with STM32) to make any such assumption.
I just know:
* all was working on the board when I got it (demo, touch screen and all 3 samples apps
* ran a generated code app (generated by STM32CodeMX) in a Visual Studio Code STM32 setup which did not seem to work properly
* stopped the generated code app
* noticed issues with board (leds staying on when board stopped, etc)
* flashed the demo software back on the board
* screen does show the 3 samples apps
* touch screen not working (I do not have a mouse (with the right connector) that I can connect to validate if it does work with a mouse - as was suggested by some AI).
STM32CodeMX version: 6.17
board: STM32H745I-disco
Thank you for any help
2026-04-15 2:28 AM
in my previous:
"...* noticed issues with board (leds staying on when board stopped, etc)..."
should read:
"...* noticed issues with board (leds staying on when the generated app stopped, etc)..."
2026-04-15 2:51 AM
The issue is not quiet clear but since you are facing a Hardfault, the program is stopped, the screen displays something but all is frozen that's why you have the impression the touchscreen is unresponsive.
Read How to debug a HardFault on an Arm® Cortex®-M STM32
2026-04-15 4:10 AM
Thank you, looking at that.