https://github.com/pegvin/ch32v003
Minimal CLI Oriented CH32V003 Build Environment (No CH32Fun)
https://github.com/pegvin/ch32v003
build-environment ch32v003
Last synced: 9 months ago
JSON representation
Minimal CLI Oriented CH32V003 Build Environment (No CH32Fun)
- Host: GitHub
- URL: https://github.com/pegvin/ch32v003
- Owner: pegvin
- Created: 2025-08-09T17:02:00.000Z (10 months ago)
- Default Branch: master
- Last Pushed: 2025-08-12T18:12:25.000Z (10 months ago)
- Last Synced: 2025-08-12T20:20:03.770Z (10 months ago)
- Topics: build-environment, ch32v003
- Language: C
- Homepage:
- Size: 109 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# CH32V003
Minimal CLI Oriented CH32V003 Build Environment (No CH32Fun)
---
## About
This repository provides a minimal cli-oriented build environment
for CH32V003 applications. This environment uses the [HAL provided
by WCH](https://www.wch.cn/downloads/CH32V003EVT_ZIP.html).
The `build.sh` script is responsible for building your code. By default
`build.sh` is configured to use [riscv-none-elf-gcc-xpack]()
toolchain (Assumed to be installed in `./toolchain`). You can run the
`./setup_toolchain.sh` script to install this toolchain in the appropriate
location or you can override the `TC` environment variable to point
to the `bin/` directory of your toolchain.
Using toolchains like `riscv-none-elf-gcc-xpack` means you cannot use
features like `WCH-Interrupt-fast` that are found in the proprietary
toolchain by WCH. If you wish to use the proprietary toolchain, You
can run `build-wch.sh` script instead. But before doing that you must
download the proprietary toolchain from
& Extract it to a location. You can then either update the `TC` variable
inside `build-wch.sh` or `TC` environment variable to point to your
toolchain's `bin/` directory.
Usage & Notes about `build.sh` (Applies to `build-wch.sh` as well):
1. If available, `ccache` is used to do incremental builds.
2. `./build.sh bear` can be run atleast once to generate a
`build/compile_commands.json` for clangd LSP.
3. `./build.sh flash` can be used to flash the code to your
MCU using the `wlink` tool.
4. `./build.sh serial` prints any data from `/dev/ttyACM0`.
- http://kofa.mmto.arizona.edu/usb/learn/acm.html
- https://rfc1149.net/blog/2013/03/05/what-is-the-difference-between-devttyusbx-and-devttyacmx/
You can also look into `.github/workflows/build.yml` to modify & use
GitHub Actions workflow for your own use. The default behavior sets up
the toolchain (caches it to speedup future builds), builds & uploads
the binaries as artifacts.
Other stuff that might be worth looking into:
-
-
## License
All the non-WCH code in this repository is under public domain license.
---
# Thanks