Stats

  • Locked Locked
  • Replies 1
  • Subscribers 124
  • Views 13285
  • 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

ncvlog netlist generation

Nasser Arif

HI,

I have schematic of transmitter, which has several blocks, which consist of functional view.

For one block (say BlockA), I have synthesized netlist with all cell definitions.

I am trying to generate the top level verilog netlist using ncvlog, I did below steps.

Created config view, and bind the  BlockA with symbol( My plan to pass the definition from out side)

and generate the netlist, it create the netlist but ignoring the blockA.

Could you please let me know if I am missing something here to netlist.

Thanks,

Nasser

Parents
  • Andrew Beckett

    Nasser,

    It's not sufficient to just bind the view with symbol. You'd have to add symbol into the stop list - otherwise it just sees it as a hierarchical block with nothing in it, and so will get automatically omitted).

    Alternatively, you can use in the hierarchy editor, Right Mouse->Add Stop Point (you probably want to go over the header of the cell table and using the right mouse menu enable the "info" column to see the stop points). That will have the same effect.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Nasser,

    It's not sufficient to just bind the view with symbol. You'd have to add symbol into the stop list - otherwise it just sees it as a hierarchical block with nothing in it, and so will get automatically omitted).

    Alternatively, you can use in the hierarchy editor, Right Mouse->Add Stop Point (you probably want to go over the header of the cell table and using the right mouse menu enable the "info" column to see the stop points). That will have the same effect.

    Regards,

    Andrew.

Children
No Data

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.