2019-05-01 00:27:23 +08:00
|
|
|
/**
|
|
|
|
@page Templates Description of the Templates example
|
|
|
|
|
|
|
|
@verbatim
|
|
|
|
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
|
|
|
|
* @file Templates/readme.txt
|
|
|
|
* @author MCD Application Team
|
|
|
|
* @brief Description of the Templates example.
|
|
|
|
******************************************************************************
|
2022-03-09 16:22:30 +08:00
|
|
|
* @attention
|
2019-05-01 00:27:23 +08:00
|
|
|
*
|
2022-03-09 16:22:30 +08:00
|
|
|
* Copyright (c) 2017 STMicroelectronics.
|
|
|
|
* All rights reserved.
|
2019-05-01 00:27:23 +08:00
|
|
|
*
|
2022-03-09 16:22:30 +08:00
|
|
|
* 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.
|
2019-05-01 00:27:23 +08:00
|
|
|
*
|
|
|
|
******************************************************************************
|
2021-03-03 21:55:52 +08:00
|
|
|
@endverbatim
|
2019-05-01 00:27:23 +08:00
|
|
|
|
|
|
|
@par Example Description
|
|
|
|
|
|
|
|
This project provides a reference template that can be used to build any firmware application.
|
|
|
|
|
|
|
|
This directory provides a reference template project that can be used to build any firmware application for
|
|
|
|
STM32F429xx/439xx devices using STM32CubeF4 HAL and running on STM324x9I-EVAL board from STMicroelectronics.
|
|
|
|
|
|
|
|
Two workspace are provided for STM32429I-EVAL (STM32F429xx devices) and STM32439I-EVAL (STM32F439xx devices)
|
|
|
|
configuration: the difference is related to the hardware Cryptographic and Hash processors which are available
|
|
|
|
only in STM32F439xx devices.
|
|
|
|
Each workspace include the right set of peripherals, linker and startup files.
|
|
|
|
|
|
|
|
|
|
|
|
@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 needs to ensure that the SysTick time base is always set to 1 millisecond
|
|
|
|
to have correct HAL operation.
|
|
|
|
|
|
|
|
|
|
|
|
@par Directory contents
|
|
|
|
|
|
|
|
- Templates/Src/main.c Main program
|
|
|
|
- Templates/Src/system_stm32f4xx.c STM32F4xx system clock configuration file
|
|
|
|
- Templates/Src/stm32f4xx_it.c Interrupt handlers
|
|
|
|
- Templates/Src/stm32f4xx_hal_msp.c HAL MSP module
|
|
|
|
- Templates/Inc/main.h Main program header file
|
|
|
|
- Templates/Inc/stm32f4xx_hal_conf.h HAL Configuration file
|
|
|
|
- Templates/Inc/stm32f4xx_it.h Interrupt handlers header file
|
|
|
|
|
|
|
|
|
|
|
|
@par Hardware and Software environment
|
|
|
|
|
|
|
|
- This example runs on STM32F429xx/STM32F439xx devices.
|
|
|
|
|
|
|
|
- This example has been tested with STMicroelectronics STM324x9I-EVAL RevB
|
|
|
|
evaluation boards 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
|
|
|
|
|
2022-03-09 16:22:30 +08:00
|
|
|
|
2019-05-01 00:27:23 +08:00
|
|
|
*/
|