#risc-v #wch #ch32v

no-std qingke

Low level access to WCH's QingKe RISC-V processors

18 releases

Uses new Rust 2024

0.6.1 Dec 8, 2025
0.5.0 Nov 3, 2024
0.2.0 May 11, 2024
0.1.9 Mar 27, 2024
0.1.0 Feb 19, 2023

#1079 in Embedded development

Download history 37/week @ 2025-12-25 61/week @ 2026-01-01 74/week @ 2026-01-08 53/week @ 2026-01-15 175/week @ 2026-01-22 104/week @ 2026-01-29 158/week @ 2026-02-05 35/week @ 2026-02-12 94/week @ 2026-02-19 122/week @ 2026-02-26 83/week @ 2026-03-05 225/week @ 2026-03-12 163/week @ 2026-03-19 218/week @ 2026-03-26 230/week @ 2026-04-02 223/week @ 2026-04-09

950 downloads per month
Used in 4 crates

MIT/Apache

19KB
387 lines

qingke & qingke-rt

Crates.io Crates.io docs.rs

Low level access to WCH's QingKe RISC-V processors.

qingke-rt

This crate provides the runtime support for QingKe RISC-V processors.

This provides riscv/riscv-rt like functionality, with the following differences:

  • Use vector table for interrupt handling
  • Handle 1KB address alignment for the entry point(Qingke V2)
  • In-SRAM code executing, highcode handling
  • PFIC support
  • Conflicts with riscv-rt crate

Usage

#[qingke_rt::entry]
fn main() -> ! {
    loop {}
}

// Or if you are using the embassy framework
#[embassy_executor::main(entry = "qingke_rt::entry")]
async fn main(spawner: Spawner) -> ! { ... }

#[qingke_rt::interrupt]
fn UART0() {
    // ...
}

#[qingke_rt::highcode]
fn some_highcode_fn() {
    // ...
    // This fn will be loaded into the highcode(SRAM) section.
    // This is required for BLE, recommended for interrupt handles.
}

Dependencies

~0.5–1MB
~21K SLoC