- ホーム
- > 洋書
- > 英文書
- > Science / Mathematics
Full Description
In August of 2006, an engineering VP from one of Altera's customers approached Misha Burich, VP of Engineering at Altera, asking for help in reliably being able to predict the cost, schedule and quality of system designs reliant on FPGA designs. At this time, I was responsible for defining the design flow requirements for the Altera design software and was tasked with investigating this further. As I worked with the customer to understand what worked and what did not work reliably in their FPGA design process, I noted that this problem was not unique to this one customer. The characteristics of the problem are shared by many Corporations that implement designs in FPGAs. The Corporation has many design teams at different locations and the success of the FPGA projects vary between the teams. There is a wide range of design experience across the teams. There is no working process for sharing design blocks between engineering teams. As I analyzed the data that I had received from hundreds of customer visits in the past, I noticed that design reuse among engineering teams was a challenge. I also noticed that many of the design teams at the same Companies and even within the same design team used different design methodologies. Altera had recently solved this problem as part of its own FPGA design software and IP development process.
Contents
Best Practices for Successful FPGA Design.- Project Management.- Design Specification.- Resource Scoping.- Design Environment.- Board Design.- Power and Thermal Analysis.- RTL Design.- IP and Design Reuse.- The Hardware to Software Interface.- Functional Verification.- Timing Closure.- In-System Debug.- Design Sign-Off.
