An open source development "environment" for the CH32V003 with gcc-riscv64 that can be used in Windows, Linux and/or WSL. The CH32V003 is 10-cent part with a RISC-V EC core that runs at 48MHz, has 16kB of flash and 2kB of RAM and a bunch of peripherals. It also comes in SOP-8, QFN-20 and SOIC packages. You can get the datasheet here.
The goal of this project is to develop the tooling and environment for efficient use of the CH32V003. This means making it possible to have basic projects that are compact and require no proprietary tooling like their MounRiver Studio(MRS).
The existing EVT is massive. Just to boot the chip at all, it requires ~2kB of support functions and has to do things like software-divides and use a ton of space at startup to use their HAL. This project specifically avoids the HAL and makes it so you can just use the TRM.
In contrast, blinky is only 500 bytes with ch32v003fun, boots faster, and significantly simpler overall.
As it currently stands it is still designed to use the WCH-Link to do the SDIO programming. Though I would like to ALSO support an open source programmer.
ch32v003fun contains:
- Examples using ch32v003fun, but not as many as using the HAL.
- "minichlink" which uses the WCH CH-Link with libusb, for cross-platform use.
- An extra copy of libgcc so you can use unusual risc-v build chains, located in the
misc/libgcc.a. - A folder named "ch32v003fun" containing a single self-contained source file and header file for compling apps for the ch32v003.
- On some systems ability to "printf" back through
- A demo bootloader.
In Progress:
- Other programmer support (ESP32-S2 works, currently)
- OpenOCD-compatible build for
minichlink. - Full-chip-write for faster flash.
- Support for
NHC-Link042 - Write more demos.
And by fast I mean very fast. Typically around 36kBytes/sec.
./minichlink -T | pv > /dev/null
Found ESP32S2 Programmer
536KiB 0:00:15 [36.7KiB/s] [ <=> ]
You can just try out the debugprintf project, or call SetupDebugPrintf(); and printf() away.
On WSL or Debian based OSes apt-get install build-essential libnewlib-dev gcc-riscv64-unknown-elf libusb-1.0-0-dev libudev-dev
On Windows, download and install (to system) this copy of GCC10. https://gnutoolchains.com/risc-v/
You can use the pre-compiled minichlink or
cd examples/blink
make
In Linux this will "just work" using the minichlink. In Windows if you want to use minichlink, you will need to use Zadig to install WinUSB to the WCH-Link interface 0.
In Windows, you can use this or you can use the WCH-LinkUtility to flash the built hex file.
It enumerates as 2 interfaces. 0. the programming interface. I can't get anything except the propreitary interface to work.
- the usb serial port built in.
If you want to mess with the programming code in Windows, you will have to install WinUSB to the interface 0. Then you can uninstall it in Device Manager under USB Devices.
To use the WCH-Link in WSL, it is required to "attach" the USB hardware on the Windows side to WSL. This is achieved using a tool called usbipd.
- On windows side, install the following MSI https://github.com/dorssel/usbipd-win/releases
- Install the WSL side client:
- For Debian:
sudo apt-get install usbip hwdata usbutils - For Ubuntu (not tested):
- For Debian:
sudo apt install linux-tools-5.4.0-77-generic linux-tools-virtual hwdata usbutils
sudo update-alternatives --install /usr/local/bin/usbip usbip `ls /usr/lib/linux-tools/*/usbip | tail -n1` 20
- Plug in the WCH-Link to USB
- Run Powershell as admin and use the
usbipd listcommand to list all connected devices - Find the this device:
1a86:8010 WCH-Link (Interface 0)and note the busid it is attached to - In powershell, use the command
usbipd wsl attach --busid=<BUSID>to attach the device at the busid from previous step - You will hear the windows sound for the USB device being removed (and silently attached to WSL instead)
- In WSL, you will now be able to run
lsusband see that the SCH-Link is attached - For unknown reasons, you must run make under root access in order to connect to the programmer with minichlink. Recommend running
sudo makewhen building and programming projects using WSL Feel free to solve this issue and figure out a way to give the user hardware access to WCH-Link and modify these instructions.
I wrote some libusb copies of some of the basic functionality from WCH-Link, so you can use the little programmer dongle they give you to program the ch32v003.
Currently, it ignores all the respone codes, except when querying the chip. But it's rather surprising how featured I could get in about 5 hours.
Anyone who wants to write a good/nice utility should probably look at the code in this folder.
This project can also be built, uploaded and debugged with VSCode and the PlatformIO extension. Simply clone and open this project in VSCode and have the PlatformIO extension installed.
See here for further details.
- Needed for programming/debugging:
SWIOis onPD1 - Optional (not needed, can be configured as output if fuse set):
NRSTis onPD7 - UART TX (optional) is on:
PD5
You can open a github ticket or join my Discord in the #ch32v003fun channel. https://discord.gg/CCeyWyZ
- https://raw.githubusercontent.com/openwch/ch32v003/main/RISC-V%20QingKeV2%20Microprocessor%20Debug%20Manual.pdf Debugging Manual
- http://www.wch-ic.com/downloads/QingKeV2_Processor_Manual_PDF.html Processor Manual
- http://www.wch-ic.com/downloads/CH32V003RM_PDF.html Technical Reference Manual
- http://www.wch-ic.com/downloads/CH32V003DS0_PDF.html Datasheet