FAQs

UM1766

25/29

DocID026352 Rev 8

5.5

Does the HAL take benefit from interrupts or DMA?

How can this be controlled?

Yes. The HAL supports three API programming models: polling, interrupt and DMA (with or

without interrupt generation).

5.6

How are the product/peripheral specific features managed?

The HAL offers extended APIs, that is, specific functions as add-ons to the common API to

support features available on some products/lines only.

5.7

How can STM32CubeMX generate code based on embedded

software?

STM32CubeMX has a built-in knowledge of STM32 microcontrollers, including their

peripherals and software. This enables the tool to provide a graphical representation to the

user and generate *.h/*.c files based on the user configuration.

5.8

How can the user get regular updates on the latest

STM32CubeF3 firmware releases?

The STM32CubeF3 firmware package comes with an updater utility, STM32CubeUpdater,

that can be configured for automatic or on-demand checks for new firmware package

updates (new releases or/and patches).

STM32CubeUpdater is also integrated within the STM32CubeMX tool. When using this tool

for STM32F3 configuration and initialization C code generation, the user can benefit from

STM32CubeMX self-updates as well as STM32CubeF3 firmware package updates.

For more details, refer to Section 4.4.

5.9

When to use HAL versus LL drivers?

HAL drivers offer high-level and function-oriented APIs, with a high level of portability.

Product/IPs complexity is hidden for end users.

LL drivers offer low-level APIs at registers level, with a better optimization but less

portability. They require a deep knowledge of product/IPs specifications.

5.10

How can the user include LL drivers in his/her environment?

Is there any LL configuration file as for HAL?

There is no configuration file. Source code shall directly include the necessary

stm32f3xx_ll_ppp.h file(s).