Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 17914
  • 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

Importing a def file (made in encounter) into virtuoso.

Mikutine

Dear users,

I've made a design in Encounter with the Nangate OpenCell Library. Everything is placed and routed, and I have extracted the def file.

I want to use that def file, so I can import it in Virtuoso, because I have to add some shape pins in there. The first thing I did, is make an new library, where I attached the technology file from the FreePDK45 of Nangate.

When I want to import the def file in Virtuoso, I fill in the following in the Virtuoso DEF In form:

-DEFin File Name: "the path to the def file"

-Target Library Name: "the new library that I've made with the attached technology file

-Ref. Technology Libraries: "the nangate opencell library"

-Target Cell Name: "the name of cell''

-Target View Name: "the name of layout" 

I get the following errors:

'The library "router_lib" is already attached to technology library "NCSU_TechLib_FreePDK45". Cannot replace this with a derived technology database unless the original attached technology library is part of the new references. defin translations has failed'

So it basically says that the attached technology file to the new library, and the ref. technology library are conflicting. But when I try to import it without one of these two libraries/technology file, I get some missing information about via's.

Can somebody explain me how I can fix this? Thank you in advance! 

Parents

  • Dear Alex,

    Basically, I understand what you are trying to say. But I think there is a misunderstanding.

    As far as I know, the via information is in the standard cell library (Nangate OpenCellLibrary). This is the library that I've used to synthesize a design (in Synopsys Design Compiler) and place&route (in Encounter). 

    Now I want to import that design back into Virtuoso, because I have to edit something in the layout (add some shape pins). I think for this, you need the technology library (NCSU_TechLib_FreePDK45). But doesn't it need at the same time that standard cell library that I used pryor to do synthesize, place&route?

    I've heard that it is easier to import a design through a gds (stream) file. But then again, I need a technology library. But it gives me the same conflicts.

    So, if you maybe have a solution for this?

    Thank you in advance.

    Kind regards,

     Milovan 

     

Reply

  • Dear Alex,

    Basically, I understand what you are trying to say. But I think there is a misunderstanding.

    As far as I know, the via information is in the standard cell library (Nangate OpenCellLibrary). This is the library that I've used to synthesize a design (in Synopsys Design Compiler) and place&route (in Encounter). 

    Now I want to import that design back into Virtuoso, because I have to edit something in the layout (add some shape pins). I think for this, you need the technology library (NCSU_TechLib_FreePDK45). But doesn't it need at the same time that standard cell library that I used pryor to do synthesize, place&route?

    I've heard that it is easier to import a design through a gds (stream) file. But then again, I need a technology library. But it gives me the same conflicts.

    So, if you maybe have a solution for this?

    Thank you in advance.

    Kind regards,

     Milovan 

     

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.