1/1

|
opencores design guidelines
by jt_eaton on Jan 27, 2010 |
jt_eaton
Posts: 88 Joined: Aug 18, 2008 Last seen: Feb 9, 2012 |
||
|
I noticed that there is an old copy of the design guidelines( both doc and pdf) in the common module. Some one should either remove them or replace with an up to date copies.
I would also like to add a section to guidelines for the SYNTHESIS flag. Synopsys originally recommended using synopsys translate_on and translate_off pragmas to surround any simulation only code in the rtl that cannot be synthesised. A lot of projects use this. But this has caused problems in that every tool that reads rtl has to support synopsys pragmas and this hasn't always been easy. The current recommendation is to create a `define SYNTHESIS flag and use this to select between the synthesis and the simulation versions of a file. All tools support this. How does opencores determine what changes should be made to the guidelines? John Eaton |
|||
|
RE: opencores design guidelines
by rfajardo on Mar 12, 2010 |
rfajardo
Posts: 270 Joined: Jun 12, 2008 Last seen: Feb 9, 2012 |
||
|
Hi John,
where can I find this common module in order to take a look on those guidelines? Thanks, Raul |
|||
|
RE: opencores design guidelines
by jt_eaton on Mar 16, 2010 |
jt_eaton
Posts: 88 Joined: Aug 18, 2008 Last seen: Feb 9, 2012 |
||
|
Hi John,
where can I find this common module in order to take a look on those guidelines? Thanks, Raul svn co http://opencores.org/ocsvn/common/common/trunk common |
|||
1/1

