STM32CubeMX配置与C代码生成工具详解

PDF文件

下载需积分: 5 | 24.87MB | 更新于2024-06-21 | 89 浏览量 | 举报收藏

立即下载

"STM32CubeMX是一款专用于STM32微控制器的图形化配置工具，它是STM32Cube计划的一部分，并且可以作为独立应用程序或嵌入在STM32CubeIDE工具链中使用。该工具提供了多种关键功能，如轻松选择STM32全系列微控制器，从STMicroelectronics板列表中选择开发板，方便地配置微控制器（引脚、时钟树、外设、中间件）并生成相应的初始化C代码，以及在不同微控制器项目之间导入和导出配置等。此外，STM32CubeMX还支持生成配置报告和嵌入式C项目，适用于多种集成开发环境工具链，包括符合MISRA 2004标准的STM32 HAL驱动器以及用户配置所需的中间件栈。" STM32CubeMX是STM32开发者的重要工具，它简化了STM32微控制器的初始设置和配置过程。以下是对STM32CubeMX主要特性的详细解释： 1. **微控制器选择**：STM32CubeMX覆盖了STM32系列的所有产品，允许用户根据项目需求选择合适的微控制器。 2. **板卡选择**：工具内置了STMicroelectronics的官方开发板列表，用户可以直接选取对应的开发板，便于快速开始项目。 3. **配置与初始化C代码生成**：用户可以通过直观的图形界面轻松配置微控制器的引脚、时钟系统、外设以及中间件，然后STM32CubeMX会自动生成对应的初始化C代码，这些代码是项目的基础，确保硬件正确运行。 4. **跨微控制器配置迁移**：用户可以将已保存的配置导入到新的微控制器项目中，无需从头开始，提高了开发效率。 5. **配置导出**：允许用户将当前配置导出到兼容的微控制器，方便在其他设备上重复使用或共享配置。 6. **配置报告**：生成详细的配置报告，帮助开发者了解和检查配置的详细信息，便于调试和团队协作。 7. **项目生成**：STM32CubeMX能够生成适用于多种集成开发环境（IDE）的项目文件，如Keil MDK, IAR EWARM, Eclipse等，项目中包含了初始化C代码、符合MISRA C 2004编码规范的STM32 HAL驱动程序以及用户配置所必需的中间件。使用STM32CubeMX，开发者可以快速建立项目框架，减少了手动编写初始化代码的时间，提升了开发效率。对于初学者，这降低了入门STM32的难度，而对于经验丰富的开发者，它则提供了更高效的工作流程。

List of figures UM1718

16/363 UM1718 Rev 31

Figure 299. Open SensorDemo project in the IDE toolchain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Figure 300. Launching the SensorDemo project in Atollic® TrueStudio® . . . . . . . . . . . . . . . . . . . . . . 299

Figure 301. Viewing the SensorDemo project in Atollic® TrueStudio® . . . . . . . . . . . . . . . . . . . . . . . . 299

Figure 302. Configuring the SensorDemo project in Atollic® TrueStudio® . . . . . . . . . . . . . . . . . . . . . 300

Figure 303. Testing the SensorDemo application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Figure 304. Java™ Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Figure 305. Pinout view - Enabling the RTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Figure 306. Pinout view - Enabling LSE and HSE clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Figure 307. Pinout view - Setting LSE/HSE clock frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Figure 308. Block mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Figure 309. Block remapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Figure 310. Block remapping - Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Figure 311. Block remapping - Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Figure 312. Block inter-dependency - SPI signals assigned to PB3/4/5 . . . . . . . . . . . . . . . . . . . . . . . 310

Figure 313. Block inter-dependency - SPI1_MISO function assigned to PA6 . . . . . . . . . . . . . . . . . . . 311

Figure 314. One block = one peripheral mode - I2C1_SMBA function assigned to PB5. . . . . . . . . . . 312

Figure 315. Block remapping - Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Figure 316. Function remapping example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Figure 317. Block shifting not applied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Figure 318. Block shifting applied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Figure 319. FreeRTOS HOOK functions to be completed by user . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Figure 320. LwIP 1.4.1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Figure 321. LwIP 1.5 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Figure 322. Libjpeg configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Figure 323. Mbed TLS without LwIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Figure 324. Mbed TLS with LwIP and FreeRTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Figure 325. Mbed TLS configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Figure 326. Enabling the TouchSensing peripheral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Figure 327. Touch-sensing sensor selection panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Figure 328. TouchSensing configuration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Figure 329. BLE and Thread middleware support in STM32CubeMX. . . . . . . . . . . . . . . . . . . . . . . . . 330

Figure 330. STM32CubeWB Package download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Figure 331. STM32CubeWB BLE applications folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Figure 332. BLE Server profile selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Figure 333. BLE Client profile selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Figure 334. Thread application selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Figure 335. Enabling OpenAmp for STM32MP1 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Figure 336. Enabling the Resource Manager for STM32MP1 devices . . . . . . . . . . . . . . . . . . . . . . . . 335

