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
There's already support for accessing registered ports of ExternalSystemVerilogModules, but it would be cool to be able to access other non-port signals in modules or submodules in the SystemVerilog.
This opens the question of "listening" to other signals in addition to just driving them. Also, this could overlap with inputs, should we be able to listen to those as well? What about handling of infinite loops of listening?
What if you have a ROHD module, within a SystemVerilog module, within a ROHD module? To access relative signals from ROHD to ROHD would require context of their relative hierarchies.
The text was updated successfully, but these errors were encountered:
There's already support for accessing registered ports of
ExternalSystemVerilogModule
s, but it would be cool to be able to access other non-port signals in modules or submodules in the SystemVerilog.This opens the question of "listening" to other signals in addition to just driving them. Also, this could overlap with inputs, should we be able to listen to those as well? What about handling of infinite loops of listening?
What if you have a ROHD module, within a SystemVerilog module, within a ROHD module? To access relative signals from ROHD to ROHD would require context of their relative hierarchies.
The text was updated successfully, but these errors were encountered: