FPGA Design Best Practices for Team-based Design
FPGA Design: Best Practices for Team-based Design Philip Simpson Many Companies struggle with establishing a working FPGA design methodology across design teams in their Company. As design teams become more dispersed globally, the need increases for a sta
- PDF / 4,077,105 Bytes
- 162 Pages / 439.37 x 666.142 pts Page_size
- 18 Downloads / 200 Views
5
Philip Simpson
FPGA Design Best Practices for Team-based Design
Philip Simpson Altera Corporation San Jose, CA 95134 USA [email protected]
ISBN 978-1-4419-6338-3 e-ISBN 978-1-4419-6339-0 DOI 10.1007/978-1-4419-6339-0 Springer New York Dordrecht Heidelberg London Library of Congress Control Number: 2010930598 © Springer Science+Business Media, LLC 2010 All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer Science+Business Media, LLC, 233 Spring Street, New York, NY 10013, USA), except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. © 2010 Altera Corporation ALTERA, ARRIA, CYCLONE, HARDCOPY, MAX, MEGACORE, NIOS, QUARTUS & STRATIX are Reg. U.S. Pat & Tm. Off. and Altera marks in and outside the U.S. Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com)
Preface
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. I worked with the top talent in Altera Engineering to develop a Best Practices Design methodology based upon Altera’s experience and the techniques used by many customers successfully in FPGA design. The resulting methodology was presented and implemented at the customer, with great success. Through the analysis of past customer data and feedb
Data Loading...
