Skip to main content
Book cover

FPGA Design

Best Practices for Team-based Design

  • Book
  • © 2010

Overview

  • Presents complete, field-tested methodology for FPGA design, focused on reuse across design teams
  • Offers best practices for FPGA timing closure, in-system debug, and board design
  • Details techniques to resolve common pitfalls in designing with FPGAs

This is a preview of subscription content, log in via an institution to check access.

Access this book

eBook USD 84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book USD 129.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book USD 109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

Table of contents (14 chapters)

Keywords

About this book

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.

Authors and Affiliations

  • Altera Corporation, San Jose, USA

    Philip Simpson

About the author

Phil Simpson is Altera’s senior manager for software technical marketing and product planning. In this role, Simpson is responsible for Altera’s Quartus II software and third-party EDA interfaces product planning and the creation of the Altera design flow software roadmap. Prior to joining Altera in 1996, Simpson held several engineering roles at various EDA and semiconductor companies, including EDA Solutions, Data I/O and Lucas Aerospace. Simpson holds a BS (with honors) in Electrical & Electronic Engineering from City University, London and an MSC (with distinction) in system design from the University of Central England, Birmingham, England.

Bibliographic Information

  • Book Title: FPGA Design

  • Book Subtitle: Best Practices for Team-based Design

  • Authors: Philip Simpson

  • DOI: https://doi.org/10.1007/978-1-4419-6339-0

  • Publisher: Springer New York, NY

  • eBook Packages: Engineering, Engineering (R0)

  • Copyright Information: Springer Science + Business Media LLC 2010

  • Hardcover ISBN: 978-1-4419-6338-3

  • Softcover ISBN: 978-1-4899-9789-0

  • eBook ISBN: 978-1-4419-6339-0

  • Edition Number: 1

  • Number of Pages: XV, 151

  • Topics: Circuits and Systems, Computer-Aided Engineering (CAD, CAE) and Design

Publish with us