PY32F0 MCU CMake project template. Using GCC, cross-platform. You can use VSCode, CLion, etc. for development.
This project is in its early stage and may have many bugs or areas that are incomplete.
Most of the information for this project comes from Puya Semiconductor. Puya Semiconductor's information is in a semi-public state, and I have collected data such as chip manuals and libraries from various sources. Please refer to:
HAL, LL, CMSIS, BSP Drivers decaday/PY32F0_Drivers
Datasheets, packs, reference manuals, etc. decaday/PY32_Docs
GCC startup and ldscript are from IOsetting/py32f0-template (this repo uses makefile on Linux), thanks to the contributors to that project.
Puya PY32F002B
Xinlinggo XL32F001*, XL32F002B*
Puya PY32F002A, PY32F003, PY32F030
Xinlinggo XL32F003*, XL32F002A*
Luat AIR001
Puya PY32F040, PY32F(M)070*, PY32F071, PY32F072
*:Guessing based on chip specifications, haven’t tried it yet.
**:There are too many naming approaches for puya MCU, some MCUs such as PY32L020, PY32C613, etc. I didn't buy these chips, if you have them, please contribute relevant information. You can try above series with the same flash, ram, and clock speed, which may work because they are most likely produced from the same die.
Downloads | GNU Arm Embedded Toolchain Downloads – Arm Developer
Choose the appropriate package for your system and add bin to your environment variable (if you use the installer, it may have already been added automatically).
git clone --recursive https://github.com/decaday/py32f0_cmake_template.git
This repo has a submodule, so you need to add --recursive.
For convenience, the configuration is done using an overriding method here.
set(ENABLE_HAL_DRIVER ON CACHE BOOL "Enable HAL driver")
set(ENABLE_LL_DRIVER OFF CACHE BOOL "Enable LL driver")
set(ENABLE_SYSTEM_XXX_C ON CACHE BOOL "Enable system_XXX.c")
set(ENABLE_STARTUP_FILE ON CACHE BOOL "Enable startup file")
set(ENABLE_LD_SCRIPT ON CACHE BOOL "Enable linker script")
set(ENABLE_DEBUG_DEFINE ON CACHE BOOL "Enable debug define")
set(MCU_MODEL "PY32F030x6" CACHE STRING "MCU model, like PY32F030x6")You can also delete these lines, modify the CMakeCache.txt file, or use GUI tools or an IDE to configure these settings.
Puya's MCU naming can be a bit cumbersome, for example, PY32F002AF15P6TU.
PY32F002A is the Product type, F1 is the 20 pins Pinout1, 5 is 20 Kbytes of code, P is Package TSSOP, 6 is Temperature range 6 = -40 to +85, TU is Tube Packing.
Therefore, you need to choose PY32F002Ax5.
If you are using AIR001, you can choose PY32F030x6. If you are using XL32, please choose the appropriate settings based on the core and flash size.
Below are all the supported MCU models:
PY32F002Ax5
PY32F002Bx5
PY32F003x4, PY32F003x6, PY32F003x8
PY32F030x4, PY32F030x6, PY32F030x7, PY32F030x8
I have written a script in CMake to automatically generate Misc/pyocd.yaml. For more information about debugging, please see below.
You can use IDEs like VSCode, CLion, or compile from the command line.
Puya has several ISP tools and official debuggers. You can find some information about them here: decaday/PY32_Docs. However, in reality, we can use a regular DAPlink. I don't have STlink or Jlink, but contributions to the documentation are welcome.
You can use the following tools for debugging:
The Py32-specific version of OpenOCD can be found in the GCC support package on the Puya official website.
- CLion: OpenOCD is supported natively.
- VSCode: Use the Cortex-Debug extension to work with OpenOCD.
probe-rs supports Py32 and can be used within VSCode for debugging.
- CLion: PyOCD is supported; you can refer to Clion PyOCD Configure.
- VSCode: Use the Cortex-Debug extension to work with PyOCD.
Note: While using PyOCD for debugging Py32, I often encounter inexplicable issues, such as: Breakpoints not being hit. Random hard faults after powering on.
If you face similar issues, consider trying another debugging tool.
The examples are under ‘Drivers/Examples’. You need to copy the files to the outside to run and debug. These examples are from Puya, using scripts to delete the MDK project related files. You may need to make slight modifications to run normally.
| Compiler | MCU | Project | RAM | FLASH |
|---|---|---|---|---|
| GCC -Og -g | F030 | HAL Toggle Pin | 1584 B | 1720 B |
| GCC -Og -g | F030 | LL Toggle Pin | 1568 B | 1156 B |
| GCC -Og -g | F002B | HAL Toggle Pin | 816 B | 1736 B |
| GCC -O1 | F030 | HAL Toggle Pin | 1584 B | 1692 B |
| MDK ARMCC6 -O1 | F030 | HAL Toggle Pin | 1240 B* | 1448 B* |
| MDK ARMCC6 -O1 | F030 | LL Toggle Pin | 1224 B* | 912 B* |
*RAM = ZI-data + RW-data
*Flash = Code + RO-data + RW-data
GCC:12.2mpacbti-rel1 ARMCC:v6.19
| code | Flash memory |
|---|---|
| 3 | 8 Kbytes |
| 4 | 16 Kbytes |
| 5 | 20/24 Kbytes |
| 6 | 32 Kbytes |
| 8 | 64 Kbytes |
| 9 | 96 Kbytes |
| B | 128 Kbytes |