Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 15674
  • 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

[Help] Warnings about metal layers in .map file

BackerShu

Hello All,

I need your suggestions the warnings I got in the report after P&R with Encounter. The warning information is as following:

Parse map file...

**WARN: (ENCOGDS-399):   Only 2 layer(s) (M2 M3) of a VIAFILL object is(are) specified in map file 'tsmc090.map'. A VIAFILL object needs 3 layers (M2 VIA2 M3) being specified at the same time in the map file. Add VIAFILL contruct(s) to the map file for the following layer(s): VIA2 or remove VIAFILL construct(s) from the map file for the following layer(s): M2 M3.
 **WARN: (ENCOGDS-399):   Only 2 layer(s) (M2 M3) of a VIAFILLOPC object is(are) specified in map file 'tsmc090.map'. A VIAFILLOPC object needs 3 layers (M2 VIA2 M3) being specified at the same time in the map file. Add VIAFILLOPC contruct(s) to the map file for the following layer(s): VIA2 or remove VIAFILLOPC construct(s) from the map file for the following layer(s): M2 M3.

As the warning suggested, I should add  Add VIAFILL contruct(s) to the map file for the following layer(s): VIA2. I don't know how to add VIAFILL only to VIA2. I tried to change VIA1 with ALL layers, shown with underline. The warning information for M1 and M2 went away.

#-------------------------------------------------------------------------------
#SOC Layer Name   SOC Layer Type   GDS Layer Number   GDS Layer Type
#==============   ==============   ================   ==============

 #VIA1              VIA              51                 0   

VIA1              ALL              51                 0

 

Question: I am nor sure whether the way I updated the .map file is correct or not although the warning information does disappear. Could you please tell me how to do this correctly, or any reference to generate correct .map file? 

 

Thank you, and the .map file I am using is as following:

 

The information in the .map file: (tsmc90)

#-------------------------------------------------------------------------------
#SOC Layer Name   SOC Layer Type   GDS Layer Number   GDS Layer Type
#==============   ==============   ================   ==============

M1                NET              31                 0
M1                SPNET            31                 0
M1                PIN              31                 0
M1                LEFPIN           31                 0
M1                FILL             31                 0
M1                FILLOPC          31                 0
M1                VIA              31                 0
M1                VIAFILL          31                 0
M1                VIAFILLOPC       31                 0
M1                LEFOBS           31                 0
NAME              M1/NET           31                 0
NAME              M1/SPNET         31                 0
NAME              M1/PIN           31                 0
NAME              M1/LEFPIN        31                 0
#M1                ALL              31                 0
#NAME              M1/NET           31                 0
#NAME              M1/SPNET         31                 0
#NAME              M1/PIN           131                0
#VIA1              VIA              51                 0
VIA1              ALL              51                 0
M2                ALL              32                 0
NAME              M2/NET           32                 0
NAME              M2/SPNET         32                 0
NAME              M2/PIN           132                0
VIA2              VIA              52                 0
M3                ALL              33                 0
NAME              M3/NET           33                 0
NAME              M3/SPNET         33                 0
NAME              M3/PIN           133                0
VIA3              VIA              53                 0
M4                ALL              34                 0
......

