Hard Fault Error relating to TouchGFX text rendering.

[RobNewbury]

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.

The memory is organised as follows.

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

[mathiasmarkussen]

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?

[RobNewbury]

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?

[mathiasmarkussen]

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

[RobNewbury]

@mathiasmarkussen Ok, I've deleted the unused texts, but get the same error. The break address in the HardFault_Handler has changed from 0x8e1397fc to 0x8fa51e18. 
May be this is a clue as there is no memory at that address?

[mathiasmarkussen]

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

[RobNewbury]

@mathiasmarkussen 

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

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

[RobNewbury · Accepted solution]

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.

@mathiasmarkussen Thanks for your input on this.