Figure 337. Resource Manager: peripheral assignment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Figure 338. STM32 microcontroller part numbering scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Figure 339. STM32Cube Embedded Software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Getting started with STM32CubeMX UM1718

18/363 UM1718 Rev 31

2 Getting started with STM32CubeMX

2.1 Principles

Customers need to quickly identify the MCU that best meets their requirements (core

architecture, features, memory size, performance…). While board designers main concerns

are to optimize the microcontroller pin configuration for their board layout and to fulfill the

application requirements (choice of peripherals operating modes), embedded system

developers are more interested in developing new applications for a specific target device,

and migrating existing designs to different microcontrollers.

The time taken to migrate to new platforms and update the C code to new firmware drivers

adds unnecessary delays to the project. STM32CubeMX was developed within STM32Cube

initiative which purpose is to meet customer key requirements to maximize software reuse

and minimize the time to create the target system:

• Software reuse and application design portability are achieved through STM32Cube

firmware solution proposing a common Hardware Abstraction Layer API across STM32

portfolio.

• Optimized migration time is achieved thanks to STM32CubeMX built-in knowledge of

STM32 microcontrollers, peripherals and middleware (LwIP and USB communication

protocol stacks, FatFs file system for small embedded systems, FreeRTOS).

STM32CubeMX graphical interface performs the following functions:

• Fast and easy configuration of the MCU pins, clock tree and operating modes for the

selected peripherals and middleware

• Generation of pin configuration report for board designers

• Generation of a complete project with all the necessary libraries and initialization C

code to set up the device in the user defined operating mode. The project can be

directly open in the selected application development environment (for a selection of

supported IDEs) to proceed with application development (see Figure 1).

During the configuration process, STM32CubeMX detects conflicts and invalid settings and

highlights them through meaningful icons and useful tool tips.

Getting started with STM32CubeMX UM1718

20/363 UM1718 Rev 31

2.2 Key features

STM32CubeMX comes with the following features:

• Project management

STM32CubeMX allows the user to create, save and load previously saved projects:

– When STM32CubeMX is launched, the user can choose to create a new project or

to load a previously saved project.

– Saving the project saves user settings and configuration performed within the

project in an .ioc file to be used when the project will be loaded in STM32CubeMX

again.

STM32CubeMX also allows the user to import previously saved projects in new ones.

STM32CubeMX projects come in two flavors:

– MCU configuration only: .ioc file is saved in a dedicated project folder.

– MCU configuration with C code generation: in this case .ioc files are saved in a

dedicated project folder along with the generated source C code. There can be

only one .ioc file per project.

• Easy MCU and STMicroelectronics board selection

When starting a new project, a dedicated window opens to select either a

microcontroller or an STMicroelectronics board from STM32 portfolio. Different filtering

options are available to ease the MCU and board selection. There is also the possibility

to select an MCU through the Cross selector tab by comparing characteristics to those

of competitors portfolio. Comparison criteria can be adjusted.

• Easy pinout configuration

– From the Pinout view, the user can select the peripherals from a list and configure

the peripheral modes required for the application. STM32CubeMX assigns and

configures the pins accordingly.

– For more advanced users, it is also possible to directly map a peripheral function

to a physical pin using the Pinout view. The signals can be locked on pins to

prevent STM32CubeMX conflict solver from moving the signal to another pin.

– Pinout configuration can be exported as a .csv file.

• Complete project generation

The project generation includes pinout, firmware and middleware initialization C code

for a set of IDEs. It is based on STM32Cube embedded software libraries. The

following actions can be performed:

– Starting from the previously defined pinout, the user can proceed with the

configuration of middleware, clock tree, services (RNG, CRC, etc...) and

peripheral parameters. STM32CubeMX generates the corresponding initialization

C code. The result is a project directory including generated main.c file and C

header files for configuration and initialization, plus a copy of the necessary HAL

and middleware libraries as well as specific files for the selected IDE.

– The user can modify the generated source files by adding user-defined C code in

user dedicated sections. STM32CubeMX ensures that the user C code is

剩余362页未读，继续阅读

tgt008

粉丝: 2

STM32CubeMX配置与C代码生成工具详解

STM32CubeMX使用说明

STM32CubeMX用户中文使用手册

STM32CubeMX 使用手册

STM32.CubeMX.用户手册.zip_cubemx_cubemx用户手册_stm32_stm32 cubemx_stop7

STM32CubeMX安装包

stm32cubeMX用户手册，英文

stm32cubeMX 串口使用文档.pdf

STM32CubeMX中文英文手册合集

STM32CubeMX中文使用指南详细解读

2020考研复试百问百答：STM32CubEMX配置与英语口试技巧

最新资源