Skip to content

[rstmgr,dv] Reset Manager DV ported to mocha#506

Open
KolosKoblasz-Semify wants to merge 6 commits into
lowRISC:mainfrom
KolosKoblasz-Semify:kk_rst_mgr_dv
Open

[rstmgr,dv] Reset Manager DV ported to mocha#506
KolosKoblasz-Semify wants to merge 6 commits into
lowRISC:mainfrom
KolosKoblasz-Semify:kk_rst_mgr_dv

Conversation

@KolosKoblasz-Semify
Copy link
Copy Markdown
Collaborator

@KolosKoblasz-Semify KolosKoblasz-Semify commented Apr 29, 2026

This PR ports Reset Manager Controller DV code from Opentitan to Mocha.

This PR will address: #433 --- Close #433

Project specific tests:

dvsim hw/top_chip/ip_autogen/rstmgr/dv/rstmgr_sim_cfg.hjson -i all --cov

Test Results

Stage Name Tests Max Job Runtime Simulated Time Passing Total Pass Rate
V1 smoke rstmgr_smoke 3.000s 146.644us 50 50 100.00 %
V1 csr_hw_reset rstmgr_csr_hw_reset 2.000s 111.996us 5 5 100.00 %
V1 csr_rw rstmgr_csr_rw 2.000s 57.904us 20 20 100.00 %
V1 csr_bit_bash rstmgr_csr_bit_bash 6.000s 837.419us 5 5 100.00 %
V1 csr_aliasing rstmgr_csr_aliasing 2.000s 141.699us 5 5 100.00 %
V1 csr_mem_rw_with_rand_reset rstmgr_csr_mem_rw_with_rand_reset 2.000s 97.203us 20 20 100.00 %
V1 regwen_csr_and_corresponding_lockable_csr rstmgr_csr_rw 2.000s 57.904us 20 20 100.00 %
V1 regwen_csr_and_corresponding_lockable_csr rstmgr_csr_aliasing 2.000s 141.699us 5 5 100.00 %
V1 TOTAL 105 105 100.00 %
V2 reset_stretcher rstmgr_por_stretcher 2.000s 193.769us 50 50 100.00 %
V2 sw_rst rstmgr_sw_rst 3.000s 112.860us 50 50 100.00 %
V2 sw_rst_reset_race rstmgr_sw_rst_reset_race 2.000s 100.244us 50 50 100.00 %
V2 reset_info rstmgr_reset 7.000s 1213.694us 50 50 100.00 %
V2 cpu_info rstmgr_reset 7.000s 1213.694us 50 50 100.00 %
V2 alert_info rstmgr_reset 7.000s 1213.694us 50 50 100.00 %
V2 reset_info_capture rstmgr_reset 7.000s 1213.694us 50 50 100.00 %
V2 stress_all rstmgr_stress_all 45.000s 11561.703us 50 50 100.00 %
V2 alert_test rstmgr_alert_test 2.000s 50.306us 50 50 100.00 %
V2 tl_d_oob_addr_access rstmgr_tl_errors 3.000s 220.485us 20 20 100.00 %
V2 tl_d_illegal_access rstmgr_tl_errors 3.000s 220.485us 20 20 100.00 %
V2 tl_d_outstanding_access rstmgr_csr_hw_reset 2.000s 111.996us 5 5 100.00 %
V2 tl_d_outstanding_access rstmgr_csr_rw 2.000s 57.904us 20 20 100.00 %
V2 tl_d_outstanding_access rstmgr_csr_aliasing 2.000s 141.699us 5 5 100.00 %
V2 tl_d_outstanding_access rstmgr_same_csr_outstanding 3.000s 109.090us 20 20 100.00 %
V2 tl_d_partial_access rstmgr_csr_hw_reset 2.000s 111.996us 5 5 100.00 %
V2 tl_d_partial_access rstmgr_csr_rw 2.000s 57.904us 20 20 100.00 %
V2 tl_d_partial_access rstmgr_csr_aliasing 2.000s 141.699us 5 5 100.00 %
V2 tl_d_partial_access rstmgr_same_csr_outstanding 3.000s 109.090us 20 20 100.00 %
V2 TOTAL 370 370 100.00 %
V2S tl_intg_err rstmgr_sec_cm 9.000s 4812.555us 5 5 100.00 %
V2S tl_intg_err rstmgr_tl_intg_err 3.000s 1004.412us 20 20 100.00 %
V2S prim_count_check rstmgr_sec_cm 9.000s 4812.555us 5 5 100.00 %
V2S prim_fsm_check rstmgr_sec_cm 9.000s 4812.555us 5 5 100.00 %
V2S sec_cm_bus_integrity rstmgr_tl_intg_err 3.000s 1004.412us 20 20 100.00 %
V2S sec_cm_scan_intersig_mubi rstmgr_sec_cm_scan_intersig_mubi 3.000s 78.230us 50 50 100.00 %
V2S sec_cm_leaf_rst_bkgn_chk rstmgr_leaf_rst_cnsty 4.000s 492.027us 24 50 48.00 %
V2S sec_cm_leaf_rst_shadow rstmgr_leaf_rst_shadow_attack 2.000s 70.779us 50 50 100.00 %
V2S sec_cm_leaf_fsm_sparse rstmgr_sec_cm 9.000s 4812.555us 5 5 100.00 %
V2S sec_cm_sw_rst_config_regwen rstmgr_csr_rw 2.000s 57.904us 20 20 100.00 %
V2S sec_cm_dump_ctrl_config_regwen rstmgr_csr_rw 2.000s 57.904us 20 20 100.00 %
V2S TOTAL 169 195 86.67 %
TOTAL 594 620 95.81 %

Coverage Results

Coverage Dashboard

TOTAL BLOCK LINE/STATEMENT BRANCH TOGGLE FSM ASSERTION FUNCTIONAL
94.58 % 94.78 % 94.67 % 90.47 % 96.99 % 72.11 % 97.21 % 97.96 %

Failure Buckets

  • UVM_FATAL (rstmgr_leaf_rst_cnsty_vseq.sv:159) [rstmgr_leaf_rst_cnsty_vseq] Timeout waiting for alert fatal_cnsty_fault has 26 failures:
    • Test rstmgr_leaf_rst_cnsty has 26 failures.
      • 0.rstmgr_leaf_rst_cnsty.3893774066561404286679873924707946454294933251846102894542716694214554564731
        Line 105, in log /home/kkoblasz/projects/mocha/scratch/kk_rst_mgr_dv/rstmgr.sim.xcelium/0.rstmgr_leaf_rst_cnsty/latest/run.log

          UVM_INFO @ 149854063 ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
          --- UVM Report catcher Summary ---
        
      • 2.rstmgr_leaf_rst_cnsty.112716547968608135960797656090285886938387398042950550123403654793875186327527
        Line 107, in log /home/kkoblasz/projects/mocha/scratch/kk_rst_mgr_dv/rstmgr.sim.xcelium/2.rstmgr_leaf_rst_cnsty/latest/run.log

          UVM_INFO @ 149876627 ps: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
          --- UVM Report catcher Summary ---
        
      • ... and 24 more failures.

        [ legend ]: [S: scheduled, Q: queued, R: running, P: passed, F: failed, K: killed, T: total]
        00:01:14 [ build ]: [S: 000, Q: 000, R: 000, P: 002, F: 000, K: 000, T: 002] 100%
        00:02:38 [ run ]: [S: 000, Q: 000, R: 000, P: 594, F: 026, K: 000, T: 620] 100%
        00:03:12 [ cov_merge ]: [S: 000, Q: 000, R: 000, P: 001, F: 000, K: 000, T: 001] 100%
        00:03:19 [ cov_report ]: [S: 000, Q: 000, R: 000, P: 001, F: 000, K: 000, T: 001] 100%

Top level tests:
dvsim hw/top_chip/dv/mocha_sim_cfgs.hjson --select-cfgs rstmgr -i smoke --cov

Test Results

Stage Name Tests Max Job Runtime Simulated Time Passing Total Pass Rate
V1 smoke rstmgr_smoke 1.000s 76.585us 1 1 100.00 %
V1 csr_hw_reset rstmgr_csr_hw_reset 2.000s 102.736us 1 1 100.00 %
V1 csr_rw rstmgr_csr_rw 1.000s 57.474us 1 1 100.00 %
V1 regwen_csr_and_corresponding_lockable_csr rstmgr_csr_rw 1.000s 57.474us 1 1 100.00 %
V1 TOTAL 3 3 100.00 %
V2 tl_d_outstanding_access rstmgr_csr_hw_reset 2.000s 102.736us 1 1 100.00 %
V2 tl_d_outstanding_access rstmgr_csr_rw 1.000s 57.474us 1 1 100.00 %
V2 tl_d_partial_access rstmgr_csr_hw_reset 2.000s 102.736us 1 1 100.00 %
V2 tl_d_partial_access rstmgr_csr_rw 1.000s 57.474us 1 1 100.00 %
V2 TOTAL 2 2 100.00 %
V2S sec_cm_sw_rst_config_regwen rstmgr_csr_rw 1.000s 57.474us 1 1 100.00 %
V2S sec_cm_dump_ctrl_config_regwen rstmgr_csr_rw 1.000s 57.474us 1 1 100.00 %
V2S TOTAL 1 1 100.00 %
TOTAL 3 3 100.00 %

Coverage Results

Coverage Dashboard

TOTAL BLOCK LINE/STATEMENT BRANCH TOGGLE FSM ASSERTION FUNCTIONAL
70.37 % 86.08 % 85.15 % 74.59 % 92.83 % 17.69 % 90.82 % 52.72 %

TOP_MOCHA_BATCH_SIM Simulation Results (Summary)

Tuesday May 26 2026 08:04:01 UTC

Github Revision: 351f095

Branch: kk_rst_mgr_dv

Name Passing Total Pass Rate Coverage
RSTMGR 3 3 100.00 % 70.37 %
      [   legend    ]: [S: scheduled, Q: queued, R: running, P: passed, F: failed, K: killed, T: total]                                                                                          

00:00:06 [ build ]: [S: 0, Q: 0, R: 0, P: 2, F: 0, K: 0, T: 2] 100%
00:00:08 [ run ]: [S: 0, Q: 0, R: 0, P: 3, F: 0, K: 0, T: 3] 100%
00:00:11 [ cov_merge ]: [S: 0, Q: 0, R: 0, P: 1, F: 0, K: 0, T: 1] 100%
00:00:16 [ cov_report ]: [S: 0, Q: 0, R: 0, P: 1, F: 0, K: 0, T: 1] 100%

@martin-velay martin-velay changed the title Reset Manager DV ported to mocha [rstmgr,dv] Reset Manager DV ported to mocha Apr 29, 2026
- files_rtl
- files_dv
default_tool: vcs
default_tool: xcelium
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the source of your issue with the src file being not generated. The .src file is your file list generated from FuseSoc. I know that confusing, I went into this trap earlier too.
The VCS backend generates a .scr file, which is an identical format to a more standard .f format. We are only running FuseSoc up to the point it generates the filelist file (.scr in this case).

@KolosKoblasz-Semify KolosKoblasz-Semify force-pushed the kk_rst_mgr_dv branch 6 times, most recently from d7f29db to 7d337b2 Compare May 5, 2026 11:14
// Wait till rst_lc_n is inactive for non-aon.
`DV_WAIT(cfg.rstmgr_vif.resets_o.rst_lc_n[1])
// Wait till rst_por_aon_n is inactive for non-aon.
`DV_WAIT(cfg.rstmgr_vif.resets_o.rst_por_aon_n[1])
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be the same reset as the one fed into the reset manager block in the top which is rst_por_io_n

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In rstmgr.sv line 351 constant zero is assigned to it:

Image

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The assignment happens here: rstmgr.sv#L340

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably makes sense to switch rst_*lc* with rst_por_io_n everywhere (and Marno agrees as well).

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, but then it is DomainAonSel right?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rst_lc_n[1] -> rst_por_io_n[1] so this is going to be Domain0Sel?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, DomainAonSel is 0, Domain0Sel is 1.

@KolosKoblasz-Semify KolosKoblasz-Semify force-pushed the kk_rst_mgr_dv branch 3 times, most recently from a5c3e8f to 3d667b7 Compare May 8, 2026 09:33
Copy link
Copy Markdown
Collaborator

@marnovandermaas marnovandermaas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments from my end.

- `CASCADED_ASSERTS(CascadeLcToLc, rst_lc_src_n[rstmgr_pkg::Domain0Sel],
- resets_o.rst_lc_n[rstmgr_pkg::Domain0Sel], SysCycles, clk_main_i)
-
- // Controlled by rst_sys_src_n.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few resets controlled by SYS SRC in Mocha, such as rst_{main,io,spi_device,spi_host,i2c}_n

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to investigate whether we should have cascade asserts for those.

else:
assert 0, "No preferred clock available"

-preferred_rst_n = f"rst_lc_{preferred_domain}_n"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we just update the preferred domain? This also fixes the power on reset preference below.

Comment thread hw/top_chip/ip_autogen/rstmgr/dv/sva/rstmgr_cascading_sva_if.sv Outdated
@martin-velay
Copy link
Copy Markdown
Contributor

Is it ready to be re-reviewed?

@KolosKoblasz-Semify
Copy link
Copy Markdown
Collaborator Author

Is it ready to be re-reviewed?

Yes it is ready for a final review.
For some reason the FPGA tests don't even start

Run actions/cache@v5
  with:
    path: build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.bit
  build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.runs/impl_1/chip_mocha_genesys2_utilization_placed.rpt
  
    fail-on-cache-miss: true
    enableCrossOsArchive: false
    lookup-only: false
    save-always: false
  env:
    BITSTREAM: build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.bit
    UTILIZATION_FILE: build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.runs/impl_1/chip_mocha_genesys2_utilization_placed.rpt
    TMPDIR: /home/runner/_work/_temp
Error: Input required and not supplied: key

@elliotb-lowrisc
Copy link
Copy Markdown
Contributor

For some reason the FPGA tests don't even start

Run actions/cache@v5
  with:
    path: build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.bit
  build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.runs/impl_1/chip_mocha_genesys2_utilization_placed.rpt
  
    fail-on-cache-miss: true
    enableCrossOsArchive: false
    lookup-only: false
    save-always: false
  env:
    BITSTREAM: build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.bit
    UTILIZATION_FILE: build/lowrisc_mocha_chip_mocha_genesys2_0/synth-vivado/lowrisc_mocha_chip_mocha_genesys2_0.runs/impl_1/chip_mocha_genesys2_utilization_placed.rpt
    TMPDIR: /home/runner/_work/_temp
Error: Input required and not supplied: key

I think I had a similar issue which was resolved by rebasing onto the latest origin/main

@KinzaQamar KinzaQamar marked this pull request as ready for review May 14, 2026 10:46
@KinzaQamar
Copy link
Copy Markdown
Contributor

Some notes for reviewers:

As we don't have Lifecycle control in Mocha, all the relevant LC related resets are replace with the following mapping:

rst_lc_aon_n[Domain0Sel] to rst_por_io_n[Domain0Sel]
rst_lc_aon_n[DomainAonSel] to rst_por_io_n[DomainAonSel]

rst_lc_n[DomainAonSel] to rst_por_io_n[DomainAonSel]
rst_lc_n[Domain0Sel] to rst_io_n[Domain0Sel]

rst_lc_io_n[DomainAonSel] to rst_por_io_n[DomainAonSel]
rst_lc_io_n[Domain0Sel] to rst_io_n[Domain0Sel]

LC related Cascaded Asserts are removed from rstmgr_cascading_sva_if. I worked out if we can replace them with relevant resets but I found some assertions already present in rstmgr_cascading_sva_if (example: CascadeEffAonToRstPorIo) that will work.

For CascadeSysToSys assertion in rstmgr_cascading_sva_if, this is replace by the assertions below as rst_sys_src_n can assert rst_{main,io,spi_device,spi_host,i2c}_n in mocha.

  `CASCADED_ASSERTS(CascadeSysToMain_A, rst_sys_src_n[rstmgr_pkg::Domain0Sel],
                    resets_o.rst_main_n[rstmgr_pkg::Domain0Sel], PeriCycles, clk_main_i)

  `CASCADED_ASSERTS(CascadeSysToIO_A, rst_sys_src_n[rstmgr_pkg::Domain0Sel],
                    resets_o.rst_io_n[rstmgr_pkg::Domain0Sel], PeriCycles, clk_io_i)

  `CASCADED_ASSERTS(CascadeSysToSpiHosts_A, rst_sys_src_n[rstmgr_pkg::Domain0Sel],
                    resets_o.rst_spi_host_n[rstmgr_pkg::Domain0Sel], PeriCycles, clk_io_i)

  `CASCADED_ASSERTS(CascadeSysToSpiDevice_A, rst_sys_src_n[rstmgr_pkg::Domain0Sel],
                    resets_o.rst_spi_device_n[rstmgr_pkg::Domain0Sel], PeriCycles, clk_io_i)

  `CASCADED_ASSERTS(CascadeSysToI2C_A, rst_sys_src_n[rstmgr_pkg::Domain0Sel],
                    resets_o.rst_i2c_n[rstmgr_pkg::Domain0Sel], PeriCycles, clk_io_i)

