Skip to main content
Associate II
April 3, 2024
Solved

CRC_Lock in touchgfx core lib triggers a bus fault

  • April 3, 2024
  • 2 replies
  • 894 views

Hi

I am integrating TouchGFX into own RTOS.

I use a TouchGFX/CubeMX generated project for STM32L4R9-DISCO board.

I have moved initialization code into a driver for my RTOS - it seems to complete without errors.

On touchgfx_init I get a bus fault from this code:

tkorsdal_0-1712168296524.png

As I cannot find anywhere in ARM documentation that 0xe000'2000 should be a valid address, it looks like the code is causing a bus fault deliberately.

The exact same code gets executed in the ToughGFX/CubeMX generated project.

Our RTOS is - of cause - set up to catch bus faults, but bus fault is not triggered/caught in the generated project.

What is going on here - and how can I fix this?

Rgds Tage

This topic has been closed for replies.
Best answer by tkorsdal

Update: Moving the code to execute in handler mode (SVC context) in the driver made the bus fault go away.

2 replies

Joe WILLIAMS
ST Employee
April 4, 2024

Hello tkorsdal

 

Your post was escalated to ST Online Support Team for additional assistance.

 

Kind Regards

Joe WILLIAMS

STMicro Support

tkorsdalAuthorBest answer
Associate II
April 5, 2024

Update: Moving the code to execute in handler mode (SVC context) in the driver made the bus fault go away.