STM32G4开发详解：HAL与低层驱动介绍

需积分: 10 159 浏览量更新于2024-07-14 收藏 10.41MB PDF 举报

"STM32G4 HAL和低层驱动器是STM32Cube软件平台的一部分，这个平台旨在提升STM32系列微控制器开发的效率、时间和成本。STM32G431RBT6是STM32G4系列的一款具体产品，常用于蓝桥杯等嵌入式竞赛或项目中。 STM32Cube由几个关键组件构成： 1. STM32CubeMX：这是一个图形化的软件配置工具，通过图形向导生成C语言的初始化代码，简化了设置过程。 2. STM32CubeHAL：STM32抽象层嵌入式软件，确保在整个STM32产品线上的最大可移植性。HAL（硬件抽象层）API提供了所有外设的通用接口。 3. 低层APIs (LL)：为一组特定的外设提供接近硬件的快速轻量级专家级接口，比HAL更接近底层。 4. 一致性中间件组件：如实时操作系统(RTOS)和USB等，方便开发者集成复杂功能。 5. 全套嵌入式软件工具，包括丰富的示例代码，帮助开发者快速上手。 HAL驱动层提供了一组简单、通用的多实例API，用于与上层应用、库和协议栈交互。这些API被分为几个部分，包括初始化、配置、读写操作以及错误管理等，使得开发者无需深入了解硬件细节就能进行操作。 STM32Cube的低层驱动器（LL）则提供了更为灵活且高效的选项，适用于需要更精确控制硬件特性的高级开发者。它们通常更快，但使用起来可能需要更多的硬件知识。LL API只对部分外设提供支持，因此在选择使用时需要根据项目需求来决定。 STM32G431RBT6作为STM32G4系列的一员，具备高性能、低功耗的特点，适用于需要高速计算和实时响应的嵌入式应用，如工业自动化、电机控制、仪器仪表等领域。在蓝桥杯这样的竞赛中，参赛者通常会利用其强大的计算能力和丰富的外设接口来设计创新的解决方案。在开发过程中，开发者可以结合STM32CubeMX配置初始设置，然后使用STM32CubeHAL或LL API编写应用程序，同时利用提供的中间件和示例代码来加速开发进程。这种结构化的软件框架极大地简化了STM32微控制器的应用开发，降低了入门难度，提高了开发效率。"

IP/Module STM32G431xx STM32G441xx STM32G471xx STM32G473xx STM32G483xx STM32G474xx STM32G484xx STM32GBK1CB STM32G491xx STM32G4A1xx

stm32g4xx_hal_pcd_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_pwr.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_pwr_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_qspi.c No No No Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_rcc.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_rcc_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_rng.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_rtc.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_rtc_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_sai.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_sai_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_smartcard.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_smartcard_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_smbus.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_spi.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_spi_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_sram.c No No No Yes Yes Yes Yes No Yes Yes

stm32g4xx_hal_tim.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_tim_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_timebase_tim_te

mplate.c

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_uart.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_uart_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_usart.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_usart_ex.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_hal_wwdg.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_adc.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_comp.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_cordic.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_crc.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_crs.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_dac.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_dma.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_exti.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

stm32g4xx_ll_fmac.c Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

UM2570

Devices supported by HAL drivers

UM2570 - Rev 2

page 16/2926

3.5 HAL driver rules

3.5.1 HAL API naming rules

The following naming rules are used in HAL drivers:

Table 6. HAL API naming rules

Generic Family specific Device specific

File names stm32g4xx_hal_ppp (c/h) stm32g4xx_hal_ppp_ex (c/h) stm32g4xx_ hal_ppp_ex (c/h)

Module

name

HAL_PPP_ MODULE

Function

name

HAL_PPP_Function

HAL_PPP_FeatureFunction_MODE

HAL_PPPEx_Function

HAL_PPPEx_FeatureFunction_MODE

HAL_PPPEx_Function

HAL_PPPEx_FeatureFunction_MODE

Handle

name

PPP_HandleTypedef NA NA

Init

structure

name

PPP_InitTypeDef NA PPP_InitTypeDef

Enum name HAL_PPP_StructnameTypeDef NA NA

• The PPP prefix refers to the peripheral functional mode and not to the peripheral itself. For example, if the

USART, PPP can be USART, IRDA, UART or SMARTCARD depending on the peripheral mode.

• The constants used in one file are defined within this file. A constant used in several files is defined in a

header file. All constants are written in uppercase, except for peripheral driver function parameters.

• typedef variable names should be suffixed with _TypeDef.

• Registers are considered as constants. In most cases, their name is in uppercase and uses the same

acronyms as in the STM32G4 reference manuals.

• Peripheral registers are declared in the PPP_TypeDef structure (for example ADC_TypeDef) in

stm32g4xxx.h header file:

stm32g4xxx.h corresponds to stm32g431xx.h, stm32g441xx.h, stm32g471xx.h, stm32g473xx.h,

stm32g483xx.h, stm32g474xx.h, stm32g484xx.h, stm32gbk1cb.h and stm32g491xx.h and stm32g4a1xx.h.

