-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
COCOTB : Unable to acess VHDL packages. #891
Labels
Comments
nickg
added a commit
that referenced
this issue
May 18, 2024
nickg
added a commit
to nickg/cocotb
that referenced
this issue
May 18, 2024
See issue cocotb#1833 and also nickg/nvc#891. I have only been able to test this with latest NVC master branch.
I've added support for accessing package constants through VHPI but it needs some cocotb changes as well, see cocotb/cocotb#3899. |
nickg
added a commit
to nickg/cocotb
that referenced
this issue
May 18, 2024
See issue cocotb#1833 and also nickg/nvc#891. I have only been able to test this with latest NVC master branch.
nickg
added a commit
to nickg/cocotb
that referenced
this issue
May 20, 2024
See issue cocotb#1833 and also nickg/nvc#891. I have only been able to test this with latest NVC master branch.
nickg
added a commit
to nickg/cocotb
that referenced
this issue
May 20, 2024
See issue cocotb#1833 and also nickg/nvc#891. I have only been able to test this with latest NVC master branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
It's common to have constants defined in VHDL packages. Based on cocotb issue 1833, the only way to access the packages is using
In NVC, there seems to be a check, which doesn't allow this. When Cocotb tries to access the package, it gives the following error:
nvc version
cocotb version =
2.0.0.dev0+65d102f2
Is it possible to relax that check ?
The text was updated successfully, but these errors were encountered: