Are there any ST 32F417 / Cube IDE / STLINK / C developers on here?

You can pm me if you like on mkATmkescdotcodotuk and we can talk about it.

MK

This is near second nature though the ST Cube hal libraries try to be all things for all men and so have a number of flaws.

Nothing wrong with arrays!

If you still want help please feel free to use the contact form on the website below.

Nothing wrong with pointers either.

ADC1->XXX, USART1->XXX and GPIOA->XXX are all pointers. How can you avoid pointers?

Not only are they pointers, but they are compile time constant value pointers so the compiler can convert the accesses to direct memory references.

I'm not saying you can't. The STM32Cube suite removes some of the need to understand pointers as everything is done through libraries. A good example is GPIO access: HAL_GPIO_WritePin(Port, Pin, value);

The HAL libraries are weak in some areas. By example it won't natively implement a fast SPI slave.

I let Cube do the original initialization from the graphical interface but after that, it's all plain old C. I prefer to understand the processor and maybe make the firmware run as fast as possible.

I'm not that great of a C programmer.

boB

Also, the ADC with DMA does a pretty good job of sequencing the outputs.