ImageVerifierCode 换一换
格式:PDF , 页数:17 ,大小:108.21KB ,
资源ID:436650      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-436650.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(ANSI INCITS TR 26-2000 Information Technology C Fibre Channel C High Speed Parallel Interface.pdf)为本站会员(赵齐羽)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

ANSI INCITS TR 26-2000 Information Technology C Fibre Channel C High Speed Parallel Interface.pdf

1、INCITS TR-26-2000 (R2010)Information Technology Fibre Channel High Speed Parallel InterfaceINCITS TR-26-2000 (R2010)NCITS Technical ReportInformation Technology Fibre Channel High Speed Parallel InterfaceSecretariatInformation Technology Industry CouncilAbstractThis technical report defines the func

2、tions and electrical characteristics of the high-speed parallel interfacebetween the physical (FC-0) layer and the transmission protocol (FC-1) layer of a Fibre Channel port. Thisinterface operates at either 2 125,0 or 1 062,5 Mbaud. This interface has additional functions and differentelectrical ch

3、aracteristics compared to the “Fibre Channel - 10-bit Interface”, previously published asX3.TR-18:1997, which operated at 1 062,5 MBaud only. This document applies in full to systems wherethe FC-0 and FC-1 layer are implemented as separate devices. For systems where the FC-0 and FC-1 de-vices are in

4、tegrated, only the functional characteristics of this document apply.This Technical Report is one in a series produced by the National Committee forInformation Technology Standards (NCITS). The secretariat for NCITS is held bythe Information Technology Industry Council (ITI), 1250 Eye Street, NW, Su

5、ite 200,Washington, DC 20005.As a by-product of the standards development process and the resources ofknowledge devoted to it, NCITS from time to time produces Technical Reports.Such Technical Reports are not standards, nor are they intended to be used assuch.NCITS Technical Reports are produced in

6、some cases to disseminate thetechnical and logical concepts reflected in standards already published or underdevelopment. In other cases, they derive from studies in areas where it is foundpremature to develop a standard due to a still changing technology, orinappropriate to develop a rigorous stand

7、ard due to the existence of a number ofviable options, the choice of which depends on the users particular requirements.These Technical Reports, thus, provide guidelines, the use of which can result ingreater consistency and coherence of information processing systems.When the draft Technical Report

8、 is completed, the Technical Committee approvalprocess is the same as for a draft standard. Processing by NCITS is also similar tothat for a draft standard.CAUTION: The developers of this Technical Report have requested that holdersof patents that may be required for the implementation of the Techni

9、cal Report,disclose such patents to the publisher. However, neither the developers nor thepublisher have undertaken a patent search in order to identify which, if any, patentsmay apply to this Technical Report.As of the date of publication of this Technical Report and following calls for theidentifi

10、cation of patents that may be required for the implementation of theTechnical Report, no such claims have been made. No further patent search isconducted by the developer or the publisher in respect to any Technical Report itprocesses. No representation is made or implied that licenses are not requi

11、red toavoid infringement in the use of this Technical Report.INCITSTechnicalReportSeriesPublished byAmerican National Standards Institute11 West 42nd Street, New York, New York 10036Copyright 2000 by Information Technology Industry Council (ITI)All rights reservedNo part of this publication may be r

12、eproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the publisher.Printed in the United States of AmericaPATENTSTATEMENTINCITS TR-26-2000 (R2005)11 ScopeThis document defines the functions and electrical characteristics of a High-Speed Parallel In

13、terface between FC-1(Transmission protocol layer) and FC-0 (Physical layer) devices at 2 125,0 and 1 062,5 MBaud data rates. This docu-ment applies in full to systems where the FC-0 and FC-1 layer are implemented as separate devices. For systems wherethe FC-0 and FC-1 devices are integrated, only th

14、e functional characteristics of this document apply.The High-Speed Parallel Interface is composed of two subinterfaces: Transmit Interface and Receive Interface. Figure 1shows the relationship of these interfaces.FIGURE 1 - HIGH-SPEED PARALLEL INTERFACE DIAGRAM2 Normative referencesThe following Ame

15、rican National Standards contain provisions which, through reference below, constitute provisionsof this Technical Report. All standards are subject to revisions, and parties to agreements based on this Technical Reportare encouraged to apply the most recent editions of the standards. Members of IEC

16、 and ISO maintain registers of cur-rently valid International Standards. ANSI performs a similar function for American National Standards.ANSI X3.230-199x, Fibre Channel Physical Interface (FC-PI)ANSI X3.230-199x, Fibre Channel Framing and Signaling Interface (FC-FS)Data FC protocol device REFCLK0:1

17、Serial data outSerial data in1010Physical layer (FC-0)Transmission protocol layer (FC-1)2Control22EWRAPEN_CDETTX0:9COM_DETRX0:9RBC0:1TBCTransmitReceivec55c85c68c81c86c80c76c87c87c72c85ReceiverPLLPLLInterfaceVREFTVREFRInterface2TX_RATERX_RATELoopbackRX_LOSINCITS TR-26-2000 (R2005)23 Definitions and c

18、onventionsThe following definitions, conventions, abbreviations, acronyms and symbols apply in addition to those in FC-PI andFC-FS.3.1 Definitions3.1.1 byte alignment: The receiver action that resets the byte boundary to the comma within the K28.5 characterbeing received.3.1.2 byte slipping: The rec

19、eiver action that eliminates the 180 phase error between the receive data and the receivebyte clock.3.1.3 comma+: The seven bit sequence (0011111) of an encoded data stream.3.1.4 comma-: The seven bit sequence (1100000) of an encoded data stream.3.1.5 sliver: A pulse with a duration which is less th

20、an that specified for that signal (e.g. a truncated clock signal).3.1.6 word alignment: The process by which an entity determines the location of the four byte (“word”) boundary ina continuous byte stream.3.2 Editorial conventionsIn this Technical Report, a number of conditions, mechanisms, sequence

21、s, parameters, event states, or similar termsare printed with the first letter of each word in uppercase and the rest in lowercase (e.g. Physical). Any lowercase usesof these words have the normal technical English meaning.Numbered items in this Technical Report do not represent any priority. Priori

22、ty, if it exists, is explicitly indicated.The ISO convention of numbering is used. The thousands and higher multiples are separated by a space and a commais used as the decimal point. A comparison of the American and ISO conventions are shown:ISO American0,1 0.11 234 1,2341 234 567,8 1,234,567.8In c

23、ase of conflict between figures, tables, and text, the text shall take precedence. Exceptions to this convention areindicated if appropriate.In figures, tables, and text, the most significant bit of a binary quantity is shown on the left side. Exceptions to thisconvention are indicated if appropriat

24、e.The term “shall” is used to indicate a mandatory rule. If the mandatory rule is not followed, the results are unpredict-able unless indicated otherwise.If a field or control bit in a frame is specified as not meaningful, the entity which receives the frame shall not checkthat field or control bit.

25、Hexadecimal notation is used to represent fields. For example, a three byte D_ID field containing a binary value of11111111 11111111 11111010 is denoted by FF FF FA.INCITS TR-26-2000 (R2005)33.3 Abbreviations, acronyms and symbolsThe following abbreviations and acronyms are applicable to this Techni

26、cal Report.FC Fibre ChannelPLL Phase Locked Loopppm parts per million4 Functional descriptionThe Transmit Interface is defined as an input to the Physical layer device with a 10-bit wide transmit data bus (Tx0:9),its associated transmit byte clock (TBC) and a speed selector (TX_RATE). The reference

27、clock is a differential 106,25MHz 100 ppm signal (REFCLK0:1). REFCLK0:1 frequency is independent of both the Transmit Interface andReceive Interface data rates. The Transmission protocol layer device presents data to the Physical layer device relativeto the falling edge of TBC when the Transmit Inte

28、rface is operating at 1 062,5 MBaud. The Transmission protocol layerdevice presents data to the Physical layer device synchronous with both rising and falling edges of TBC when theTransmit Interface is operating at 2 125,0 MBaud. The speed of the Transmit Interface is set by the TX_RATE signal. Atra

29、nsmit reference voltage (VREFT) is provided to ensure that TBC and Tx0:9 have a well-defined threshold betweenlow and high values in order to reduce jitter.The Receive Interface is defined as an output of the Physical layer device with a 10-bit wide data bus (Rx0:9), tworeceive byte clocks (RBC0:1),

30、 an optional comma detection enable (EN_CDET), a comma detection indication(COM_DET) and a speed selector (RX_RATE). The receive byte clocks operate at 53,125 MHz when the ReceiveInterface data rate is 1 062,5 MBaud and at 106,25 MHz when the Receive Interface data rate is 2 125,0 MBaud. Thereceive

31、byte clocks are 180 out of phase with each other. Receive data is presented to the Transmission protocol layerdevice relative to the rising edge of each of RBC0 and/or RBC1. The speed of the Receive Interface is set by theRX_RATE signal. A receive reference voltage (VREFR) is provided to ensure that

32、 RBC0:1 and Rx0:9 have well-defined threshold between low and high values in order to reduce jitter.Two additional signals complete the definition of the High-Speed Parallel Interface. The first is the wrap or loopbacksignal (EWRAP). This signal is defined as an input to the Physical layer device wh

33、ich causes serialized transmit data tobe looped back to the auxiliary inputs of the receiver deserializer. The second is receiver loss-of-signal (RX_LOS). Thissignal indicates when the amplitude of the incoming serial data is low enough to be considered invalid.4.1 Data flowThe 10-bit data presented

34、 to the Physical layer device shall be serially transmitted to the cable plant, bits Tx0-Tx9sequentially. The relationship of transmit bits and the 10-bit 8B/10B-encoded characters is described in FC-FS.The receiver in the Physical layer device shall receive and frame data at an arbitrary byte bound

