Home > Community > Blogs > Logic Design > introducing quot team fed quot
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more convenient.

Register | Membership benefits
Get email delivery of the Logic Design blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Introducing "Team FED"

Comments(2)Filed under: logic design, FED, TeamFED

Today we are launching the "Team FED" blog.  Similar to some of the other "Team" blogs here at Cadence, this will be focused on technical tips and tricks to help you get the most out of our products and methodologies.  In our case, the focus is on Front-End Design, hence the "FED" moniker.

We have some great Applications Engineers lined up to regularly post items, you can get a glimpse at the Team FED profile page.  And we will also have guest posters from time to time.

Please feel free to post comments in the blog posts to keep the discussions lively, or even to post suggestions for future topics.

And with that I will step out of the way and let the technical guys take over.

Jack Erickson
Product Marketing Director
Cadence Front-End Design

Comments(2)

By Pete Thomsen on March 5, 2009
I'd like to know what best practices people have found for entering VHDL at the RTL level. I haven't found any tools from Cadence to help with this, such as a state machine drawing to VHDL tool, or early design auto instantiation from an entity definition (cut and paste works, but the syntax is not identical. I'd also like to see the pin type added as a comment on the instantiation automatically by the tool). Another tool I'd like to see is one that would allow you to add a pin/signal through all levels of hierarchy automatically by specifying the top-level and final-level VHDL file/instance and the pin/signal name/type/size. This alone would save a LOT of time. Same thing goes for deleting pins/signals through a design hierarchy. Obviously these type of tools would have to be able to work with customer VHDL at any time during FED so we aren't locked into using the tools for everything.
Any FED improvements would be EXTREMELY welcome and there are probably TON's of ideas.  Maybe there are even tools that others have written that they would be able to make open-source to help the community?

By theASICguy on March 10, 2009
Pete,
With regards to the second tool you are asking for, you might want to look at Atrenta Genesis atrenta.com/.../1team_genesis.htm. I have not used it ... a friend at Atrenta pitched it to me over lunch at DAC last year. It might address what you are looking for or it might not.
Harry

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
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.