lowRISC / lowRISC/opentitan

[test-triage] chip_sw_pwrmgr_sleep_power_glitch_reset

Open
#24,377 1 comment 0 reactions 0 assignees View on GitHub
Component:TestTriage
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

The test started failing after the commit https://github.com/lowRISC/opentitan/commit/b5b4087210d18e313839ed5b3043c4804d4cbb13.

@rswarbrick as the author of the commit, could you please share your insights into the root cause?

### Hierarchy of regression failure

Chip Level

### Failure Description

* `UVM_ERROR @ * us: (rom_ctrl_fsm.sv:209) [ASSERT FAILED] SecCmCFILinear_A` has 3 failures:
* Test chip_sw_pwrmgr_sleep_power_glitch_reset has 3 failures.
* 0.chip_sw_pwrmgr_sleep_power_glitch_reset.34030237317708132276532455862227856016108686307012230113182261396102806932244\
Line 383, in log /root/git/opentitan/scratch/HEAD/chip_earlgrey_asic-sim-vcs/0.chip_sw_pwrmgr_sleep_power_glitch_reset/latest/run.log

UVM_ERROR @ 3314.677900 us: (rom_ctrl_fsm.sv:209) [ASSERT FAILED] SecCmCFILinear_A
UVM_INFO @ 3314.677900 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
--- UVM Report catcher Summary ---

### Steps to Reproduce

- GitHub Revision: [b5b408](https://github.com/lowRISC/opentitan/commit/b5b4087210d18e313839ed5b3043c4804d4cbb13)
- dvsim invocation command to reproduce the failure, inclusive of build and run seeds:
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_pwrmgr_sleep_power_glitch_reset

### Tests with similar or related failures

- [ ] chip_sw_pwrmgr_sleep_power_glitch_reset

Contributor guide

Open the contributing guide

Research direction

Start by checking commit b5b408 and reproduce with the provided dvsim command using hw/top_earlgrey/dv/chip_sim_cfg.hjson. Inspect the failure in the referenced run.log and rom_ctrl_fsm.sv:209, focusing on the SecCmCFILinear_A assertion during chip_sw_pwrmgr_sleep_power_glitch_reset. Done means identifying the regression cause and confirming the test no longer reports the assertion failure.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.