Stats

  • Locked Locked
  • Replies 9
  • Subscribers 91
  • Views 19333
  • 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

A problem with a BlackBox

meri

 Hi! I'm using a RAM of the AMS in my digital circuit. 

I've defined a blockbox with the line:  setImportMode -treatUndefinedCellAsBbox 1, and now I'm trying to load its floorPan (because I would like to see in the layout the metal of this block). These are the errors and warnings (they appears either if I load the floorPlan before then after defining the floorplan of the whole circuit):

**ERROR: Die Area is not defined
**WARN: Design Area's lower left corner is not on manufacture grid.
**WARN: Design Area's upper right corner is not on manufacture grid.
**ERROR: Incorrect width (0.00000)

Thanks a lot! 

 

Parents

  •  Meri,

    You would only use a .fp file of the RAM if you are currently designing the RAM itself in Encounter. If the RAM is a macro in your block or chip, all the physical info is represented by the LEF file. It still sounds like the blockages aren't right. Look inside the RAM LEF for the OBS section. Do you see anything there?

    As for the DRC issues, it's hard to know what's going on without a picture. When you say antenna violations, do you mean process antennas or geometry antennas? It sounds like you mean geometry antennas.

    - Kari

Reply

  •  Meri,

    You would only use a .fp file of the RAM if you are currently designing the RAM itself in Encounter. If the RAM is a macro in your block or chip, all the physical info is represented by the LEF file. It still sounds like the blockages aren't right. Look inside the RAM LEF for the OBS section. Do you see anything there?

    As for the DRC issues, it's hard to know what's going on without a picture. When you say antenna violations, do you mean process antennas or geometry antennas? It sounds like you mean geometry antennas.

    - Kari

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.