• 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. Custom IC Design
  3. How to convert a technology file to a layer mapping fil...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 20515
  • 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

How to convert a technology file to a layer mapping file

SUEE
SUEE over 12 years ago

Hi all,

From one foundry I have one technology file with a name called "techfile"

How could I get a layer mapping file from this fiile?

 

I want to do so is because:

(1) I have a gds file from another souce, that has some layers (number) not defined in said "techfile". Let's call those special layers "LayersS". I do not have a tech file from that source. In addition to those

(2) I want to use some layers we generally not used in "techfile", eg TSV and SOI, to show the those "LayerS" in Cadence

(3) So I need a layer mapping file in "stream in"/'stream out" to translate those "LayerS" to TSV layer. 

(4) This is not only stream in but also stream out, because eventually I will tapeout a chip containing those "LayerS" with correct layer numbers.

 

Could someone tech me how to do it ?  Or how to solve my problem in another way?

Many thanks !! 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago
    If the technology library is called, say, gpdk045, then the file would be inside the library and called gpdk045.layermap

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago
    If the technology library is called, say, gpdk045, then the file would be inside the library and called gpdk045.layermap

    Andrew
    • 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