VeRForTe
← Back to CH32V208-EVT
LiteOS on CH32V208-EVT

System Version

Not specified

Status

basic

Last Update

2025-03-03

LiteOS CH32V208 Test Report

Test Environment

The test environment is Ubuntu 22.04.5 LTS

Operating System Information

Hardware Information

  • CH32V208WBU6-EVT-R0-1v4
  • A USB to UART Debugger (not required, WCH-Link or WCH-LinkE can be used instead)
  • A WCH-Link or WCH-LinkE

Installation Steps

Install PlatformIO Core

Install using an installation script (PlatformIO installed with apt lacks some features such as pkg)

Before installing PlatformIO, install Python and the Python virtual environment (venv)

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

Try wget if you have network problems

wget -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 (may need to change GROUP according to the 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:

  • For Debian-based systems:
sudo usermod -a -G dialout $USER
sudo usermod -a -G plugdev $USER
  • For Arch-based systems:
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-harmony-liteos
pio run

The output when the compilation is successful

Building .pio/build/genericCH32L103C8T6/firmware.bin
========================= [SUCCESS] Took 1.76 seconds =========================

Environment          Status    Duration
-------------------  --------  ------------
genericCH32V103C8T6  SUCCESS   00:00:01.559
genericCH32V203K8T6  SUCCESS   00:00:01.630
genericCH32V208CBU6  SUCCESS   00:00:01.462
ch32v307_evt         SUCCESS   00:00:01.639
genericCH32V303CBT6  SUCCESS   00:00:01.632
genericCH32V305FBP6  SUCCESS   00:00:01.666
genericCH32V307WCU6  SUCCESS   00:00:01.551
genericCH32X035C8T6  SUCCESS   00:00:01.786
genericCH32L103C8T6  SUCCESS   00:00:01.758
========================= 9 succeeded in 00:00:14.682 =========================

Flashing Image

After confirming the connection of WCH-Link(E) to the SWD debug port (P6 pin header of the official EVT development board), manually specify the development board using pio and burn the image:

pio run -e genericCH32V208CBU6 --target upload

(The test confirmed that the CH32V208CBU6 example can be successfully run on the CH32V208WBU6 chip of the official EVT development board)

The output information when the image is successfully burned

[wch_riscv.cpu.0] Target successfully examined.
** Programming Started **
** Programming Finished **
** Verify Started **
** Verified OK **
** Resetting Target **
shutdown command invoked
========================= [SUCCESS] Took 7.61 seconds =========================

Environment          Status    Duration
-------------------  --------  ------------
genericCH32V208CBU6  SUCCESS   00:00:07.610
========================= 1 succeeded in 00:00:07.610 =========================

Common Issues

  • Error: error writing to flash at address 0x00000000 at offset 0x00000000
    • This is due to the low firmware version of WCH-Link. (See important-notices).
    • Please use WCH-Link Utility to connect once with WCH-Link to update automatically. This tool currently only has a Windows version.
  • Error: Read-Protect Status Currently Enabled
    • This is caused by the write protection enabled on the chip. On Windows, we can use WCH-Link Utility to remove the protection, and on Linux, OpenOCD can be used:
    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 -
  • Error: Can not install PlatformIO Core due to a missed venv module in your Python installation.
    • Missing Python-venv package, install venv of the corresponding python version (3.10 as example) :
    sudo apt-get install python3.10-venv

Logging into the System

Connect to the development board via serial port. If it is an official EVT development board, the P6 pin header are also connected.

Expected Results

The system starts normally, and information can be viewed via the onboard serial port.

Actual Results

The system starts normally, and information can be viewed via the onboard serial port.

Boot Log

SystemClk:96000000
ChipID:2080051c
entering kernel init...
Entering scheduler
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry2 running,task2 SP:200023d4
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry2 running,task2 SP:200023d4
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry1 running,task1 SP:20001ecc
taskSampleEntry2 running,task2 SP:200023d4

Test Criteria

Successful: The actual result matches the expected result.

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

Test Conclusion

Test successful.

Source: Support Matrix