Skip to content
Discussion options

You must be logged in to vote

Parameterization is generally the better choice when the underlying functionality is the same and only the data width or configuration changes. Instead of maintaining separate 8bit, 16bit, and 32bit versions, a single parameterized module can be reused by simply overriding the parameter during instantiation.

Besides reducing code duplication, parameterized modules are easier to maintain because any bug fixes or improvements only need to be made in one place. This also keeps the repository more organized as the number of modules grows.

From a synthesis perspective, parameters are resolved at compile time, so the synthesis tool generates hardware for the specified width. In most cases, ther…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by samimcooks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants