Ability to import specific module from Verilog/model from BLIF without making its io the block's IO #398
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will import the Verilog module without making its i/o wires the block's i/o wires. Instead, it returns an object whose attributes are input/output wires, accessible via the name of the wires defined on the Verilog module.
Given this Verilog file
You can import it like so
foo.x
andfoo.y
areWireVector
s, notInput
, and they are named with internal names so the module can be imported multiple times without clashes. Similarly,foo.z
isWireVector
, notOutput
. All these wires can be connected to others like normal:The key is the
**as_block**
parameter you pass toinput_from_verilog
, which will determine if block-level I/O is created, or instead a "submodule".This PR also adds support for importing particular models from a BLIF file (since the
input_from_verilog()
function basically wraps the call toinput_from_blif()
).