Skip to content
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

VQ file: bus signal are split into individual signals #677

Open
rakeshm75 opened this issue Nov 15, 2021 · 2 comments
Open

VQ file: bus signal are split into individual signals #677

rakeshm75 opened this issue Nov 15, 2021 · 2 comments
Assignees

Comments

@rakeshm75
Copy link

In the VQ file (Verilog post-layout netlist), the bus signals are split into individual signals:

Its should be:
output [15:0] count;

In VQ file:
output \count[0] ,
output \count[1] ,
output \count[2] ,
output \count[3] ,
output \count[4] ,
output \count[5] ,
output \count[6] ,
output \count[7] ,
output \count[8] ,
output \count[9] ,
output \count[10] ,
output \count[11] ,
output \count[12] ,
output \count[13] ,
output \count[14] ,
output \count[15]

counter_16bit.zip

@mkurc-ant
Copy link

@rakeshm75 @lnsharma This is done intentionally. The problem is that for post-layout simulation with Icarus Verilog all cell ports (including top-level) must be 1-bit wide because Icarus does not support SDF annotations for wide ports. There is even an issue reported in its main repository: steveicarus/iverilog#509

@sharmaln
Copy link

@rakeshm75 @lnsharma This is done intentionally. The problem is that for post-layout simulation with Icarus Verilog all cell ports (including top-level) must be 1-bit wide because Icarus does not support SDF annotations for wide ports. There is even an issue reported in its main repository: steveicarus/iverilog#509

@mkurc-ant : Is it feasible to generate 2 vq files - one with all cell ports of 1-bit wide and other with vector representation of cell ports? These files can then be accordingly used in different simulators?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants