ORCA® Synplicity® Interface Manual

Total Page:16

File Type:pdf, Size:1020Kb

ORCA® Synplicity® Interface Manual Last Link Previous Next ORCA® Synplicity® Interface Manual For Use With Synplicity® Synplify® Version 6.2.4 or higher and ORCA 2002, and ispLEVER 2.0 and higher Technical Support Line: 1-800-LATTICE or 408-826-6002 (international) Version 2002 1 Last Link Previous Next Synplicity Interface Manual Synplicity, Synplify, Simply Better Synthesis, and the ’S’, ’Y’, ’N’ blocks logo are registered trademarks of Syn- plicity, Inc. EPIC and Timing Wizard are trademarks of Xilinx, Inc. Exemplar is a trademark of Exemplar Logic, Inc. ORCA and Scuba are registered trademarks of Lattice Semiconductor Corporation. Synopsys is a trademark of Synopsys, Inc. Verilog and Verilog-XL are registered trademarks of the Cadence Design Systems, Inc. Viewlogic and ViewSim are registered trademarks of Viewlogic Systems,Inc. All other brands or product names are the trademarks or registered trademarks of their respective owners. Lattice Semiconductor Corporation Field Programmable Gate Arrays 5555 NE Moore Court Hillsboro, OR 97124 Copyright © 2004, Lattice Semiconductor Corporation, All rights reserved. 2 ORCA Foundry/Syplicity Interface Last Link Previous Next GO TO ¾ ORCA Foundry/Synplicity Interface Table of CONTENTS Contents OVERVIEW .................................................................................................................1 Cover Page SOFTWARE REQUIREMENTS ..............................................................................1 SETTING THE DESIGN ENVIRONMENT ..........................................................2 ORCA Web Site Environment Variables ..................................................................................2 ORCA/SYNPLIFY LIBRARY FILES .....................................................................3 ORCA FAQs DESIGN FLOW ...........................................................................................................5 Series 4 Synthesis Flow ................................................................................7 Tech Support DESIGN ENTRY .......................................................................................................10 SETTING TIMING CONSTRAINTS ....................................................................14 Index When to Set Timing Constraints ...............................................................14 Synplify Timing Attributes ........................................................................14 Synplify Timing Report ..............................................................................16 I/O BUFFER INSERTION .......................................................................................17 I/O Macrocell Instantiation ........................................................................17 Overriding the Default Padtype for Automatic I/O Insertion ...............22 Locking I/O Pins ..........................................................................................23 Locking I/O in the HDL File ..............................................................23 Locking I/O in the ORCA Preference File .......................................25 Placing Registers Near I/Os .......................................................................26 Bidirectional Buffer Insertion ....................................................................27 DESIGN EXAMPLES ..............................................................................................29 Designing with ORCA ................................................................................29 MACROCELL INSTANTIATION .........................................................................31 ORCA 2CA/2TA/2TB Macro Library Elements ....................................31 ORCA Series 3 Macro Library Elements ................................................32 ORCA Series 4 Macro Library Elements ................................................34 ORCA/Synplicity Interface i Contents Last Link Previous Next GO TO ¾ ORCA Foundry/Synplicity Interface Table of CONTENTS Contents Hard Macro Instantiation ............................................................................38 Cover Page SIMULATION OF NETLISTS GENERATED BY SYNPLIFY .......................40 DESIGN IMPLEMENTATION ...............................................................................41 ORCA Web Site DESIGN VERIFICATION .......................................................................................43 ORCA THE ORCA ENVIRONMENT in ispLEVER ......................................................44 FAQs Mapping the Design ....................................................................................44 Tech APPENDIX .................................................................................................................46 Support Memory Initialization .................................................................................46 Setting Initial Values in the in the HDL File ....................................46 Index Setting Initial RAM Values .................................................................47 Using GSR in ORCA Designs With Synplify .........................................51 Illegal Names/Characters in ORCA Design Flows ................................51 Programmable GSR Support (Series 3) ...................................................51 Passing Frequency Preferences (Series 3 and 4) .....................................53 ORCA/Synplicity Interface ii Contents Last Link Previous Next GO TO ¾ ORCA/Synplicity Interface Table of Contents Cover Page OVERVIEW ORCA This manual describes the Optimized Reconfigurable Cell Array (ORCA)® Library and Web Site the interface between the Synplicity® design tools and the ORCA place and route tools. Together, the tools provide a powerful and integrated high-level design environment for ORCA ORCA Field-Programmable Gate Arrays (FPGA). FAQs Note Tech Support Note that version numbers for the interface software are continually being updated with each release. Check with the vendor on version number and how it Index affects the file names or syntax that make it possible to perform tasks as they relate to creating designs with ORCA. Check with technical support with compatibility and support issues. SOFTWARE REQUIREMENTS The ORCA/Synplicity Interface is compatible with the following software: • Latest version of ispLEVER software with ORCA devices installed • Synplify version 7.3 or later ORCA/Synplicity Interface 1 Last Link Previous Next GO TO ¾ SETTING THE DESIGN ENVIRONMENT Table of Contents This section helps you customize your Synplicity environment for designing an ORCA FPGA. Cover Page Environment Variables ORCA Make sure you have installed the latest version of ispLEVER with ORCA devices Web Site installed and that the FOUNDRY environment variable is set. The FOUNDRY variable points to the ispFPGA (PC) or ispfpga (UNIX) directory. ORCA FAQs The variable should be set as follows: Tech $ setenv FOUNDRY <ispfpga_directory> Support Note Index Note that these variables are automatically set by the software and you should not have to manually set them. If for some reason, they are changed, this provides instruction for resetting them. ORCA/Synplicity Interface 2 Last Link Previous Next GO TO ¾ ORCA/SYNPLIFY LIBRARY FILES Table of Contents The following libraries are provided for the ORCA 2A FPGAs. These files are available in your synplcty/lib/lucent directory. Cover Page orca.vhd This VHDL file defines the ORCA components. In order to be able to directly instantiate ORCA library primitives in your VHDL design files, you will need to add the ORCA Web Site following statements in your VHDL design to access these components: ORCA library orca; FAQs use orca.orcacomp.all; Tech Support orca.v This Verilog® file defines the ORCA components for use with Verilog designs. Include this file at the top of the source file list when you want to directly instantiate Index ORCA library primitives in your verilog source. If you have version 7.3 or later of Synplify with ORCA Series 3 and Series 4 support, the library files have been renamed as below: orca2.vhd The VHDL library file for ORCA 2 components. For Synplify version 7.3 and later, if targeting the ORCA 2 architecture, add the following: library orca2; use orca2.orcacomp.all; orca3.vhd The VHDL library file for ORCA Series 3 components. For Synplify version 7.3 and later, if targeting the Series 3 architecture, add the following: library orca3; use orca3.orcacomp.all; orca4.vhd The VHDL library file for ORCA Series 4 components. For Synplify version 7.3 and later, if targeting the Series 4 architecture, add the following: ORCA/Synplicity Interface 3 Last Link Previous Next GO TO ¾ library orca4; use orca4.orcacomp.all; Table of Contents Cover The Verilog library files are now named orca2.v, orca3.v, and orca4.v for the respective Page architectures. Please contact Synplicity support in case of discrepancies. For updated library files for Verilog and VHDL in the ispLEVER environment, you can ORCA Web Site retrieve the files in the userware directory after ispLEVER installation. Refer to the complete paths below for PC and UNIX. ORCA Verilog header files: FAQs $FOUNDRY\userware\NT\4E_VERILOG_HEADERS\orca4_synplify.v Tech $FOUNDRY/userware/unix/4E_Verilog_Headers/orca4_synplify.v Support VHDL header files (also in same path): Index $FOUNDRY\userware\NT\4E_VERILOG_HEADERS\orca4_synplify.vhd $FOUNDRY/userware/unix/4E_Verilog_Headers/orca4_synplify.vhd Note There are many HDL source files available in the userware directory to ensure the successful instantiation
Recommended publications
  • Customer PPT Rev 30
    LATTICE SEMICONDUCTOR The Leader in Low Power, Small Form Factor, Secure FPGAs First Quarter, 2019 Lattice Semiconductor (NASDAQ: LSCC) [1] Safe Harbor This presentation contains forward-looking statements that involve estimates, assumptions, risks and uncertainties, including all information under the heading 1Q 19 Business Outlook. Lattice believes the factors identified below could cause our actual results to differ materially from the forward-looking statements. Factors that may cause our actual results to differ materially from the forward-looking statements in this presentation include global economic uncertainty, overall semiconductor market conditions, market acceptance and demand for our new and existing products, the Company's dependencies on its silicon wafer suppliers, the impact of competitive products and pricing, and technological and product development risks. In addition, actual results are subject to other risks and uncertainties that relate more broadly to our overall business, including those risks more fully described in Lattice’s filings with the SEC including its annual report on Form 10-K for the fiscal year ended December 30, 2017 and its quarterly filings on Form 10-Q. Certain information in this presentation is identified as having been prepared on a non-GAAP basis. Management uses non- GAAP measures to better assess operating performance and to establish operational goals. Non-GAAP information should not be viewed by investors as a substitute for data prepared in accordance with GAAP. You should not unduly rely on forward-looking statements because actual results could differ materially from those expressed in any forward- looking statements. In addition, any forward-looking statement applies only as of the date on which it is made.
    [Show full text]
  • FPGA Design Security Issues: Using the Ispxpga® Family of Fpgas to Achieve High Design Security
    White Paper FPGA Design Security Issues: Using the ispXPGA® Family of FPGAs to Achieve High Design Security December 2003 5555 Northeast Moore Court Hillsboro, Oregon 97124 USA Telephone: (503) 268-8000 FAX: (503) 268-8556 www.latticesemi.com WP1010 Using the ispXPGA Family of FPGAs to Lattice Semiconductor Achieve High Design Security Introduction In today’s complex systems, FPGAs are increasingly being used to replace functions traditionally performed by ASICs and even microprocessors. Ten years ago, the FPGA was at the fringe of most designs; today it is often at the heart. With FPGA technology taking gate counts into the millions, a trend accelerated by embedded ASIC-like functionality, the functions performed by the FPGA make an increasingly attractive target for piracy. Many tech- niques have been developed over the years to steal designs from all types of silicon chips. Special considerations must now be made when thinking about protecting valuable Intellectual Property (IP) implemented within the FPGA. The most common FPGA technology in use today is SRAM-based, which is fast and re-configurable, but must be re-configured every time the FPGA is powered up. Typically, an external PROM is used to hold the configuration data for the FPGA. The link between the PROM and FPGA represents a significant security risk. The configuration data is exposed and vulnerable to piracy while the device powers up. Using a non-volatile-based FPGA eliminates this security risk. Traditionally, non-volatile FPGAs were based on Antifuse technology that is secure, but very expensive to use due to its one-time programmability and higher manufacturing costs.
    [Show full text]
  • Handoutshandouts
    HandoutsHandouts FPGA-related documents 1. Introduction to Verilog, P. M. Nyasulu and J. Knight, Carleton University, 2003 (Ottawa, Canada). 2. Quick Reference for Verilog HDL, R. Madhavan, AMBIT Design Systems, Inc, Automata Publishing Company, 1995 (San Jose, CA). Project-related documents 3. Project Guidelines and Project Specifications. (I’ll hand these out in lab) IntroductionIntroduction toto FPGAsFPGAs Outline: 1. What’s an FPGA ? Æ logic element “fabric”, i.e. logic gates + memory + clock trigger handling. 2. What’s so good about FPGAs ? Æ FPGA applications and capabilities Æ FPGAs for physicists 3. How do you program an FPGA ? Æ Intro to Quartus II Æ Schematic design Æ Verilog HDL design WhatWhat’’ss anan FPGAFPGA An FPGA is: - a Field Programmable Gate Array. - a programmable breadboard for digital circuits on chip. The FPGA consists of: - programmable Logic Elements (LEs). - programmable interconnects. - custom circuitry (i.e. multipliers, phase- lock loops (PLL), memory, etc …). Programmable Programmable Interconnects Logic [Figure adapted from Low Energy FPGAs – Architecture and Design, by V. George and J. M. Rabaey, Kluwer Academic Publishers, Boston (2001).] LogicLogic ElementElement (LE)(LE) An FPGA consists of a giant array of interconnected logic elements (LEs). The LEs are identical and consist of inputs, a Look-Up Table (LUT), a little bit of memory, some clock trigger handling circuitry, and output wires. global LUTLUT inputs inputs outputs local outputs MemoryMemory local clock (a few bits) CLOCK triggers signals feedback Figure: Architecture of a single Logic Element InterconnectInterconnect ArchitecturesArchitectures Row-Column Architecture Island Style Architecture Sea-of-Gates Architecture Hierarchical Architecture FPGAFPGA devicesdevices (I)(I) 2 primary manufacturers: 1.
    [Show full text]
  • FPGA Design Guide
    FPGA Design Guide Lattice Semiconductor Corporation 5555 NE Moore Court Hillsboro, OR 97124 (503) 268-8000 September 16, 2008 Copyright Copyright © 2008 Lattice Semiconductor Corporation. This document may not, in whole or part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine- readable form without prior written consent from Lattice Semiconductor Corporation. Trademarks Lattice Semiconductor Corporation, L Lattice Semiconductor Corporation (logo), L (stylized), L (design), Lattice (design), LSC, E2CMOS, Extreme Performance, FlashBAK, flexiFlash, flexiMAC, flexiPCS, FreedomChip, GAL, GDX, Generic Array Logic, HDL Explorer, IPexpress, ISP, ispATE, ispClock, ispDOWNLOAD, ispGAL, ispGDS, ispGDX, ispGDXV, ispGDX2, ispGENERATOR, ispJTAG, ispLEVER, ispLeverCORE, ispLSI, ispMACH, ispPAC, ispTRACY, ispTURBO, ispVIRTUAL MACHINE, ispVM, ispXP, ispXPGA, ispXPLD, LatticeEC, LatticeECP, LatticeECP-DSP, LatticeECP2, LatticeECP2M, LatticeMico8, LatticeMico32, LatticeSC, LatticeSCM, LatticeXP, LatticeXP2, MACH, MachXO, MACO, ORCA, PAC, PAC-Designer, PAL, Performance Analyst, PURESPEED, Reveal, Silicon Forest, Speedlocked, Speed Locking, SuperBIG, SuperCOOL, SuperFAST, SuperWIDE, sysCLOCK, sysCONFIG, sysDSP, sysHSI, sysI/O, sysMEM, The Simple Machine for Complex Design, TransFR, UltraMOS, and specific product designations are either registered trademarks or trademarks of Lattice Semiconductor Corporation or its subsidiaries in the United States and/or other countries. ISP, Bringing the Best Together, and More
    [Show full text]
  • FPGA Configuration Flash Memory AT17F32
    Features • Programmable 33,554,432 x 1-bit Serial Memories Designed to Store Configuration Programs for Field Programmable Gate Arrays (FPGAs) • 3.3V Output Capability • 5V Tolerant I/O Pins • Program Support using the Atmel ATDH2200E System or Industry Third Party Programmers • In-System Programmable (ISP) via 2-wire Bus • Simple Interface to SRAM FPGAs • Compatible with Atmel AT40K and AT94K Devices, Altera® FLEX®, APEX™ Devices, FPGA Stratix™, Lattice Semiconductor® (ORCA®) FPGAs, Spartan®, Virtex™ FPGAs • Cascadable Read-back to Support Additional Configurations or Higher-density Arrays Configuration • Low-power CMOS FLASH Process • Available in 44-lead PLCC Package Flash Memory • Emulation of Atmel’s AT24CXXX Serial EEPROMs • Low-power Standby Mode • Single Device Capable of Holding 4 Bit Stream Files Allowing Simple System AT17F32 Reconfiguration • Fast Serial Download Speeds up to 33 MHz • Endurance: 10,000 Write Cycles Typical • LHF Package Available (Lead and Halide Free) 1. Description The AT17F Series of In-System Programmable Configuration PROMs (Configurators) provide an easy-to-use, cost-effective configuration memory for Field Programmable Gate Arrays. The AT17F Series device is packaged in the 44-lead PLCC, see Table 1- 1. The AT17F Series Configurator uses a simple serial-access procedure to configure one or more FPGA devices. The AT17F Series Configurators can be programmed with industry-standard program- mers, Atmel’s ATDH2200E Programming Kit or Atmel’s ATDH2225 ISP Cable. Table 1-1. AT17F Series Packages Package AT17F32 44-lead PLCC Yes 3393C–CNFG–6/05 2. Pin Configuration 44-lead PLCC NC CLK NC NC DATA PAGE_EN VCC NC NC SER_EN NC 6 5 4 3 2 1 NC 7 44 43 42 41 3940 NC NC 8 38 NC NC 9 37 NC NC 10 36 NC NC 11 35 NC NC 12 34 NC NC 13 33 NC NC 14 32 NC NC 15 31 NC NC 16 30 NC NC 17 29 READY 18 19 20 21 22 23 24 25 26 27 28 CE NC NC NC NC NC GND CEO/A2 RESET/OE PAGESEL0 PAGESEL1 2 AT17F32 3393C–CNFG–6/05 AT17F32 3.
    [Show full text]
  • In Re: Lattice Semiconductor Corporation Securities Litigation 04
    LERACH COUGHLIN STOIA GELLER RUDMAN & ROBBINS LLP WILLIAM S. LERACH [email protected] DARREN J. ROBBINS [email protected] 401 B Street, Suite 1600 San Diego, CA 92101 Telephone: 619/231-1058 619/231-7423 (fax) DENNIS J. HERMAN [email protected] 100 Pine Street, Suite 2600 San Francisco, CA 94111 Telephone: 415/288-4545 415/288-4534 (fax) TAMARA J. DRISCOLL [email protected] 700 Fifth Avenue, Suite 5600 Seattle, WA 98104 Telephone: 206/749-5544 206/749-9978 (fax) Lead Counsel for Plaintiffs [Additional counsel appear on signature page.] UNITED STATES DISTRICT COURT DISTRICT OF OREGON In re LATTICE SEMICONDUCTOR CORP. CV-04-01255-HU (Consolidated Cases) SECURITIES LITIGATION CLASS ACTION This Document Relates To: CONSOLIDATED CLASS ACTION ALL ACTIONS. COMPLAINT FOR VIOLATION OF THE FEDERAL SECURITIES LAWS [Caption continued on following page.] DEMAND FOR JURY TRIAL CONSOLIDATED CLASS ACTION COMPLAINT FOR VIOLATION OF THE FEDERAL SECURITIES LAWS AUTUMN PARTNERS, LLC, Individually Case No. CV-04-01255-HU and On Behalf of Itself and All Others Similarly Situated, CLASS ACTION Plaintiff, vs. LATTICE SEMICONDUCTOR CORP., CYRUS Y. TSUI, STEPHEN A. SKAGGS, STEVEN A. LAUB and RONALD HOYT, Defendants. CONSOLIDATED CLASS ACTION COMPLAINT FOR VIOLATION OF THE FEDERAL SECURITIES LAWS TABLE OF CONTENTS Page I. INTRODUCTION............................................................................................................... 1 II. JURISDICTION AND VENUE..........................................................................................6
    [Show full text]
  • International Standard
    This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-8023417 IEC 62680-1-2 ® Edition 1.0 2016-11 INTERNATIONAL STANDARD colour inside Universal serial bus interfaces for data and power – Part 1-2: Common components – USB Power Delivery specification ) en ( 11 - 6 :201 2 - 1 - 62680 IEC Copyright © IEC, 2016, Geneva, Switzerland. All rights reserved. Sold by SIS under license from IEC and SEK. No part of this document may be copied, reproduced or distributed in any form without the prior written consent of the IEC. This preview is downloaded from www.sis.se. Buy the entire standard via https://www.sis.se/std-8023417 THIS PUBLICATION IS COPYRIGHT PROTECTED Copyright © 2016 IEC, Geneva, Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or your local IEC member National Committee for further information. IEC Central Office Tel.: +41 22 919 02 11 3, rue de Varembé Fax: +41 22 919 03 00 CH-1211 Geneva 20 [email protected] Switzerland www.iec.ch About the IEC The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes International Standards for all electrical, electronic and related technologies.
    [Show full text]
  • Lattice Semiconductor Corp (Lscc) 10-K
    LATTICE SEMICONDUCTOR CORP (LSCC) 10-K Annual report pursuant to section 13 and 15(d) Filed on 03/12/2012 Filed Period 12/31/2011 UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 FORM 10-K (Mark One) [X] ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 FOR THE FISCAL YEAR ENDED DECEMBER 31, 2011 or o TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 FOR THE TRANSITION PERIOD FROM TO Commission file number: 000-18032 ________________________________________ LATTICE SEMICONDUCTOR CORPORATION (Exact name of registrant as specified in its charter) Delaware 93-0835214 (State of Incorporation) (I.R.S. Employer Identification Number) 5555 NE Moore Court Hillsboro, Oregon 97124-6421 (Address of principal executive offices) (Zip Code) Registrant's telephone number, including area code: (503) 268-8000 Securities registered pursuant to Section 12(b) of the Act: ________________________________________ (Title of Class) (Name of each exchange on which registered) Common Stock, $.01 par value NASDAQ Global Select Market Securities registered pursuant to Section 12(g) of the Act: None Indicate by check mark if the registrant is a well-known seasoned issuer, as defined in Rule 405 of the Securities Act. Yes o No [X] Indicate by check mark if the registrant is not required to file reports pursuant to Section 13 or Section 15(d) of the Act. Yes o No [X] Indicate by check mark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days.
    [Show full text]
  • Introduction
    Field-Programmable Gate Arrays: A Fresh Look at a Classic Embedded Design Tool Leah VanSyckel and Greg Harrison Introduction In “Using FPGAs to Improve Embedded Design,” Sealevel Engineer Greg Harrison explains FPGAs on a technical level and illustrates their use cases with Sealevel products. He shows FPGAs to be useful in interface conversions, COM Express simplification and optimizing embedded systems. In this white paper, we will dis- cuss the basic definitions and the benefits of using FPGAs as well as their future in smart technology. 1 Sealevel.com • 864.843.4343 SL9299-h18 Field-Programmable Gate Arrays: A Fresh Look at a Classic Embedded Design Tool What is an FPGA? A Field Programmable Gate Array (FPGA) is an integrated circuit (IC), or chip, used in embedded system design. There are four main FPGA producers: Xilinx, Intel Programmable Solutions Group (Intel PSG, formerly Altera), Lattice Semiconductor and Microsemi, a Microchip company (formerly Actel). The primary characteristic of an FPGA is that it is programmable after manufacturing, which gives it versatility in application use and customization. These architectures are built and programmed by embedded hardware engineers, such as Sealevel’s Greg Harrison. They require a fundamental understanding of computing hardware. Engineers design with FPGAs using hardware description languages (HDL), including VHDL and Verilog. These devices contain architectures of interconnects and logical elements that are highly configurable. These elements, when in a completed, programmed device, can accept an input and produce a logical output based on the programmed configuration. These activities happen at high speeds due to parallel, independent logic. Their programmable, flexible routing and low-power demands make them ideal for telecommunications, networking, and signal/data processing.
    [Show full text]
  • IN the UNITED STATES DISTRICT COURT for the DISTRICT of DELAWARE COMMONWEALTH RESEARCH GROUP, LLC, Plaintiff, V. MICROCHIP
    Case 1:11-cv-00655-RGA Document 5 Filed 09/16/11 Page 1 of 30 PageID #: 35 IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF DELAWARE COMMONWEALTH RESEARCH GROUP, LLC, Plaintiff, v. C.A. No. 1:11-cv-00655-PD MICROCHIP TECHNOLOGY INC., ALTERA CORPORATION, LATTICE JURY TRIAL DEMANDED SEMICONDUCTOR CORPORATION, MINDSPEED TECHNOLOGIES, INC., CYPRESS SEMICONDUCTOR CORPORATION, CONEXANT SYSTEMS, INC., TRIAD SEMICONDUCTOR, SILICON LABORATORIES INC., ZIILABS, ZILOG, ENGERGY MICRO AS, MAXIM INTEGRATED PRODUCTS, INC., EPSON ELECTRONICS AMERICA, INC., CSR PLS, ON SEMICONDUCTOR CORPORATION, DUST NETWORKS, INC., EMBER CORPORATION, NUVOTON TECHNOLOGY CORPORATION AMERICA, ALPS ELECTRIC (NORTH AMERICA), INC., and CAVIUM NETWORKS, INC., Defendants. FIRST AMENDED COMPLAINT FOR PATENT INFRINGEMENT Plaintiff Commonwealth Research Group, LLC (“CRG”), for its Complaint against Microchip Technology Incorporated., Altera Corporation, Lattice Semiconductor Corporation, Mindspeed Technologies, Inc., Cypress Semiconductor Corporation, Conexant Systems, Inc., Triad Semiconductor Inc., Silicon Laboratories Inc., ZiiLABS, Zilog, Inc., Energy Micro AS, Maxim Integrated Products, Inc., Epson Electronics America, Inc., CSR plc, ON Semiconductor Corporation, Dust Networks, Inc., Ember Corporation, Nuvoton Technology Corporation America, Alps Electric (North America), Inc., and Cavium Networks, Inc., hereby alleges as Case 1:11-cv-00655-RGA Document 5 Filed 09/16/11 Page 2 of 30 PageID #: 36 follows: Nature of the Case 1. This is an action for patent infringement arising under the patent laws of the United States, 35 U.S.C. §§ 271, et seq., to enjoin and obtain damages resulting from Defendants’ unauthorized manufacture, use, sale, offer to sell, and/or importation into the United States for subsequent use or sale of products and/or systems that infringe one or more claims of United States Patent No.
    [Show full text]
  • LATTICE SEMICONDUCTOR CORPORATION (Exact Name of Registrant As Specified in Its Charter)
    Table of Contents UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 FORM 10-K (Mark One) [X] ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 FOR THE FISCAL YEAR ENDED DECEMBER 28, 2013 or o TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 FOR THE TRANSITION PERIOD FROM TO Commission file number: 000-18032 ________________________________________ LATTICE SEMICONDUCTOR CORPORATION (Exact name of registrant as specified in its charter) Delaware 93-0835214 (State of Incorporation) (I.R.S. Employer Identification Number) 5555 NE Moore Court Hillsboro, Oregon 97124-6421 (Address of principal executive offices) (Zip Code) Registrant's telephone number, including area code: ( 503) 268-8000 Securities registered pursuant to Section 12(b) of the Act: ________________________________________ (Title of Class) (Name of each exchange on which registered) Common Stock, $.01 par value NASDAQ Global Select Market Securities registered pursuant to Section 12(g) of the Act: None Indicate by check mark if the registrant is a well-known seasoned issuer, as defined in Rule 405 of the Securities Act. Yes o No [X] Indicate by check mark if the registrant is not required to file reports pursuant to Section 13 or Section 15(d) of the Act. Yes o No [X] Indicate by check mark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days.
    [Show full text]
  • LOW-COST FPGA CONFIGURATION VIA INDUSTRY-STANDARD SPI SERIAL FLASH & Latticeecp/EC Fpgas
    LOW-COST FPGA CONFIGURATION VIA INDUSTRY-STANDARD SPI SERIAL FLASH & LatticeECP/EC FPGAs A Lattice Semiconductor White Paper June 2004 Lattice Semiconductor 5555 Northeast Moore Ct. Hillsboro, Oregon 97124 USA Telephone: (503) 268-8000 www.latticesemi.com 1 Low-Cost FPGA Configuration Via Industry-Standard SPI Serial Flash A Lattice Semiconductor White Paper Introduction There are many criteria that a system designer must evaluate before making a choice of FPGA family and supplier. One of the decision criterion is FPGA “boot-up” configuration methodology. If the system design requires non-volatility, this issue is moot. A non- volatile FPGA, such as the Lattice ispXPGA®, will be selected. The ispXPGA family provides a single chip, self-booting FPGA solution. If, however, the system design needs are best met by a volatile FPGA, then the designer must also plan how that FPGA is going to be configured upon system boot-up. If the system design has ready access to an on-board microcontroller and available system memory, and the designer is willing to write the code to properly configure the FPGA, then the incremental “configuration” cost of the total FPGA solution is insignificant. For many system designs, however, a dedicated “Boot” memory is used to configure the FPGA at each system power-up. The unfortunate economic reality of this situation is that the vendor-specific Boot memory traditionally represents up to 30% of the total FPGA “solution” cost (FPGA + Boot memory). Lattice has addressed this significant cost issue with its new LatticeECPTM (low-cost with high-performance dedicated functions) and LatticeECTM (optimized for low-cost) families of FPGAs.
    [Show full text]