• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. layer map file for GDS transfer to virtuoso

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 15896
  • 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

layer map file for GDS transfer to virtuoso

oAwad
oAwad over 8 years ago

Hello all,

I have a GDS layout previously designed in SoC encounter, I want to import it in Virtuoso but I don't have a layer map provided with PDK (I'm using Nangate Open Cell Library 45nm). I now have two files; a technology file provided with PDK and a streamOut.map file generated from GDS export in Encounter. 

I need to understand the purpose of the map file and should I have provided it during GDS export in Encounter. If not, how to modify it for correct streamIn in Virtuoso.

 

Here is part of the technology file:

; Technology File NCSU FreePDK 45nm
;********************************
; LAYER DEFINITION
;********************************
layerDefinitions(
 techLayers(
 ;( LayerName                 Layer#     Abbreviation )
 ;( ---------                 ------     ------------ )
  ( IP                        63         IP )
  ( nwell                     3          nwell )
  ( pwell                     2          pwell )
  ( nimplant                  4          nimplant )
  ( pimplant                  5          pimplant )
  ( active                    1          active )
  ( vtg                       6          vtg )
  ( vth                       7          vth )
  ( thkox                     8          thkox )
  ( poly                      9          poly )
  ( contact                   10         contact )
  ( metal1                    11         metal1 )
  ( via1                      12         via1 )
  ( metal2                    13         metal2 )
  ( via2                      14         via2 )
  ( metal3                    15         metal3 )
  ( via3                      16         via3 )
  ( metal4                    17         metal4 )
  ( via4                      18         via4 )
  ( metal5                    19         metal5 )
  ( via5                      20         via5 )
  ( metal6                    21         metal6 )
  ( via6                      22         via6 )
  ( metal7                    23         metal7 )
  ( via7                      24         via7 )
  ( metal8                    25         metal8 )
  ( via8                      26         via8 )
  ( metal9                    27         metal9 )
  ( via9                      28         via9 )
  ( metal10                   29         metal10 )
  ( DRC                       400        DRC )
 ) ;techLayers
 techLayerPurposePriorities(
 ;layers are ordered from lowest to highest priority
 ;( LayerName                 Purpose    )
 ;( ---------                 -------    )
  ( IP                        drawing )
  ( nwell                     drawing )
  ( pwell                     drawing )
  ( nimplant                  drawing )
  ( pimplant                  drawing )
  ( active                    drawing )
  ( vtg                       drawing )
  ( vth                       drawing )
  ( thkox                     drawing )
  ( poly                      drawing )
  ( contact                   drawing )
  ( metal1                    drawing )
  ( via1                      drawing )
  ( metal2                    drawing )
  ( via2                      drawing )
  ( metal3                    drawing )
  ( via3                      drawing )
  ( metal4                    drawing )
  ( via4                      drawing )
  ( metal5                    drawing )
  ( via5                      drawing )
  ( metal6                    drawing )
  ( via6                      drawing )
  ( metal7                    drawing )
  ( via7                      drawing )
  ( metal8                    drawing )
  ( via8                      drawing )
  ( metal9                    drawing )
  ( via9                      drawing )
  ( metal10                   drawing )
  ( DRC                       drawing )
 ) ;techLayerPurposePriorities
 techDisplays(
 ;( LayerName    Purpose      Packet          Vis Sel Con2ChgLy DrgEnbl Valid )
 ;( ---------    -------      ------          --- --- --------- ------- ----- )
  ( IP           drawing      PacketName_0     t t t t t )
  ( nwell        drawing      PacketName_2     t t t t t )
-------------------------------------------------------------------------------------------------------------------
and here is part of my streamOut.map file generated by Encounter:
metal1 NET 1 0
metal1 SPNET 2 0
metal1 PIN 3 0
metal1 LEFPIN 4 0
metal1 FILL 5 0
metal1 FILLOPC 6 0
metal1 VIA 7 0
metal1 VIAFILL 8 0
metal1 VIAFILLOPC 9 0
metal1 LEFOBS 10 0
NAME metal1/NET 11 0
NAME metal1/SPNET 12 0
NAME metal1/PIN 13 0
NAME metal1/LEFPIN 14 0
via1 LEFPIN 15 0
via1 FILL 16 0
via1 FILLOPC 17 0
via1 VIA 18 0
via1 VIAFILL 19 0
via1 VIAFILLOPC 20 0
Any help would be appreciated 
  • Cancel
Parents
  • Kari
    Kari over 8 years ago
    you need the stream-in map, which should have come with the PDK. It's not the same format as the Encounter streamOut map. since this question is virtuoso-centric, maybe post to the Custom IC forum. There might be someone there who can tell you exactly what file to look for or where to find it.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 8 years ago
    you need the stream-in map, which should have come with the PDK. It's not the same format as the Encounter streamOut map. since this question is virtuoso-centric, maybe post to the Custom IC forum. There might be someone there who can tell you exactly what file to look for or where to find it.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information