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

需积分: 10 67 浏览量更新于2024-07-15 收藏 25.02MB PDF 举报

"UM1718 User manual STM32CubeMX for STM32.pdf - 这是一本关于STM32CubeMX的用户手册，适用于STM32微控制器的技术开发指导，英文版，内容详尽。" STM32CubeMX是STM32微控制器的图形化配置工具，它是STM32Cube计划的一部分，该计划旨在提供一站式的软件、固件和服务，以简化STM32系列产品的开发流程。STM32CubeMX作为一个独立的应用程序，同时也整合在STM32CubeIDE工具链中。该工具的关键特性包括： 1. **广泛的微控制器选择**：覆盖STM32产品线的所有微控制器，使得用户可以方便地挑选合适的MCU。 2. **板卡选择**：提供STMicroelectronics官方板卡列表，帮助用户快速匹配合适的开发板。 3. **轻松配置**：用户可以便捷地配置微控制器的引脚、时钟树、外设和中间件，并自动生成相应的初始化C代码。 4. **项目迁移**：允许用户将已保存的配置导入新的MCU项目，实现不同微控制器间的快速切换。 5. **配置导出**：可以将当前的配置导出到兼容的MCU，便于共享或备份。 6. **配置报告生成**：工具能够生成配置报告，便于分析和理解项目的配置状态。 7. **嵌入式C项目生成**：根据选定的集成开发环境（IDE）工具链生成嵌入式C项目。STM32CubeMX项目包含了初始化C代码、符合MISRA 2004标准的STM32 HAL驱动、用户配置所需的中间件堆栈。通过STM32CubeMX，开发者能够高效地进行项目初始化，大大降低了STM32应用开发的入门难度和复杂性。无论是新手还是经验丰富的开发者，都能从中受益，快速搭建起基于STM32的系统框架，进一步专注于应用程序的开发。手册中详细介绍了如何使用这些功能，是STM32开发者的重要参考资料。

List of figures UM1718

16/366 UM1718 Rev 32

Figure 299. Enabling X-Cube-BLE1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Figure 300. Configuring the SensorDemo project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Figure 301. Open SensorDemo project in the IDE toolchain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Figure 302. Launching the SensorDemo project in Atollic® TrueStudio® . . . . . . . . . . . . . . . . . . . . . . 301

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

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

Figure 305. Testing the SensorDemo application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Figure 306. Java Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Figure 307. Pinout view - Enabling the RTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

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

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

Figure 310. Block mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Figure 311. Block remapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

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

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

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

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

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

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

Figure 318. Function remapping example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Figure 319. Block shifting not applied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Figure 320. Block shifting applied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

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

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

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

Figure 324. Libjpeg configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Figure 325. Mbed TLS without LwIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

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

Figure 327. Mbed TLS configuration window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Figure 328. Enabling the TouchSensing peripheral. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

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

Figure 330. TouchSensing configuration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Figure 331. BLE and Thread middleware support in STM32CubeMX. . . . . . . . . . . . . . . . . . . . . . . . . 332

Figure 332. STM32CubeWB Package download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Figure 333. STM32CubeWB BLE applications folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Figure 334. BLE Server profile selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Figure 335. BLE Client profile selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Figure 336. Thread application selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Figure 337. Enabling OpenAmp for STM32MP1 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

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

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

Figure 340. STM32 microcontroller part numbering scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Figure 341. STM32Cube Embedded Software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Getting started with STM32CubeMX UM1718

18/366 UM1718 Rev 32

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/366 UM1718 Rev 32

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 project creation starting from an MCU, a board or an example

The new project window allows the user to create a project by selecting a

microcontroller, a board, or an example project from STMicroelectronics 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. 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

剩余365页未读，继续阅读

butterfly

粉丝: 13
资源: 17

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

!! STM32CubeMX用于STM32配置和初始化C代码生成(UM1718).pdf

STM32cubeMX manual

STM32CubeMX用户手册中文版UM1718-翻译版.rar

优化这段SQL： SELECT CONCAT(UM.USER_ID,UM.USER_NAME) Creat_USERNAME, CONCAT(UM.USER_ID,UM.USER_NAME) Update_USERNAME FROM P1RPT.CARRIER_MASTER CM, P1RPT.USER_MASTER UM WHERE 1=1 AND CM.CREATE_USER_RRN = UM.USER_RRN AND CM.UPDATE_USER_RRN = UM.USER_RRN

stm32 um220

如何利用STM32CubeWB平台开发BLE功能的IoT设备，并使用Middleware组件进行设备管理？

stm32f4xx_dsp_stdperiph_lib_um.chm

如何利用STM32CubeWB平台开发支持BLE的IoT设备，并利用其提供的Middleware组件进行设备管理？

stm32标准库例程

最新资源