-
Notifications
You must be signed in to change notification settings - Fork 89
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
Issues with AUTOINOUTMODPORT and Handling Master and Slave interface names #1690
Comments
Figured out the answer to Issue 3: The examples need to be elaborated to show this 3rd parameter |
This extends the question in Issue 3 to AUTOASSIGNMODPORT as well. |
As to point 1, you are correct the second set is not created because the names are the same - this is a general verilog-mode rule that it won't declare something already declared. As to point 2 there wasn't any example in the docs showing AUTOASSIGNMODPORT despite what the docs said. This is now fixed. Looking at point 3, I understand your point, stay tuned. |
* verilog-mode.el (verilog-auto-assign-modport, verilog-auto-inout-modport): Support adding prefix to AUTOASSIGNMODPORT and AUTOINOUTMODPORT (#1690).
Added support.
|
…pool#1690). * verilog-mode.el (verilog-auto-assign-modport, verilog-auto-inout-modport): Support adding prefix to AUTOASSIGNMODPORT and AUTOINOUTMODPORT (veripool#1690).
I am trying to convert a module with interface modports into SV ports by using a wrapper and AUTOINOUTMODPORT and AUTOASSIGNMODPORT.
Assume that the instance module has two interface mod-ports -
(1) AXI-Master axi_if.master
(2) AXI-Slave axi_if.slave
The signals names are exactly the same name in the axi_if mod ports.
Here are some of the issues I discovered in this scenario
Issue 1) Port creation gets skipped for the second mod-port.
When I use AUTOINOUTMODPORT to create ports as below
module wrapper (
/* AUTOINOUTMODPORT "axi_if" "master" / <- The ports get created.
/ AUTOINOUTMODPORT "axi_if" "slave" */ <- port creation gets skipped.
I am guessing that this happening because the signal names are same..
How does one resolve this issue...
Issue 2) AUTOASSIGNMODPORT expects 3 parameters but examples show 2 parameters
I am trying create assignments between the created SV ports and SV interface as -
/* AUTOASSIGNMODPORT "axi_if" "master" */
My expectation is that a bunch of assigns get created. But I get an error as "Expected 3 parameters"
The few examples shown has just 2 parameters.
What is the usage issue here..?
Issue 3) Appending a character to the created ports.
I further want to append the created SV-ports with a character such as "M" for master and "S" for slave.
How do we make this happen?
Thanks,
Engr
The text was updated successfully, but these errors were encountered: