STM32CubeMX用户手册：配置与初始化C代码生成

需积分: 15 130 浏览量更新于2024-07-16 收藏 30.37MB PDF 举报

"STM32CuBeMX是ST公司提供的一款图形化配置工具，用于STM32微控制器的配置和初始化C代码生成。它属于STM32Cube项目的一部分，可以作为一个独立的应用程序使用，也可以集成在STM32CubeIDE工具链中。这款工具拥有众多优势特性，包括全系列STM32微控制器的便捷选择、ST微电子板的支持、微控制器配置、C代码生成、项目移植、配置导出和项目生成等。STM32CubeMX还支持生成配置报告和嵌入式C项目，适用于多种集成开发环境的工具链，并包含符合MISRA2004标准的STM32HAL驱动和所需的中间件栈。" STM32CuBeMX是STM32开发中的重要工具，它简化了STM32微控制器的选型过程。用户可以从ST提供的完整STM32产品线中轻松选择合适的微控制器。此外，它还支持ST的各类开发板，使得硬件选择更为便捷。该工具的核心功能在于配置。用户可以通过直观的图形界面配置微控制器的引脚、时钟树、外设以及中间件。这些配置完成后，STM32CuBeMX能够自动生成对应的初始化C代码，这大大减少了手动编写初始化代码的工作量和错误率。 STM32CuBeMX的一大亮点是其项目迁移能力。用户可以将之前保存的配置导入到新的MCU项目中，方便在不同微控制器之间切换，保持项目的连续性和一致性。同时，也能将当前的配置导出到兼容的MCU，增强了代码的复用性。除了代码生成，STM32CuBeMX还能够生成配置报告，帮助开发者了解和检查项目配置的详细信息。此外，它能生成适用于多种集成开发环境（IDE）的嵌入式C项目，包括STM32HAL驱动库和所需的中间件栈。这些中间件栈通常包括了如USB、TCP/IP、 FatFS等常用协议和文件系统，便于用户快速构建应用层。 STM32CubeMX遵循MISRA2004编码规则的HAL驱动，确保了代码质量和安全性。MISRA（Motor Industry Software Reliability Association）是一套严格的编码规范，旨在减少软件中的错误和提高可靠性。 STM32CuBeMX是STM32开发者不可或缺的工具，它提供了从项目初期选型到代码生成的全套解决方案，极大地提高了开发效率和代码质量。无论是新手还是经验丰富的工程师，都能从中受益，实现更高效、更可靠的STM32应用开发。

List of figures UM1718

16/365 UM1718 Rev 30

Figure 299. STemWin GUIBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Figure 300. StemWin generated project and files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Figure 301. GFXSIMULATOR in Configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Figure 302. Graphics simulator user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Figure 303. Graphics simulator - Current Configuration fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Figure 304. Enabling ST-TouchGFX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Figure 305. TouchGFXDesigner: installer location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Figure 306. TouchGFX incompatible LTDC Pixel format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Figure 307. Setting TouchGFX compatible LTDC pixel format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Figure 308. TouchGFXDesigner path missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Figure 309. ST-TouchGFXDesigner executable file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Figure 310. Generate project before ST-TouchGFXDesigner launch . . . . . . . . . . . . . . . . . . . . . . . . . 301

Figure 311. Launching ST-TOUCHGFXDesigner tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Figure 312. ST-TOUCHGFXDesigner user interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Figure 313. ST-TOUCHGFX generated project and files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Figure 314. Java™ Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

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

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

Figure 317. Pinout view - Setting LSE/HSE clock frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Figure 318. Block mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Figure 319. Block remapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Figure 320. Block remapping - Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

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

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

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

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

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

Figure 326. Function remapping example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Figure 327. Block shifting not applied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Figure 328. Block shifting applied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Figure 329. FreeRTOS HOOK functions to be completed by user . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Figure 330. LwIP 1.4.1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Figure 331. LwIP 1.5 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Figure 332. Libjpeg configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Figure 333. Mbed TLS without LwIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Figure 334. Mbed TLS with LwIP and FreeRTOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Figure 335. Mbed TLS configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Figure 336. Enabling the TouchSensing peripheral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Figure 337. Touch-sensing sensor selection panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Figure 338. TouchSensing configuration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Figure 339. Graphics application architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Figure 340. BLE and Thread middleware support in STM32CubeMX. . . . . . . . . . . . . . . . . . . . . . . . . 333

Figure 341. STM32CubeWB Package download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Figure 342. STM32CubeWB BLE applications folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Figure 343. BLE Server profile selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Figure 344. BLE Client profile selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Figure 345. Thread application selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Figure 346. Enabling OpenAmp for STM32MP1 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Figure 347. Enabling the Resource Manager for STM32MP1 devices . . . . . . . . . . . . . . . . . . . . . . . . 338

Figure 348. Resource Manager: peripheral assignment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Figure 349. STM32 microcontroller part numbering scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Figure 350. STM32Cube Embedded Software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Getting started with STM32CubeMX UM1718

18/365 UM1718 Rev 30

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/365 UM1718 Rev 30

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 that will be used the next time the project will be loaded in

STM32CubeMX.

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

剩余364页未读，继续阅读

大圆萝卜

粉丝: 0
资源: 3

STM32CubeMX用户手册：配置与初始化C代码生成

轻松玩转STM32Cube 第1章 ppt

Cubemx系列教程共16课.zip

轻松玩转STM32Cube 第4章 ppt

嵌入式系统设计——基于stm32cubemx与hal库pdf

stm32cubemx开contiki

stm32cubemx下载

stm32cube 输出 pdf配置

stm32从入门到精通.pdf

stm32单片机pdf

轻松玩转stm32cube pdf

最新资源