[chip-test] chip_sw_usbdev_pincfg
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Test point name
chip_sw_usbdev_pincfg
### Host side component
None
### OpenTitanTool infrastructure implemented
None
### Silicon Validation (SiVal)
Yes
### Emulation Targets
- [ ] None
- [X] CW310
- [X] Hyperdebug + CW310
### Contact person
alees24
### Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.
- [x] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
- [ ] Device-side (C) component developed
- [ ] Bazel build rules developed
- [ ] Host-side component developed
- [x] HJSON test plan updated with test name (so it shows up in the dashboard)
- [x] Test added to dvsim nightly regression (and passing at time of checking)
- [ ] For SiVal test cases, test is running relevant FPGA or silicon regression
Bazel target is //sw/device/tests:usbdev_pincfg_test and should work on all targets - DVsim, Verilator, CW FPGAs
Contributor guide
Research direction
Start with the //sw/device/tests:usbdev_pincfg_test target and review the existing test coverage referenced in the checklist. Implement the missing device-side C component and Bazel build rules, then verify that the target works on DVsim, Verilator, and CW FPGAs as stated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100