lxGenFromSource - BUT ignore existing layout views and give me "flat" devices

The schematic/layout binding initialisation is defined in the physConfig cellview. Follow these steps...

Edit the physConfig, You will need to add at least one 'Physical stop Library'. Typically the pdk device lib (XL needs to know where to stop descending the hierarchy).

Then select all the instnaces: RMB -> Set hierarchical force descend. Save CPH.

Layout -> Generate From Source: Should result in all hierarchy expanded down to primitive devices.

Also consider the Design Planning and Analysis flow...

Virtuoso Design Planning and Analysis (IC25.1)

Offers a more flexible approach to design planning.

In addition to Rob's suggestions, if this is all being done from SKILL, there are "cph" functions for setting force descend too...

Andrew

Yes, this is all being done inside my code so I'll look up the cph fuctions. Thanks

I've read through lots of documentations and it seems I need to run the "cphSetCellForceDescend" command for each cell in my top level schematics hierarchy in order for it to not use the existing layout view, am I understanding this correctly? Next question, assuming I do need to run the command on each cell, will I need write permission in the schematics to modify this property (which would be a showstopper for my use case). 

A bit more background in case it helps. I'm opening a top level schematic, graphically, and then running my code which calls the lxGenFromSource function. I need to generate every level of hierarchy (except std cells) flat so that I can do some area calculations. My hope was to define a stop library for the std cells vs. alter the props of every schematic.

lxGenFromSource(cv
?layLibName layoutLibName ;LAYOUT LIB NAME
?layCellName layoutCellName ;LAYOUT CELL NAME
?layViewName layoutViewName ;LAYOUT VIEW NAME
?configLib layoutLibName
?configCell layoutCellName
?configView layoutViewName
?initDoStacking "t" ;AUTO ABUT MOS INTO CHAIN
?initCreateInstances t ;GEN ALL INSTANCES IN SCH W/O IGNORE PROP
?lxGenerateInBoundary t ;GEN INSIDE BOUNDARY SHAPE
?lxPositionMinSep 20 ;DEVICE SEPERATION IS IMPORTANT BECAUSE I OVERSIZE SOME LAYERS BELOW, IF FETS ARE TO CLOSE IT WILL MERGE AND IMPACT AREA ACCURACY.
?initAreaSource1 "Utilization"
?initAreaSource1Val 100.0
?initAreaSource2 "AspectRatio"
?initAreaSource2Val 1.0
?extractAfterGenerateAll nil
?ignoreSchematicCheck t
;?extractSchematic nil
);end lxGenFromSource

I've read through lots of documentations and it seems I need to run the "cphSetCellForceDescend" command for each cell in my top level schematics hierarchy in order for it to not use the existing layout view, am I understanding this correctly? Next question, assuming I do need to run the command on each cell, will I need write permission in the schematics to modify this property (which would be a showstopper for my use case). 

A bit more background in case it helps. I'm opening a top level schematic, graphically, and then running my code which calls the lxGenFromSource function. I need to generate every level of hierarchy (except std cells) flat so that I can do some area calculations. My hope was to define a stop library for the std cells vs. alter the props of every schematic.

lxGenFromSource(cv
?layLibName layoutLibName ;LAYOUT LIB NAME
?layCellName layoutCellName ;LAYOUT CELL NAME
?layViewName layoutViewName ;LAYOUT VIEW NAME
?configLib layoutLibName
?configCell layoutCellName
?configView layoutViewName
?initDoStacking "t" ;AUTO ABUT MOS INTO CHAIN
?initCreateInstances t ;GEN ALL INSTANCES IN SCH W/O IGNORE PROP
?lxGenerateInBoundary t ;GEN INSIDE BOUNDARY SHAPE
?lxPositionMinSep 20 ;DEVICE SEPERATION IS IMPORTANT BECAUSE I OVERSIZE SOME LAYERS BELOW, IF FETS ARE TO CLOSE IT WILL MERGE AND IMPACT AREA ACCURACY.
?initAreaSource1 "Utilization"
?initAreaSource1Val 100.0
?initAreaSource2 "AspectRatio"
?initAreaSource2Val 1.0
?extractAfterGenerateAll nil
?ignoreSchematicCheck t
;?extractSchematic nil
);end lxGenFromSource

No, the schematic does not get touched. You'd need write access to a physConfig view to do this.

Andrew

Thanks. Because I can't guarantee write access to even the library, I'll switch gears and do a hierarchal copy into a temp lib, minus the layout views, and then run the GenFromSource. 

So how are you going to generate the layout? The physConfig view can be wherever the layout is.

Andrew

I would create a temp lib and specify it with ?layLibName flag so it writes the new layout there and not inside the read only schematic library. 

OK, so the physConfig could go in the same temp lib.

Andrew