System Clock[SysClk setting details for STM32]

This chapter explains how to create the system clock, which is the operating frequency of MCU based on the clock signal generated by an oscillator such as a crystal resonator, and how to set the clock to be supplied to each peripheral.

As explained in the chapter on "the basics of embedded technology", a clock is a pulse signal that serves as the timing for all circuits, including the CPU of MCU. The clock setting in an embedded device is important to ensure that MCU can operate at a speed that allows it to demonstrate its performance and consume as little power as possible.

The STM32 MCU incorporates an RC oscillation circuit consisting of a resistor R and a capacitor C, in addition to an oscillation circuit using an external crystal or ceramic resonator to supply clock signals.

While the use of a built-in oscillation circuit has the advantage of simplifying the peripheral circuits of the microcontroller by eliminating the need for an external resonator, it is possible that the frequency may fluctuate due to variations among products and the surrounding environment.

On the other hand, an external oscillation source such as a crystal oscillator has a constant and accurate frequency; however, when connecting to external devices asynchronously, such as in UART communications, the clock must be accurate because an unstable clock may cause unstable communication speed and communication problems. See the section on "External Clock for MCU".

Whether the clock source is internal or external depends on the application use and is ultimately up to the designer.

There are four types of clock sources available for STM MCU. This section explains how to generate the system clock from the HSE clock using an external oscillation source and how to set the clock to be supplied to each peripheral.

When an external oscillation source such as a crystal oscillator is used in the STM32 microcontroller or other microcontrollers, the oscillation frequency of the oscillator is not used as-is as the system clock (operating frequency), but is often made several times faster.

To achieve a high operating frequency, for example, it seems simple to use a 200 MHz external oscillation source to operate at a 200 MHz system clock, but the higher the frequency, the more power is consumed, the more heat is generated, and the more unstable the oscillation becomes.

Unlike PCs, embedded devices often have to endure use in environments with poor heat dissipation, so heat generation is fatal.

In the STM32 MCU, the clock is configured as shown in the figure above, and the system clock and peripheral clocks are created according to the parameters you set.

The clock settings may seem complicated at first glance, but once you understand how it works, you will be able to easily set it up outside of the peripheral libraries used here and in other microcontroller systems.

We will now explain using the example of using an 8 MHz crystal for the external oscillation HSE. The clock setting procedure for the system clock SYSCLK at 72 MHz, the APB1 peripheral clock PCLK1 at 18 MHz, and the APB2 peripheral clock PCLK2 at 72 MHz is as follows.

First, reset the microcontroller clock system by executing RCC_DeInit().

Immediately after power-on, the clock system is in its initial state (Internal HSI: 8 MHz), so this function does not need to be executed, but it is executed for fail-safe reasons.

Enables external clock HSE; the argument of the HSE enable function RCC_HSEConfig is RCC_HSE_ON to enable HSE and RCC_HSE_OFF to disable HSE.

For reference, there is also an argument RCC_HSE_Bypass, which is used to bypass the HSE by inputting an external clock source to the OSC_IN pin without using a crystal or ceramic resonator.

When using the internal clock HSI (8 MHz), execution of RCC_HSEConfig() is not necessary.

Since the external oscillator is an oscillation circuit combined with a capacitor, it takes some time for the clock to stabilize after startup. To wait until it stabilizes, RCC_WaitForHSEStartUp() is executed to obtain the return value HSEStartUpStatus.

When the returned HSEStartUpStatus value is SUCCESS(1), the next process proceeds.

Set PLLCLK by PLL circuit.
The PLLCLK is created by executing RCC_PLLConfig.

In the above program example, the HSE clock is 8 MHz with a division ratio of 1 and a multiplication factor of 9, so PLLCLK is 72 MHz.

Next, divide settings for HCLK, PCLK1, and PCLK2 are made.

HCLK is generated by executing SYSCLK with the division ratio specified as an argument in RCC_HCLKConfig.

PCLK1 and PCLK2 are generated by executing HCLK with the division ratio specified as an argument in RCC_PLCK1Config() and RCC_PLCK2Config(), respectively.

PLL_PLLConfig() sets the PLL circuit multiplication factor, but the PLL circuit is not yet active.
RCC_PLLCmd() is used to start the PLL circuit. The argument ENABLE activates the PLL circuit, and DISABLE deactivates the circuit.

Since it takes some time for the PLL circuit to start properly after it is set to run, use RCC_GetFlagStatus() to check if the PLL circuit is ready, and if the return flag of this function goes from RESET to SET, it means it is ready.

The program waits while the return flag is RESET.
RCC_GetFlagStatus() can be used to check various states other than the PLL circuit.

The following is a description of the RCC_FLAG macro specified as an argument, which is related to clock settings. The setting example confirms that the PLL is ready.

In addition, RCC_FLAG_PINRST, RCC_FLAG_PRTRST, RCC_FLAG_SFTRST, RCC_FLAG_IWDGRST, RCC_FLAG_WWDGRST, and RCC_FLAG_LPWRST are available for use as needed.

At the end of the clock setup, PLLCLK is specified as SYSCLK, the operating frequency of the system clock. This is set by executing RCC_SYSCLKConfig().

Finally, to check if PLLCLK is set to SYSCLK, the return value of RCC_GetSYSCLKCource() is checked and if it is as set, the operation is completed. In this program, PLLCLK is set, so if the return value is 0x08, the setting is complete.

The program has been used as an example to explain the settings, but in reality, it would be sufficient to use the program as it is and change only the parameters. In reality, you can use this setup program as it is and change only the parameters.