TouchGfx modifies FMC SRAM lines

[AHugh.3]

Hello, I'm using a STM32L4S9 with TouchGFX and an external SRAM on my custom board with cubeMX. However, I've found that after initialising the FMC lines, MX_TouchGFX_Init modifies the configuration of SRAM_D0 and SRAM_D1 on GPIOD, so that they can't be used.

I'm using a Singlebuffer and the DMA2D accelerator is off (I had to switch the DMA2D accelerator off due to the fact that lockDMAToFrontPorch(true); had no effect when DMA2D is enabled). My only work around at the moment is to re-initialise the FMC lines manually again after the touchgfx is initialised.

Is this a known issue?

[AHugh.3]

Apologies, it's SRAM_D2 (GPIOD.0), SRAM_D3 (GPIOD.1) that are being modified by the call to MX_TouchGFX_Init();

[MM..1]

check your target files, both generated and user.

[AHugh.3]

Thanks. The change comes from the generated file when HAL::initialize(); is called in TouchGFXGeneratedHAL.cpp. It appears to modify the lines during this library call.

[AHugh.3]

Found it thanks!! There's a callback for the touch control initialisation. I had a bug in there. Thanks for the pointer @MM..1​