Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 1453
  • 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

How to get around 'no library changes' in Config views?

TempViator

Hi,

I am working on testing modifications for a chip revision and thought I could use config views to pull in schematic cells, possibly of different names, from different libraries.  But schematics in config views cannot change the library of schematics (though it can be done for verliog files).

To give an example, suppose the following

library: chip_revA
cell: amp_revA; view: schematic

library: chip_revB
cell: amp_revA_fixed; view: schematic

library: test_benches
cell: chip_test_bench; views: schematic, config_revA, config_revB

ADE Assembler
test1: spec1_chip_revA;
        Design = lib:test_benches/cell:chip_test_bench/view:config_revA
               that would refer to chip_revA/amp_revA/schematic in the middle of its hierarchy
test2: spec1_chip_revB;
        Design = lib:test_benches/cell:chip_test_bench/view:config_revB
               that would refer to chip_revB/amp_revA_fixed/schematic in the middle of its hierarchy

This way, if test1 and test2 are duplicates (other than to refer to different config views), I can test both the old version and the fixed version in the same Assembler run. But since I cannot swap schematic libraries in the config view, this is not viable.

Without re-doing how we separate the libraries, is there a way to accomplish the goal of using ADE Assembler to run new and old schematics this way using config views,,, or some other method?

Really, I am seeking a clean methodology that uses standard features of Cadence (not a custom solution) and has logical sense to it.  Suggestions?

  • You can't library-switch within a schematic because the library is bound in the database (Verilog doesn't really have libraries, which is why you have the freedom to switch libraries for Verilog). So there isn't a way of doing this. I did have a prototype way of achieving this (actually it was for switching cells, but it would work for libraries too) in ADE simulation, but it's not in production so not a "standard feature".

    The best approach would be to create a branch using a design management solution. Most customers use one of the supported third-party DM integrations - currently (in no particular order) Keysight (Cliosoft) SOS, Dassault MatrixOne DesignSync, IC Manage, Perforce (MethodICs) VersIC, IBM ClearCase.

    Regards,

    Andrew

  • in reply to Andrew Beckett

    Thanks Andrew. 

    We do use one of those DM solutions... so just to clarify, are you suggesting that using branching really keeps the same base library so that all of the cells are accessible from the Hierarchy Tool? 

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.