You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thank you for the open source project. We are using the project in several of our projects and we are really satisfied with it.
We are also heavily using the verification components especially in combination with AXI interfaces.
What we are missing is a full axi master verification component. Is there a plan from your side to implement this component or is there a special reason why you are not implement it?
If this feature is not planned from your side we would really like to support the implementation of this feature with our development team and would be pleased to get in direct contact for discussion.
Thank you.
The text was updated successfully, but these errors were encountered:
FWIW, people I work with would also be very interested in a component like this. We have hacked together streaming VCs to achieve an "AXI Master" in the past, but it's not the same as having a true AXI Master VC.
I'm also interested and would be happy to help out with this.
I have been looking at the boards and see that some comments indicate that there is progress in rewriting the verification components (#726 and #480 for example).
I couldn't find the repository where this work is happening though.
Is there an update on the status of the verification components and is there a way for me to contribute?
Hi, after a longer break from my side i would like to start with the implementation of the axi master verification component. Are there any updates related to this component or to any other rewriting progress?
Hi guys,
thank you for the open source project. We are using the project in several of our projects and we are really satisfied with it.
We are also heavily using the verification components especially in combination with AXI interfaces.
What we are missing is a full axi master verification component. Is there a plan from your side to implement this component or is there a special reason why you are not implement it?
If this feature is not planned from your side we would really like to support the implementation of this feature with our development team and would be pleased to get in direct contact for discussion.
Thank you.
The text was updated successfully, but these errors were encountered: