Thursday, July 29, 2010     Register | Login | Search | Contact Us
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Subject: about the error of "checkDesign -all"
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
sbssdh
Posts: 6
Online: User is Offline
7/20/2008 12:29 AM  
hi:

who can tell the cause of the following the error in the command "checkDesign -all"


**ERROR: Input netlist has a cell PANA1AP which is marked dont_use in the library.
**ERROR: Input netlist has a cell PX2 which is marked dont_use in the library.
**ERROR: Input netlist has a cell PI which is marked dont_use in the library.
**ERROR: Input netlist has a cell PO2 which is marked dont_use in the library.
**ERROR: Input netlist has a cell PO16 which is marked dont_use in the library.


3ks
Black Lutin
Posts: 11
Online: User is Offline
7/21/2008 1:04 AM  
Hi,

Generally, it is not a real problem. I suppose, according the names, these masters to be pads or macros. You have certainly a dont_use in your .lib file for these masters.
An other case is that the dont_use for the syntesis are not teh same than the dont_use for the encounter flow.
The last case is when during synthesis, people add master manually (by vhdl, or by editing the netlist). An with this method you cab add dont_use masters.

Regards ...
sbssdh
Posts: 6
Online: User is Offline
7/21/2008 1:56 AM  
hi:
   yes, these masters are pads, but they are the type that used by the IO  instance.
and when i synthesis, these masters are not set the "dont_use" attribute. 
   so  why  encounter report these errors?

  3ks
Black Lutin
Posts: 11
Online: User is Offline
7/21/2008 2:43 AM  
Hi,

Are you using the same .lib files under encounter and your synthesis tool ?
Perhaps also that encounter puts automatically a dont_use attribute on all pad masters. You can check this after having read your lib and LEF files with dbCommand.

Regards ....
Kari
Posts: 81
Online: User is Offline
7/21/2008 6:54 AM  
Hi 3ks,

Encounter is just warning you that you have a dont_use attribute on these cells in your .lib files, but they appear in the netlist. Since they are IO Pads, you can ignore this and continue with your flow (unless there is some reason those IO cells should not be used). It's always good to check these warnings though. Let's say you didn't want to use any buffers higher than 16x, so you had a dont_use on BUF24X and BUF32X, but the starting netlist contained some BUF24X cells. Then you would want to see this warning, so that you could swap those buffers out for lower drive buffers.

- Kari
sbssdh
Posts: 6
Online: User is Offline
7/22/2008 10:43 PM  

hi:
   i have solved these errors . this just because i set the IO's operation condition in VP script, but i
don't set the operation condition in implementation script. now i set the same operation conditon, these warning disappear.

  3ks

Posting to forums is available to community members only.
Login or Register

Forums > Digital IC > Floorplanning, Place and route > about the error of "checkDesign -all"


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.