35、ary until a commasequence is received. The receiver shall realign its current byte boundary, if necessary, to that of the received comma.This process is called “byte alignment”. During the byte alignment process the Physical layer device may delete up to 4characters in order to align the receive clo

36、ck and the data byte containing the comma character (byte 0). This process iscalled “byte slipping”.INCITS TR-26-2000 (R2005)44.2 Electrical interface signalsThe Transmit Interface and Receive Interface signals listed below shall comprise the minimum set of signals whichmust be supplied for complian

37、ce with this Technical Report. Each signal is described in its own subsection which isheaded with the signal name followed by the logic family in parentheses. In case of conflict between specifications inthis document and other documents describing similarly-named logic families, this document shall

38、 take precedence.The two static reference voltage signals do not have associated logic families. Electrical signal levels are described inSection 5.4.2.1 Tx0:9 (SSTL_2)Tx0:9 is the 10-bit parallel transmit data presented to the Physical layer device for serialization and transmissiononto the media.

39、The order of transmission is Tx0 first, followed by Tx1 through Tx9. If the Transmit Interface isoperating at 2 125,0 MBaud, Tx0:9 shall be 212,50 MBaud. If the Transmit Interface is operating at 1 062,5MBaud, Tx0:9 shall be 106,25 MBaud.4.2.2 TBC (SSTL_2)TBC is the transmit byte clock which operate

40、s at 106,25 MHz independent of the Transmit Interface data rate. TBC isused to read data into the Physical layer device for transmission. When the Transmit Interface is operating at 2 125,0MBaud, TBC shall be synchronous with Tx0:9 (“source-synchronous”) and data shall be read into the Physicallayer

41、 device on both edges of TBC. When the Transmit Interface is operating at 1 062,5 MBaud, data shall be readinto the Physical layer device on the falling edge of TBC. TBC shall be frequency locked to REFCLK0:1. Thephase relationship of TBC to REFCLK0:1 must be maintained within +/- 90 degrees and is

42、vendor-dependent.4.2.3 REFCLK0:1 (PECL)REFCLK0:1 is the differential 106,25 MHz transmit PLL reference clock. The frequency tolerance for this clockshall be 100 ppm. REFCLK0:1 may be used by the transmitter PLL to generate the 2 125,0 or 1 062,5 MHz bitrate clocks used in serial data transmission. R

43、eceivers shall automatically lock to REFCLK0:1. REFCLK0:1 isactive on the rising edge of REFCLK1.4.2.4 TX_RATE (SSTL_2)TX_RATE is the speed selector for the Transmit Interface. When TX_RATE is set to logical 0, the Transmit Interfaceshall operate at 1 062,5 MBaud. When TX_RATE is set to logical 1, t

44、he Transmit Interface shall operate at 2 125,0MBaud.4.2.5 VREFTVREFT is the reference voltage for Tx0:9, TBC, TX_RATE, RX_RATE, EWRAP and EN_CDET. The Physicallayer device shall interpret Tx0:9, TBC, TX_RATE, RX_RATE, EWRAP and EN_CDET as logical 1 when theirvoltages are greater than VREFT. The Phys

45、ical layer device shall interpret Tx0:9, TBC, TX_RATE, RX_RATE,EWRAP and EN_CDET as logical 0 when their voltages are less than VREFT. VREFT may be supplied by theTransmission protocol layer device.4.2.6 Rx0:9 (SSTL_2)Rx0:9 is the 10-bit parallel receive data presented to the Transmission protocol l

46、ayer device for further processing.Data byte 0 of a four-byte receive word containing the comma character shall be byte aligned to RBC1 (byte 0 is inphase with RBC1).4.2.7 RBC0 (SSTL_2)RBC0 is the receive byte clock. On the rising edge of RBC0, the Transmission protocol layer device shall latchbytes

47、 1 and 3 of the receive data word. RBC0 is 53,125 MHz when the Receive Interface is operating at 1 062,5MBaud. RBC0 is 106,25 MHz when the Receive Interface is operating at 2 125,0 MBaud. RBC0 may be stretchedduring byte and word alignment. RBC0 shall not be truncated or slivered.INCITS TR-26-2000 (

48、R2005)54.2.8 RBC1 (SSTL_2)RBC1 is the receive byte clock. On the rising edge of RBC1, the Transmission protocol layer device shall latch bytes0 and 2 of the receive data word. RBC1 is 53,125 MHz when the Receive Interface is operating at 1 062,5 MBaud.RBC1 is 106,25 MHz when the Receive Interface is

49、 operating at 2 125,0 MBaud. RBC1 is 180 out of phase withRBC0. RBC1 may be stretched during byte and word alignment. RBC1 shall not be truncated or slivered.4.2.9 EWRAP (SSTL_2)EWRAP shall cause the Physical layer device to electrically loop serialized transmit data to the deserializer. The pri-mary serial outputs on the transmitter shall be held in a static state during EWRAP operation. EWRAP may be tied tological 0 (disabled) by the Transmission protocol layer device.4.

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1