Yosys $paramod issue #5090
-
I’m using Yosys to generate a synthesized netlist for my design without applying the flatten command. As a result, Yosys creates parameterized module instances with $paramod prefixes. I’ve successfully used the rename command to change these module names; however, the instantiations still reference the original $paramod names, which leads to mismatches. I'm exploring whether box_derive can help address this issue by generating named specializations of parameterized modules with more meaningful identifiers. If so, could you briefly explain how to use box_derive correctly to ensure that both the module definitions and their instantiations are consistently renamed? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 12 replies
-
I haven't used it, but https://github.com/YosysHQ/yosys/blob/main/tests/various/box_derive.ys shows an example use of it. Looking at the source code, it only works on cells where the module is a blackbox or whitebox (because they are ignored by |
Beta Was this translation helpful? Give feedback.
-
Also, yosys/docs/source/code_examples/fifo/fifo.v Lines 43 to 49 in 6378ba1 Calling
But it is still called |
Beta Was this translation helpful? Give feedback.
-
hello in your fifo.v example i tried also and after uniquify i am getting this: 4 modules: |
Beta Was this translation helpful? Give feedback.
-
sky130_fd_sc_hd__mux2_1 02 ( |
Beta Was this translation helpful? Give feedback.
-
\ibex_core.core_clock_gate_i core_clock_gate_i ( |
Beta Was this translation helpful? Give feedback.
-
hello i am creating netlist but at the end i am still getting these conditional conditions |
Beta Was this translation helpful? Give feedback.
The
$paramod
module shouldn't be used if you've calleduniquify
and callinghierarchy
again will remove it: