Enhanced Configuration Devices

Similar documents
Enhanced Configuration Devices

DSP Development Kit, Stratix II Edition

Implementing LED Drivers in MAX and MAX II Devices. Introduction. Commercial LED Driver Chips

Table 1 shows the issues that affect the FIR Compiler v7.1.

Implementing LED Drivers in MAX Devices

Stratix FPGA Family. Table 1 shows these issues and which Stratix devices each issue affects. Table 1. Stratix Family Issues (Part 1 of 2)

RapidIO Physical Layer MegaCore Function

Stratix II FPGA Family

Using MAX II & MAX 3000A Devices as a Microcontroller I/O Expander

Video and Image Processing Suite

Table 1 shows the issues that affect the FIR Compiler, v6.1. Table 1. FIR Compiler, v6.1 Issues.

RLDRAM II Controller MegaCore Function

DDR & DDR2 SDRAM Controller

DDR & DDR2 SDRAM Controller

UTOPIA Level 2 Slave MegaCore Function

DSP Builder. DSP Builder v6.1 Issues. Error When Directory Pathname is a Network UNC Path

Using the Serial FlashLoader With the Quartus II Software

Implementing LVDS in Cyclone Devices

Using the Nios Development Board Configuration Controller Reference Designs

Nios II Embedded Design Suite 6.1 Release Notes

AN 547: Putting the MAX II CPLD in Hibernation Mode to Achieve Zero Standby Current

Arria II GX FPGA Development Board

Cyclone II FPGA Family

Using MAX 3000A Devices as a Microcontroller I/O Expander

Excalibur Solutions Using the Expansion Bus Interface. Introduction. EBI Characteristics

ByteBlaster II Parallel Port Download Cable

ByteBlaster II Download Cable User Guide

Interfacing Cyclone III Devices with 3.3/3.0/2.5-V LVTTL/LVCMOS I/O Systems

POS-PHY Level 4 MegaCore Function

Simulating the ASMI Block in Your Design

Legacy SDRAM Controller with Avalon Interface

RapidIO MegaCore Function

AN 549: Managing Designs with Multiple FPGAs

FPGA Design Security Solution Using MAX II Devices

PCI Express Compiler. System Requirements. New Features & Enhancements

Arria II GX FPGA Development Board

White Paper Configuring the MicroBlaster Passive Serial Software Driver

DDR & DDR2 SDRAM Controller Compiler

Introduction. Synchronous vs. Asynchronous Memory. Converting Memory from Asynchronous to Synchronous for Stratix & Stratix GX Designs

AN 523: Cyclone III Devices Configuration Interface Guidelines with EPCS Devices

SONET/SDH Compiler. Introduction. SONET/SDH Compiler v2.3.0 Issues

Simple Excalibur System

FFT MegaCore Function

Quad-Serial Configuration (EPCQ) Devices Datasheet

White Paper Using the MAX II altufm Megafunction I 2 C Interface

FFT/IFFT Block Floating Point Scaling

For Quartus II Software. This Quick Start Guide will show you how to set up a Quartus

Implementing Bus LVDS Interface in Cyclone III, Stratix III, and Stratix IV Devices

ZBT SRAM Controller Reference Design

Signal Integrity Comparisons Between Stratix II and Virtex-4 FPGAs

High-Performance FPGA PLL Analysis with TimeQuest

Quad-Serial Configuration (EPCQ) Devices Datasheet

QDR II SRAM Board Design Guidelines

Video Input Daughter Card Reference Manual

White Paper The Need for a High-Bandwidth Memory Architecture in Programmable Logic Devices

USB BitJetLite Download Cable

MAX 10 User Flash Memory User Guide

Matrices in MAX II & MAX 3000A Devices

AN822: Intel Configuration Device Migration Guideline

Errata Sheet for Cyclone V Devices

Nios Soft Core Embedded Processor

Nios II Embedded Design Suite 7.1 Release Notes

AN822: Intel FPGA Configuration Device Migration Guideline

DDR & DDR2 SDRAM Controller Compiler

FPGA Power Management and Modeling Techniques

Designing RGMII Interface with FPGA and HardCopy Devices

Figure 1. Device Package Ordering Information for Stratix, Stratix GX, Cyclone, APEX 20KC, APEX II, Mercury & Excalibur Devices EP1S 25 F 780 C 5 N

AN423: Configuring the MicroBlaster Passive Serial Software Driver

4. Hot Socketing and Power-On Reset in MAX V Devices

Excalibur Solutions DPRAM Reference Design

Using Flexible-LVDS I/O Pins in

DDR & DDR2 SDRAM Controller Compiler

White Paper Performing Equivalent Timing Analysis Between Altera Classic Timing Analyzer and Xilinx Trace

RapidIO MegaCore Function

RapidIO MegaCore Function

Estimating Nios Resource Usage & Performance

Practical Hardware Debugging: Quick Notes On How to Simulate Altera s Nios II Multiprocessor Systems Using Mentor Graphics ModelSim

Quad-Serial Configuration (EPCQ) Devices Datasheet

EPCQA Serial Configuration Device Datasheet

Using Flexible-LVDS Circuitry in Mercury Devices

MasterBlaster Serial/USB Communications Cable User Guide

Cyclone Device Handbook, Volume 2

Stratix vs. Virtex-II Pro FPGA Performance Analysis

Active Serial Memory Interface

Toolflow for ARM-Based Embedded Processor PLDs

PCI Express Multi-Channel DMA Interface

Increasing Productivity with Altera Quartus II to I/O Designer/DxDesigner Interface

December 2002, ver. 1.3 Application Note 191. Six individual interrupts Six-bit priority scheme Five-bit priority scheme plus one individual interrupt

AN 370: Using the Serial FlashLoader with the Quartus II Software

FPGAs Provide Reconfigurable DSP Solutions

Benefits of Embedded RAM in FLEX 10K Devices

24K FFT for 3GPP LTE RACH Detection

Converting.srec Files to.flash Files for Nios Embedded Processor Applications

Transient Voltage Protection for Stratix GX Devices

CORDIC Reference Design. Introduction. Background

5. Using MAX V Devices in Multi-Voltage Systems

POS-PHY Level 4 POS-PHY Level 3 Bridge Reference Design

White Paper. Floating-Point FFT Processor (IEEE 754 Single Precision) Radix 2 Core. Introduction. Parameters & Ports

How FPGAs Enable Automotive Systems

AN 610: Implementing Deterministic Latency for CPRI and OBSAI Protocols in Altera Devices

Transcription:

Enhanced Configuration Devices October 2007, Version 1.2 Errata Sheet Introduction Intel-Flash- Based EPC Device Protection f This errata sheet provides updated information on enhanced configuration devices EPC4, EPC8, and EPC16 which are used to configure SRAM-based programmable logic devices (PLDs). This document addresses known issues and includes methods to work around the issues. Altera performed a die-sub replacement for the EPC4, EPC8, and EPC16 devices with Intel flash. Intel flash devices do not have the lock bit protection feature to lock the flash for protection during power-up or power-down. The lock bit protection feature is used to prevent unintentional writes and ensure data retention. For more information about the flash die change in the Altera enhanced configuration devices, refer to Process Change Notification PCN0506: Addition of Intel Flash Memory as Source for EPC4, EPC8 & EPC16 Enhanced Configuration Devices. In the absence of the lock bit protection feature in the EPC4, EPC8, and EPC16 devices with Intel flash, Altera recommends four methods to protect the Intel flash content in EPC4, EPC8, and EPC16 devices. Any method alone is sufficient to protect the flash. The methods are listed below in the order of descending protection level: 1. Using an RP# of less than 0.3 V on power-up and power-down for a minimum of 100 ns to a maximum 25 µs disables all control pins, making it impossible for a write to occur. 2. Using V PP <V PPLK, where the maximum value of V PPLK is 1 V, disables writes. V PP <V PPLK means programming or writes cannot occur. V PP is a programming supply voltage input pin on the Intel flash. V PP is equivalent to the V CCW pin on EPC16 devices. 3. Using a high CE# disables the chip. The requirement for a write is a low CE# and low WE#. A high CE# by itself prevents writes from occurring. 4. Using a high WE# prevents writes because a write only occurs when the WE# is low. Altera Corporation 1 ES-DCLKSIG-1.2

Intel-Flash-Based EPC Device Protection Performing all four methods simultaneously is the safest protection for the flash content. The ideal power-up sequence is as follows: 1. Power up V CC. 2. Maintain V PP < V PPLK until V CC is fully powered up. 3. Power up V PP. 4. Drive RP# low during the entire power-up process. RP# must be released high within 25 µs after V PP is powered up. 1 CE# and WE# must be high for the entire power-up sequence. The ideal power-down sequence is as follows: 1. Drive RP# low for 100 ns before power-down. 2. Power down V PP < V PPLK. 3. Power down V CC. 4. Drive RP# low during the entire power-down process. 1 CE# and WE# must be high for the entire power-down sequence. The RP# pin is not internally connected to the controller. Therefore, an external loop-back connection between C-RP# and F-RP# must be made on the board even when you are not using the external flash interface. When using the external flash interface, connect the external device to the RP# pin with the loop back. Tri-state RP# at all times when the flash is not in use. If an external power-up monitoring circuit is connected to the RP# pin with the loop-back, use the following guidelines to avoid contention on the RP# line: The power-up sequence on the 3.3-V supply should complete within 50 ms of power-up. The 3.3-V V CC should reach the minimum V CC before 50 ms and RP# should then be released. RP# should be driven low by the power-up monitoring circuit during power-up. After power-up, RP# should be tri-stated externally by the power-up monitoring circuit. 2 Altera Corporation

