[test-triage, darjeeling] chip_sw_sram_ctrl_scrambled_access
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Hierarchy of regression failure
Block level
### Failure Description
```
* `UVM_ERROR @ * us: (sw_logger_if.sv:526) [sram_ctrl_scrambled_access_test_sim_dv(sw/device/tests/sram_ctrl_scrambled_access_test.c:472)] CHECK-STATUS-fail: @@@:* = ErrorError` has 1 failures:
* Test chip_sw_sram_ctrl_scrambled_access has 1 failures.
* 0.chip_sw_sram_ctrl_scrambled_access.1\
Line 1540, in log /home/doreis/git/opentitan.git/master/scratch/master/chip_darjeeling_asic-sim-xcelium/0.chip_sw_sram_ctrl_scrambled_access/latest/run.log
UVM_ERROR @ 7236.366398 us: (sw_logger_if.sv:526) [sram_ctrl_scrambled_access_test_sim_dv(sw/device/tests/sram_ctrl_scrambled_access_test.c:472)] CHECK-STATUS-fail: @@@:0 = ErrorError
UVM_INFO @ 7236.366398 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
--- UVM Report catcher Summary ---
```
### Steps to Reproduce
- GitHub Revision: master
- dvsim invocation command to reproduce the failure, inclusive of build and run seeds:
```sh
util/dvsim/dvsim.py hw/top_darjeeling/dv/chip_sim_cfg.hjson --tool xcelium -v m --fi 1 -i chip_sw_sram_ctrl_scrambled_access
```
### Tests with similar or related failures
- [ ] chip_sw_sram_ctrl_scrambled_access
Contributor guide
Research direction
Run the provided util/dvsim/dvsim.py command with the Darjeeling chip simulation and Xcelium to reproduce the failure. Start at sw/device/tests/sram_ctrl_scrambled_access_test.c:472 and the referenced run.log line 1540, then trace the failing status check. Done means chip_sw_sram_ctrl_scrambled_access passes without the CHECK-STATUS failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100