STM32G030C8 and Cube MX bugs/errors, DMA/MUX on G0xx devices.

[GBral.1]

1: Is it so that DMA/MUX on all STM32G0xx devices cant access GPIO?

2: Cube MX cant enable 64Mhz on the clock config (max 48Mhz) a bug?

3:TIM15 can be enbled by CubeMX G030Cx but is not on G030Cx devices, bug in CubeMX? 

[TDK]

> 1: Is it so that DMA/MUX on all STM32G0xx devices cant access GPIO?

Correct, DMA doesn't have a connection to GPIO in this family. See "Figure 1. System architecture" in the reference manual.

> 2: Cube MX cant enable 64Mhz on the clock config (max 48Mhz) a bug?

Works fine for me.

> 3:TIM15 can be enbled by CubeMX G030Cx but is not on G030Cx devices, bug in CubeMX?

I don't see a TIM15 for this chip.

Maybe update your software and make sure your project is using the chip you think it is.

[GBral.1]

Thanks TDK!

But according to datasheet page 20 and reference manual page 220 STM32G030/G070 have a DMAMUX

who can do DMA between GPIO both as I/O triggers and memory to GPIO I/O. AN5224 covers DMAMUX. A atraining presentation paper called STM32G0-DMAMUX

includes mapping and examples.

Have the latest Cube MX 5.6.1 , it shows TIM15 but PLL have only div/mul stage

and 3 way mux and not as in your picture. However if i switch over to a G030K/071C

then i can set 64Mhz core clock and TIM15 vanish and can set the DMAMUX .

So something is weird with Cube MX and as usually with ST data sheets needs revisions, e.g picture on cpu says 56Mhz!

[rromano001]

Hi

CubeMX 5.6.1

STMCudeIDE 1.3.1 (CubeIDE 1.3.0 was not working properly.)

None of issue mentioned, work fine no trouble on DMAMux, PLL too.

DMAMux can generate an alternate DMA service with selectable channel out of 5/remaning.

Then about best answer: Your answer resemble what TDK wrote.

[GBral.1]

TDK did his best but wrote the opposite ,and factually incorrect, of what i wrote

so best answer is not an issue!

[Amel NASRI]

Hi @GBral.1​ ,

I selected STM32G030C8Tx on STM32CubeMX and try to check what is the issue, but didn't catch it, sorry.

Could you please explain more what is wrong from your point of view on documentation and STM32CubeMX?

Thanks.

-Amel

[GBral.1]

Sorry but there is no more then explained in previous posts!