Set-Up Time Issue If the preceding guidelines cannot be completed within 50 ms, then the OE pin must be driven low externally until RP# is ready to be released. Set-Up Time Issue The set-up time issue described here refers to the revision B silicon of the Altera enhanced configuration devices. The issue described in this errata sheet has now been corrected in the revision C silicon of this device. All revision C devices are fully backward compatible with the revision B devices. As of the date of this errata sheet, the EPC4, EPC8, and EPC16 devices in the 100-pin quad flat pack (QFP) package are shipped with revision C silicon. The EPC16UC88 device has a special ordering code (EPC16UB88AA) to identify revision C silicon. The EPC16UC88 ordering code is used to deliver revision B silicon at this time. Once the transition from revision B to revision C silicon is complete, the EPC16UC88 ordering code will be used going forward to deliver revision C silicon, and the EPC16UC88AA ordering code will be made obsolete. For identification purposes, the fourth character of the 11-character date code indicates the die revision. For a revision B component, this character will be a B, and for a revision C component, this character will be a C. For more information regarding the device marking, refer to customer advisories 9916 and 9707. Customers who are using enhanced configuration devices and configuring one or more SRAM-based devices may encounter configuration device failure. This failure may be temperature- or voltage-dependent. The problem is due to a set-up time violation of the DATA signal. The enhanced configuration device generates the DATA and DCLK signals so that they arrive at the PLD simultaneously. The PLD requires a set-up time of 10 ns. However, since the DCLK and DATA signals transition simultaneously, the set-up time at the PLD is actually zero. Figure 1 shows the DATA and DCLK signals generated by enhanced configuration devices. Altera Corporation 3

Set-Up Time Issue Figure 1. DATA and DCLK Signals Generated by Enhanced Configuration Devices DCLK DATA Bit/Byte 1 Bit/Byte 2 Bit/Byte 3 Bit/Byte 4 No Set-up Time Design Guidelines To achieve a successful configuration, required set-up time must be provided to the DATA signal or signals of SRAM-based devices. Depending on the layout of the board, there may already be sufficient set-up time at the PLD. Measure the DCLK to DATA relationship at the PLD. If the DATA changes prior to the rising edge of the DCLK signal more than the required set-up time (10 ns for all SRAM-based devices), then the board will configure correctly. If the set-up time parameter is not met, then the DATA signal must be delayed so that it changes after the DCLK transition (DATA latches on next rising edge of the clock). A delay of 10 ns is sufficient to provide the required set-up time for the DATA signal or signals. This delay between DCLK and DATA is measured at the PLD. The delay is introduced by adding a resistor to the DATA path from the enhanced configuration devices to the SRAM-based PLDs, as shown in Figure 2. Figure 2. Adding a Resistor to DATA Path Enhanced Configuration Device DATA Resistor SRAM-Based PLD DATA The delay is created by a resistor-capacitor network. The resistor is added to the circuit and the capacitance is provided by the board trace. The RC combination should be chosen such that the path delay is equal to 10 ns. 4 Altera Corporation

Set-Up Time Issue A typical combination would use a 100- to 200-Ω resistor with a trace length of four inches between the DATA pins of the enhanced configuration device and the PLD. After inserting the delay, the DATA transition would shift to the right so that the first bit or byte of data would be latched on the second rising edge of DCLK, as shown in Figure 3. This shift meets the required set-up time for the DATA signal. Figure 3. DATA Latches on Second Rising Edge of DCLK after DATA Path Delay DCLK DATA Bit/Byte 1 Bit/Byte 2 Bit/Byte 3 Bit/Byte 4 Data Delayed to Next Clock Cycle Set Up Hold } } This technique enables existing enhanced configuration devices to configure PLDs. Future updated versions of enhanced configuration devices will be modified so that the DCLK and DATA signals arrive at the PLD to meet the required set-up time. A board that is laid out with an in-line resistor will work with updated versions of enhanced configuration devices, but the maximum frequency for configuration would be limited to 33 MHz. Altera Corporation 5

Contact Information Contact Information Revision History For more information, go to Altera's mysupport website at www.altera.com/mysupport and click Create New Service Request. Choose the Product Related Request form. Table 1 shows the revision history for this errata sheet. Table 1. Revision History Version Date Errata Summary 1.2 October 2007 Added section on Intel-Flash-Based EPC Device Protection. Updated section on Set-Up Time Issue. 1.1 December 2003 Addressed known issues and includes methods to work around the issues for enhanced configuration devices EPC4, EPC8, and EPC16. 101 Innovation Drive San Jose, CA 95134 www.altera.com Technical Support: www.altera.com/support/ Literature Services: literature@altera.com Copyright 2007 Altera Corporation. All rights reserved. Altera, The Programmable Solutions Company, the stylized Altera logo, specific device designations, and all other words and logos that are identified as trademarks and/or service marks are, unless noted otherwise, the trademarks and service marks of Altera Corporation in the U.S. and other countries. All other product or service names are the property of their respective holders. Altera products are protected under numerous U.S. and foreign patents and pending applications, maskwork rights, and copyrights. Altera warrants performance of its semiconductor products to current specifications in accordance with Altera's standard warranty, but reserves the right to make changes to any products and services at any time without notice. Altera assumes no responsibility or liability arising out of the application or use of any information, product, or service described herein except as expressly agreed to in writing by Altera Corporation. Altera customers are advised to obtain the latest version of device specifications before relying on any published information and before placing orders for products or services. 6 Altera Corporation