/**
@page RCC_ClockConfig RCC Clock Config example
@verbatim
******************************************************************************
* @file RCC/RCC_ClockConfig/readme.txt
* @author MCD Application Team
* @brief Description of the RCC Clock Config example.
******************************************************************************
* @attention
*
* Copyright (c) 2016 STMicroelectronics.
* All rights reserved.
*
* This software is licensed under terms that can be found in the LICENSE file
* in the root directory of this software component.
* If no LICENSE file comes with this software, it is provided AS-IS.
*
******************************************************************************
@endverbatim
@par Example Description
Configuration of the system clock (SYSCLK) and modification of the clock settings in Run mode, using the RCC HAL API.
In this example, after startup SYSCLK is configured to the max frequency using the PLL with
HSE as clock source, the User push-button (connected to EXTI_Line15_10) will be
used to change the PLL source:
- from HSI to HSE bypass
- from HSE bypass to HSI
@note In HSE bypass mode, input clock will come from the MCO from
ST_LINK MCU. This frequency cannot be changed, and it is fixed
at 8 MHz. To use MCO from ST_LINK you need to check the Board
User Manual to know how to connect the MCO pin to the STM32 device.
Each time the User push-button is pressed; EXTI_Line15_10 interrupt is generated and in the ISR
the PLL oscillator source is checked using __HAL_RCC_GET_PLL_OSCSOURCE() macro:
- If the HSE bypass oscillator is selected as PLL source, the following steps will be followed to switch
the PLL source to HSI oscillator:
a- Switch the system clock source to HSE bypass to allow modification of the PLL configuration
b- Enable HSI Oscillator, select it as PLL source and finally activate the PLL
c- Select the PLL as system clock source and configure the HCLK, PCLK1 and PCLK2 clocks dividers
d- Disable the HSE bypass oscillator (optional, if the HSE bypass is no more needed by the application)
- If the HSI oscillator is selected as PLL source, the following steps will be followed to switch
the PLL source to HSE bypass oscillator:
a- Switch the system clock source to HSI to allow modification of the PLL configuration
b- Enable HSE bypass Oscillator, select it as PLL source and finally activate the PLL
c- Select the PLL as system clock source and configure the HCLK, PCLK1 and PCLK2 clocks dividers
d- Disable the HSI oscillator (optional, if the HSI is no more needed by the application)
In this example the SYSCLK / 1 is outputted on the MCO1 pin(PA.08).
=> PA.08 connected to pin 23 on CN12 connector
LED1 is toggled with a timing defined by the HAL_Delay() API.
LED3 toggles in case of error handler.
@note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)
based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from
a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)
than the peripheral interrupt. Otherwise the caller ISR process will be blocked.
To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.
@note The application need to ensure that the SysTick time base is always set to 1 millisecond
to have correct HAL operation.
@par Keywords
RCC, System, Clock Configuration, HSE bypass mode, HSI, System clock, Oscillator, PLL
@Note<74>If the user code size exceeds the DTCM-RAM size or starts from internal cacheable memories (SRAM1 and SRAM2),that is shared between several processors,
<20><><A0><A0><A0>then it is highly recommended to enable the CPU cache and maintain its coherence at application level.
<0A><><A0><A0><A0><A0>The address and the size of cacheable buffers (shared between CPU and other masters) must be properly updated to be aligned to cache line size (32 bytes).
@Note It is recommended to enable the cache and maintain its coherence, but depending on the use case
<0A><><A0><A0><A0> It is also possible to configure the MPU as "Write through", to guarantee the write access coherence.
<0A><><A0><A0><A0><A0>In that case, the MPU must be configured as Cacheable/Bufferable/Not Shareable.
<0A><><A0><A0><A0><A0>Even though the user must manage the cache coherence for read accesses.
<0A><><A0><A0><A0><A0>Please refer to the AN4838 <20>Managing memory protection unit (MPU) in STM32 MCUs<55>
<0A><><A0><A0><A0><A0>Please refer to the AN4839 <20>Level 1 cache on STM32F7 Series<65>
@par Directory contents
- RCC/RCC_ClockConfig/Inc/stm32f7xx_hal_conf.h HAL configuration file
- RCC/RCC_ClockConfig/Inc/stm32f7xx_it.h Interrupt handlers header file
- RCC/RCC_ClockConfig/Inc/main.h Header for main.c module
- RCC/RCC_ClockConfig/Src/stm32f7xx_it.c Interrupt handlers
- RCC/RCC_ClockConfig/Src/main.c Main program
- RCC/RCC_ClockConfig/Src/system_stm32f7xx.c STM32F7xx system source file
@par Hardware and Software environment
- This example runs on STM32F722xx/STM32F723xx/STM32F732xx/STM32F733xx devices.
- This example has been tested with STM32F722ZE-Nucleo
board and can be easily tailored to any other supported device
and development board.
@par How to use it ?
In order to make the program work, you must do the following :
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the example
*/
767d083e20