Add 13 missing issues and 1 missing patch

#7
.gitattributes CHANGED
@@ -805,3 +805,4 @@ Repos/HWE/agents/Lingxi/docs/Lingxi[[:space:]]Technical[[:space:]]Report[[:space
805
  Repos/HWE/agents/Lingxi/docs/Lingxi[[:space:]]v1.5[[:space:]]Technical[[:space:]]Report[[:space:]]200725.pdf filter=lfs diff=lfs merge=lfs -text
806
  Repos/HWE/agents/Lingxi/docs/Lingxi[[:space:]]v2.0[[:space:]]Technical[[:space:]]Report[[:space:]]2026.pdf filter=lfs diff=lfs merge=lfs -text
807
  Repos/HWE/agents/Lingxi/imgs/overview_fig.pdf filter=lfs diff=lfs merge=lfs -text
 
 
805
  Repos/HWE/agents/Lingxi/docs/Lingxi[[:space:]]v1.5[[:space:]]Technical[[:space:]]Report[[:space:]]200725.pdf filter=lfs diff=lfs merge=lfs -text
806
  Repos/HWE/agents/Lingxi/docs/Lingxi[[:space:]]v2.0[[:space:]]Technical[[:space:]]Report[[:space:]]2026.pdf filter=lfs diff=lfs merge=lfs -text
807
  Repos/HWE/agents/Lingxi/imgs/overview_fig.pdf filter=lfs diff=lfs merge=lfs -text
808
+ patches/esa-tu-darmstadt_tapasco_pr105.patch filter=lfs diff=lfs merge=lfs -text
issues/OpenPOWERFoundation_a2o_pr18 ADDED
@@ -0,0 +1,31 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Fix uncompliant begin in generate blocks
2
+
3
+ Instance: OpenPOWERFoundation_a2o_pr18
4
+ Source: https://github.com/OpenPOWERFoundation/a2o/pull/18
5
+ Fetched: 2026-04-26
6
+ Repository: OpenPOWERFoundation/a2o
7
+ Pull request: #18
8
+ Author: flaviens
9
+ State: closed
10
+ Base branch: master
11
+ Head branch: fix_begin_genvar
12
+ Created: 2022-10-26T08:57:01Z
13
+ Updated: 2022-11-30T00:04:25Z
14
+ Closed: 2022-11-30T00:04:25Z
15
+ Merged: 2022-11-30T00:04:25Z
16
+
17
+ Hi there!
18
+
19
+ This fixes [this Verilog uncompliance issue](https://github.com/pulp-platform/morty/issues/50).
20
+
21
+ Thanks!
22
+ Flavien
23
+
24
+ ## Local Reproducer Notes
25
+
26
+ OpenPOWERFoundation/a2o PR 18 reproducer.
27
+
28
+ The reduced module keeps the PR's generate-block compliance issue observable
29
+ as a design output while also exercising normal sequential behavior. The buggy
30
+ snapshot represents an unconditional `generate begin`; the patch changes it to
31
+ the compliant `generate if (1) begin` form and raises the compliance output.
issues/alexforencich_verilog-pcie_pr19 ADDED
@@ -0,0 +1,40 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Fix multi-driven net issue when S_RAM_SEL_WIDTH = 0
2
+
3
+ Instance: alexforencich_verilog-pcie_pr19
4
+ Source: https://github.com/alexforencich/verilog-pcie/pull/19
5
+ Fetched: 2026-04-26
6
+ Repository: alexforencich/verilog-pcie
7
+ Pull request: #19
8
+ Author: Basseuph
9
+ State: closed
10
+ Base branch: master
11
+ Head branch: mle/fix_multi_net_driver
12
+ Created: 2021-12-10T16:52:24Z
13
+ Updated: 2021-12-10T20:56:16Z
14
+ Closed: 2021-12-10T20:47:04Z
15
+ Merged: 2021-12-10T20:47:04Z
16
+
17
+ ## PR Title
18
+ Fix multi-driven net issue when S_RAM_SEL_WIDTH = 0
19
+
20
+ ## PR Description
21
+ As per a discussion on slack we built a corundum design with a single interface and multiple ports and there were actually two issues. One was fixed already, see 3a124837115e51e2273ab7d1c61d80ee01f891c1 in verilog-pcie. A very similar one was still to be fixed and this PR now proposes the respective fix.
22
+
23
+ The PR adapts the same fix that was already applied to the `dma_ram_demux_rd.v` module to the `dma_ram_demux_wr.v` module.
24
+
25
+ ## PR Comments
26
+
27
+ **Basseuph** (Dec 10, 2021):
28
+ The submitter's initial message explained the context and referenced a similar fix that had already been applied to the `dma_ram_demux_rd.v` module, noting this PR adapts that same solution to the `dma_ram_demux_wr.v` module.
29
+
30
+ **alexforencich** (Dec 10, 2021):
31
+ "LGTM" (looks good to me)
32
+
33
+ **alexforencich** (Dec 10, 2021):
34
+ "dang it, I thought I selected the right option to avoid the merge commit. I guess I need to clean that up..."
35
+
36
+ **alexforencich** (Dec 10, 2021):
37
+ "I just pulled it directly from your branch; I'll get this merged into Corundum shortly. Also, I recommend adding your MLE email address to your github profile so your commits will link back to your github account."
38
+
39
+ ## Linked Issues
40
+ No linked issues are referenced in this pull request.
issues/chipsalliance_caliptra-rtl_pr757 ADDED
@@ -0,0 +1,30 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # [RTL] AXI Sub Arb fix. Add recovery inf synchros. Export trace signals. Move SS dbg unlock reg to pwrgood.
2
+
3
+ Instance: chipsalliance_caliptra-rtl_pr757
4
+ Source: https://github.com/chipsalliance/caliptra-rtl/pull/757
5
+ Fetched: 2026-04-26
6
+ Repository: chipsalliance/caliptra-rtl
7
+ Pull request: #757
8
+ Author: calebofearth
9
+ State: closed
10
+ Base branch: msft-daily-20250226
11
+ Head branch: cwhitehead-msft-axi-sub-fix
12
+ Created: 2025-02-26T06:10:12Z
13
+ Updated: 2025-02-27T07:10:02Z
14
+ Closed: 2025-02-27T07:09:58Z
15
+ Merged: 2025-02-27T07:09:58Z
16
+
17
+ AXI Sub Arb fix.
18
+ * Resolves #753
19
+
20
+ Add synchronizers to input signals from subsystem recovery interface.
21
+ Export RISC-V trace signals for debug.
22
+ Move SS dbg unlock level reg to pwrgood so it's sticky and persists across warm resets without having to redo the debug unlock flow.
23
+
24
+ ## Local Reproducer Notes
25
+
26
+ # chipsalliance_caliptra-rtl_pr757
27
+
28
+ Minimal fail-to-pass Verilator case for the AXI subordinate arbiter priority fix.
29
+
30
+ The buggy arbiter does not keep write priority while a held final write beat is still in progress, allowing a later read to steal the component interface. The patch keeps priority for any in-progress transfer.
issues/efabless_clear_pr20 ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Cocotb updates
2
+
3
+ Instance: efabless_clear_pr20
4
+ Source: https://github.com/efabless/clear/pull/20
5
+ Fetched: 2026-04-26
6
+ Repository: efabless/clear
7
+ Pull request: #20
8
+ Author: M0stafaRady
9
+ State: closed
10
+ Base branch: RTL-dev
11
+ Head branch: cocotb-dev
12
+ Created: 2023-04-05T10:01:26Z
13
+ Updated: 2023-04-05T10:01:43Z
14
+ Closed: 2023-04-05T10:01:43Z
15
+ Merged: 2023-04-05T10:01:43Z
16
+
17
+ - Develop script to get the hierarchy of the programming chain
18
+ - Add test for counter
19
+
20
+ ## Local Reproducer Notes
21
+
22
+ efabless/clear PR 20 reproducer.
23
+
24
+ The reduced RTL keeps the GPIO power-on macro touched by the PR and exposes
25
+ the decoded GPIO 3 pull configuration as signals. The buggy snapshot powers
26
+ GPIO 3 up with the management pulldown setting; the patch changes it to the
27
+ management pullup setting expected by the cocotb update.
issues/hdl-util_hdmi_pr12 ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Source tweaks for clean compilation on Verilator
2
+
3
+ Instance: hdl-util_hdmi_pr12
4
+ Source: https://github.com/hdl-util/hdmi/pull/12
5
+ Fetched: 2026-04-26
6
+ Repository: hdl-util/hdmi
7
+ Pull request: #12
8
+ Author: jamesbowman
9
+ State: closed
10
+ Base branch: master
11
+ Head branch: master
12
+ Created: 2020-07-17T20:58:39Z
13
+ Updated: 2020-07-18T01:06:15Z
14
+ Closed: 2020-07-18T01:06:15Z
15
+ Merged: 2020-07-18T01:06:15Z
16
+
17
+ Hi Sameer, I'm working on a verification testbench for your HDMI code base.
18
+ This first commit makes some small syntax changes to get to clean build with Verilator and Icarus Verilog.
19
+
20
+ The next steps are:
21
+ * a testbench that dumps the 3 x 10 bit TMDS values for N clocks
22
+ * a stream analyzer that verifies HDMI against the spec and the settings
issues/lowRISC_ibex_pr1821 ADDED
@@ -0,0 +1,31 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # [dv] Add MHPM Counter number param to SpikeCosim
2
+
3
+ Instance: lowRISC_ibex_pr1821
4
+ Source: https://github.com/lowRISC/ibex/pull/1821
5
+ Fetched: 2026-04-26
6
+ Repository: lowRISC/ibex
7
+ Pull request: #1821
8
+ Author: ctopal
9
+ State: closed
10
+ Base branch: master
11
+ Head branch: mhpmcounter_spikecosim
12
+ Created: 2022-09-28T16:20:26Z
13
+ Updated: 2022-10-11T14:52:49Z
14
+ Closed: 2022-10-11T14:52:42Z
15
+ Merged: 2022-10-11T14:52:42Z
16
+
17
+ This commit adds another field in SpikeCosim class so that Spike can hardcode the correct event registers.
18
+
19
+ Signed-off-by: Canberk Topal <ctopal@lowrisc.org>
20
+
21
+ Needs: https://github.com/lowRISC/riscv-isa-sim/pull/17
22
+
23
+ Resolves https://github.com/lowRISC/ibex/issues/1820
24
+
25
+ ## Local Reproducer Notes
26
+
27
+ # lowRISC_ibex_pr1821
28
+
29
+ Minimal fail-to-pass Verilator case for passing the MHPM counter count into the Spike cosim checker.
30
+
31
+ The buggy checker ignores the configured MHPM counter count. The patch forwards it to the observable cosim creation configuration.
issues/lowRISC_opentitan_pr28469 ADDED
@@ -0,0 +1,27 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # [hw,pinmux,rtl] Remove sys reset when no strap sampling
2
+
3
+ Instance: lowRISC_opentitan_pr28469
4
+ Source: https://github.com/lowRISC/opentitan/pull/28469
5
+ Fetched: 2026-04-26
6
+ Repository: lowRISC/opentitan
7
+ Pull request: #28469
8
+ Author: Razer6
9
+ State: closed
10
+ Base branch: master
11
+ Head branch: pinmux-sys-reset
12
+ Created: 2025-10-11T22:52:30Z
13
+ Updated: 2025-10-13T14:44:34Z
14
+ Closed: 2025-10-13T14:44:33Z
15
+ Merged: 2025-10-13T14:44:33Z
16
+
17
+ The sys reset in pinmux is only needed for the strap sampling logic. Since that feature is gated behind an ipgen parameter, also gate the reset with this flag and remove it for Darjeeling.
18
+
19
+ Closes https://github.com/lowRISC/opentitan/issues/25410
20
+
21
+ ## Local Reproducer Notes
22
+
23
+ # lowRISC_opentitan_pr28469
24
+
25
+ Minimal fail-to-pass Verilator case for removing the sys reset dependency from pinmux strap sampling.
26
+
27
+ The buggy pinmux clears the sampled strap when `rst_sys_ni` is asserted low even though strap sampling should only depend on the primary reset. The patch ignores the sys reset for the sampled strap state.
issues/pulp-platform_carfield_pr27 ADDED
@@ -0,0 +1,48 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # hw: Bump security island
2
+
3
+ Instance: pulp-platform_carfield_pr27
4
+ Source: https://github.com/pulp-platform/carfield/pull/27
5
+ Fetched: 2026-05-03
6
+ Repository: pulp-platform/carfield
7
+ Pull request: #27
8
+ Author: alex96295
9
+ State: closed
10
+ Base branch: main
11
+ Head branch: aottaviano/synth-fix
12
+ Created: 2023-05-09
13
+ Updated: 2023-07-21
14
+ Closed: 2023-05-09
15
+ Merged: 2023-05-09
16
+
17
+ ## PR Title
18
+ hw: Bump security island
19
+
20
+ ## PR Description
21
+ Remove behavioral string parameters: use combinational ROM and OTP. Fixes #26.
22
+
23
+ ## PR Comments
24
+
25
+ **alex96295** (May 9, 2023):
26
+ "Remove behavioral string parameters: use combinational ROM and OTP" / "Fixes #26"
27
+
28
+ **alex96295** (May 9, 2023):
29
+ Added the bug label.
30
+
31
+ **alex96295** (May 9, 2023):
32
+ Self-assigned the PR.
33
+
34
+ **alex96295** (May 9, 2023):
35
+ Requested review from luca-valente as code owner.
36
+
37
+ **alex96295** (May 9, 2023):
38
+ Merged commit 37d82b5 into main.
39
+
40
+ **micprog** (Jul 21, 2023):
41
+ Deleted the aottaviano/synth-fix branch.
42
+
43
+ ## Linked Issues
44
+
45
+ **Issue #26: SYNTHESIS ERROR**
46
+ Line 294 and 295 of carfield_pkg generate synthesis errors:
47
+ "Error: ...carfield_pkg.sv:294: The construct 'string' is not supported in synthesis."
48
+ "Error: ...carfield_pkg.sv:295: The construct 'string' is not supported in synthesis."
issues/pulp-platform_cheshire_pr189 ADDED
@@ -0,0 +1,35 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # hw: Fix uncached SPM execute region
2
+
3
+ Instance: pulp-platform_cheshire_pr189
4
+ Source: https://github.com/pulp-platform/cheshire/pull/189
5
+ Fetched: 2026-04-26
6
+ Repository: pulp-platform/cheshire
7
+ Pull request: #189
8
+ Author: paulsc96
9
+ State: closed
10
+ Base branch: main
11
+ Head branch: paulsc/spmu-ex
12
+ Created: 2025-03-28T11:57:58Z
13
+ Updated: 2025-04-13T18:42:51Z
14
+ Closed: 2025-04-13T18:42:50Z
15
+ Merged: 2025-04-13T18:42:50Z
16
+
17
+ Fixes #188.
18
+
19
+ Changes:
20
+
21
+ * Add uncached SPM as its own executable region (simplify parameterization a bit in the process)
22
+ * Add a test `spm_uncached` executing from uncached SPM and verifying it is not cached
23
+
24
+ Additional changes:
25
+
26
+ * Add argument to DMA calls to enable dynamic use of decoupling flags (this breaks DMA API compatibility)
27
+ * Add `wfi` to default trap handler (this quiets core on exceptions, including on unhandled `ebreak`)
28
+
29
+ ## Local Reproducer Notes
30
+
31
+ # pulp-platform_cheshire_pr189
32
+
33
+ Minimal fail-to-pass Verilator case for the uncached SPM execute region fix.
34
+
35
+ The buggy configuration models cached and uncached SPM as one large executable region. The patch creates an explicit `AmSpmUnc` region and exposes cached and uncached SPM as separate execute rules.
issues/pulp-platform_cheshire_pr203 ADDED
@@ -0,0 +1,31 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # treewide: Update iDMA and fix 1D transfers
2
+
3
+ Instance: pulp-platform_cheshire_pr203
4
+ Source: https://github.com/pulp-platform/cheshire/pull/203
5
+ Fetched: 2026-04-26
6
+ Repository: pulp-platform/cheshire
7
+ Pull request: #203
8
+ Author: alex96295
9
+ State: closed
10
+ Base branch: main
11
+ Head branch: aottaviano/dma
12
+ Created: 2025-05-07T12:48:47Z
13
+ Updated: 2025-07-08T20:06:36Z
14
+ Closed: 2025-07-08T20:06:35Z
15
+ Merged: 2025-07-08T20:06:35Z
16
+
17
+ * [x] Move DMA to Regbus, simplifying interconnect and fixing a known issue with accessing beyond 32-bit boundary
18
+ * [x] Fix DMA HAL for 1D transfers (currently not working)
19
+ * [x] Update iDMA
20
+ * [x] Add new regression test for 1D transfers to CI (https://iis-git.ee.ethz.ch/pulp-restricted/cheshire-nonfree/-/merge_requests/22)
21
+ * [x] Fix #208.
22
+ * [x] Add new regression test for accesses beyond 32-bit boundary (access over serial link)
23
+
24
+ ## Local Reproducer Notes
25
+
26
+ pulp-platform/cheshire PR 203 reproducer.
27
+
28
+ The reduced RTL models the 1D DMA programming path through the AXI-to-register
29
+ adapter. The buggy snapshot instantiates the legacy adapter, which gates a
30
+ valid register write with test mode and drops the one-cycle start command.
31
+ The patch switches the wrapper to the v2 adapter interface used by the PR.
issues/pulp-platform_register_interface_pr23 ADDED
@@ -0,0 +1,40 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Add simple error slave
2
+
3
+ Instance: pulp-platform_register_interface_pr23
4
+ Source: https://github.com/pulp-platform/register_interface/pull/23
5
+ Fetched: 2026-04-26
6
+ Repository: pulp-platform/register_interface
7
+ Pull request: #23
8
+ Author: Vyeow
9
+ State: closed
10
+ Base branch: master
11
+ Head branch: feature/err_slv
12
+ Created: 2022-10-31T14:59:41Z
13
+ Updated: 2022-11-02T08:03:34Z
14
+ Closed: 2022-11-02T08:03:26Z
15
+ Merged: 2022-11-02T08:03:26Z
16
+
17
+ PR Title: Add simple error slave
18
+
19
+ PR #23 (Merged November 2, 2022)
20
+
21
+ Author: Vyeow
22
+ Merged by: meggiman
23
+
24
+ Description:
25
+ The PR description was minimal. Vyeow noted that "req_i is not needed in the module, but thought it a good idea to keep it for cosmetic reasons."
26
+
27
+ Review Comments:
28
+
29
+ meggiman's Initial Feedback (Nov 1, 2022):
30
+
31
+ 1. Metadata files: Contributor requested updates to Bender.yml and src_files.yml to register the error slave module.
32
+
33
+ 2. Type parameter suggestion: Proposed adding a `payload_t` type parameter defaulting to `logic[DW-1:0]` to support packed struct payloads, noting: "the error slave cannot be used as is" without this flexibility.
34
+
35
+ 3. Parameter defaults: Recommended using `-1` as the default for DW to discourage using modules "without explicitly specifying the parameter values."
36
+
37
+ 4. Error value defaults: Suggested changing to `'0` as default, stating users should "explicitly choose which error value they want to return."
38
+
39
+ Resolution:
40
+ Vyeow implemented the requested changes in a second commit. Meggiman approved with "lgtm. Thanks a lot!" and merged the PR on November 2, 2022, subsequently deleting the feature branch.
issues/taichi-ishitani_tvip-axi_pr36 ADDED
@@ -0,0 +1,46 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # add null check to avoid null pointer exception
2
+
3
+ Instance: taichi-ishitani_tvip-axi_pr36
4
+ Source: https://github.com/taichi-ishitani/tvip-axi/pull/36
5
+ Fetched: 2026-05-03
6
+ Repository: taichi-ishitani/tvip-axi
7
+ Pull request: #36
8
+ Author: taichi-ishitani
9
+ State: closed
10
+ Base branch: master
11
+ Head branch: fix_35
12
+ Created: 2022-05-19
13
+ Updated: 2022-05-19
14
+ Closed: 2022-05-19
15
+ Merged: 2022-05-19
16
+
17
+ ## PR Title
18
+ add null check to avoid null pointer exception
19
+
20
+ ## PR Description
21
+ "This PR is to fix #35."
22
+
23
+ The change adds a null-check guard so that the slave driver does not dereference a null sequence-item handle when it is reset partway through a transaction; the issue had been reported as a NULL pointer dereference in `uvm_transaction::get_event_pool` triggered by `tue_sequence_item_base::get_event` / `ended` being called from `tvip_axi_slave_driver`'s start-delay thread after a mid-transaction reset.
24
+
25
+ ## PR Comments
26
+ **taichi-ishitani** (May 19, 2022): "This PR is to fix #35." (Author/owner; this is the only conversation entry, posted at submission time.)
27
+
28
+ No code-review comments were posted; the PR was self-merged by taichi-ishitani at commit e2d29ef. The branch `fix_35` was deleted shortly after merge.
29
+
30
+ ## Linked Issues
31
+ **Issue #35 - "Another NULL pointer dereference after reset in the middle"** (closed by this PR).
32
+
33
+ Issue body (verbatim from the source URL):
34
+ "The latest version has another NULL pointer dereference as below:
35
+ ```
36
+ xmsim: *E,TRNULLID: NULL pointer dereference.
37
+ File: /opt/eda/cadence/XCELIUM2103/tools/methodology/UVM/CDNS-1.2/sv/src/base/uvm_transaction.svh, line = 521, pos = 14
38
+ Scope: worklib.uvm_pkg::uvm_transaction::get_event_pool
39
+ Time: 7134 NS + 13
40
+ Verilog Stack Trace:
41
+ 0: function worklib.uvm_pkg::uvm_transaction::get_event_pool at /opt/eda/cadence/XCELIUM2103/tools/methodology/UVM/CDNS-1.2/sv/src/base/uvm_transaction.svh:521
42
+ 1: function worklib.tue_pkg::tue_sequence_item_base#(uvm_pkg::uvm_sequence_item,tvip_axi_pkg::tvip_axi_configuration,tvip_axi_pkg::tvip_axi_status,tvip_axi_pkg::tvip_axi_configuration,tvip_axi_pkg::tvip_axi_status)::get_event at /path/to/tvip-axi/tue/src/seq/tue_sequence_item_base.svh:41
43
+ 2: function worklib.tue_pkg::tue_sequence_item_base#(uvm_pkg::uvm_sequence_item,tvip_axi_pkg::tvip_axi_configuration,tvip_axi_pkg::tvip_axi_status,tvip_axi_pkg::tvip_axi_configuration,tvip_axi_pkg::tvip_axi_status)::ended at /path/to/tvip-axi/tue/src/seq/tue_sequence_item_base.svh:51
44
+ 3: task worklib.tvip_axi_pkg::tvip_axi_slave_driver_start_delay_consumer@13753_2.delay_thread at /path/to/tvip-axi/src/tvip_axi_slave_driver.svh:66
45
+ 4: process in worklib.tvip_axi_pkg::tvip_axi_slave_driver_start_delay_consumer@13753_2.start_delay_thread.unmblk1 at /path/to/tvip-axi/src/tvip_axi_slave_driver.svh:48
46
+ ```"
issues/taichi-ishitani_tvip-axi_pr47 ADDED
@@ -0,0 +1,50 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Problem with On the Fly Reset
2
+
3
+ - Source URL: https://github.com/taichi-ishitani/tvip-axi/issues/46
4
+
5
+ Hi @taichi-ishitani ! I have a problem when i have reset on AXI.
6
+ In my test I have AXI4 slave and DUT.
7
+ When i asserted reset the BValid, Bid not reset to zero.
8
+ The figure below
9
+ ![1_problem](https://user-images.githubusercontent.com/35744340/209571013-9d82fc3e-18c5-40e0-9aba-e40201c0ee53.jpg)
10
+
11
+ So i find the problem. I think it happened because of race conditions
12
+ https://github.com/taichi-ishitani/tvip-axi/blob/master/src/tvip_axi_slave_driver.svh#L524
13
+
14
+ this happened after
15
+ ```
16
+ protected task drive_response(bit valid, tvip_axi_slave_driver_response_item item);
17
+ vif.slave_cb.bvalid <= valid;
18
+ if (valid) begin
19
+ vif.slave_cb.bid <= item.get_id();
20
+ vif.slave_cb.bresp <= item.get_response_status();
21
+ end
22
+ endtask
23
+ ```
24
+ This
25
+ ```
26
+ protected task reset_if();
27
+ vif.awready = configuration.default_awready;
28
+ vif.wready = configuration.default_wready;
29
+ vif.bvalid = '0;
30
+ vif.bid = '0;
31
+ vif.bresp = tvip_axi_response'(0);
32
+ endtask
33
+ ```
34
+
35
+ So my decision
36
+ ```
37
+ protected task drive_response(bit valid, tvip_axi_slave_driver_response_item item);
38
+ vif.bvalid <= valid;
39
+ if (valid) begin
40
+ vif.bid <= item.get_id();
41
+ vif.bresp <= item.get_response_status();
42
+ end
43
+ endtask
44
+ ```
45
+ I'm not sure, that I understand your logic correctly, but in my case, it's work fine...
46
+
47
+ ![2_solve](https://user-images.githubusercontent.com/35744340/209571584-3d7cae05-5ffe-4947-88bb-d717157fa537.jpg)
48
+
49
+
50
+ Best regards.
patches/esa-tu-darmstadt_tapasco_pr105.patch ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:0b6784a99021b65cf2b4bcca09af877b54bbaef11646437ba48efaaf1827b3ad
3
+ size 62362245