• 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. Techfile, GDS Import, Layout DRC Verification

Stats

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

Techfile, GDS Import, Layout DRC Verification

StreamCX
StreamCX over 14 years ago
I have My_ADC ( cds6 project initially )project with cds.lib containing link to cds.lib file of DRC Project and techfile project.

I have layout in GDS converted to use in My_ADC by import.

I have convert layout from GDS to My_ADC using standard Cadence tech.lib but I need convert this by using my tech.lib

I have DRC Rules Project (cds5 converted to 6).

I have techfile project where I keep techfile.db and file with ext .oa. That files were maked from copying them from converted DRC project.

Convertion of DRC project from cds5 to 6 format was with no errors.

When I try to load layout from My_ADC project using DRC rules from DRC Rules Project project, error and warnings appears (in file).

When I try to verificate layout, IC crushed with panic error.

When I try to reimport GDS layout another errors appears, and error messages are different depending of what I have write in attach techfile tab in FILE/Import/STREAm

1) Attach  technology library field is "cdsDefTechLib"

Loading transUI.cxt
XStream/strminui is running (PID = ipc:3 )...
*WARNING* ddLibDefListCallback::onLoadWarnings: libdef file 'lib.defs' load warning:
 'Unable to open library test at path /home/starsa/lib018/Myxnor/./test: Invalid Lib Path'
*WARNING* The directory: '/home/starsa/lib018/Myxnor/test' does not exist
        but was defined in libFile '/home/starsa/lib018/Myxnor/cds.lib' for Lib 'test'.
INFO (TECH-150003): The technology database "cdsDefTechLib" has been automatically
updated from revision 226610(DM 0) to revision 227612(DM 0)
in virtual memory. It will be opened in 'a' mode for you to save it to disk.
*WARNING* (TECH-250037): The technology database "cdsDefTechLib" has been automatically
updated from revision 226610 to revision 227612 in virtual memory,
but is not good to be saved to disk because Attempt to save a read-only technology database.
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L20 (#20); cdsDefTechLib/cutactive (#20);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L26 (#26); cdsDefTechLib/L26 (#26);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L26 (#26); cdsDefTechLib/L26 (#26);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L16 (#16); cdsDefTechLib/L16 (#40);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L16 (#16); cdsDefTechLib/cpimp (#16);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L52 (#52); cdsDefTechLib/L52 (#48);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L52 (#52); cdsDefTechLib/mcap (#52);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L22 (#22); cdsDefTechLib/L22 (#19);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L22 (#22); cdsDefTechLib/L39 (#22);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L41 (#41); cdsDefTechLib/dummy (#41);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L32 (#32); cdsDefTechLib/L32 (#37);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L32 (#32); cdsDefTechLib/poly1txt (#32);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L13 (#13); cdsDefTechLib/L13 (#46);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L13 (#13); cdsDefTechLib/poly2 (#13);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L17 (#17); cdsDefTechLib/ckimp (#17);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L53 (#53); cdsDefTechLib/mdiod (#53);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L12 (#12); cdsDefTechLib/psv (#12);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L8 (#8); cdsDefTechLib/nimp (#8);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L6 (#6); cdsDefTechLib/cnimp (#6);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L5 (#5); cdsDefTechLib/active (#5);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L4 (#4); cdsDefTechLib/protn (#4);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L3 (#3); cdsDefTechLib/protp (#3);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L1 (#1); cdsDefTechLib/L1 (#45);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L1 (#1); cdsDefTechLib/pwell (#1);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L9 (#9); cdsDefTechLib/pimp (#9);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L51 (#51); cdsDefTechLib/mres (#51);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L7 (#7); cdsDefTechLib/poly1 (#7);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L10 (#10); cdsDefTechLib/con (#10);
*WARNING* : A Layer Name conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L30 (#30); cdsDefTechLib/L30 (#0);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L30 (#30); cdsDefTechLib/L27 (#30);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L31 (#31); cdsDefTechLib/textu (#31);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L15 (#15); cdsDefTechLib/me2 (#15);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L11 (#11); cdsDefTechLib/me1 (#11);
*WARNING* : A Layer Number conflict has been detected in the technology hierarchy.
     It is caused by the following list of layers: My_ADC/L14 (#14); cdsDefTechLib/via (#14);
*WARNING* Unable to set references on tech because conflicts would result in tech My_ADC.
ERROR (179): StrmIn has detected a conflict in the technology database graph. This could be because the technology library of the target library has conflict in its technology database graph or the specified reference technology libraries have a conflict with the technology library of the target library. Resolve the conflict manually before running the StrmIn application.
ERROR (79): Failed to attach technology file from the library cdsDefTechLib because a technology file already exists in the target library.
Translation Failed.

Or 2)

Attach  technology library field is empty

 ********************************************************************************
Product   : Virtuoso(R) XStream In
Program   : @(#)$CDS: strminui version 6.1.3 01/16/2009 01:23 (cic612lnx) $
          : sub-version IC6.1.3.500.6
Started at: 22-Oct-2010  15:40:35
User Name : starsa
Host Name : host
Directory : /home/starsa/lib018/Myxnor
CADENCE Design Systems, Inc.
********************************************************************************
Info: Cellview Rev Num:99,  Tech Rev Num:59
ERROR (179): StrmIn has detected a conflict in the technology database graph. This could be because the technology library of the target library has conflict in its technology database graph or the specified reference technology libraries have a conflict with the technology library of the target library. Resolve the conflict manually before running the StrmIn application.

How can I fix this and verify layout?
  • layer5normalerror.txt
  • View
  • Hide
  • Cancel
Parents
  • StreamCX
    StreamCX over 14 years ago

     Quek

    Thanks. 

    I found that file in my tech library. Problem was in that I earlier try to divide that library.

    But I have another question.

    For example, when I try import .gds file to destination library with path equal to tech library path, results are with no errors.

    But when they are different  

    ERROR (79): Failed to attach technology file from the library techtest because a technology file already exists in the target library.
    Translation Failed.
    ERROR (76): Failed to open technology file `My_LIb` in the append mode. Therefore, automatic layer mapping cannot be done. Use the layer map file to continue.
    Translation Failed.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StreamCX
    StreamCX over 14 years ago

     Quek

    Thanks. 

    I found that file in my tech library. Problem was in that I earlier try to divide that library.

    But I have another question.

    For example, when I try import .gds file to destination library with path equal to tech library path, results are with no errors.

    But when they are different  

    ERROR (79): Failed to attach technology file from the library techtest because a technology file already exists in the target library.
    Translation Failed.
    ERROR (76): Failed to open technology file `My_LIb` in the append mode. Therefore, automatic layer mapping cannot be done. Use the layer map file to continue.
    Translation Failed.

    • 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