Product Documentation
Virtuoso Parasitic Aware Design SKILL Reference
Product Version IC23.1, June 2023

mspsMapNetName

mspsMapNetName(
h_hdbConfigId
t_name
)
=> t_frag_name / nil

Description

Maps a hierarchical schematic net name to a fragment of the equivalent net in the extracted view.

This function is required to be used only with the Virtuoso executable and not with OCEAN executable. OCEAN and ADE data access functions automatically map schematic names into the simulated extracted view and it is no longer necessary to call this function.

Arguments

h_hdbConfigId

Configuration cellview identifier returned by hdbOpen.

t_name

Hierarchical schematic net name.

Value Returned

t_frag_name

Hierarchical name of a net fragment in the extracted view that maps to the net name in the schematic view. This can be any one of the net fragments in the extracted view that map to schematic net.

If none of the instances in the hierarchical schematic name is bound to an extracted view, the schematic name is returned unmodified. In this case the supplied hierarchical name does not lead into an extracted view. For example, if you have the name /I0/I1/I2/netA it means that none of I0, I1, I2 have been bound to an extracted view in the config. In this case, the name is returned unmodified as it does not need to be mapped into an extracted view.

nil

The schematic name does not match the extracted view.

In this case, the supplied name does lead into an extracted view, but the net name cannot be mapped into that view because, for example, a wrong net name is given. For example, if you bind I1 to an extracted view in the previous example, the name /I0/I1/I2/netA needs to be mapped now. But, if netA does not exist, then the function returns nil.

Examples

In these examples, instance /X1 is bound to an extracted view and instance /XA to the schematic view.

cfg = hdbOpen("worklib" "TB1_vco_RCXcompare" "config" "r") 
=> hdbcConfigType:0x0xbe9d948

Here, net /X1/I15|n3 in the schematic maps to net /X1/2:I15/n3 in the extracted view.

mspsMapNetName( cfg "/X1/I15/n3" )
=> "/X1/2:I15|n3"
Here, instance XA is bound to the schematic view. Therefore, the name does not need to be mapped.
mspsMapNetName( cfg "/XA/I15/n3" )
=> "/XA/I15/n3"
Here, inx2 is not a valid net name in the design.
mspsMapNetName( cfg "/X1/I15/inx2" )
=> nil

Related Topics

Parasitic Aware Design Functions


Return to top
 ⠀
X