メニュー
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
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | embedded-test-hil |
| description | 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 |
Use this skill for the driver-level HIL track: Rust #[test] cases run on real WS63 silicon through
embedded-test, semihosting, hisi-riscv-rt, and hil/embedded-test-runner.sh. Do not use it for
example UART smoke; that is $hil-smoke.
crates/hisi-hal/tests/hil.rscrates/hisi-hal/tests/hil/<driver>.rshil/embedded-test-runner.shdocs/src/reference/10-stable-api.mddocs/src/how-to/07-run-hil-tests.mdpython3 .agents/skills/embedded-test-hil/scripts/hil_inventory.py
| Need | Location | Rule |
|---|---|---|
| HAL driver/API evidence | crates/hisi-hal/tests/hil.rs + tests/hil/<driver>.rs | Preferred path for stable API graduation |
| CPU/PAC/critical-section cross-cutting smoke | tests-hil/tests/hil.rs | Not tied to one HAL driver |
| Complete example image behavior | hil/hil-smoke.sh + example crate | Use $hil-smoke, not this skill |
crates/hisi-hal/tests/hil/<driver>.rs.#[path = "hil/<driver>.rs"] mod <driver>; lines in tests/hil.rs.#[embedded_test::tests] mod tests:#[cfg(feature = "chip-ws63")]
#[test]
fn wdt_leak_keeps_watchdog_armed() {
crate::wdt::wdt_leak_keeps_watchdog_armed();
}
#[cfg(feature = "unstable")] for tests that exercise unstable API.#[cfg(feature = "hil-loopback")] for jumper-required tests.#[cfg(feature = "hil-rtc")] for RTC crystal tests.docs/src/reference/10-stable-api.md in the same change.For detailed patterns and anti-patterns, read references/patterns.md.
Build the HAL test ELF only:
cargo test -Zbuild-std=core,alloc -p hisi-hal \
--no-default-features --features chip-ws63,rt \
--target riscv32imfc-unknown-none-elf \
--test hil --no-run
Run on real WS63:
PROBE_YAML=/path/HiSilicon_WS63.yaml \
CARGO_TARGET_RISCV32IMFC_UNKNOWN_NONE_ELF_RUNNER=hil/embedded-test-runner.sh \
cargo test -Zbuild-std=core,alloc -p hisi-hal \
--no-default-features --features chip-ws63,rt \
--target riscv32imfc-unknown-none-elf \
--test hil
Filter one test:
PROBE_YAML=/path/HiSilicon_WS63.yaml \
CARGO_TARGET_RISCV32IMFC_UNKNOWN_NONE_ELF_RUNNER=hil/embedded-test-runner.sh \
cargo test -Zbuild-std=core,alloc -p hisi-hal \
--no-default-features --features chip-ws63,rt \
--target riscv32imfc-unknown-none-elf \
--test hil -- wdt_leak_keeps_watchdog_armed
Run cross-cutting tests-hil:
PROBE_YAML=/path/HiSilicon_WS63.yaml \
CARGO_TARGET_RISCV32IMFC_UNKNOWN_NONE_ELF_RUNNER=hil/embedded-test-runner.sh \
cargo test -Zbuild-std=core,alloc -p tests-hil --target riscv32imfc-unknown-none-elf
SAFETY: comment and leave the peripheral in a known state.--test hil is used; bare cargo test --target riscv32imfc... builds the host libtest target and is wrong here.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").
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.
Build a ws63-rs example for a HiSilicon chip (ws63/bs21/bs21e/bs22/bs20) and boot it in the hisi-riscv-qemu fork, asserting the expected UART banner / GPIO toggle / embassy interleave / IRQ delivery. Use to validate firmware end-to-end in emulation, or after touching a driver/example/the QEMU model.