Skip to main content
franck23
Associate III
January 20, 2021
Solved

Do Not Generate Function Call option for MX_TouchGFX_Init not working

  • January 20, 2021
  • 12 replies
  • 3586 views

Hi,

In CubeMx, Project Manager tab -> Advanced Settings, the "Do Not Generate Function Call" for MX_TouchGFX_Init is not working.

After selecting it and generating the code, the MX_TouchGFX_Init() is still present in the main.c and going back to the Advanced Settings, the previously selected check box got deselected.

This is a problem because when using the QuadSpi with TouchGFx, it needs to be mapped before TouchGFX initialization.

The mapping cannot be made in the MX_QUADSPI_Init because there is no USER CODE section at the end of this function (Hey ST, what about having a user code section at the end of EVERY HAL init function???).

Settings:

MCU: STM32H743

CubeMx: 6.1.1

CubeIDE: 1.5.1

Firmware Package: FW_H7 1.8.0

This topic has been closed for replies.
Best answer by Romain DIELEMAN

So I did a bit more testing and this issue seems to happen for all functions from additional X-Cube packages (like X-Cube-TouchGFX, X-CubeBLE, X-CubeNFC4, ...).

I created an internal ticket to investigate and fix this, thank you for reporting this.

12 replies

franck23
franck23Author
Associate III
February 3, 2021

Maybe not a bug, but definitely an annoying oversight :(.

I don't see any valid reason for ST to populate the Mx functions differently depending on their location.

It looks like they have 2 sets of functions, which is a bit scary for maintenance!