Instantiating a schematic view in another schematic

[Brandon Hoppe]

Hi all,

I was wondering if there are any issues that could come up by placing a
schematic instantiation into another schematic cellview instead of using
a symbol view to instantiate?

Thanks

 

[daytripper]

On Tue, 25 Jul 2006 15:05:57 -0500, Brandon Hoppe <bhoppe@ti.com> wrote:

Hi all,

I was wondering if there are any issues that could come up by placing a
schematic instantiation into another schematic cellview instead of using
a symbol view to instantiate?

Thanks

Conflicting hard properties. Unintended connections due to the use of
identical signal names within the "macro" that weren't intended to be globals
but become globals when instantiated at the root level.

Stoopid stuff like that ;-)

 

[Andrew Beckett]

On Tue, 25 Jul 2006 16:54:33 -0400, daytripper <day_trippr@REMOVEyahoo.com>
wrote:

On Tue, 25 Jul 2006 15:05:57 -0500, Brandon Hoppe <bhoppe@ti.com> wrote:


Hi all,

I was wondering if there are any issues that could come up by placing a
schematic instantiation into another schematic cellview instead of using
a symbol view to instantiate?

Thanks

Conflicting hard properties. Unintended connections due to the use of
identical signal names within the "macro" that weren't intended to be globals
but become globals when instantiated at the root level.

Stoopid stuff like that ;-)

I don't think this should matter. This would only be an issue if you flattened
it - they're not at the same level of hierarchy. Put another way, I don't think
any of these are any different if you instantiate a symbol and then view switch
during netlisting into the schematic, or you directly instantiate a schematic.

I've not personally come across problems, but this is not exactly widely used.

After all, one of the main purposes of symbols is to hide detail - to prevent a
higher level schematic from getting too cluttered. If you're just instantiating
the schematic, it's harder to abstract what a block does when trying to
understand the schematic.

Andrew.
--
Andrew Beckett
Principal European Technology Leader
Cadence Design Systems, UK.