throbber
\'-
`PR INC IP;LES
`PRACTICBS .
`'""~ :" .........
`.. 4\ . . ,,
`
`"1".\ .
`
`........ . . ,
`
`o.J
`
`~"- ...
`'"':t:
`
`Petition for Inter Partes Review of 
`U.S. Pat. No. 7,296,121
`IPR2015‐00158
`EXHIBIT
`Sony‐
`
`

`
`Page 57
`
`Todd Green
`Nate McFadden
`Andre Cuello
`Alisa Andreola
`
`AC(/uiring l!Clitor:
`Development Editor:
`Project Manager:
`Designer:
`Morgan Kaufinann Publishers is an imprint of Elsevier.
`30 Corporate Drive, Suite 400, Burlington, MA 01803, USA
`This book iis printed on acid-free p aper. §
`Copyright© 2010, Elsevier Inc. All rights reserved.
`
`No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including
`photocopying, recording, or any information storage and retrieval system, without permission in writing from the publisher. Details on
`how to seek permission, further information about the Publisher's permissions policies and our arrangements with organizations such
`as the Copyright Clearance Center and the Copyright Licensing Agency, can be found at our Web site: www. elsevier. com/permissions.
`
`This book and the individual contributions contained in it are protected under copyright by the Publisher (other than as may be noted
`herein).
`
`Notices
`Knowledge and best practice :in this field are constantly changing. As new research and experience broaden our understanding,
`changes in research methods, professional practices, or medical treatment may become necessary.
`
`Practitioners and researchers must-always rely on their own experience and knowledge in evaluating and using any information,
`methods, compounds, or experimen-ts described herein. In using such information or methods they should be mindful of their own
`safety and the safety of others, including parties for whom they have a professional responsibi.llity.
`
`To the fullest extent of the law, neither the Publisher nor the authors, contributors, or editors assume any liability for any injury and/ or
`damage to persons or property as a matter of product liability, negligence or otherwise, or from any use or operation of any methods,
`products, instructions, or ideas contained in the material herein.
`
`Library of Congress Cataloging-in-Publication Data
`Sass, Ronald (Ronald R.)
`Embedded systems design with platform FPGAs: Principles and Practices I Ronald Sass.
`p.cm.
`Includes bibliographical references.
`ISBN 978-0-12-374333-6
`1. Embedded computer systems. 2. Field programmable gate arrays. I. Title.
`TK7895.E42S27 2010
`004.16-<:lc22
`
`2010010632
`
`British Library Cataloguing-in-Publication Data
`A catalogue record for this book is available from the British Library.
`
`For information on all Morgan Kaufmann publications
`visit our Web site at www.mkjJ.comor www.elseuierdirect.com
`
`Printed in the United States of America
`10 11 12 13 5 4 3 2 1
`
`Typeset by: diacriTech, India
`
`Working together to grow
`libraries in developing countries
`www.elsevier.com I www.bookaid.org I www.sabre.org
`I .
`S b. f'
`ELSEVIER
`BOOK AID
`' a
`I e OUI1C at1011
`Intcrnation.•l
`
`

`
`58 Chapter 2 THE TARGET
`
`·,.
`' •
`
`1 I 1 I'
`
`r
`
`hardware. Over time, it was recognized that the descriptions could
`be used to simulate hardware circuits on a general-purpose pro(cid:173)
`cessor. This process of translating an HDL source into a form
`suitable for a general-purpose processor to mimic the hardware
`described is called simulation. Simulation has proven to be an
`extremely useful tool for developing hardware and verifying the
`functionality before physically manufacturing the hardware. It was
`only later that people began to synthesize hardware, automatically
`generating the logic configuration for the specified device from the
`hardware description language.
`Unfortunately, while simulation provided a rich set of con(cid:173)
`structs to help the designer test and analyze the design, many of
`these constructs extend beyond what is physically implementable
`within hardware (on the FPGA) or synthesize inefficiently into the
`FPGA resources. As a result, only a subset of hardware descrip(cid:173)
`tion languages can be used to synthesize designs to hardware. The
`objective of this section is to present two ofth_e more popular hard(cid:173)
`ware description languages, VHDL and Verilog. It is arguable to
`which is better suited !for FPGA design; both are presented here for
`completeness, but it is left to the readers to decide which (if any)
`is best suited for their needs. We will focus on VHDL throughout
`the remainder of this book as it becomes redundant to give two
`examples, one in VHDL and one in Verilog, for every concept. That
`being said, we will also focus within this section on synthesizable
`HDL and how it maps to the previous section's components.
`
`2.4.1 . VHDL
`VHDL, which stands for VHSIC1 Hardware Description Language,
`describes digital circuits. In simulation, VHDL source files are ana(cid:173)
`lyzed and a description of the behavior is expressed in the form
`of a netlist. A netlist is a computer representation of a collection
`of logic units and how they are to be connected. The logic units
`are typically AND/OR/NOT gates or some set of primitives that
`makes sense for the target (4-LUTs, for example). The behavior
`of the circuit is exercised by providing a sequence of inputs. The
`inputs, called test vectors, can be created manually or by writing a
`program/script that generates them. The component that is gen(cid:173)
`erating test vectors and driving the device under test is typically
`called a test bench.
`Synthesizable VHDL
`In VHDL, there are two major styles or forms ofwriting hard(cid:173)
`ware descriptions. Both styles are valid VHDL codes; however, they
`
`1 Very high-speed integrated circuit.
`
`I
`
`I
`
`I
`j
`i
`I
`I
`I
`
`J

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket