As far as cost goes, it again comes down to what you are trying to achieve. Many times, the cost of the tools could be justified easily by showing the savings - for example, saving a speedgrade (use a slower speedgrade part) by the use of physical synthesis has a great impact on the total cost of your board.
Using placement constraints is okay if you are trying to meet timing on certain small sections of the designs AND you know if these are going to be the bottleneck. It is not feasible to do this if you have a big design that is using 90+% of the slices/LEs etc.
As FPGAs are getting bigger and can accomodate complex designs, there are newer physical synthesis tools in the market that have different approaches to solving the timing closure issue. It is definitely worthwhile to check them out.
IMHO these tools are very expensive and for my needs I am better with
> placement constraints by hand then using these tools. This gives me even
> better control and saves me time and money. But your needs may be
> different. To be honest I don't see the benefit of e.g. Amplify which
> would be worth the money.
>
> BR Chris
>
>
> Alfredo wrote:
>
> > Thanks Neeraj, I have some notion of the benefits of these tools but I
do not
> fully understand how to differentiate them and how to choose one for a
specific
> task: which one is better for IP immersion, which one help manage better
for
> stitching blocs at the top level (modular design), which one interfaces
better
> with STA tools for timing closure, ...
> > I think I'll need to run some testbenches to get a good grasp on these
tools and
> how to better use them.
> >
> > Does anyone have a book or documetation that I can read to learn more
about this
> subject?
> >
> > The only documentation I have now is what the vendors are providing.
> >
> > Thanks,
> >
> > ***
> > Alfredo.
> >
> >
> >>The Physical synthesis and SVP tools from 3rd parties are not just mere
> >>Floorplanners. In a nutshell, Amplify and Precision Physical do
something
>>called "Placement Aware Synthesis", which is the most important thing to
do
>>to bring down the routing delays...whereas SVP tools like the one from
Hier
>>help provide final representation of the PLD design early in the design
> >>stage.
> >>
> >>Floorplanning is just one of the many features built into these tools,
> >>though an important one, to help achieve performance goals and reducing
the
>>compile time of the design by working closely with the P&R tools...
> >>
> >>Feel free to correct me if I am wrong...
> >>
> >>--Neeraj
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>>Hi,
> >>>physical synthesis tools for FPGAs are being introduced by a few
vendors.
>>
> >>Have
> >>
> >>>you read, evaluated or seen a presentation about these tools:
> >>>Synplicity's Amplify:
> >>
> >>
formatting link
> >>
> >>>Mentor's Precision:
formatting link
> >>>Hier Design's Plan Ahead:
formatting link
> >>>
> >>>Do you have any thoughts about what you would be looking for in an FPGA
> >>>floorplanner from a 3rd party (not the FPGA manufacturer)?
> >>>
> >>>Do you use Altera's or Xilinx floorplanner now?
> >>>
> >>>Thanks for you input,
> >>>
> >>>***
> >>>Alfredo.
> >>>
> >>>
> >>
> >>
> >
> >
>