`CASCADED_ASSERTS(CascadeSysToIO_A, rst_sys_src_n[rstmgr_pkg::Domain0Sel],
resets_o.rst_io_n[rstmgr_pkg::Domain0Sel], PeriCycles, clk_io_i)

`CASCADED_ASSERTS(CascadeSysToSpiHosts_A, rst_sys_src_n[rstmgr_pkg::Domain0Sel],
Copy link
Copy Markdown
Contributor

@KinzaQamar KinzaQamar May 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace CascadeSysToSpiHosts_A with CascadeSysToSPIHost_A as SPI is a abbreviation and there is only one SPI Host

@KinzaQamar
Copy link
Copy Markdown
Contributor

KinzaQamar commented May 15, 2026

@engdoreis / @machshev Do you know what is wrong with the fpga-cache-check job?

@engdoreis
Copy link
Copy Markdown
Collaborator

engdoreis commented May 15, 2026

@engdoreis / @machshev Do you know what is wrong with the fpga-cache-check job?

It's because the nix app that computes the bitstream hash is failing with the following error:

fusesoc --cores-root=. run --target=synth --setup lowrisc:mocha:chip_mocha_genesys2
ERROR: Failed to resolve dependencies. Conflicting requirements:
Requirements: 'lowrisc_mocha_chip_mocha_genesys2 == 0-0' <- 'lowrisc_prim_xilinx_all >= 0-0'
    +lowrisc_mocha_chip_mocha_genesys2-0-0 was ignored because it depends on missing packages
Requirements: 'lowrisc_mocha_chip_mocha_genesys2 == 0-0'
    Install command rule (+lowrisc_mocha_chip_mocha_genesys2-0-0)

I opened a PR improving the logs.

@KolosKoblasz-Semify
Copy link
Copy Markdown
Collaborator Author

KolosKoblasz-Semify commented May 18, 2026

@engdoreis / @machshev Do you know what is wrong with the fpga-cache-check job?

It's because the nix app that computes the bitstream hash is failing with the following error:

fusesoc --cores-root=. run --target=synth --setup lowrisc:mocha:chip_mocha_genesys2
ERROR: Failed to resolve dependencies. Conflicting requirements:
Requirements: 'lowrisc_mocha_chip_mocha_genesys2 == 0-0' <- 'lowrisc_prim_xilinx_all >= 0-0'
    +lowrisc_mocha_chip_mocha_genesys2-0-0 was ignored because it depends on missing packages
Requirements: 'lowrisc_mocha_chip_mocha_genesys2 == 0-0'
    Install command rule (+lowrisc_mocha_chip_mocha_genesys2-0-0)

I opened a PR improving the logs.

And how could be the root problem resolved?
I mean what are these version mismatches and how should I fix them? Actually who should fix them?

@elliotb-lowrisc
Copy link
Copy Markdown
Contributor

Sorry @KolosKoblasz-Semify, I meant to reply to your comment, no edit it. I'll try to revert it. Here is my comment:

And how could be the root problem resolved?

Looks like it is because the Xilinx prims got removed by commit 771b9f0 of this PR

Comment thread hw/vendor/lowrisc_ip.vendor.hjson Outdated
// Primitives.
{from: "hw/ip/prim", to: "ip/prim", patch_dir: "prim"},
{from: "hw/ip/prim_generic", to: "ip/prim_generic"},
{from: "hw/ip/prim_xilinx", to: "ip/prim_xilinx", patch_dir: "prim_xilinx"},
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your issue might come from here, why have you deleted this line?

@KolosKoblasz-Semify KolosKoblasz-Semify force-pushed the kk_rst_mgr_dv branch 3 times, most recently from f56675d to a554a9b Compare May 21, 2026 07:05
@KolosKoblasz-Semify KolosKoblasz-Semify marked this pull request as draft May 21, 2026 09:20
 * open titan specific paths changed to mocha specific ones
   in the template files
 * 0001_Fix_Paths_And_Tools.patch file created with the changes
 * rstmgr_cascading_sva_if.sv.tpl updated with new domain names

Signed-off-by: Kolos Koblasz <kolos.koblasz@semify-eda.com>
 * The patched config and template config files
   added to the source code

Signed-off-by: Kolos Koblasz <kolos.koblasz@semify-eda.com>
 * rstmgr added to hw/top_chip/dv/mocha_sim_cfgs.hjson

Signed-off-by: Kolos Koblasz <kolos.koblasz@semify-eda.com>
 * 0002 patch fixes the auto generated
   reset manager's dv files therefore enabling
   block level simulations to be run

Signed-off-by: Kolos Koblasz <kolos.koblasz@semify-eda.com>
 * These modifications will enable to run
   block level simulations on rstmgr
   while using correct reset signals and domains
   in the UVM tb.

Signed-off-by: Kolos Koblasz <kolos.koblasz@semify-eda.com>
 * These modifications will enable to run
   block level simulations on autogenerated rstmgr
   while using correct reset signals and domains
   in the UVM tb.

 * Both source and testbench files regenerated

Signed-off-by: Kolos Koblasz <kolos.koblasz@semify-eda.com>
@KolosKoblasz-Semify KolosKoblasz-Semify marked this pull request as ready for review May 26, 2026 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reset Manager DV - Block-level env to be imported from OT

6 participants