Comments (7)
resp_t
vs axi_pkg::resp_t
conflict
I agree that using resp_t
as parameter to hold the entire response struct is not ideal, since it could collide with axi_pkg::resp_t
when the latter is imported into module namespace. However, with namespaces guarding from exactly such conflicts, I am against changing this to rsp_t
right now. Can you check in which modules exactly the conflict happens?
For instance, there are wildcard imports in axi_cdc
, axi_intf
, axi_test
, tb_axi_cdc
, and tb_axi_atop_filter
. Is one of those imports not bounded by a module scope? I would prefer to fix this problem this way.
Typedefs in axi_dw_upsizer
I agree with your solution. Please open a PR against the DWC branch.
from axi.
I had the problem also for example in axi_demux
. There no import is happening.
from axi.
I see, but if one of the instances above is compiled before axi_demux
and has a globally visible import
, that could cause the problem, no?
from axi.
This was it, removing the global imports fixed the compile and simulation worked. See fixes in #70.
from axi.
Nice catch and fix! The compilation units in SV are really a pain.
from axi.
This can be closed now that #70 is merged, right?
from axi.
Yes #70 solved the compile issues, partially.
However Verilator does not like in the assertions in the interface AXI_BUS_DV
in axi_interface
.
Guarding them with
// pragma translate_off
`ifndef VERILATOR
`endif
// pragma translate_on
resolves the compile issue
from axi.
Related Issues (20)
- `axi_to_mem`: Comb path from `b_ready` to `w_ready` HOT 1
- axi_to_mem: Starvation issue: AW channel blocks AR channel forever
- axi_dw_downsizer: AXI Slave BRESP changes in value during BVALID’s wait for BREADY
- axi_pkg::LenWidth not compatible with vivado IP packager
- axi_cdc fpga implementation very inefficient HOT 2
- run_vsim.sh: Run simulations in parallel HOT 4
- tb_axi_lite_xbar is not included in scripts/run_vsim.sh
- Vivado Synthesis Error - [Synth 8-6038] cannot resolve hierarchical name
- ``axi_to_mem``: Error response signals in B and R response channels
- axi_dw_downsizer writing data beats with wstrb == 0
- Logging not supported for Queue item error : AXI HOT 2
- axi_iw_convertor connection
- AXI_BUS and AXI_BUS_DV package missing? HOT 2
- Pipelines between demux and mux would still cause deadlock in an axi_xbar? HOT 2
- Can't find cdc_fifo_gray_dst HOT 2
- Compile errors with CDC module
- "MaxTrans" defined incorrectly in the module documentation
- Error when IdMapNumEntries =0 with VCS
- Why is `xbar_latency_e` an `enum`? HOT 1
- Expose `AxiLookBits` as a parameter in `axi_burst_splitter` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from axi.