Tuesday, January 06, 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: EBD file simulation
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
zhuofan
Posts: 3
Online: User is Offline
5/30/2005 8:26 PM  
hi,
I have a question in EBD file simulation with SpecctraQuest.The IC vendor affords ibis files and EBD files for modeling the chip package.How could I implement the simulation using EBD files in SQ? Should I carry out the simulation with multi-board modeling? If so, how can I extract the EBD file to build a brd file?

Thanks!
horner
Posts: 0
Online: User is Offline
5/30/2005 9:20 PM  
The ibis2signoise program can be used to convert the EBD models into either boardmodels or, in some cases, package models. If there is a single path, or more importantly a one to one map of the pins in the EBD to a single IOCell(not like a memory module, where one connector pin goes to many IOCells) then you can use the
-ebdcomp switch when running ibis2signoise. This should then make a pkg model that you can use for the package. You build up the IBISDevice file as normal with the IOcells defined by the vendor, with the EBD converted package model assigned.

If you don't use this route, then you need to convert the EBD into a boardmodel and use the designlink process to simulate. This approach has a caveat right now in that the boardmodel cannot be used to extract a accurate model into SigXP. Look for an appnote to be posted soon to address this issue in more detail
zhuofan
Posts: 3
Online: User is Offline
5/31/2005 8:05 PM  
Thanks for your instant reply. The EBD just models the chip's package.I followed your instruction and translated the EBD file to a package model with ibis2signoise –ebdcomp command. Then I loaded the resulting IBISDevice model and assigned the model to the corresponding device. But some warning(some pin numbers are not defined in model) appeared, and some error occurred when I extract the net topology between this chip and other device. I found in the produced DML file, only chip die’s pin numbers exist, and there were no chip’s pin numbers description.But these pin numbers are present with boardmodel conversion method. Any other step should be done with the IBISDevice file?
Thanks!
Posting to forums is available to community members only.
Login or Register



ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.