RapidIO Physical Layer MegaCore Function

Similar documents
POS-PHY Level 4 MegaCore Function

RapidIO MegaCore Function

DSP Development Kit, Stratix II Edition

RapidIO MegaCore Function

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

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

RapidIO MegaCore Function

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

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

DDR & DDR2 SDRAM Controller Compiler

Video and Image Processing Suite

FFT MegaCore Function

PCI Express Compiler. System Requirements. New Features & Enhancements

DDR & DDR2 SDRAM Controller Compiler

RLDRAM II Controller MegaCore Function

DDR & DDR2 SDRAM Controller Compiler

UTOPIA Level 2 Slave MegaCore Function

Enhanced Configuration Devices

DDR & DDR2 SDRAM Controller

DDR & DDR2 SDRAM Controller

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

FFT/IFFT Block Floating Point Scaling

Simulating the PCI MegaCore Function Behavioral Models

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

Enhanced Configuration Devices

Nios II Embedded Design Suite 6.1 Release Notes

White Paper AHB to Avalon & Avalon to AHB Bridges

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

Using the Serial FlashLoader With the Quartus II Software

Simulating the PCI MegaCore Function Behavioral Models

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

PCI Express Multi-Channel DMA Interface

FPGAs Provide Reconfigurable DSP Solutions

Avalon Streaming Interface Specification

Using the Nios Development Board Configuration Controller Reference Designs

24K FFT for 3GPP LTE RACH Detection

Cyclone II FPGA Family

FPGA Design Security Solution Using MAX II Devices

Simultaneous Multi-Mastering with the Avalon Bus

Matrices in MAX II & MAX 3000A Devices

Nios II Embedded Design Suite 7.1 Release Notes

Active Serial Memory Interface

Arria II GX FPGA Development Board

Errata Sheet for Cyclone IV Devices

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

Simulating the Reed-Solomon Model

DSP Builder Release Notes

100G Interlaken MegaCore Function User Guide

POS-PHY Level 4 MegaCore Function (POSPHY4)

Stratix II FPGA Family

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

E3 Mapper MegaCore Function (E3MAP)

ZBT SRAM Controller Reference Design

Implementing CRCCs. Introduction. in Altera Devices

Implementing LED Drivers in MAX Devices

AN 549: Managing Designs with Multiple FPGAs

Legacy SDRAM Controller with Avalon Interface

Video Input Daughter Card Reference Manual

