Thursday, January 08, 2009     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 Encounter Warning 'TA-549'
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
eminemshow
Posts: 75
Online: User is Offline
2/26/2008 6:55 PM  
hi All:

I get the following message when run timing analysis:

--> WARNING: Pin 'msd_ddr_phy/ddr_sstl/dll_ato_io125/AE' is driven 'ZERO' and
             'X' simultaneously, preserving 'X.' .
--> WARNING: Pin 'msd_ddr_phy/ddr_sstl/dll_dto_0_io121/OJ' is driven 'ZERO' and
             'X' simultaneously, preserving 'X.' .


Why? Does it relate to constant propagation? where comes the 'X'?
ejm
Posts: 8
Online: User is Offline
3/27/2008 3:14 PM  
If there a different drivers on a net, and they are not driving the same signal state (0,1,X) on to the
net, then system has to resolve which state the signal is in in order to propagate forward.

The Warning you see indicates that there is such a conflict - in the case between a X (unknown) state and 0 (ZERO)
state. The timer resolves this "conservatively" by keeping the X. All signals have a state value of X in the timer
unless some explicit state assertion is made (set_case_analysis), and propagated forward.

Other tools (PT I think) resolve the above scenario to ZERO rather than X. There is a CTE global to provide a similar
resolution policy:

set_global timing_resolve_driver_conflicts {conservative | aggressive}

default: conservative

(Note: for some reason this global is not in the current doc set. We'll look into getting that added)
eminemshow
Posts: 75
Online: User is Offline
3/27/2008 7:40 PM  
Many thanks. EJM!

If there is a X state, what does this stand for? Does X means '0' or '1'? Or X means 'high resistance state'?
Posting to forums is available to community members only.
Login or Register

Forums > Digital IC > Floorplanning, Place and route > About Encounter Warning 'TA-549'


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.