Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I'm reasonably certain the answer to this question no, but will pose it anyway, hoping to stimulate some thought.Can an attachment (axlDBCreateAttachment) to a symbol be accessed in the design where the symbol is referenced?We know that an attachment can exist in a .dra or .brd file. It appears as the axl*Attachment functions only support accessing the attachment at the same level where it is created.Attachments look to be a very interesting vehicle for several purposes. One thought was to use them to manage revision history. In a scenario such as this, it would be useful to interrogate the design in which the symbols are placed and peruse their revision attachments. But it appears as if you would have to dump the symbols and then open each of the .dra files. Not a pleasant thought.Anyone have any additional thoughts?
Hi Charlie,How have you been? I thought about somthing like this a few months back, but never got the time to investigate this.I believe you if you say that you can't access symbol level attachements, which in a way is in line with the hierarchy architecure for Allegro platform tools. What I mean is that once the symbol is instantiated, it becomes a different component with unique attributes etc. Kind of like hierarchical block in ConceptHDL.A solution could be to create an attachement in the board file that tracks all components by refdes and their respective symbol revision. In other words, after you placed a compmonent you go out and find the revision of the symbol (where ever that comes from; i.e File system like ADW or systems like Windchill or Agile ;-)) add update the brd revision attachment list. Similarly you then can write startup routines that check the database symbol revision against the PDM system.Think about linking padstacks, shapes and all the other good stuff and you have a pretty good solution in place that ensures consistent symbol usage.I'll investigate this a bit over the next weeks and let you know if their is a way in SKILL to access this type of info. This shouldn't be to hard to do.Andy
As a followup to this, it does appear as if the attachments are actuallly NOT carried forward from the symbol into the design. if the symbols are dumped from the design, the resulting .dra contains no attachments, even though the original .dra file did.Andy,Yes there are a number of other ways to track revisions. We are currently doing that today and have been for many years. We can tell the user today that they have out-of-date symbols by comparing the library revs with the revin the database. What is doesn't tell them is exactly what changed from revision to revsion (the history). We were hoping to embed this within the symbol itself using the attachment. We can extend the functionality using additional properties and scripts. This just looked to be an intriguing solution.Let me know if you find anything useful.
While attachments are carried from the dra to psm they are not imported into a board when the symbol is loaded into a design.
Are the any thoughts of changing that behavior?
There have been no requests in this area.
PCR 4015565 has been filed to request this enhancement. If there are others out there that would see value in this addition, please add you names to the list. Here is a description of the requested PCR.Description: Attachments made to symbols using the axlDBCreateAttachment function arenot carried forward into the parent design. If we dump the librariesfrom a design, the resulting .dra file do not have the attachments, eventhough they were in the original symbol when it was created andsusequently placed in the board.We would like to see this functionality implemented. Specifically, wewould like the attachments to be made available in the symbol defintionobject in Allegro and the axlDBGetAttachment function to be updated toallow a symbol DBID object to be passed to allow the retrieval of theattachments on that object. This would require that theaxlGBGetAllAttachments function be enhanced to allow similarfunctionality.
This is great. Thanks Charlie. Count me in!