AIRbus Interface. Features Fixed width (8-, 16-, or 32-bit) data transfers (dependent on the width. Functional Description. General Arrangement

White Paper Configuring the MicroBlaster Passive Serial Software Driver

Excalibur Solutions DPRAM Reference Design

Nios DMA. General Description. Functional Description

Nios Embedded Processor UART Peripheral

Introduction. Design Hierarchy. FPGA Compiler II BLIS & the Quartus II LogicLock Design Flow

MAX 10 User Flash Memory User Guide

T3 Framer MegaCore Function (T3FRM)

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

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

EFEC20 IP Core. Features

Recommended Protocol Configurations for Stratix IV GX FPGAs

OTU2 I.4 FEC IP Core (IP-OTU2EFECI4Z) Data Sheet

PCI-to-DDR2 SDRAM Reference Design

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

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

CORDIC Reference Design. Introduction. Background

FFT MegaCore Function User Guide

Toolflow for ARM-Based Embedded Processor PLDs

Low Latency 40G Ethernet Example Design User Guide

Arria II GX FPGA Development Board

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

White Paper Enabling Quality of Service With Customizable Traffic Managers

Error Correction Code (ALTECC_ENCODER and ALTECC_DECODER) Megafunctions User Guide

Estimating Nios Resource Usage & Performance

OTU2 I.9 FEC IP Core (IP-OTU2EFECI9) Data Sheet

PCI Express Compiler. PCI Express Compiler Version Issues

Implementing 9.8G CPRI in Arria V GT and ST FPGAs

SONET/SDH STS-12c/STM-4 Framer MegaCore Function (STS12CFRM)

Implementing LVDS in Cyclone Devices

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

Using Flexible-LVDS I/O Pins in

Nios Soft Core Embedded Processor

AN423: Configuring the MicroBlaster Passive Serial Software Driver

11. SEU Mitigation in Stratix IV Devices

Using DCFIFO for Data Transfer between Asynchronous Clock Domains

ByteBlaster II Parallel Port Download Cable

White Paper Low-Cost FPGA Solution for PCI Express Implementation

Altera I/O Phase-Locked Loop (Altera IOPLL) IP Core User Guide

Arria II GX FPGA Development Kit HSMC Loopback Tests Rev 0.1

AN 836: RapidIO II Reference Design for Avalon-ST Pass-Through Interface

Simulating the ASMI Block in Your Design

Transcription:

RapidIO Physical Layer MegaCore Function April 2005, MegaCore version 2.2.1 Errata Sheet Introduction This document addresses known errata and documentation changes for version 2.2.1 of the RapidIO Physical Layer MegaCore Errata are design functional defects or errors. Errata may cause the RapidIO Physical Layer MegaCore function to deviate from published specifications. Documentation changes include typos, errors, unclear descriptions or omissions from current published specifications or product documents. These documentation changes or clarifications will be incorporated into an upcoming release of the RapidIO Physical Layer RapidIO Physical Layer MegaCore Function v2.2.1 Issues Altera has identified the following issues that affect the RapidIO Physical Layer MegaCore function v2.2.1: 1. A Packet ackid Is Sometimes Skipped After a Retried Packet on page 2. 2. The Lane Aligner Sometimes Does Not Align on page 2. 3. The Receiver Sometimes Mistakenly Detects a CRC Error on a Valid Packet on page 3. 4. The End of Packet of a Valid Incoming Packet Is Sometimes Lost on page 3. 5. The Transmitter's Frame Signal Sometimes Toggles Incorrectly, Causing the Receiver to Reject the Packet on page 4. 6. The Transmitter Sometimes Generates an Incorrect CRC When a Packet Larger Than 80 Bytes Is Followed by a Packet with Zero Latency on page 5. 7. A Control Symbol Is Sometimes Overwritten on page 5. 8. An Avoidable Compensation Sequence Insertion Sometimes Causes a Packet to Be Stomped and Retried on page 6. 9. The Header of an Outgoing Packet Is Sometimes Lost on page 6. Altera Corporation 1 ES-040705-1.0

RapidIO Physical Layer MegaCore Function 10. The Packet Immediately Following a Stomped Packet Sometimes Makes it Through to the Atlantic Interface on page 7. 11. Idle Characters Sometimes Appear in the Start-of-Packet (SOP) Word on the Receiver Signals of the Atlantic Interface on page 7. 12. The CRC of the Previous Packet Sometimes Appears in the SOP Word on the Receiver Signals of the Atlantic Interface on page 8. 13. A Control Symbol Is Sometimes Lost on page 8. 14. A Control Symbol Is Sometimes Retransmitted Endlessly on page 9. A Packet ackid Is Sometimes Skipped After a Retried Packet If the transmitter receives a packet-retry control symbol while the transmit buffer is busy, the ackid status of the next normal packet is incorrectly incremented. This issue affects all variations of the A valid packet is sometimes not accepted. The Lane Aligner Sometimes Does Not Align The lane aligner sometimes gets into a state where it is not aligned and no longer tries to align. This happens when alignment is initiated while alignment is drifting, for example, when the clocks have not entirely stabilized. This issue affects all serial, 4 mode variations of the 2 Altera Corporation

RapidIO Physical Layer MegaCore Function v2.2.1 Issues The port_initialized signal remains deasserted, and traffic cannot pass. The MegaCore function must be reset to force re-alignment. If the MegaCore function stays out of alignment for extended periods of time, assert the reset_n signal. The Receiver Sometimes Mistakenly Detects a CRC Error on a Valid Packet When an incoming packet is terminated by the eop/symbol/sop/symbol pattern, the receiver extends the internal end-of-packet data for one more clock cycle, causing the cyclic redundancy code (CRC) checker to detect a CRC error. A valid packet is sometimes not accepted, but is sent again. The End of Packet of a Valid Incoming Packet Is Sometimes Lost When an incoming packet is terminated by the sym/data/eop/idles pattern, the receiver skips the last data word of the packet. Altera Corporation 3

RapidIO Physical Layer MegaCore Function The last word of a valid packet is sometimes lost without retry. The Transmitter's Frame Signal Sometimes Toggles Incorrectly, Causing the Receiver to Reject the Packet When a control symbol is inserted right before a packet, the transmitter extends the internal start-of-packet signal to one more clock cycle. This causes the frame signal to toggle twice at the start of the packet. This issue affects all parallel variations of the A valid packet is sometimes not accepted, but is sent again. 4 Altera Corporation

RapidIO Physical Layer MegaCore Function v2.2.1 Issues The Transmitter Sometimes Generates an Incorrect CRC When a Packet Larger Than 80 Bytes Is Followed by a Packet with Zero Latency When a long (larger than 80 bytes) outgoing packet is followed by a packet with zero internal latency, the CRC value gets overwritten by the new packet. The overwritten CRC is inserted at the end of the long packet, causing a CRC error on the receiver. This issue affects all parallel variations of the A valid packet is sometimes not accepted, but is sent again. A Control Symbol Is Sometimes Overwritten Under some circumstances, a control symbol that is scheduled to be transmitted can be overwritten by packet data. This issue affects all parallel variations of the Depending on the type of control symbol that is lost, recoverable or fatal errors can occur, eventually leading to packet loss. Altera Corporation 5

RapidIO Physical Layer MegaCore Function An Avoidable Compensation Sequence Insertion Sometimes Causes a Packet to Be Stomped and Retried If a continuous stream of packets is being transmitted and stype0 control symbols (e.g., packet-accepted) become available for transmission at exactly the instant when the start-of-packet control symbol is inserted, the compensation sequence is not inserted between the packets. This can lead to a compensation sequence timeout, which causes the packet to be stomped to allow the forced insertion of a compensation sequence before the 5,000 column limit is reached. This issue causes an occasional recoverable error and the retransmission of a packet. The protocol recovers from the error, the compensation sequence is inserted in time, and no packets are lost. However, some bandwidth is lost. The Header of an Outgoing Packet Is Sometimes Lost If a symbol is inserted between two packets with one clock cycle latency, the packet header is lost. This issue affects all parallel variations of the 6 Altera Corporation

RapidIO Physical Layer MegaCore Function v2.2.1 Issues A valid packet is sometimes transmitted without a header, but is recoverable. The Packet Immediately Following a Stomped Packet Sometimes Makes it Through to the Atlantic Interface If a packet is received immediately after a stomped packet, the receiver passes that received packet through to the Atlantic interface. All received packets should be dropped or marked as invalid by asserting the arxerr signal until a restart-from-retry symbol is received. This issue affects all serial variations of the A packet can be received twice. Idle Characters Sometimes Appear in the Start-of-Packet (SOP) Word on the Receiver Signals of the Atlantic Interface If an incoming packet is terminated by the stomp/status/idle pattern, the receiver wrongly treats the idle as the header of the next packet, causing it to be rejected. Altera Corporation 7

RapidIO Physical Layer MegaCore Function A valid packet is sometimes not accepted, but is recoverable. The CRC of the Previous Packet Sometimes Appears in the SOP Word on the Receiver Signals of the Atlantic Interface Under some circumstances, the second packet of two consecutive incoming packets has the CRC of the first packet as a SOP word. A valid packet is sometimes not accepted, but is recoverable. A Control Symbol Is Sometimes Lost Under some circumstances, a control symbol that is scheduled to be transmitted can be lost before it is transmitted. 8 Altera Corporation

RapidIO Physical Layer MegaCore Function v2.2.1 Issues Depending on the type of control symbol that is lost, recoverable or fatal errors can occur, eventually leading to packet loss. A Control Symbol Is Sometimes Retransmitted Endlessly Under some circumstances, a control symbol can be continually retransmitted every few clock cycles. Depending on the type of control symbol that is repeated, the RapidIO protocol can be, more or less, seriously violated. In the best case scenario, throughput is severely reduced; in the worst case scenario, transmission stops completely. Altera Corporation 9

RapidIO Physical Layer MegaCore Function 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. Table 1. Revision History Version Date Details of Change 1.0 April 2005 First release of the RapidIO Physical Layer MegaCore function errata sheet for v2.2.1. 101 Innovation Drive San Jose, CA 95134 (408) 544-7000 www.altera.com Applications Hotline: (800) 800-EPLD Literature Services: literature@altera.com Copyright 2005 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. 10 Altera Corporation