How to learn STM32 programming?

[Amelie ACKERMANN]

I'm new to ST family and right now I am working with avr controllers, but I want to move from there and want to learn STM32 programming. How can I learn this?

[Tesla DeLorean]

People learn and absorb information differently, what methods work for you? Have you ever done a "Learn how to learn" class?

I've always found reviewing the Reference and Data Manuals provides some level of scale or scope to the problem. Reviewing different perspectives of different authors.

Problem here probably two fold, you'd need to understand how a more complicated MCU functions, and the peripherals that are layered on top.

Pick your battles, start with things that you're familiar with, and those of most interest. Experiment with those.

[Roman LUDIN]

Thank you for your question. We provide wide range of MOOC courses free of charge. The best for you are following https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/STM32CubeIDE_basics_MOOC.html and https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/stm32cubemx-and-cubeHhal-basics.html . For sure you can search other online courses focusing to your needs and interests. In case of any troubles during developing you can reach our community https://www.st.com/content/st_com/en/stm32-mcu-developer-zone.html

[RomainR.]

Hi @Amelie ACKERMANN 

I think that to learn and have good knowledge, you have to approach subjects head on.
This is not necessarily just for programming an STM32 but also applicable on a larger scale.
Always start an unknown domain with something basic or elementary. Try the STM32 code examples, try several methods, some times it works and other times it doesn't. So you have to be persistent.

A good starting point is https://wiki.st.com/stm32mcu/wiki/Microcontroller.
Then always refer to our official documentation as Reference Manual, Data sheet and Errata Sheet.
When we are stuck we tend to cry out for help to anyone who will listen and justify that what is written in documentation or example code does not work.

Also, there are many good and less good resources, you have to know how to sort the useful from the non-useful. It is better to have a small collection of very good books (like programming language, electrical engineering, etc.) rather than waste your time on Google or a famous AI Bot.

Then you just have to apply the methodology, analyze and measure. But keep in mind what exactly you want to do and what you can do.
This is how I always do it.

With regards,
Romain