Parents

  •  Thank you Kari,

    I checked the mapfile in the PDK folder, there is no layer named VIAFILL. Part of the file information is shown below just to make sure I am checking the correct file. If this is not the file I should check, could you please enlight me which file I should refer to?

     

    #*****************************************************************************
    # TSMC 65nm / 55nm Layout Editor Mapping File - virtuoso_65nm_1P9M_6X1Z1U_2.0a.pre010810.map, 01/08/2010
    # 1P9M PROCESS WITH 6X1Z1U METAL SCHEME
    # Technology File Document: T-N65-CL-LE-002 Ver 2.0a.pre010810
    # Ref Document: T-N65-CL-LE-001 Ver 2.0a
    #*****************************************************************************
    # DISCLAIMER
    #
    # The information contained herein is provided by TSMC on an "AS IS" basis
    # without any warranty, and TSMC has no obligation to support or otherwise
    # maintain the information.  TSMC disclaims any representation that the
    # information does not infringe any intellectual property rights or proprietary
    # rights of any third parties.  There are no other warranties given by TSMC,
    # whether express, implied or statutory, including, without limitation, implied
    # warranties of merchantability and fitness for a particular purpose.
    #
    # STATEMENT OF USE
    #
    # This information contains confidential and proprietary information of TSMC.
    # No part of this information may be reproduced, transmitted, transcribed,
    # stored in a retrieval system, or translated into any human or computer
    # language, in any form or by any means, electronic, mechanical, magnetic,
    # optical, chemical, manual, or otherwise, without the prior written permission
    # of TSMC.  This information was prepared for informational purpose and is for
    # use by TSMC's customers only.  TSMC reserves the right to make changes in the
    # information at any time and without notice.
    #*****************************************************************************
    # IMPORTANT NOTICE
    #
    # Though PDIFF(7;0) & NDIFF(8;0) are tape out layers, it's strongly suggested
    # to use OD(6;0) instead, which is the standard "Gate Oxide and Diffusion"
    # (OD) layer. Be sure to check carefully the related mask logic operation if
    # PDIFF/NDIFF layers are used.
    #*****************************************************************************
    # techLayer     techPurpose     stream# dataType
    # ---------     -----------     ------- --------
      ref           drawing         0       0
      DNW           drawing         1       0
      PW            drawing         2       0
      NW            drawing         3       0
      PM            drawing         5       0
      PM            drawing1        5       1
      PM            drawing2        5       2
      OD            drawing         6       0
     

Reply

  •  Thank you Kari,

    I checked the mapfile in the PDK folder, there is no layer named VIAFILL. Part of the file information is shown below just to make sure I am checking the correct file. If this is not the file I should check, could you please enlight me which file I should refer to?

     

    #*****************************************************************************
    # TSMC 65nm / 55nm Layout Editor Mapping File - virtuoso_65nm_1P9M_6X1Z1U_2.0a.pre010810.map, 01/08/2010
    # 1P9M PROCESS WITH 6X1Z1U METAL SCHEME
    # Technology File Document: T-N65-CL-LE-002 Ver 2.0a.pre010810
    # Ref Document: T-N65-CL-LE-001 Ver 2.0a
    #*****************************************************************************
    # DISCLAIMER
    #
    # The information contained herein is provided by TSMC on an "AS IS" basis
    # without any warranty, and TSMC has no obligation to support or otherwise
    # maintain the information.  TSMC disclaims any representation that the
    # information does not infringe any intellectual property rights or proprietary
    # rights of any third parties.  There are no other warranties given by TSMC,
    # whether express, implied or statutory, including, without limitation, implied
    # warranties of merchantability and fitness for a particular purpose.
    #
    # STATEMENT OF USE
    #
    # This information contains confidential and proprietary information of TSMC.
    # No part of this information may be reproduced, transmitted, transcribed,
    # stored in a retrieval system, or translated into any human or computer
    # language, in any form or by any means, electronic, mechanical, magnetic,
    # optical, chemical, manual, or otherwise, without the prior written permission
    # of TSMC.  This information was prepared for informational purpose and is for
    # use by TSMC's customers only.  TSMC reserves the right to make changes in the
    # information at any time and without notice.
    #*****************************************************************************
    # IMPORTANT NOTICE
    #
    # Though PDIFF(7;0) & NDIFF(8;0) are tape out layers, it's strongly suggested
    # to use OD(6;0) instead, which is the standard "Gate Oxide and Diffusion"
    # (OD) layer. Be sure to check carefully the related mask logic operation if
    # PDIFF/NDIFF layers are used.
    #*****************************************************************************
    # techLayer     techPurpose     stream# dataType
    # ---------     -----------     ------- --------
      ref           drawing         0       0
      DNW           drawing         1       0
      PW            drawing         2       0
      NW            drawing         3       0
      PM            drawing         5       0
      PM            drawing1        5       1
      PM            drawing2        5       2
      OD            drawing         6       0
     

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.