Stats

Locked Locked
Replies 5
Subscribers 66
Views 1776
Members are here 0

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

using ncverilog with synthesized ".vo" files from altera

Hi,

I am trying to use an existing testbench and would like to use synthesized (.vo) files from altera. The issue that I am running into is that some of the test bench code (in files which are compiled by ncvlog) access signals which are in the .vo file. ncelab can't find the signal -- it gives "Hierarchical name lookup failure" -- Has anyone done anything like this ?

Thanks,

Mickey over 15 years ago

what does the *.vo file look like? is it some kind of encrpyted or proprietary format? or is it a regulat verilog gate netlist?
Cancel
Vote Up 0 Vote Down

Cancel
sbeling over 15 years ago

It is a regular netlist -- and does work with the simulator, it is just that the internal signals are not visible when directly referenced
Cancel
Vote Up 0 Vote Down

Cancel
Mickey over 15 years ago

Can you send an example (jrodrig@cadence.com)? i don't see why the signals can't be found via an out-of-module reference
Cancel
Vote Up 0 Vote Down

Cancel
TAM1 over 15 years ago

The most likely cause was that Altera (or whatever the synthesis tool was called) did not preserve the net names in the synthesized netlist. It could be that the netlist is flattened from the RTL hierarchy or that the signals you are trying to probe have been optimized away.
There are usually commands you can add to your synthesis scripts that tell the tool to preserve the hierarchy and/or RTL signal names. But you usually end up with a less efficient synthesized netlist at the end when you do that.
Cancel
Vote Up 0 Vote Down

Cancel
sbeling over 15 years ago

That was the problem (Mickey sent me the flattening in private email).

Thanks all

Steve
Cancel
Vote Up 0 Vote Down

Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.