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

vpi_get_str: unhandled property arises when BusMonitor object is created #71

Open
efedepeo opened this issue Dec 4, 2023 · 3 comments

Comments

@efedepeo
Copy link

efedepeo commented Dec 4, 2023

Hi,

I'm trying to create a BusMonitor object to be used in a Scoreboard for my testbench. I've just followed the approach of the mean example provided in the repository.

When I try to create the object a lot of vpi_get_str: unhandled property errors appear. Doing some debugging I detected this event arises when the function dir() in _caseInsensGetattr (line 78) of bus.py is called, the call comes from _add_signal in bus.py (line 83). I do not understand what this error means. The signals are called exactly as defined in the top entity.

If I try to create the BusMonitor with the parameter case_insensitive=False, the error disappear.

monitor_outs = MyMonitor(dut, "o", dut.clk, case_insensitive=False)

To complement the information I'm running this on a WSL 22.04, python 3.10.6 with cocotb 1.8.0 and cocotb-bus 0.2.1.

@alexforencich
Copy link
Contributor

What simulator are you using?

@efedepeo
Copy link
Author

efedepeo commented Mar 4, 2024

All this happened with GHDL

@gbowers4
Copy link

Currently doing a bit of debugging on this now - seems to be an issue with how the GHDL VPI returns array types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants