lowRISC / lowRISC/opentitan

gpio_tl_intg_err test failing on Questa

Open
#22,755 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Description

Hi

I am trying to execute a GPIO test gpio_tl_intg_err test with Questa, The test fails, below is the output from log file

Compiling /tmp/farid@dsc007_dpi_3644952/linux_x86_64_gcc-7.4.0/exportwrapper.c
# Loading /tmp/farid@dsc007_dpi_3644952/linux_x86_64_gcc-7.4.0/vsim_auto_compile.so
do /home/idsproj01/trusted/projects/TrEB/Design/TReB_ASIC_01/_cad/Digital/user/farid/se-metis/hw/dv/tools/questa/sim.tcl
0
0
UVM_INFO @ 0 ps: reporter [RNTST] Running test gpio_base_test...
** Warning: (vsim-3829) Non-existent associative array entry. Returning default value.
   Time: 0 ps  Iteration: 54  Process: /cip_base_pkg::cip_base_scoreboard #(gpio_ral_pkg::gpio_reg_block, gpio_env_pkg::gpio_env_cfg, gpio_env_pkg::gpio_env_cov)::check_alerts/#FORK#259_7feff064a0d File: /home/idsproj01/trusted/projects/TrEB/Design/TReB_ASIC_01/_cad/Digital/user/farid/se-metis/scratch/48-dv-questa-questa-dvsim-run-breaking-at/gpio-sim-questa/cover_reg_top/sim-vcs/../src/lowrisc_dv_cip_lib_0/cip_base_scoreboard.sv Line: 260
UVM_INFO @         0 ps: (gpio_base_vseq.sv:36) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.gpio_common_vseq] weak pulldown applied to gpio's
** Warning: (vsim-3829) Non-existent associative array entry. Returning default value.
   Time: 16757 ps  Iteration: 2  Process: /cip_base_pkg::cip_base_scoreboard #(gpio_ral_pkg::gpio_reg_block, gpio_env_pkg::gpio_env_cfg, gpio_env_pkg::gpio_env_cov)::check_alerts/#FORK#259_7feff064a0d File: /home/idsproj01/trusted/projects/TrEB/Design/TReB_ASIC_01/_cad/Digital/user/farid/se-metis/scratch/48-dv-questa-questa-dvsim-run-breaking-at/gpio-sim-questa/cover_reg_top/sim-vcs/../src/lowrisc_dv_cip_lib_0/cip_base_scoreboard.sv Line: 260
UVM_INFO @   2665702 ps: (cip_base_vseq__tl_errors.svh:289) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.gpio_common_vseq] Running run_tl_intg_err_vseq 1/10
UVM_INFO @   5032344 ps: (cip_tl_seq_item.sv:121) uvm_test_top.env.m_tl_agent_gpio_reg_block.sequencer [uvm_test_top.env.virtual_sequencer.gpio_common_vseq.tl_seq.req] TL data or integrity bits have been flipped, see the changes as below:
	 a_data: 0x219ece5a
 -> 0x219eee42
UVM_ERROR @   5399007 ps: (cip_base_vseq.sv:595) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.gpio_common_vseq] expect alert:fatal_fault to fire
UVM_INFO @   5399007 ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER] 
--- UVM Report catcher Summary ---


Number of demoted UVM_FATAL reports  :    0
Number of demoted UVM_ERROR reports  :    0
Number of demoted UVM_WARNING reports:    0
Number of caught UVM_FATAL reports   :    0
Number of caught UVM_ERROR reports   :    0
Number of caught UVM_WARNING reports :    0

UVM_INFO @   5399007 ps: (uvm_report_server.svh:847) [UVM/REPORT/SERVER] 
--- UVM Report Summary ---

Quit count reached!
Quit count :     1 of     1
** Report counts by severity
UVM_INFO :    5
UVM_WARNING :    0
UVM_ERROR :    1
UVM_FATAL :    0

Can you please point us how can we solve this error, the error appears to be related to alerts in cip_base_scoreboard.sv, It looks like that element is not found on accessed index of associative array "expected_alert[]" in cip_base_scoreboard.sv hence a default value is being returned.

The test passes with xcelium....

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce gpio_tl_intg_err with Questa and compare its output with the passing Xcelium run. Inspect cip_base_scoreboard.sv around line 260 and cip_base_vseq.sv around line 595, focusing on expected_alert[] and the missing fatal_fault alert. Done means the test completes successfully under Questa with the expected alert observed.

Written by the indexing model from the issue text.

Assessment

Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.