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?

  • Andrew Beckett
    in reply to JohnTweed

    I'm wondering whether it's maybe being set in a .simrc - but that doesn't quite explain how it ends up unset (if set in a .simrc then setting in your .cdsinit wouldn't be enough because it would get clobbered by the .simrc setting). The symptoms absolutely match the behaviour of that variable, including the complaints about __tmpLib.

    I think it would be best to follow this up with customer support via one of your full-time colleagues, since debugging this via the forums will be hard - especially as this is a rather esoteric non-production setting and I can't see any other way of it getting stuck in that part of the code. Maybe the behaviour was different in the specific IC6.1.8 sub-version you're using (I was using the very latest, ISR24) - getVersion(t) in the CIW or Help->About will report that (I can do a little more digging if I know the sub-version)

    Andrew

  • JohnTweed
    in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your time,  version is 500.11
    I'll look at .simrc but not hopeful.  I was a completely fresh setup, so had no time to tweak things like I used to do, which did cause problems for Cadence support from time to time. The addage 'a little knowledge...' comes to mind.

    But this is the vanilla Cadence for this company AFIK, they don't have a lot of company experts 'improving' the basic Cadence setup, like in my previous life.

    I'd just leave it for now,  I was hoping for a 'duhhh' moment, 'You didn't do this or that'.
    I can just run AMS if I want to try a mixed config.
    Regards.

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.