RT-Thread CH32V303 Test Report

Test Environment

Operating System Information

Source code link: https://github.com/Community-PIO-CH32V/ch32-pio-projects
Reference Installation Document:
- PlatformIO Core: https://docs.platformio.org/en/latest/core/installation/index.html
- PlatformIO CH32V: https://pio-ch32v.readthedocs.io/en/latest/installation.html

Hardware Information

CH32V303VCT6-EVT-R0-1v0
A USB to UART debugger
A WCH-Link(E)

Installation Steps

Install PlatformIO Core

You can first check if your package manager contains a package like platformio-core. If not, you can use the installation script:

curl -fsSL -o get-platformio.py https://raw.githubusercontent.com/platformio/platformio-core-installer/master/get-platformio.py
python3 get-platformio.py

PlatformIO Environment Configuration

Install CH32V development environment:

pio pkg install -g -p https://github.com/Community-PIO-CH32V/platform-ch32v.git

Add udev rules and apply them (you may need to change GROUP according to your distribution):

curl -fsSL https://raw.githubusercontent.com/platformio/platformio-core/develop/platformio/assets/system/99-platformio-udev.rules | sudo tee /etc/udev/rules.d/99-platformio-udev.rules
cat << EOF | sudo tee -a /etc/udev/rules.d/99-platformio-udev.rules
SUBSYSTEM=="usb", ATTR{idVendor}="1a86", ATTR{idProduct}=="8010", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}="4348", ATTR{idProduct}=="55e0", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}="1a86", ATTR{idProduct}=="8012", GROUP="plugdev"
EOF
sudo udevadm control --reload-rules
sudo udevadm trigger

Add user groups:

Debian-based:

sudo usermod -a -G dialout $USER
sudo usermod -a -G plugdev $USER

Arch-based:

sudo usermod -a -G uucp $USER
sudo usermod -a -G lock $USER

Prepare Project Repository

Clone the relevant repositories:

git clone https://github.com/Community-PIO-CH32V/platform-ch32v.git

Code Compilation

Compile the code using pio:

cd platform-ch32v/examples/hello-world-rt-thread
pio run

Flashing Image

After confirming that WCH-Link(E) is connected to the SWD debug port, use pio to flash the image:

pio run --target upload

If the flashing fails, you can try specifying manually:

pio run -e your_board --target upload

Add Development Board Series

Ignore this if you are using the FBP6 series This is because other chips are not in the default chip list, so we need to add them manually. You can find the corresponding json name for your board in platform-ch32v/boards.

cat << EOF | tee -a platformio.ini
[env:your_board]
board = your_board
EOF

FBP6 Flashing Issue

This is due to the debug pins of FBP6 being interconnected with UART, making it impossible to use the debug port when the chip is running a program that uses UART. See: WCH Official Post

To resolve this, WCH-LinkE needs to use nRST for flash erase, as detailed in the documentation: https://www.wch.cn/uploads/file/20230227/1677463712756616.pdf

Also, do not connect the serial port during flashing.

Common Issues

Error: error writing to flash at address 0x00000000 at offset 0x00000000
- This is due to a low firmware version of WCH-Link. (See important-notices).
- Please use the WCH-Link Utility Tool to connect once to update with CH-Link on W2. This tool is currently available only for Windows
Error: Read-Protect Status Currently Enabled
- This is caused by the chip’s write protection being enabled. On Windows, we can use the WCH-Link Utility Tool to disable protection, while on Linux, you can use OpenOCD:

cd ~/.platformio/packages/tool-openocd-riscv-wch/bin
./openocd -f wch-riscv.cfg -c init -c halt -c "flash protect wch_riscv 0 last  off " -c exit
cd -

Log into the System

Connect to the development board via serial port.

For FBP6 connection methods, refer to: WCH Official Post

Expected Results

The system should start up normally, and information should be viewable through the onboard serial port.

Actual Results

The system started up normally, and information was viewable through the onboard serial port.

Boot Log

Screen recording (from compilation to startup):

The MCU in the log below is incorrect due to the example hardcoding this string. Refer to main.c#L:65 From the DeviceID, it is evident that it is indeed running on the target board.

 \ | /
- RT -     Thread Operating System
 / | \     3.1.3 build Apr 25 2024
 2006 - 2019 Copyright by rt-thread team

 MCU: CH32V307
SystemClk:96000000
ChipID: 30520518
 www.wch.cn
msh >

Test Criteria

Successful: The actual result matches the expected result.

Failed: The actual result does not match the expected result.

Test Conclusion

Test successful.

System Version

Status

Last Update