STM Micro Controllers Course

• Introduction to STM 32 controllers
• Pinout Configuration
• Clock Configuration
•  GPIO Configuration
• Issues with STM32 Blue Pill Board
• Configure project and generate source code
• Boot pins and how to use them
• Connecting STM controller with PC
•  Introduction to FTDI board and its functionality
•  FTDI board pin configuration
• Connecting FTDI with STM
•  Intro to Arduino IDE
• Configuring Arduino IDE to Program STM32F103C8T6 Blue Pill
• Installing STM library to IDE
• Adding STM board to IDE
• INTRODUCTION TO STM32CubeProgrammer
• Download and install the CUBE programme
• Build the Project
• Debug the Project
• Declaring GPIO pins  in IDE
• Writing and uploading code in STM
• Blinking the LED
• Interfacing temperature sensor with STM
• Measuring temperature with STM
• Configure 61X2 LCD with STM32
• Intro to PWM
• Generating PWM with STM
• Controlling servo motor with STM32
• Interfacing HC-05 Bluetooth with STM32 Blue Pill
• To use ADC in STM32F103C8T6
•  ADC in STM32 Blue Pill
•  Interfacing DHT11 Humidity and Temperature Sensor with STM32F103C8T4

The STM32 family of 32-bit flash microcontrollers, based on the Arm® Cortex®-M processor,offers microcontroller users unimagined freedom. STM32 is a microcontroller family from ST with a 32-bit ARM Cortex-M0 / M3 / M4 CPU. This architecture has been specially developed for use in microcontrollers and thus largely replaces the previous ARM7-based controllers. The STM32 is available from ST in countless versions with variable peripherals and different housing sizes and shapes. Due to the small chip area of ​​the core, ST is able to offer a 32-bit CPU for less than € 1.The STM32 family offers products that combine very high performance, real-time capability, digital signal processing and low-power, low-voltage operation and connectivity, while ensuring full integration and ease of development.

First of all, the differences between the individual processors are not SOOO big. All have inputs / outputs and in order to be able to control an LED by means of a port pin, the pin must first be parameterized for each processor, regardless of whether it is an STM32 or an AVR or an MSP430 . But with an STM32 you have a few more functions, e.g. switchable pull-up or pull-down resistor and special set / reset registers that other processors do not have, but simplifyprogramming. The main difference to the other processors is that the STM32 houses so manyperipheral modules that you always have to activate them individually with a clock, because this saves a lot of electricity.And let’s be honest, the discussion about which µc is easier to configure is absolute nonsense

. The way is always the same:

• Look at the data sheet to see which registers are required for this function.
• Determine the values   that are entered in the registers.
• Write values   into the register. It made NO DIFFERENCE whether it was an AVR , 
• 8051/2, ARM , 

It’s true, there are differences. The registers have different names, different addresses, and different bit meanings, but everything is in the datasheet. And whether I have an AVR or an ARM in front of me for the first time. I need the steps outlined above in all cases. The interrupt system is also prioritized with an STM32. This can be used to determine which interrupt is processed with priority. The prioritization is also not rocket science. The respective manufacturers supply extensive demo codes and libraries for all processors. Most of them are all written in C, so the C programming language should also be used. Especially if you are pursuing professional intentions. And if you can use an STM32, then switching to an LPC1xxx (NXP) or another manufacturer is no problem at all (*), because they also offer processors with a Cortex-M3 core and you can program them with the same programming environment. This means that you are not necessarily dependent on the manufacturer. (* each manufacturer installs its own peripherals, which have different functionalities.)As a hobby hobbyist and professional, almost all applications can be implemented with an STM32. It has enough RAM and FLASH memory and also enough speed. Many housing variants create small to larger devices. Many interfaces are described in the article STM32. It must be added that these are mostly based on the standard ST-Libs. On the one hand, these libs simplify the control/use of the peripheral functions, and on the other hand, you have to get to know them first. This is simplified because ALL ST demo code examples are also based on these Lib and thus the change within the STM32 is significantly simplified.

“STSW-STM32065 STM32F4 DSP and standard peripherals library” including documentation and demo projects for all CPU functions.

So far there are eleven STM32 families:

• STM32F0
• STM32F1
• STM32F2
• STM32F3
• STM32F4
• STM32F7
• STM32H7
• STM32L0
• STM32L1
• STM32L4
• STM32G0
• STM32G4
• STM32WB
• STM32T – no longer in production
• STM32W – no longer in production

As with many other controllers, the STM32 mainly uses C and C ++. But also Pascal or Basic is possible without any problems (e.g. from mike) You should already know the programming language C, if you have no idea about it then you should first write a console program using a tutorial on a PC so that you get to know it to some extent. There are also articles here in the forum. If the aim is a (later) application in industry, C (or C ++) should definitely be chosen due to its widespread use; most of the available libraries are also written in C.
The assembler should only be understood roughly, details of how an instruction works is unimportant. Even if you want to know the cycles for a function call, the STM32 (Cortex-M3) offers a cycle counter that can be read out; However, due to the more complex pipeline and cache effects, the runtimes cannot be precisely foreseen. If cycle-precise timing is required, timers should be used – the STM32 has enough of that. The 32-bit address space, which can address RAM, Flash, and I / O registers in a standardized way (in contrast to AVR, for example ) is ideal for use by high-level languages; In the case of pointers, there is no need to manage additional information about the type of memory in which they point. The address clearly states this (there is only one address 42, and not 2 for example with the AVR (Flash, RAM & I / O)) and the hardware automatically addresses the correct memory. The options for offset addressing, the barrel shifter, division unit, the FPU (with STM32F4), interrupt model, etc. also favor the generation of more efficient codes. In addition, the STM32 simply has more “raw performance”, i.e. more Flash / RAM memory and higher clock frequencies.