Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 7414
  • 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

Manual editing of a p2lvsfile

Slawa

 Hello

 After I have faced the following error: ERROR (LBMISC-215480): at "RCXdspf": LVS connectivity file /.../  is missing .2. in the course of start qrc at me there was a necessity of editing p2lvsfile.

In a "ICT.file" is
  # Diffusion Layers
diffusion NP {thickness, resistivity} and

 # dielectric Layers
dielectric   STI {conformal FALSE, height, thickness, dielectric_constant}.

How they are necessary for setting in p2lvsfile if to them as a matter of fact corresponds nothing in a RULEfile? 

 How to be with layers which are created directly in RULEfile but are used in LVSFILE? For example there is layer PACTIVE=Layer1 and (Layer2 or Layer3) which is set in RULEfile and in LVSFILE it is used only as:

 model = diode[DP],DP
element diode[DP] DPPLUS PACTIVE NWELL

 It turns out that in LVSFILE there is no information on the given layer as well as there is no information on it in ICT.

 

Best regards

Beginner engineer from Russia 

Parents

  • Hi Slawa

    You will only need the layers that are listed in the lvsfile. There are many layers in the rules file and as you have noted, most are just intermediate layers that need not be mapped. The lvsfile rules file contains the important lvs layers that directly contribute to connectivity and device formation. Some level of knowlege regarding the rule deck layers is needed in order to do the mapping in the layer_setup file.

    The interconnect lvs layers are easy because they usually have names such as "m1_conn" or "m1" or "metal1", etc. For the other process layers such as such as STI and NPJunc, we have to figure out the corresponding lvs layers. Look for names such as source_drain, sd, psub, substrate, etc. In the lvsfile, take note of the layers that are connected through "contact" layer. Usually you would want to map such layers (e.g. psub, nimp, pimp, etc) to the process layers that represent substrate and diffusion.

    By the way, please do not use p2lvsfile format as it has already been replaced by layer_setup file. You must provde some mapping to all process layers so that the extraction results can be accurate.

    Best regards
    Quek

Reply

  • Hi Slawa

    You will only need the layers that are listed in the lvsfile. There are many layers in the rules file and as you have noted, most are just intermediate layers that need not be mapped. The lvsfile rules file contains the important lvs layers that directly contribute to connectivity and device formation. Some level of knowlege regarding the rule deck layers is needed in order to do the mapping in the layer_setup file.

    The interconnect lvs layers are easy because they usually have names such as "m1_conn" or "m1" or "metal1", etc. For the other process layers such as such as STI and NPJunc, we have to figure out the corresponding lvs layers. Look for names such as source_drain, sd, psub, substrate, etc. In the lvsfile, take note of the layers that are connected through "contact" layer. Usually you would want to map such layers (e.g. psub, nimp, pimp, etc) to the process layers that represent substrate and diffusion.

    By the way, please do not use p2lvsfile format as it has already been replaced by layer_setup file. You must provde some mapping to all process layers so that the extraction results can be accurate.

    Best regards
    Quek

Children
No Data

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.