vscode扩展 - STM32工程助手
English | 简体中文
本vscode扩展适用于使用STM32CubeMX生成的工程，用于生成vscode的代码浏览、编辑、编译、下载、调试的配置文件。
作者：jswyll，文档链接：https://jswyll.com/note/embed/jswyll-stm32-assistant/。
快速开始
使用VSCode打开用STM32CubeMX生成的工程的主目录，即xxx.ioc文件所在的文件夹
点击VSCode状态栏的生成配置图标按钮，根据引导，生成配置文件。
浏览代码；点击状态栏按钮进行编译或下载；按F5键进行调试程序……
软件特性
生成.vscode/tasks.json配置文件，便于按快捷键使用GCC编译器编译、下载代码
说明
支持Jlink、CMSIS-DAP、ST-Link调试器。
生成.vscode/c_cpp_properties.json配置文件，便于在VSCode浏览、编辑STM32CubeMX生成的工程代码
在Core/Src/main.c中生成同时适用于Keil MDK和GCC编译器的重定向函数
优化Makefile类型的编译输出：
compiling Core/Src/sysmem.c...
compiling Core/Src/syscalls.c...
compiling startup_stm32f407xx.s...
linking...
text data bss dec hex filename
21592 488 1664 23744 5cc0 build/工程名称.elf
生成.vscode/launch.json配置文件，可用于启动（快捷键F5）Cortex-Debug调试：
说明
这个功能由Cortex-Debug扩展提供，本扩展仅负责生成配置文件。
多根工作区
诊断中断函数是否符合RT-Thread要求
生成适用于jswyll-iap在线升级调试的代码
说明
如果你使用的调试器是JLink，有两种选择：
使用使用JLink驱动直接下载程序，缺点是不能调试程序，需要安装JLink软件包。
使用OpenOCD下载或调试程序，需要使用Zadig把Jlink的驱动改为winusb：
修改驱动后在MDK就不能使用JLink下载了，可以使用OpenOCDUsbDriverTool.exe把驱动恢复为JLlink驱动：
多根工作区
vscode支持多根工作区，可以在一个工作区中同时打开多个工程。
本扩展兼容多根工作区。当你打开了一个多根工作区，点击状态栏的操作按钮时，首次将弹出提示选择当前操作的是哪个工作区文件夹：
后续的操作都将基于该工作区文件夹，相关的配置文件会保存在该工作区文件夹。
说明
你可以点击状态栏的子文件夹图标，切换当前工作区文件夹：
诊断中断函数
使用了RT-Thread后，使用STM32CubeMX重新配置并生成代码后可能新增中断函数，你可能忘记添加调用rt_interrupt_enter()和rt_interrupt_leave()。
当stm32*_it.c文件（例如Core/Src/stm32f4xx_it.c）中存在以下任意一行之一：
#include <rtthread.h>
#include "rtthread.h"
rt_interrupt_enter();
rt_interrupt_leave();
将自动对该文件发起诊断：检查是否在每个xxx_IRQHandler函数中调用了rt_interrupt_enter()和rt_interrupt_leave()，不符合要求时，会发出警告：
可以在问题面板中的警告上右键（或编辑器出现警告波浪线的地方点击快速修复），选择添加所有缺少的调用即可补齐该文件中的所有缺失的调用：
修复完成：
说明
================================================================================
================================================================================
================================================================================
English | 简体中文
This vscode extension is suitable for projects generated using STM32CubeMX, used to generate vscode code browsing, editing, compiling, downloading, debugging configuration files.
Author: jswyll, link to documentation: https://jswyll.com/note/embed/jswyll-stm32-assistant/.
Quick Start
Open the main directory of the project generated by STM32CubeMX using VSCode, i.e., the folder where the xxx.ioc file is located.
Click the Generate Configuration icon button in the VSCode status bar, and follow the prompts to generate the configuration file.
Browse the code; click the status bar button to compile or download; press F5 to debug the program...
Software Features
Generates a .vscode/tasks.json configuration file for easy compilation and downloading using the GCC compiler.
Note
Supports Jlink, CMSIS-DAP, and ST-Link debuggers.
Generates a .vscode/c_cpp_properties.json configuration file for browsing and editing the code generated by STM32CubeMX in VSCode.
Generates redirect functions in Core/Src/main.c that are compatible with both Keil MDK and GCC compilers.
Optimizes Makefile-type compilation output:
compiling Core/Src/sysmem.c...
compiling Core/Src/syscalls.c...
compiling startup_stm32f407xx.s...
linking...
text data bss dec hex filename
21592 488 1664 23744 5cc0 build/project_name.elf
Generates a .vscode/launch.json configuration file for starting (F5 shortcut) Cortex-Debug debugging:
Note
This feature is provided by the Cortex-Debug extension; this extension only generates the configuration file.
Multi-root Workspaces
Diagnose Interrupt Functions to ensure they meet RT-Thread requirements
Generates code suitable for jswyll-iap online upgrade debugging
Note
If you are using a JLink debugger, you have two options:
Use the JLink driver to directly download the program. The downside is that you cannot debug the program. You need to install the JLink software package.
Use OpenOCD to download or debug the program. You need to use Zadig to change the JLink driver to winusb:
After modifying the driver, you cannot use JLink to download in MDK. You can use UsbDriverTool.exe to restore the driver to JLink:
Multi-root Workspaces
VSCode supports multi-root workspaces, allowing multiple projects to be opened simultaneously in one workspace.
This extension is compatible with multi-root workspaces. When you open a multi-root workspace and click the status bar operation button, a prompt will appear the first time to select which workspace folder the current operation should apply to:
Subsequent operations will be based on the selected workspace folder, and related configuration files will be saved in that folder.
Note
You can click the Subfolder icon in the status bar to switch the current workspace folder:
Diagnose Interrupt Functions
After using RT-Thread, if you reconfigure and regenerate the code using STM32CubeMX, new interrupt functions may be added, and you might forget to add calls to rt_interrupt_enter() and rt_interrupt_leave().
When the stm32*_it.c file (e.g., Core/Src/stm32f4xx_it.c) contains any of the following lines:
#include <rtthread.h>
#include "rtthread.h"
rt_interrupt_enter();
rt_interrupt_leave();
The file will automatically be diagnosed: it checks whether each xxx_IRQHandler function calls rt_interrupt_enter() and rt_interrupt_leave(). If not, a warning will be issued:
You can right-click on the warning in the Problems panel (or click Quick Fix on the wavy underline in the editor) and select Add All Missing Calls to add all missing calls in the file:
Completion:
Note
In the settings of this extension, you can choose whether to enable automatic diagnosis and modify the file matching pattern for automatic diagnosis.
You can right-click on a file in the file tree and manually trigger the diagnosis:
