Skip to main content
Associate III
October 27, 2025
Solved

Hard Fault Error relating to TouchGFX text rendering.

  • October 27, 2025
  • 3 replies
  • 220 views

I am using STM32F469I-DISCO interfaced to a custom display operating in DSI-Video Burst mode.

I'm using TouchGFX, all compiles ok, however I am getting a HardFault_Handler error relating to TouchGFX::TextProvider as follows.

 

RobNewbury_2-1761598393827.png

The memory is organised as follows.

RobNewbury_0-1761598271886.png

I think the fault may relate to text object(s) with related wildcards that have been deleted from within TouchGFX designer.

 

I am using TOUCHGFX V4.26.0 but had the same problem with V4.25.0

 

Best answer by RobNewbury

It turns out that rendering any text results in a Hard Fault.

I'm using QSPI as external flash, I hadn't included an external loader in the debugger. I am using the STM32F469I-DISCO so I added MT25QL128A_STM32F469I-DK.stdlr to the external loaders section of the project debug configuration. This solved the problem.

RobNewbury_0-1761773543606.png

@mathiasmarkussen Thanks for your input on this.

3 replies

ST Employee
October 28, 2025

Hello,

Do you currently show any text on the screen? Do they use wildcards?

Do you have any texts that are not in use in the Texts tab in TouchGFX Designer?

Associate III
October 28, 2025

Hi @mathiasmarkussen ,

Do you currently show any text on the screen? Do they use wildcards? - Yes & No.

Do you have any texts that are not in use in the Texts tab in TouchGFX Designer? - Yes

I guess I should delete the unused texts?

 

ST Employee
October 28, 2025

Yes, delete the unused texts and see if that fixes your issue.

ST Employee
October 28, 2025

You could check that in you .map file - also check where Texts.o ends up being linked.

Associate III
October 28, 2025

@mathiasmarkussen 

I'm not overly familiar with reading .map files, but it looks like Texts.o is linked to 0x0802e90c

RobNewbury_1-1761662355513.png

 

There is no reference in the .map file to any addresses in the region of 0x8fa51e18

RobNewburyAuthorBest answer
Associate III
October 29, 2025

It turns out that rendering any text results in a Hard Fault.

I'm using QSPI as external flash, I hadn't included an external loader in the debugger. I am using the STM32F469I-DISCO so I added MT25QL128A_STM32F469I-DK.stdlr to the external loaders section of the project debug configuration. This solved the problem.

RobNewbury_0-1761773543606.png

@mathiasmarkussen Thanks for your input on this.