STM32G4 SPI: wrongly set LL_DMAMUX_SetSyncRequestNb after LL_DMAMUX_EnableSync

[DR1001]

STM32G491

Code generator generate wrong order of calls for SPI initialization for LL driver: LL_DMAMUX_SetSyncRequestNb  calls after LL_DMAMUX_EnableSync

[Souhaib MAZHOUD]

Hello @DR1001 

Thank you for posting!

Could you please add an ioc for further investigation?

KR, Souhaib

[DR1001]

Please find atached the ioc-file

[TDK]

I think you forgot to attach the IOC file. I don't see one.

[DR1001]

Hello,
Ok, I attached it to e-mail - but is seems like e-mail attaches do not pass the filters...

Please find attached...

[Souhaib MAZHOUD]

Hello @DR1001 

The initialization sequence generated by STM32CubeMX for DMAMUX synchronization is functionally correct and safe. LL_DMAMUX_SetSyncRequestNb() only programs a configuration field and does not rely on synchronization being enabled beforehand. In a typical startup sequence, the DMA channel is not yet active and no meaningful sync events are processed while these registers are being configured, so the exact order of these two calls has no impact on runtime behavior.

[DR1001]

Hello,

According to the documentation:

[Souhaib MAZHOUD]

Hello @DR1001 

Thank you for your valuable contribution,
This issue has been raised internally to the dedicated team for review. (Ticket #0061235 This is an internal tracking number and is not accessible or usable by customers) 

KR, Souhaib