Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cv_dv_utils AXI2MEM] Ready signals are stuck at 1. #2403

Open
khandelwaltanuj opened this issue Apr 5, 2024 · 3 comments
Open

[cv_dv_utils AXI2MEM] Ready signals are stuck at 1. #2403

khandelwaltanuj opened this issue Apr 5, 2024 · 3 comments
Assignees
Labels
Common Infrastructure: UVM Agent question Further information is requested

Comments

@khandelwaltanuj
Copy link
Contributor

Hello,

While working on the verification of HPDcache, I observed that ready signals of AXI2MEM are internally driven to 1. The readme of AXI2MEM says that user should drive these signals.

Thanks and Regards
Tanuj Khandelwal

@MikeOpenHWGroup
Copy link
Member

Thanks for the issue. Can you point to the specific file and line number?

@khandelwaltanuj
Copy link
Contributor Author

Hi @MikeOpenHWGroup

The file is:
https://github.com/openhwgroup/core-v-verif/blob/master/lib/cv_dv_utils/uvm/memory_rsp_model/axi2mem/axi_intf.sv

line 82 to 86; I need to comment out these lines.

Regards
Tanuj

@MikeOpenHWGroup
Copy link
Member

Hi @ludovicpion, I think @khandelwaltanuj is correct. The file and line numbers he references hardcode aw_ready, ar_ready and assign w_ready to 1'b1. Can you submit a pull-request to remove these assignments and allow the user to control them via a sequence?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Common Infrastructure: UVM Agent question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants