Since ST create a lot of barriers and obstacles for STM32 chinese clones development (clone stlink dongle + cs32f1 bluepill), one cannot benefit from ST provided mainstream STM32CubeIDE + one click ready to use gdb debugger with Eclipse frontend + integrated CubeMX. I experimented with a lot of ways to find the easiest + fastest way to working with STM32 chinese clones. This is the way that I found.
- Smarter code linting thanks to
"ms-vscode.cpptools"
extension - Far quicker startup time thanks to VSCode's lightweight
- Enable boilerplate code generation thanks to CubeMX
- Enable interactive debug using
"marus25.cortex-debug"
For debug build:
# Generate Makefile
cmake -B Debug -DCMAKE_BUILD_TYPE=Debug -G "Unix Makefiles"
# Building using cmake
cmake --build Debug -j <nproc>
# Clean project
cmake --build Debug --target clean
For release build:
# Generate Makefile
cmake -B Release -DCMAKE_BUILD_TYPE=Release -G "Unix Makefiles"
# Building using cmake
cmake --build Release -j <nproc>
# Clean project
cmake --build Release --target clean
You can open .mxproject to reconfigure and regenerate code as expected.