메뉴
Build, check, lint, and test the ws63-rs embedded HAL for HiSilicon WS63 (RISC-V). Use when asked to build, verify, run checks, or test hisi-hal, ws63-pac, or any crate in this workspace.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Maintain hisi-hal register access through SVD/PAC truth sources. Use when changing HAL MMIO/register code, reviewing raw PAC usage, fixing check-register-access CI failures, adding or correcting SVD/PAC fields/access types, regenerating ws63-pac or bs2x-pac, deciding whether a register should be modeled in SVD versus handled in HAL, or auditing read/modify/write behavior for write-only or dynamically masked registers.
Commit + push changes that span ws63-rs git submodules in dependency order, then bump the parent repo's submodule pointers. Use when you've edited files inside one or more submodules (ws63-pac/hal/rt/examples/guide, chips/ws63/rf/ws63-RF, ws63-pac/ws63-svd) and need to land them correctly.
Make a hisi-hal driver's CONFIG surface "if it compiles, it runs on silicon" — design, review, or tighten a Config / new() / configure() so a value you can WRITE is a value that RUNS, with no parameter that compiles but is silently clamped, truncated, left without a clock, or dependent on an unenforced precondition. Use when adding a driver, reviewing/PR-ing a config API, tightening one for the 0.5.0 config pass, or diagnosing a "compiles but wrong/dead on hardware" bug. Applies the project's primary API convention (see root Agent Instructions "Typed config").
Create, modify, audit, build, or run on-target embedded-test HIL tests for hisi-hal and tests-hil. Use when adding HAL driver silicon evidence, writing crates/hisi-hal/tests/hil/*.rs cases, registering
Diagnose a HIL CI failure on real WS63/BS2X silicon — compare the failed CI run against the last passing run, identify whether the regression is caused by a code change, toolchain update, or rig issue, and output a triage report. Use when a HIL CI job fails on the main branch or a PR.
Build a ws63-rs example for a HiSilicon chip, flash it to a REAL board via the repo HIL flash path, read UART, and assert the example marker — the silicon twin of qemu-smoke. Use for example-level hardware smoke; HAL driver-level evidence uses embedded-test via hil/embedded-test-runner.sh instead.
| name | run-ws63-rs |
| description | Build, check, lint, and test the ws63-rs embedded HAL for HiSilicon WS63 (RISC-V). Use when asked to build, verify, run checks, or test hisi-hal, ws63-pac, or any crate in this workspace. |
Paths below are relative to the repo root, a Cargo workspace with ws63-pac,
hisi-hal, hisi-riscv-rt, ws63-examples/blinky, and ws63-flashboot.
ws63-rs builds with the official upstream Rust nightly pinned in
rust-toolchain.toml. The WS63 target is riscv32imfc-unknown-none-elf
(RV32IMFC, hardware single-float ilp32f, no atomics). rustc knows this target,
but rustup does not ship a prebuilt std component for it yet, so RISC-V builds use
-Zbuild-std=core,alloc. The default target is set in .cargo/config.toml.
Install the pinned toolchain first:
rustup toolchain install nightly-2026-07-09 \
--profile minimal \
--component rust-src \
--component clippy \
--component rustfmt \
--component llvm-tools-preview
The hisi-riscv-rust-toolchain repo is now the upstream nightly radar, not the
default custom rustc install path.
bash .agents/skills/run-ws63-rs/driver.sh all # check + fmt + clippy + blinky build
bash .agents/skills/run-ws63-rs/driver.sh check # cargo check + doc + blinky release build
bash .agents/skills/run-ws63-rs/driver.sh fmt # cargo fmt --check
bash .agents/skills/run-ws63-rs/driver.sh clippy # cargo clippy
All steps target riscv32imfc-unknown-none-elf (the config default). blinky is built
for real in release (it links — the dual-PAC bug is fixed and hisi-riscv-rt exports its linker
scripts to downstream bins).
cargo build -Zbuild-std=core,alloc # default-members: libs + blinky
cargo check -Zbuild-std=core,alloc --workspace # everything incl. flashboot
cargo clippy -Zbuild-std=core,alloc --workspace -- -D warnings
cargo fmt --all -- --check
cargo build -Zbuild-std=core,alloc -p ws63-flashboot --release # experimental flashboot
cargo doc -Zbuild-std=core,alloc -p hisi-hal -p ws63-pac -p hisi-riscv-rt --no-deps
# Output: target/riscv32imfc-unknown-none-elf/doc/hisi_hal/index.html
In-binary unit tests (#[cfg(test)]) cannot run on the host: hisi-hal contains RISC-V
inline asm (e.g. asm!("ebreak")), so the crate does not compile for an x86 host. They
are compile-checked only as part of cargo check. Running real host unit tests requires
cfg-gating the riscv asm (ROADMAP phase 2). On-silicon validation is ROADMAP phase 1.
-Zbuild-std=core,alloc
or rust-src usually shows up as "can't find crate for core".Cargo.toml [patch.crates-io] redirects the
ws63-pac registry dep to the local submodule. Don't add a second ws63-pac source.ws63-pac/src/lib.rs is svd2rust-generated — do not hand-edit it (a PreToolUse
hook blocks edits). Change ws63-svd/WS63.svd and regenerate (ROADMAP phase 2).submodule-commit skill.git submodule update --init --recursive if you get missing-manifest errors.| Symptom | Fix |
|---|---|
can't find crate for core | Install rust-src and pass -Zbuild-std=core,alloc for RISC-V commands |
failed to load manifest for workspace member | git submodule update --init --recursive |
error[E0463]: can't find crate for proc_macro2 (fresh CI) | Stale cross-toolchain target/ cache — don't cache target/ across toolchains |
clippy FAILED | cargo clippy -Zbuild-std=core,alloc --workspace -- -D warnings to see warnings |
formatting FAILED | cargo fmt --all to auto-fix (a PostToolUse hook also auto-formats .rs on edit) |
blinky link error __*_stack_top__ undefined | ensure hisi-riscv-rt is up to date (it exports ws63-link.x for downstream bins) |