• 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. Configuring new PDK

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 127
  • Views 20142
  • 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

Configuring new PDK

Vishnuram
Vishnuram over 11 years ago

I was configuring the new PDK in Cadence virtuoso version IC6.1.4.500.12( one PDK is already existing in the home directory). so i make a new folder(named "new_PDK") in the home directory and added the files(cadence.cshrc, cds.lib, .cdsinit, .cdsenv, bindkeys and the PDK folder). when i source the cadence.cshrc file from from folder new_PDK, i am listing out the problems i am facing:

 

1. its shows techfile conflict

" there is a conflict in techfile graph

  Look at techfile reported error massage in CIW

  correct techfile conflict before proceeding "

 

  Whill loading the files, it takes techfile.tf, pdkutil and display.drf file from PDK folder olny.

 

2. In the schematic window, i can call the instances but unable to connect using wires(wires are not coming. rest all shortcut keys are working.

 

3. In the layer selection windows(LSW) palletes are not visible.

" (LE-101804): Cannot get valid layer form LSW window. "

 

   i can see the layer when i click on layer but again shows blank when i scroll it down.

 

4. Cadence windows crash when i try to make any layer in the layout.

"  \o (LE-101804): Cannot get valid layer form LSW window.
   \a leSetLSWBBox(list(57:328 207:1028)) "

 

Everthing working properly with the old PDK exist in home directory.

 

Please help me out.

 

  • Cancel
Parents
  • theopaone
    theopaone over 11 years ago

     I would suspect that this conflict is causing the problem or it may be an issue with the dbuPerUU on the viewTypes (usually the layout viewType). I don't have access to Virtuoso at this time, I'm on holiday, but check the dbuPerUU and the mfgGridResolution in both techfiles (dump the techfiles if you don't have a .tf) and post the relevant sections here.

    *WARNING* (TECH-2000178): A Default Manufacturing Grid conflict has been detected in the technology hierarchy.

    It is caused by the following list of Libraries: silterraB18V; cdsDefTechLib;

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • theopaone
    theopaone over 11 years ago

     I would suspect that this conflict is causing the problem or it may be an issue with the dbuPerUU on the viewTypes (usually the layout viewType). I don't have access to Virtuoso at this time, I'm on holiday, but check the dbuPerUU and the mfgGridResolution in both techfiles (dump the techfiles if you don't have a .tf) and post the relevant sections here.

    *WARNING* (TECH-2000178): A Default Manufacturing Grid conflict has been detected in the technology hierarchy.

    It is caused by the following list of Libraries: silterraB18V; cdsDefTechLib;

     

    • 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