• Peripheral function names are prefixed by HAL_, then the corresponding peripheral acronym in uppercase

followed by an underscore. The first letter of each word is in uppercase (for example

HAL_UART_Transmit()). Only one underscore is allowed in a function name to separate the peripheral

acronym from the rest of the function name.

• The structure containing the PPP peripheral initialization parameters are named PPP_InitTypeDef (for

example ADC_InitTypeDef).

• The structure containing the Specific configuration parameters for the PPP peripheral are named

PPP_xxxxConfTypeDef (for example ADC_ChannelConfTypeDef).

• Peripheral handle structures are named PPP_HandleTypedef (e.g DMA_HandleTypeDef)

• The functions used to initialize the PPP peripheral according to parameters specified in PPP_InitTypeDef are

named HAL_PPP_Init (for example HAL_TIM_Init()).

• The functions used to reset the PPP peripheral registers to their default values are named HAL_PPP_DeInit

(for example HAL_TIM_DeInit()).

• The MODE suffix refers to the process mode, which can be polling, interrupt or DMA. As an example, when

the DMA is used in addition to the native resources, the function should be called: HAL_PPP_Function_DMA

().

• The Feature prefix should refer to the new feature.

UM2570

HAL driver rules

UM2570 - Rev 2

page 18/2926

• The macros that handle interrupts and specific clock configurations are defined in each peripheral/module

driver. These macros are exported in the peripheral driver header files so that they can be used by the

extension file. The list of these macros is defined below:

Note: This list is not exhaustive and other macros related to peripheral features can be added, so that they can be

used in the user application.

Table 7. Macros handling interrupts and specific clock configurations

Macros Description

__HAL_PPP_ENABLE_IT(__HANDLE__, __INTERRUPT__) Enables a specific peripheral interrupt

__HAL_PPP_DISABLE_IT(__HANDLE__,

__INTERRUPT__)

Disables a specific peripheral interrupt

__HAL_PPP_GET_IT (__HANDLE__, __ INTERRUPT __) Gets a specific peripheral interrupt status

__HAL_PPP_CLEAR_IT (__HANDLE__, __ INTERRUPT __) Clears a specific peripheral interrupt status

__HAL_PPP_GET_FLAG (__HANDLE__, __FLAG__) Gets a specific peripheral flag status

__HAL_PPP_CLEAR_FLAG (__HANDLE__, __FLAG__) Clears a specific peripheral flag status

__HAL_PPP_ENABLE(__HANDLE__) Enables a peripheral

__HAL_PPP_DISABLE(__HANDLE__) Disables a peripheral

__HAL_PPP_XXXX (__HANDLE__, __PARAM__) Specific PPP HAL driver macro

__HAL_PPP_GET_ IT_SOURCE (__HANDLE__, __

INTERRUPT __)

Checks the source of specified interrupt

• NVIC and SYSTICK are two Arm

Cortex

core features. The APIs related to these features are located in

the stm32g4xx_hal_cortex.c file.

• When a status bit or a flag is read from registers, it is composed of shifted values depending on the number

of read values and of their size. In this case, the returned status width is 32 bits. Example : STATUS = XX |

(YY << 16) or STATUS = XX | (YY << 8) | (YY << 16) | (YY << 24)".

• The PPP handles are valid before using the HAL_PPP_Init() API. The init function performs a check before

modifying the handle fields.

HAL_PPP_Init(PPP_HandleTypeDef)

if(hppp == NULL)

{

return HAL_ERROR;

}

• The macros defined below are used:

– Conditional macro:

#define ABS(x) (((x) > 0) ? (x) : -(x))

– Pseudo-code macro (multiple instructions macro):

#define __HAL_LINKDMA(__HANDLE__, __PPP_DMA_FIELD_, __DMA_HANDLE_) \

do{ \

(__HANDLE__)->__PPP_DMA_FIELD_ = &(__DMA_HANDLE_); \

(__DMA_HANDLE_).Parent = (__HANDLE__); \

} while(0)

3.5.3 HAL interrupt handler and callback functions

Besides the APIs, HAL peripheral drivers include:

• HAL_PPP_IRQHandler() peripheral interrupt handler that should be called from stm32g4xx_it.c

• User callback functions.

UM2570

HAL driver rules

UM2570 - Rev 2

page 20/2926

剩余2925页未读，继续阅读

xiaolan@

粉丝: 53
资源: 23

STM32G4开发详解：HAL与低层驱动介绍

UM2570_STM32G4的HAL和LL驱动程序介绍 - 用户手册.pdf

从STM32G4系列的STM32CubeG4开始的用户手册_ENV2_20201118.pdf STM32G4xx系列固件库驱动库软件开发包使用说明英文

UM2570_STM32G4的HAL和LL驱动程序介绍20201105.pdf

stm32g070 hal库

stm32g0 hal库中文手册

stm32g0 hal 配置usb口

stm32g4 hal库配置dac

stm32G474 hal库 配置RS485

stm32g4 flash hal

#include "stm32g0xx_hal.h"这个的作用

最新资源

stm32G474 hal库配置RS485