Stats

  • Locked Locked
  • Replies 12
  • Subscribers 125
  • Views 14989
  • 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

Simulating Config with veriloga view set, does not simulate the veriloga version but still runs the schematic.

JohnTweed

Spectre 17.1.0

Virtuoso 6.1.8

Been away from Cadence for a few years, but now I'm back,  and as usual, nothing is simple.
I have a top level schematic,  calling one instance to test, driven by various analoglib sources.
I have a schematic, symbol and veriloga view of the instance DUT.

I have a config view of the testbench.  In the config,  I've set the view list order so that verloga comes before schematic.  The config then sets DUT to be veriloga view.

That's all as expected.

But now with ADL and selecting 'design' as the config view,  I expect the netlister to give me a netlist with the instance and an ahdl_include to the path to the verloga.
What I get is a netlist with the DUT schematic netlisted. So it's ignoring the hierarchy config.

So what do I need to do to get this to 'just work' as I expect? 

Ie,  expected outcome is that 'Netlist &Run'  respected the config, generates the correct netlist and runs the simulation.

If I go to the original run / netlist dir and edit  input.scs, take out the DUT schematic subckt definition, add in the ahdl_include to the VA path....
Then ./runSimulation then it runs correctly.

I shouldn't need to do this should I?  But what do I need to do, that means that the netlister will do the ahdl_include  etc for me?

Parents
  • Andrew Beckett

    That's very odd and should not be necessary. I'm rather surprised that you're seeing this because this should be robust and I've not seen this elsewhere (other than some user mistake where the design was really not set to be the config, or there was a mistake in the config).

    Can you contact customer support please? That's going to be the fastest way of seeing what is going on and identifying how to fix it.

    Regards,

    Andrew

  • ShawnLogan
    in reply to Andrew Beckett

    Dear JohnTweed,

    If I may add a possibility, that of course Andrew's suggestion would cover with you. Are you sure you selected the "config" view when you selected the design for the Assembler or Explorer test? I know this has happened to me occasionally when I find the desired config view is not selected in the netlist created b Assembler and Explorer.

    Specifically, as shown in Figure 1 where the I show how to select the design for a test, in the subsequent dialog box (Figure 2), one can select its "schematic" or its "config" view. I thought I would at least check that your test has "config" selected and not 'schematic".

    Shawn

    Figure 1

    Figure 2

Reply
  • ShawnLogan
    in reply to Andrew Beckett

    Dear JohnTweed,

    If I may add a possibility, that of course Andrew's suggestion would cover with you. Are you sure you selected the "config" view when you selected the design for the Assembler or Explorer test? I know this has happened to me occasionally when I find the desired config view is not selected in the netlist created b Assembler and Explorer.

    Specifically, as shown in Figure 1 where the I show how to select the design for a test, in the subsequent dialog box (Figure 2), one can select its "schematic" or its "config" view. I thought I would at least check that your test has "config" selected and not 'schematic".

    Shawn

    Figure 1

    Figure 2

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.