ZL30301GAG

ZL30301 Timing over Packet (ToP) Technology Data Sheet Features September 2005 • Recovers and transmits network synchronization over Ethernet, IP and MPLS Networks • Output clocks meet ITU-T G.823 and G.824 traffic interface specifications, and ANSI T1.403 timing requirements • Fully configurable, enabling performance to be tailored to application and network requirements • Generates outgoing packet reference locked to the TS_CLKi electrical reference clock • Recovers up to 4 independent clock frequencies from packet streams, in the frequency range 1.544 MHz to 10 MHz • Average frequency accuracy better than ± 15 ppb • Supports Master, Slave and Repeater modes of operation • • • Ordering Information ZL30301GAG 324 PBGA Trays -40°C to +85°C • Flexible classification of incoming packets at layers 2, 3, 4 and 5 • Flexible, multi-protocol packet encapsulation, with support for Ethernet, VLAN, IPv4/6, MPLS, L2TPv3, UDP and RTP • JTAG (IEEE 1149) boundary-scan interface Applications • GSM, UMTS air interface synchronization over a packet network Supports user defined timing recovery algorithms • Dual configurable packet interface: • Two MII interfaces • One MII and one GMII/TBI Circuit Emulation Service over Packets (CESoP), TDM over IP (TDMoIP) • IP-PBX • VoIP Gateways • Video Conferencing • Broadband Video Distribution Flexible 32 bit host CPU interface (Motorola PowerQUICCTM 1 and 2 compatible) Host Processor running Zarlink Timing Recovery Algorithm Host Processor Interface ZL30301 ZL30301 Host Processor Interface Timestamp Engine MII MAC GMII/PCS or MII Clock Synthesis CLKo[0] CLKo[1] CLKo[2] CLKo[3] Packet Engine CLKi[0] CLKi[1] CLKi[2] CLKi[3] JTAG EXT_CLKo_REF TS_CLKi TCK TDI TDO TMS TRST Figure 1 - ZL30301 Functional Block Diagram 1 Zarlink Semiconductor Inc. Zarlink, ZL and the Zarlink Semiconductor logo are trademarks of Zarlink Semiconductor Inc. Copyright 2005, Zarlink Semiconductor Inc. All Rights Reserved. ZL30301 2 Zarlink Semiconductor Inc. Data Sheet ZL30301 Data Sheet Table of Contents 1.0 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2.0 Physical Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.0 External Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1 Clock Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.2 Packet Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.3 CPU Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.4 System Function Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.5 Test Facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.5.1 Administration, Control and Test Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.5.2 JTAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.6 Miscellaneous Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.7 Power and Ground Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.8 Internal Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.9 No Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.10 Device ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.0 Typical Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4.1 Edge of the PSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4.2 Wireless Access Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.0 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.1 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.1.1 Master Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.1.2 Slave Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.1.3 Timing Repeater Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.2 Timing Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5.3 Clock Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5.3.1 Adaptive Clock Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5.3.2 Differential Clock Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.3.3 Combination of Adaptive and Differential Clock Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.4 Handling of Non-Timing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.4.1 Snoop Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.4.2 Pass-through Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.4.3 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.5 Contribution of the Network and Local Oscillator on the Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.6 CPU Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 5.7 Management and Clock Quality Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.7.1 Statistics on Received Timing Packets (Slave mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.7.2 Statistics on Transmitted Timing Packets (Master mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.7.3 Status Information on Recovered Clocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.8 Processing of Incoming Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.0 System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.1 Loopback Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.2 Host Packet Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.3 Power Up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 6.4 JTAG Interface and Board Level Test Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.5 External Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.6 Miscellaneous Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 6.7 Test Modes Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.7.1.1 System Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.7.1.2 System Tri-State Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.7.2 Test Mode Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3 Zarlink Semiconductor Inc. ZL30301 Data Sheet Table of Contents 6.7.3 System Normal Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6.7.4 System Tri-state Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 7.0 DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 8.0 AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 8.1 Clock Interface Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 8.2 Timestamp Reference Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 8.3 Packet Interface Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 8.3.1 MII Transmit Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 8.3.2 MII Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 8.3.3 GMII Transmit Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 8.3.4 GMII Receive Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 8.3.5 TBI Interface Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 8.3.6 Management Interface Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 8.4 CPU Interface Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 8.5 System Function Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 8.6 JTAG Interface Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 9.0 Design and Layout Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 9.1 High Speed Clock & Data Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 9.1.1 GMAC Interface - Special Considerations During Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 9.1.2 Clock Interface - Special Considerations during Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 9.1.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 9.2 CPU TA Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 10.0 Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 10.1 External Standards/Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 11.0 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 4 Zarlink Semiconductor Inc. ZL30301 Data Sheet List of Figures Figure 1 - ZL30301 Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Figure 2 - ZL30301 Package View and Ball Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Figure 3 - Edge of the PSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 4 - Example of Wireless Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 5 - ZL30301 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Figure 6 - ZL30301 Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Figure 7 - ZL30301 Timing Repeater Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 8 - Adaptive Clock Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Figure 9 - Adaptive Clock Recovery State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Figure 10 - Differential Clock Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Figure 11 - Combination of Adaptive and Differential Clock Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Figure 12 - Application to Circuit Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Figure 13 - Snoop or Listen-only Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Figure 14 - “Pass-Through” Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Figure 15 - Block Diagram of ZL30301 to MPC8260 Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Figure 16 - Powering Up the ZL30301 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Figure 17 - Clock Interface Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Figure 18 - MII Transmit Timing Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Figure 19 - MII Receive Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Figure 20 - GMII Transmit Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Figure 21 - GMII Receive Timing Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Figure 22 - TBI Transmit Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Figure 23 - TBI Receive Timing Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Figure 24 - Management Interface Timing for Ethernet Port - Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Figure 25 - Management Interface Timing for Ethernet Port - Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Figure 26 - CPU Read - MPC8260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Figure 27 - CPU Write - MPC8260. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Figure 28 - CPU DMA Read - MPC8260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Figure 29 - CPU DMA Write - MPC8260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Figure 30 - JTAG Signal Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Figure 31 - JTAG Clock and Reset Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Figure 32 - CPU_TA Board Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5 Zarlink Semiconductor Inc. ZL30301 Data Sheet List of Tables Table 1 - ZL30301 Ball Signal Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Table 2 - Clock Interface Pin Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Table 3 - Packet Interface Signal Mapping - MII to GMII/TBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Table 4 - MII Management Interface Package Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Table 5 - MII Port 0 Interface Package Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Table 6 - MII Port 1 Interface Package Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Table 7 - CPU Interface Package Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Table 8 - System Function Interface Package Ball Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Table 9 - Administration/Control Interface Package Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table 10 - JTAG Interface Package Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table 11 - Miscellaneous Inputs Package Ball Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Table 12 - Power and Ground Package Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Table 13 - Internal Connections Package Ball Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Table 14 - Internal Connections Package Ball Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Table 15 - Miscellaneous Inputs Package Ball Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Table 16 - Device ID Ball Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Table 17 - Management Statistics on Received Timing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Table 18 - Management Statistics on Transmitted Timing Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Table 19 - Status Information on the Recovered Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Table 20 - DMA Maximum Bandwidths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Table 21 - Test Mode Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Table 22 - Clock Interface Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Table 23 - Timestamp Reference Timing Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Table 24 - MII Transmit Timing - 100 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Table 25 - MII Receive Timing - 100 Mbps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Table 26 - GMII Transmit Timing - 1000 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Table 27 - GMII Receive Timing - 1000 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Table 28 - TBI Timing - 1000 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Table 29 - MAC Management Timing Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Table 30 - CPU Timing Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Table 31 - System Clock Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Table 32 - JTAG Interface Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 6 Zarlink Semiconductor Inc. ZL30301 1.0 Data Sheet Description Network infrastructures are gradually converging onto an asynchronous packet-based architecture. With this convergence, there are an increasing number of synchronous applications that require accurate timing to be distributed over the packet network. Examples of precision timing sensitive applications that need to transport synchronization over asynchronous packet networks include transport of TDM over packet networks, connections to 2 G and 3 G wireless base stations, Voice over IP, IP PBXs, videoconferencing and broadband video. Zarlink’s Timing over Packet (ToP) technology enables accurate timing and synchronization to be distributed across an asynchronous packet network. This patent-pending technology is implemented in the ZL3030x family of devices, which in combination with the line card microprocessor provide a complete solution for high performance clock synchronization over an asynchronous packet network. The family supports synchronization transfer across both layer 2 and layer 3 networks, using a range of standard protocols including Ethernet, VLAN, MPLS, IP, L2TPv3, UDP and RTP. The ZL30301 recovers up to 4 independent clocks that are locked to 4 independent references. It receives synchronization information in the form of numbered and time-stamped packets, whose arrival time is crossreferenced to the local clock source. This information is transmitted to the microprocessor, which in turn controls synthesis of the recovered clock. The ZL30301 algorithm continuously tracks the frequency offset (phase drift) between the clocks located at the master and the slave nodes connected via the packet switched network. This algorithm is tolerant of packet delay variation caused by packet queuing; the precision of the timing recovery depends on statistical properties of the propagation delay of timing packets through the network. The device is highly configurable to ensure that in the presence of jitter and wander of the reference signals, and short network interruptions, the generated clocks meet the appropriate international standards. The ZL30301 is designed to maintain average frequency accuracy better than +/-15 ppb with a Stratum 3 quality TCXO system clock and it is tolerant of packet network impairments. However network effects, and the behavior of the sending side of the synchronization link can degrade clock frequency accuracy. In the event of a failure in the packet network, or the advent of severe congestion preventing or seriously delaying the delivery of timing packets, the ZL30301 will put the recovered clocks into holdover until the flow of timing packets is restored. When the device is in holdover mode the drift of the system clock directly affects the accuracy of the holdover. The ZL30301 provides the JTAG (Joint Test Action Group) interface. 2.0 Physical Specification The package for the ZL30301 is a 324-ball PBGA. Features: • Body Size: 23 mm x 23 mm (typ) • Ball Count: 324 • Ball Pitch: 1.00 mm (typ) • Ball Matrix: 22 x 22 • Ball Diameter: 0.60 mm (typ) • Total Package Thickness: 2.03 mm (typ) 7 Zarlink Semiconductor Inc. ZL30301 Data Sheet ZL30301 Package view from TOP side. Note that ball A1 is non-chamfered corner. 1 2 3 4 A VDD_IO B M1_TXD[2] VDD_IO C M1_TXD[3] GND D M1_RXD[1] M1_RXD[0] M1_RXD[2] E M1_RXD[3] M0_GIGABI M1_TXCLK M1_RXER T_LED F NC 5 6 7 8 9 10 11 12 M1_TXEN M0_TXCLK M0_RXD[7] M0_RXD[6] M0_RXD[4] M0_COL M0_GTX_C M0_TXEN DEVICE_ID CPU_DATA[CPU_DATA[ LK [2] 28] 24] GND M1_TXD[0] M1_TXD[1] M0_CRS M0_RXD[0] M0_RBC1 M0_RBC0 M0_TXER VDD_IO M1_RXCLK M1_COL VDD_IO GND 13 14 15 GND CPU_DATA[ 23] GND VDD_IO 17 18 19 VDD_IO 20 GND VDD_IO CPU_DATA[ M1_LINKU CPU_DATA[CPU_DATA[ VDD_IO 31] P_LED 29] 26] M0_RXD[5] VDD_COR M0_RXD[2] M0_REFCL M0_TXD[6] M0_TXD[1] VDD_COR VDD_COR E K E E 21 22 CPU_DATA[CPU_DATA[CPU_DATA[CPU_DATA[CPU_DATA[ CPU_SDAC VDD_IO 19] 12] 9] 8] 7] K1 M0_TXD[5] M0_TXD[3] M0_TXD[2] M1_ACTIV CPU_DATA[CPU_DATA[CPU_DATA[CPU_DATA[ E_LED 27] 22] 20] 13] M1_TXER M0_RXDV M0_RXD[3] M0_RXD[1] M0_RXCLK M0_TXD[7] M0_TXD[4] M0_TXD[0] M1_RXDV M0_RXER 16 VDD_IO M0_ACTIV VDD_COR E_LED E VDD_IO CPU_TA GND CPU_DRE Q1 VDD_IO CPU_DATA[CPU_ADDR CPU_DATA[ 25] [23] 6] CPU_DATA[CPU_DATA[CPU_DATA[ CPU_DATA[ 30] 21] 15] 14] M1_CRS DEVICE_ID VDD_COR [1] E VDD_COR CPU_DATA[CPU_DATA[ CPU_DATA[ E 18] 17] 16] G M_MDIO DEVICE_ID M0_LINKU [0] P_LED VDD_IO VDD_IO CPU_IREQ CPU_DATA[ CPU_DATA[ 1 11] 0] H M_MDC GND NC VDD_COR E J NC NC NC VDD_COR E GND GND GND GND GND GND K NC NC NC VDD_IO GND GND GND GND GND GND GND CPU_DATA[ 2] L GND CON_L3 CON_L2 VDD_COR E GND GND GND GND GND GND CPU_CLK GND M CLKi[3] IC IC VDD_IO GND GND GND GND GND GND GND N IC CLKo[3] IC VDD_COR E GND GND GND GND GND GND VDD_IO P CLKi[2] GND VDD_IO VDD_COR E GND GND GND GND GND GND R CLKo[2] IC CLKi[0] IC GND CPU_ADD CPU_ADDR CPU_ADDR R[11] [13] [20] T CLKi[1] CLKo[1] IC VDD_IO VDD_IO VDD_IO CPU_ADDR CPU_ADDR [14] [16] U IC VDD_IO GND IC VDD_COR JTAG_TMS CPU_ADDR CPU_ADDR E [15] [12] V IC CLKo[0] IC TS_CLKI DEVICE_ID JTAG_TCK CPU_ADDR CPU_ADDR [3] [10] [9] W IC IC IC VDD_IO VDD_IO VDD_COR E VDD_IO VDD_IO Y IC GND VDD_IO IC IC VDD_COR E IC IC IC IC AA IC VDD_IO GND VDD_IO VDD_IO IC GND A1VDD_PL L1 IC IC AB VDD_IO IC IC IC GND IC IC IC GPIO[0] GPIO[3] CPU_DATA[CPU_DATA[CPU_DATA[ 10] 1] 4] VDD_COR EXT_CLKo E _ REF IC_GND GND IC_GND IC SYSTEM_C VDD_COR LK E GND SYSTEM_D SYSTEM_R GPIO[1] EBUG ST GPIO[4] GPIO[5] GPIO[6] VDD_COR CPU_DATA[CPU_DATA[ CPU_IREQ E 5] 3] 0 Zarlink Semiconductor Inc. IC CPU_SDAC IC_VDD_IO K2 CPU_TS_A CPU_WE LE CPU_ADD R[22] CPU_DRE Q0 CPU_OE CPU_CS CPU_ADDR [19] VDD_COR CPU_ADD CPU_ADDR CPU_ADDR E R[17] [18] [21] IC VDD_IO IC GND IC IC TEST_MOD JTAG_TRS E[1] T IC_GND VDD_IO GPIO[2] GPIO[7] IC TEST_MOD JTAG_TDI E[0] IC_GND GND IC IC IC TEST_MOD IC_GND E[2] Figure 2 - ZL30301 Package View and Ball Positions 8 IC DEVICE_ID VDD_IO [4] JTAG_TDO CPU_ADDR CPU_ADDR [4] [8] GND CPU_ADDR [7] VDD_IO CPU_ADDR [6] CPU_ADD CPU_ADD CPU_ADDR VDD_IO R[2] R[3] [5] ZL30301 Ball # ZL30301 Signal Name Ball # ZL30301 Signal Name Data Sheet ZL30301 Signal Name Ball # A1 VDD_IO B6 M0_CRS D2 M1_RXD[0] A10 DEVICE_ID[2] B7 M0_RXD[0] D3 M1_RXD[2] A11 CPU_DATA[28] B8 M0_RBC1 D4 VDD_IO A12 CPU_DATA[24] B9 M0_RBC0 D5 M1_RXDV A13 GND C1 M1_TXD[3] D6 M0_RXER A14 CPU_DATA[23] C10 M0_RXCLK D7 VDD_IO A15 GND C11 M0_TXD[7] D8 M0_RXD[5] A16 CPU_DATA[19] C12 M0_TXD[4] D9 VDD_CORE A17 CPU_DATA[12] C13 M0_TXD[0] E1 M1_RXD[3] A18 CPU_DATA[9] C14 VDD_IO E19 CPU_DATA[30] A19 CPU_DATA[8] C15 VDD_IO E20 CPU_DATA[21] A20 CPU_DATA[7] C16 CPU_DATA[31] E21 CPU_DATA[15] A21 CPU_SDACK1 C17 M1_LINKUP_LED E22 CPU_DATA[14] A22 VDD_IO C18 CPU_DATA[29] E2 M0_GIGABIT_LED A2 M1_TXEN C19 CPU_DATA[26] E3 M1_TXCLK A3 M0_TXCLK C20 VDD_IO E4 M1_RXER A4 M0_RXD[7] C21 GND F1 NC A5 M0_RXD[6] C22 CPU_DREQ1 F19 VDD_CORE A6 M0_RXD[4] C2 GND F20 CPU_DATA[18] A7 M0_COL C3 VDD_IO F21 CPU_DATA[17] A8 M0_GTX_CLK C4 M1_RXCLK F22 CPU_DATA[16] A9 M0_TXEN C5 M1_COL F2 M1_CRS B1 M1_TXD[2] C6 M1_TXER F3 DEVICE_ID[1] B10 M0_TXER C7 M0_RXDV F4 VDD_CORE B11 GND C8 M0_RXD[3] G1 M_MDIO B12 M0_TXD[5] C9 M0_RXD[1] G19 VDD_IO B13 M0_TXD[3] D1 M1_RXD[1] G20 CPU_IREQ1 B14 M0_TXD[2] D10 M0_RXD[2] G21 CPU_DATA[11] B15 M1_ACTIVE_LED D11 M0_REFCLK G22 CPU_DATA[0] B16 CPU_DATA[27] D12 M0_TXD[6] G2 DEVICE_ID[0] B17 CPU_DATA[22] D13 M0_TXD[1] G3 M0_LINKUP_LED B18 CPU_DATA[20] D14 VDD_CORE G4 VDD_IO B19 CPU_DATA[13] D15 VDD_CORE H1 M_MDC B20 GND D16 VDD_IO H19 CPU_DATA[10] B21 VDD_IO D17 M0_ACTIVE_LED H20 CPU_DATA[1] B22 CPU_TA D18 VDD_CORE H21 CPU_DATA[4] B2 VDD_IO D19 VDD_IO H22 IC B3 GND D20 CPU_DATA[25] H2 GND B4 M1_TXD[0] D21 CPU_ADDR[23] H3 NC B5 M1_TXD[1] D22 CPU_DATA[6] H4 VDD_CORE Table 1 - ZL30301 Ball Signal Assignment Table 1 - ZL30301 Ball Signal Assignment (continued) 9 Zarlink Semiconductor Inc. Table 1 - ZL30301 Ball Signal Assignment (continued) ZL30301 ZL30301 Signal Name Ball # ZL30301 Signal Name Ball # Data Sheet ZL30301 Signal Name Ball # J1 NC L4 VDD_CORE P2 GND J10 GND L9 GND P3 VDD_IO J11 GND M1 CLKi[3] P4 VDD_CORE J12 GND M10 GND P9 GND J13 GND M11 GND R1 CLKo[2] J14 GND M12 GND R19 GND J19 VDD_CORE M13 GND R20 CPU_ADDR[11] J20 CPU_DATA[5] M14 GND R21 CPU_ADDR[13] J21 CPU_DATA[3] M19 GND R22 CPU_ADDR[20] J22 CPU_IREQ0 M20 CPU_TS_ALE R2 IC J2 NC M21 CPU_WE R3 CLKi[0] J3 NC M22 CPU_OE R4 IC J4 VDD_CORE M2 IC T1 CLKi[1] J9 GND M3 IC T19 VDD_IO K1 NC M4 VDD_IO T20 VDD_IO K10 GND M9 GND T21 CPU_ADDR[14] K11 GND N1 IC T22 CPU_ADDR[16] K12 GND N10 GND T2 CLKo[1] K13 GND N11 GND T3 IC K14 GND N12 GND T4 VDD_IO K19 GND N13 GND U1 IC K20 CPU_DATA[2] N14 GND U19 VDD_CORE K21 IC N19 VDD_IO U20 JTAG_TMS K22 CPU_DREQ0 N20 CPU_ADDR[22] U21 CPU_ADDR[15] K2 NC N21 CPU_CS U22 CPU_ADDR[12] K3 NC N22 CPU_ADDR[19] U2 VDD_IO K4 VDD_IO N2 CLKo[3] U3 GND K9 GND N3 IC U4 IC L1 GND N4 VDD_CORE V1 IC L10 GND N9 GND V19 DEVICE_ID[3] L11 GND P1 CLKi[2] V20 JTAG_TCK L12 GND P10 GND V21 CPU_ADDR[10] L13 GND P11 GND V22 CPU_ADDR[9] L14 GND P12 GND V2 CLKo[0] L19 CPU_CLK P13 GND V3 IC L20 GND P14 GND V4 TS_CLKI L21 CPU_SDACK2 P19 VDD_CORE W1 IC L22 IC_VDD_IO P20 CPU_ADDR[17] W10 EXT_CLKo_REF L2 CON_L3 P21 CPU_ADDR[18] W11 IC_GND L3 CON_L2 P22 CPU_ADDR[21] W12 GND Table 1 - ZL30301 Ball Signal Assignment (continued) Table 1 - ZL30301 Ball Signal Assignment (continued) 10 Zarlink Semiconductor Inc. Table 1 - ZL30301 Ball Signal Assignment (continued) ZL30301 ZL30301 Signal Name Ball # ZL30301 Signal Name Ball # Data Sheet ZL30301 Signal Name Ball # W13 SYSTEM_CLK AA1 IC AB6 IC W14 VDD_CORE AA10 IC AB7 IC W15 IC AA11 SYSTEM_DEBUG AB8 IC W16 VDD_IO AA12 SYSTEM_RST AB9 GPIO[0] W17 IC AA13 GPIO[1] W18 DEVICE_ID[4] AA14 GPIO[2] W19 VDD_IO AA15 GPIO[7] W20 JTAG_TDO AA16 IC W21 CPU_ADDR[4] AA17 TEST_MODE[0] W22 CPU_ADDR[8] AA18 JTAG_TDI W2 IC AA19 IC_GND W3 IC AA20 GND W4 VDD_IO AA21 VDD_IO W5 VDD_IO AA22 CPU_ADDR[6] W6 VDD_CORE AA2 VDD_IO W7 VDD_IO AA3 GND W8 VDD_IO AA4 VDD_IO W9 VDD_CORE AA5 VDD_IO Y1 IC AA6 IC Y10 IC AA7 GND Y11 IC_GND AA8 A1VDD_PLL1 Y12 IC AA9 IC Y13 GND AB1 VDD_IO Y14 GND AB10 GPIO[3] Y15 IC AB11 GPIO[4] Y16 IC AB12 GPIO[5] Y17 TEST_MODE[1] AB13 GPIO[6] Y18 JTAG_TRST AB14 IC Y19 IC_GND AB15 IC Y20 VDD_IO AB16 IC Y21 GND AB17 TEST_MODE[2] Y22 CPU_ADDR[7] AB18 IC_GND Y2 GND AB19 CPU_ADDR[2] Y3 VDD_IO AB20 CPU_ADDR[3] Y4 IC AB21 CPU_ADDR[5] Y5 IC AB22 VDD_IO Y6 VDD_CORE AB2 IC Y7 IC AB3 IC Y8 IC AB4 IC Y9 IC AB5 GND Table 1 - ZL30301 Ball Signal Assignment (continued) Table 1 - ZL30301 Ball Signal Assignment (continued) 11 Zarlink Semiconductor Inc. Table 1 - ZL30301 Ball Signal Assignment (continued) NC - Not Connected - leave open circuit. IC - Internally Connected - leave open circuit. IC_GND - Internally Connected - tie to ground IC_VDD_IO - Internally Connected - tie to VDD_IO CON_L2 - connect to ball L2 CON_L3 - connect to ball L3 ZL30301 3.0 Data Sheet External Interface Description The following key applies to all tables: 3.1 I Input O Output D Internal 100 kΩ pull-down resistor present U Internal 100 kΩ pull-up resistor present T Tri-state Output Clock Interface All Clock Interface signals are 5 V tolerant. All Clock Interface outputs are high impedance while System Reset is LOW. All Clock Interface inputs have internal pull-down resistors so they can be safely left unconnected if not used. Signal I/O Package Balls Description CLKi[3:0] ID [3] [2] [1] [0] M1 P1 T1 R3 Clock inputs. In master mode these input are connected to CLKo[3:0], respectively. In slave mode these inputs can be connected to CLKo[3:0] for some applications. These inputs accepts frequencies from 8 kHz up to 34.368 MHz CLKo[3:0] OT [3] [2] [1] [0] N2 R1 T2 V2 Clock outputs. In slave mode, these are the recovered clocks from the packet network. These clocks may be connected to CLKi[3:0] for some applications, e.g., selection of a single output clock, or selection of a timestamp reference for a repeater function. In master mode these outputs are connected to CLKi[3:0], respectively. The recovered clocks are 8 kHz multiples in the range 1.544 MHz to 10 MHz. TS_CLKi ID V4 Time Stamp clock input. In master mode and/or repeater mode, this input is multiplexed with the four input clock signals CLKi[3:0] to select the clock to be distributed over the packet network. It is used as the timestamp clock, or as a reference clock input for differential clock recovery. Acceptable frequency range: 1.544 MHz 10 MHz (timestamp clock) or 4 MHz to 40 MHz (differential reference clock). Table 2 - Clock Interface Pin Definition 12 Zarlink Semiconductor Inc. ZL30301 Signal EXT_CLKo_REF I/O Data Sheet Package Balls OT W10 Description Multiplexed output signal, selecting one of the clock inputs, CLKi[3:0]. The source clock may be frequency divided internally prior to output on EXT_CLKo_REF pin. Expected frequency range: 8 kHz - 10 MHz. Table 2 - Clock Interface Pin Definition Note: All Clock Interface inputs have internal pull-down resistors so they can be safely left unconnected if not used. 3.2 Packet Interfaces The ZL30301 packet interface features either 2 MII interfaces, or 1 MII and 1 GMII interfaces, or 1 MII and 1 TBI (1000 Mbps) interfaces. The TBI interface is a PCS interface supported by an integrated 1000BASE-X PCS module. Data for all three types of packet switching is based on Specification IEEE Std. 802.3 - 2000. Only Port 0 has the 1000 Mbps capability necessary for the GMII/TBI interface. Table 3 maps the signal pins used in the MII interface to those used in the GMII and TBI interface. Table 4 through Table 6 show all the pins and their related package balls, based on the GMII/MII configuration. All Packet Interface signals are 5 V tolerant, and all outputs are high impedance while System Reset is LOW. MII GMII TBI (PCS) Mn_LINKUP_LED Mn_LINKUP_LED Mn_LINKUP_LED Mn_ACTIVE_LED Mn_ACTIVE_LED Mn_ACTIVE_LED - Mn_GIGABIT_LED Mn_GIGABIT_LED - Mn_REFCLK Mn_REFCLK Mn_RXCLK Mn_RXCLK Mn_RBC0 Mn_COL Mn_COL Mn_RBC1 Mn_RXD[3:0] Mn_RXD[7:0] Mn_RXD[7:0] Mn_RXDV Mn_RXDV Mn_RXD[8] Mn_RXER Mn_RXER Mn_RXD[9] Mn_CRS Mn_CRS Mn_Signal_Detect Mn_TXCLK - - Mn_TXD[3:0] Mn_TXD[7:0] Mn_TXD[7:0] Mn_TXEN Mn_TXEN Mn_TXD[8] Mn_TXER Mn_TXER Mn_TXD[9] - Mn_GTX_CLK Mn_GTX_CLK Table 3 - Packet Interface Signal Mapping - MII to GMII/TBI Note: Mn can be either M0 or M1 for ZL30301. 13 Zarlink Semiconductor Inc. ZL30301 Signal I/O Package Balls Data Sheet Description M_MDC O H1 MII management data clock. Common for both MII ports. It has a minimum period of 400 ns (maximum frequency 2.5 MHz), and is independent of the TXCLK and RXCLK. M_MDIO ID/ OT G1 MII management data I/O. Common for both MII ports at up to 2.5 MHz. It is bi-directional between the ZL30301 and the Ethernet station management entity. Data is passed synchronously with respect to M_MDC. Table 4 - MII Management Interface Package Ball Definition MII Port 0 Signal I/O Package Balls Description M0_LINKUP_LED O G3 LED drive for MAC 0 to indicate port is linked up. Logic 0 output = LED on Logic 1 output = LED off M0_ACTIVE_LED O D17 LED drive for MAC 0 to indicate port is transmitting or receiving packet data. Logic 0 output = LED on Logic 1 output = LED off M0_GIGABIT_LED O E2 LED drive for MAC 0 to indicate operation at Gbps. Logic 0 output = LED on Logic 1 output = LED off M0_REFCLK ID D11 GMII/TBI - Reference Clock input at 125 MHz. Can be used to lock receive circuitry (RX) to M0_GTXCLK rather than recovering the RXCLK (or RBC0 and RBC1). Useful, for example, in the absence of valid serial data. NOTE: In MII mode this pin must be driven with the same clock as M0_RXCLK. M0_RXCLK IU C10 GMII/MII - M0_RXCLK. Accepts the following frequencies: 25.0 MHz MII 100 Mbps 125.0 MHz GMII 1 Gbps M0_RBC0 IU B9 TBI - M0_RBC0. Used as a clock when in TBI mode. Accepts 62.5 MHz and is 180°C out of phase with M0_RBC1. Receive data is clocked at each rising edge of M0_RBC1 and M0_RBC0, resulting in 125 MHz sample rate. Table 5 - MII Port 0 Interface Package Ball Definition 14 Zarlink Semiconductor Inc. ZL30301 Data Sheet MII Port 0 Signal I/O Package Balls Description M0_RBC1 IU B8 TBI - M0_RBC1 Used as a clock when in TBI mode. Accepts 62.5 MHz, and is 180° out of phase with M0_RBC0. Receive data is clocked at each rising edge of M0_RBC1 and M0_RBC0, resulting in 125 MHz sample rate. M0_COL ID A7 GMII/MII - M0_COL. Collision Detection. This signal is independent of M0_TXCLK and M0_RXCLK, and is asserted when a collision is detected on an attempted transmission. It is active high, and only specified for half-duplex operation. M0_RXD[7:0] IU [7] [6] [5] [4] M0_RXDV / M0_RXD[8] ID C7 GMII/MII - M0_RXDV Receive Data Valid. Active high. This signal is clocked on the rising edge of M0_RXCLK. It is asserted when valid data is on the M0_RXD bus. TBI - M0_RXD[8] Receive Data. Clocked on the rising edges of M0_RBC0 and M0_RBC1. M0_RXER / M0_RXD[9] ID D6 GMII/MII - M0_RXER Receive Error. Active high signal indicating an error has been detected. Normally valid when M0_RXDV is asserted. Can be used in conjunction with M0_RXD when M0_RXDV signal is de-asserted to indicate a False Carrier. TBI - M0_RXD[9] Receive Data. Clocked on the rising edges of M0_RBC0 and M0_RBC1. M0_CRS / M0_Signal_Detect ID B6 GMII/MII - M0_CRS Carrier Sense. This asynchronous signal is asserted when either the transmission or reception device is non-idle. It is active high. TBI - M0_Signal Detect Similar function to M0_CRS. M0_TXCLK IU A3 MII only - Transmit Clock Accepts the following frequencies: 25.0 MHz MII 100 Mbps A4 A5 D8 A6 [3] [2] [1] [0] C8 D10 C9 B7 Receive Data. Only half the bus (bits [3:0]) are used in MII mode. Clocked on rising edge of M0_RXCLK (GMII/MII) or the rising edges of M0_RBC0 and M0_RBC1 (TBI). Table 5 - MII Port 0 Interface Package Ball Definition (continued) 15 Zarlink Semiconductor Inc. ZL30301 Data Sheet MII Port 0 Signal I/O Package Balls M0_TXD[7:0] O [7] [6] [5] [4] M0_TXEN / M0_TXD[8] O A9 GMII/MII - M0_TXEN Transmit Enable. Asserted when the MAC has data to transmit, synchronously to M0_TXCLK with the first preamble of the packet to be sent. Remains asserted until the end of the packet transmission. Active high. TBI - M0_TXD[8] Transmit Data. Clocked on rising edge of M0_GTXCLK. M0_TXER / M0_TXD[9] O B10 GMII/MII - M0_TXER Transmit Error. Transmitted synchronously with respect to M0_TXCLK, and active high. When asserted (with M0_TXEN also asserted) the ZL30301 will transmit a nonvalid symbol, somewhere in the transmitted frame. TBI - M0_TXD[9] Transmit Data. Clocked on rising edge of M0_GTXCLK. M0_GTX_CLK O A8 GMII/TBI only - Gigabit Transmit Clock Output of a clock for Gigabit operation at 125 MHz. C11 D12 B12 C12 [3] [2] [1] [0] B13 B14 D13 C13 Description Transmit Data. Only half the bus (bits [3:0]) are used in MII mode. Clocked on rising edge of M0_TXCLK (MII) or the rising edge of M0_GTXCLK (GMII/TBI). Table 5 - MII Port 0 Interface Package Ball Definition (continued) MII Port 1 Signal I/O Package Balls Description M1_LINKUP_LED O C17 LED drive for MAC 1 to indicate port is linked up. Logic 0 output = LED on Logic 1 output = LED off M1_ACTIVE_LED O B15 LED drive for MAC 1 to indicate port is transmitting or receiving packet data. Logic 0 output = LED on Logic 1 output = LED off M1_RXCLK IU C4 MII only - Receive Clock. Accepts the following frequencies: 25.0 MHz MII 100 Mbps Table 6 - MII Port 1 Interface Package Ball Definition 16 Zarlink Semiconductor Inc. ZL30301 Data Sheet MII Port 1 Signal I/O Package Balls Description M1_COL ID C5 Collision Detection. This signal is independent of M1_TXCLK and M1_RXCLK, and is asserted when a collision is detected on an attempted transmission. It is active high, and only specified for half-duplex operation. M1_RXD[3:0] IU [3] [2] M1_RXDV ID D5 Receive Data Valid. Active high. This signal is clocked on the rising edge of M1_RXCLK. It is asserted when valid data is on the M1_RXD bus. M1_RXER ID E4 Receive Error. Active high signal indicating an error has been detected. Normally valid when M1_RXDV is asserted. Can be used in conjunction with M1_RXD when M1_RXDV signal is de-asserted to indicate a False Carrier. M1_CRS ID F2 Carrier Sense. This asynchronous signal is asserted when either the transmission or reception device is non-idle. It is active high. M1_TXCLK IU E3 MII only - Transmit Clock Accepts the following frequencies: 25.0 MHz MII 100 Mbps M1_TXD[3:0] O [3] [2] M1_TXEN O A2 Transmit Enable. Asserted when the MAC has data to transmit, synchronously to M1_TXCLK with the first preamble of the packet to be sent. Remains asserted until the end of the packet transmission. Active high. M1_TXER O C6 Transmit Error. Transmitted synchronously with respect to M1_TXCLK, and active high. When asserted (with M1_TXEN also asserted) the ZL30301 will transmit a nonvalid symbol, somewhere in the transmitted frame. E1 D3 C1 B1 [1] [0] [1] [0] D1 D2 B5 B4 Receive Data. Clocked on rising edge of M1_RXCLK. Transmit Data. Clocked on rising edge of M1_TXCLK. Table 6 - MII Port 1 Interface Package Ball Definition (continued) 17 Zarlink Semiconductor Inc. ZL30301 3.3 Data Sheet CPU Interface All CPU Interface signals are 5 V tolerant. All CPU Interface outputs are high impedance while System Reset is LOW. Signal CPU_DATA[31:0] CPU_ADDR[23:2] I/O I/ OT I Package Balls Description [31] [30] [29] [28] [27] [26] [25] [24] [23] [22] [21] [20] [19] [18] [17] [16] C16 E19 C18 A11 B16 C19 D20 A12 A14 B17 E20 B18 A16 F20 F21 F22 [15] [14] [13] [12] [11] [10] [9] [8] [7] [6] [5] [4] [3] [2] [1] [0] E21 E22 B19 A17 G21 H19 A18 A19 A20 D22 J20 H21 J21 K20 H20 G22 CPU Data Bus. Bi-directional data bus, synchronously transmitted with CPU_CLK rising edge. [23] [22] [21] [20] [19] [18] [17] [16] [15] [14] [13] [12] D21 N20 P22 R22 N22 P21 P20 T22 U21 T21 R21 U22 [11] [10] [9] [8] [7] [6] [5] [4] [3] [2] R20 V21 V22 W22 Y22 AA22 AB21 W21 AB20 AB19 CPU Address Bus. Address input from processor to ZL30301, synchronously transmitted with CPU_CLK rising edge. NOTE: as with all ports in the ZL30301 device, CPU_DATA[0] is the least significant bit (lsb). NOTE: as with all ports in the ZL30301 device, CPU_ADDR[2] is the least significant bit (lsb). CPU_CS IU N21 CPU Chip Select. Synchronous to rising edge of CPU_CLK and active low. Is asserted with CPU_TS_ALE. Must be asserted with CPU_OE to asynchronously enable the CPU_DATA output during a read, including DMA read. CPU_WE I M21 CPU Write Enable. Synchronously asserted with respect to CPU_CLK rising edge, and active low. Used for CPU writes from the processor to registers within the ZL30301. Asserted one clock cycle after CPU_TS_ALE. Table 7 - CPU Interface Package Ball Definition 18 Zarlink Semiconductor Inc. ZL30301 Signal I/O Package Balls Data Sheet Description CPU_OE I M22 CPU Output Enable. Synchronously asserted with respect to CPU_CLK rising edge, and active low. Used for CPU reads from the processor to registers within the ZL30301. Asserted one clock cycle after CPU_TS_ALE. Must be asserted with CPU_CS to asynchronously enable the CPU_DATA output during a read, including DMA read. CPU_TS_ALE I M20 Synchronous input with rising edge of CPU_CLK. Latch Enable (ALE), active high signal. Asserted with CPU_CS, for a single clock cycle. CPU_SDACK1 I A21 CPU/DMA 1 Acknowledge Input. Active low synchronous to CPU_CLK rising edge. Used to acknowledge request from ZL30301 for a DMA write transaction. Only used for DMA transfers, not for normal register access. CPU_SDACK2 I L21 CPU/DMA 2 Acknowledge Input Active low synchronous to CPU_CLK rising edge. Used to acknowledge request from ZL30301 for a DMA read transaction. Only used for DMA transfers, not for normal register access. CPU_CLK I L19 CPU PowerQUICC™ II Bus Interface clock input. 66 MHz clock, with minimum of 6 ns high/low time. Used to time all host interface signals into and out of ZL30301 device. OT B22 CPU Transfer Acknowledge. Driven from tri-state condition on the negative clock edge of CPU_CLK following the assertion of CPU_CS. Active low, asserted from the rising edge of CPU_CLK. For a read, asserted when valid data is available at CPU_DATA. The data is then read by the host on the following rising edge of CPU_CLK. For a write, is asserted when the ZL30301 is ready to accept data from the host. The data is written on the rising edge of CPU_CLK following the assertion. Returns to tri-state from the negative clock edge of CPU_CLK following the de-assertion of CPU_CS. CPU_TA Table 7 - CPU Interface Package Ball Definition (continued) 19 Zarlink Semiconductor Inc. ZL30301 Signal I/O Package Balls Data Sheet Description CPU_DREQ0 OT K22 CPU DMA 0 Request Output Active low synchronous to CPU_CLK rising edge. Asserted by ZL30301 to request the host initiates a DMA write. Only used for DMA transfers, not for normal register access. CPU_DREQ1 OT C22 CPU DMA 1 Request Active low synchronous to CPU_CLK rising edge. Asserted by ZL30301 to indicate packet data is ready for transmission to the CPU, and request the host initiates a DMA read. Only used for DMA transfers, not for normal register access. CPU_IREQO O J22 CPU Interrupt 0 Request (Active Low) CPU_IREQ1 O G20 CPU Interrupt 1 Request (Active Low) Table 7 - CPU Interface Package Ball Definition (continued) 3.4 System Function Interface All System Function Interface signals are 5 V tolerant. The core of the chip will be held in reset for 16383 SYSTEM_CLK cycles after SYSTEM_RST has gone HIGH to allow the PLL’s to lock. Signal I/O Package Balls Description SYSTEM_CLK I W13 System Clock Input. The system clock frequency is 100 MHz. SYSTEM_RST I AA12 System Reset Input. Active low. The system reset is asynchronous, and causes all registers within the ZL30301 to be reset to their default state. SYSTEM_DEBUG I AA11 System Debug Enable. This is an asynchronous signal that, when deasserted, prevents the software assertion of the debug-freeze command, regardless of the internal state of registers, or any error conditions. Active high. Table 8 - System Function Interface Package Ball Definition 20 Zarlink Semiconductor Inc. ZL30301 3.5 3.5.1 Data Sheet Test Facilities Administration, Control and Test Interface All Administration, Control and Test Interface signals are 5 V tolerant. Signal I/O Package Balls Description GPIO[7:0] ID/ OT [7] [6] [5] [4] [3] [2] [1] [0] AA15 AB13 AB12 AB11 AB10 AA14 AA13 AB9 General Purpose I/O pins. Connected to an internal register, so customer can set userdefined parameters. TEST_MODE[2:0] ID [2] [1] [0] AB17 Y17 AA17 Test Mode input - ensure these pins are tied to ground for normal operation. 000 SYS_NORMAL_MODE 001-010 RESERVED 011 SYS_TRISTATE_MODE 100-111 RESERVED Table 9 - Administration/Control Interface Package Ball Definition 3.5.2 JTAG Interface All JTAG Interface signals are 5 V tolerant, and conform to the requirements of IEEE1149.1 (2001). Signal I/O Package Balls Description JTAG_TRST IU Y18 JTAG Reset. Asynchronous reset. In normal operation this pin should be pulled low. JTAG_TCK I V20 JTAG Clock - maximum frequency is 25 MHz, typically run at 10 MHz. In normal operation this pin should be pulled either high or low. JTAG_TMS IU U20 JTAG test mode select. Synchronous to JTAG_TCK rising edge. Used by the Test Access Port controller to set certain test modes. JTAG_TDI IU AA18 JTAG test data input. Synchronous to JTAG_TCK. JTAG_TDO O W20 JTAG test data output. Synchronous to JTAG_TCK. Table 10 - JTAG Interface Package Ball Definition 21 Zarlink Semiconductor Inc. ZL30301 3.6 Data Sheet Miscellaneous Inputs The following unused inputs must be tied low or high as appropriate. Signal Package Balls Description IC_GND W11, Y11, Y19, AA19, AB18 Internally connected. Tie to GND. IC_VDD_IO L22 Internally connected. Tie to VDD_IO. Table 11 - Miscellaneous Inputs Package Ball Definitions 3.7 Power and Ground Connections Signal Package Balls Description VDD_IO A1 AA4 B2 C20 D4 K4 T19 W16 W7 A22 AA5 B21 C3 D7 M4 T20 W19 W8 AA2 AB1 C14 D16 G19 N19 T4 W4 Y20 AA21 AB22 C15 D19 G4 P3 U2 W5 Y3 3.3 V VDD Power Supply for IO Ring GND A13 AA7 B3 J10 J14 K12 K9 L12 L9 M13 N10 N14 P12 P9 Y13 A15 AB5 C2 J11 J9 K13 L1 L13 M10 M14 N11 N9 P13 R19 Y14 AA20 B11 C21 J12 K10 K14 L10 L14 M11 M19 N12 P10 P14 U3 Y2 AA3 B20 H2 J13 K11 K19 L11 L20 M12 M9 N13 P11 P2 W12 Y21 0 V Ground Supply VDD_CORE D14 F19 J4 P4 W9 D15 F4 L4 U19 Y6 D18 H4 N4 W14 D9 J19 P19 W6 1.8 V VDD Power Supply for Core Region A1VDD AA8 1.8 V PLL Power Supply Table 12 - Power and Ground Package Ball Definition 22 Zarlink Semiconductor Inc. ZL30301 3.8 Data Sheet Internal Connections The following pins are connected internally, and must be left open circuit. Signal IC Package Balls AA1 AA9 AB2 AB7 M2 R2 U4 W17 Y1 Y15 Y7 AA10 AB14 AB3 AB8 M3 R4 V1 W2 Y9 Y16 Y8 Description AA16 AB15 AB4 H22 N1 T3 V3 W3 Y10 Y4 AA6 AB16 AB6 K21 N3 U1 W1 W15 Y12 Y5 Internally connected. Leave open circuit Table 13 - Internal Connections Package Ball Definitions The following pins must be connected together. Signal Package Balls Description CON_L3 L2 Connect to ball L3. Balls L2 and L3 perform a loopback, and should be connected only to each other CON_L2 L3 Connect to ball L2. See L2. Table 14 - Internal Connections Package Ball Definitions 3.9 No Connections The following pins are not connected internally, and should be left open circuit. Signal NC Package Balls F1 J3 H3 K1 Description J1 K2 J2 K3 No connection. Leave open circuit. Table 15 - Miscellaneous Inputs Package Ball Definitions 3.10 Device ID Signal I/O DEVICE_ID[4:0] O Package Balls [4] [3] [2] [1] [0] Description Device ID. ZL30300 = 00100 ZL30301 = 10001 ZL30302 = 00110 W18 V19 A10 F3 G2 Table 16 - Device ID Ball Definition 23 Zarlink Semiconductor Inc. ZL30301 4.0 Data Sheet Typical Applications Many carriers are now beginning the process of moving their networks over to a packet-based structure. This breaks the circuit-switched nature of the telecommunications network, and divorces the delivery of data from the delivery of timing and synchronization. However, there are many applications which still require accurate timing and synchronization, including: • Circuit Emulation Service over packets, TDM over IP • GSM, UMTS air interface synchronization over a packet network • IP-PBX • VoIP Gateways • Video Conferencing • Broadband Video Distribution 4.1 Edge of the PSN There are a wide variety of applications and equipment that require synchronization, whether for voice, video or data. Figure 3 is a representation of a few different situations where synchronization from a PRS (primary reference source) is required to be carried across a packet network to its outer edges. At the PRS a ZL30301 is used to encode timing information. This timing is routed through the packet network to the boundaries at the outer edges of the PSN (packet-switched network). At the edge of the PSN another ZL30301 is used to regenerate or recover the timing. BITS SSU ZL30301 ZL30301 GSM / UMTS Basestation ZL30301 GSM / UMTS Basestation TDM PBX ZL30301 V.90 MODEM ZL30301 VoIP Gateway Ethernet Synchronous Analog Figure 3 - Edge of the PSN 24 Zarlink Semiconductor Inc. ZL30301 Data Sheet Unlike VoIP, fax and modem connections are not tolerant of buffer slips or a large number of data errors. A ZL30301 is used to synchronize the fax/modem inter-working functions to ensure no buffer slips. A second application is legacy PBX support. Using TDM pseudo-wires or Circuit Emulation Services over Packet (CESoP) the T1/E1 interface trunk to the PBX may be carried across a PSN. A ZL30301 may be used in this case to synchronize both ends of the CESoP connection to ensure the T1/E1 line meets the required ITU-T and ANSI timing and synchronization specifications. A third application is for VoIP. Traditionally VoIP did not put much emphasis on timing and synchronization in the gateway. It is becoming more important, for good voice quality, to reduce buffer slips by synchronizing the VoIP gateway. A ZL30301 is a perfect fit here, as well. 4.2 Wireless Access Applications Traditionally within the UMTS Terrestrial Radio Access Network the Node B (basestation) is connected to the Radio Network Controller (RNC) through a T1/E1 link. The remote base stations must remain synchronized to the network, and synchronization is also derived from the T1/E1 link. When this link is replaced by a packet network, an alternative means of synchronization must be provided. Current generation wireless base stations often meet synchronization requirements through GPS clocks when PRS traceable network references are not available. The ZL30301 can replace expensive parts such as GPS, distributing the clock over the packet network from the RNC. The transmit frequency must be maintained at a highly reliable frequency, within +/- 15 ppb from the master clock. This is because the clock is used to generate the radio signals for the air interface, and frequency deviations will cause interference with adjacent cell sites. The master clock can be distributed to the wireless network to maintain all nodes in complete synchronicity. Figure 2 depicts an example of such Wireless Infrastructure. Ethernet NodeB RNC Ethernet ZL30301 Slave Core Network ZL30301/2 Master PSTN NodeB ZL30301 Slave Figure 4 - Example of Wireless Infrastructure 25 Zarlink Semiconductor Inc. ZL30301 5.0 Functional Description 5.1 Modes of Operation Data Sheet The ZL30301 can operate in three primary modes: • as a timing master • as a timing slave • as a timing repeater Figure 5 shows an application diagram of the ZL30301 operating in Master, Slave or in a Timing Repeater Mode. ZL30301/2 Timing Repeater BITS SSU ZL30300/1/2 Slave 4 Slave Master GPS Primary ZL30301/2 Master Network 2 Network 1 ZL30300/1/2 Slave 2 ZL30300/1/2 Slave 3 ZL30300/1/2 Slave 1 Figure 5 - ZL30301 Operating Modes 5.1.1 Master Mode of Operation The ZL30301 is capable of transmitting network synchronization over Ethernet, IP and MPLS Networks. It may generate streams of packets in the required format, referenced to a master clock in the frequency range 1.544 MHz to 10 MHz. These packets may be either broadcast to all devices in the network, multicast to a number of selected devices (i.e., those in the addressed multicast group), or unicast to up to five separate slave devices. In unicast mode, the connections can be differentiated by address or port number, e.g., IP destination address (Unicast or Multicast), MPLS inner label, UDP port number, VLAN ID, etc. The master reference clock is connected to the timestamp input, TS_CLKi. All outgoing timing packets are timestamped from this clock. TS_CLKi accepts clocks from 1.544 MHz up to 10 MHz, but for better resolution the higher clock rates are recommended. In master operation, the DCOs are used to govern the rate of the packet streams. Therefore the DCO outputs need to be looped back into clock inputs of the device as follows: CLKo[0] into CLKi[0], CLKo[1] into CLKi[1], CLKo[2] into CLKi[2], and CLKo[3] into CLKi[3] (see Figure 6). Note that a further DCO is available internally to the device, to drive the fifth unicast packet stream. Typical packet rates are in the range 30 - 100 packets per second. 26 Zarlink Semiconductor Inc. ZL30301 Data Sheet . Host Processor running Zarlink Timing Recovery Algorithm Host Processor Interface ZL30301 ZL30301 control of packet rate Host Processor Interface Timestamp Engine MII MAC GMII/PCS or MII CLKo[0] CLKo[1] CLKo[2] CLKo[3] Clock Synthesis Packet Engine CLKi[0] CLKi[1] CLKi[2] CLKi[3] JTAG EXT_CLKo_REF TS_CLKi Master Reference TCK TDI TDO TMS TRST ~ Figure 6 - ZL30301 Master Mode 5.1.2 Slave Mode of Operation In slave mode, the ZL30301 can recover up to 4 independent clocks locked to 4 separate master clocks in the frequency range 1.544 MHz to 10 MHz. This may be utilized as part of a redundancy strategy, to minimize the effect of failure of a master clock or its distribution path. It is designed to maintain average frequency accuracy better than +/-15 ppb with a Stratum 3 quality TCXO system clock and it is tolerant of packet network impairments. However network effects, and the behavior of the sending side of the synchronization link can degrade clock frequency accuracy. The device is able to recover clocks from packet streams encoded in any of the following standardized formats: 1. “Timing over Packet” (ToP) streams with the packet header format Ethernet/IP/UDP/RTP1. 2. Standard CES data streams in one of the following formats: • ITU-T Recommendation Y.1413, March 2004 • IETF, draft-ietf-pwe3-satop-02, work in progress, July 2005 • IETF, draft-ietf-pwe3-cesopsn-03, work in progress, July 2005 • IETF, draft-iettf-pwe3-tdmoip-03, work in progress, February 2005 (unstructured data transfer only) • Metro Ethernet Forum, MEF 8, November 2004 • MPLS Forum, MFA 8.0.0, November 2004 1. Format could also be Ethernet/IP/L2TP/RTP, or Ethernet/MPLS/MPLS/RTP to suit different types of packet switched networks. 27 Zarlink Semiconductor Inc. ZL30301 Data Sheet One of the following methods is used to recover the clock. These methods are described in Section 5.3: • Adaptive clock recovery based on RTP timestamp (standard method for ToP streams) • Adaptive clock recovery based on sequence number (used for CES data streams where there may not be a timestamp. Since the packets are constant length, an effective timestamp is calculated based on the sequence number and the length of the constant-bit-rate payload) • Differential clock recovery based on RTP timestamp (used for CES data streams where a timestamp is provided relative to a known reference clock which is available at both master and slave devices) 5.1.3 Timing Repeater Mode of Operation The ZL30301 can also function as a timing repeater. This feature is very useful if there is a need for the synchronization information to be transmitted over a large network. Not only is the volume of timing packets reduced around the timing master device, reducing congestion, but the quality of the recovered clock is improved by breaking the trail through the packet network into two shorter segments. For example, in Figure 5, at the repeater node the ZL30301 will work as a slave node for the Network 1 and as a master node for the Network 2. The device is simultaneously operates in both Master and Slave modes to achieve the repeater function. Figure 7 shows the detailed connection for the ZL30301 operating in Repeater Timing mode. CLKo[0] is the clock recovered from the incoming packet stream. This is used to timestamp the outgoing packets sent to the subsequent slave devices. CLKo[1] - CLKo[3] are used to control the rate of the outgoing packet streams. Host Processor running Zarlink Timing Recovery Algorithm Host Processor Interface recovered clock ZL30301 ZL30301 Host Processor Interface Timestamp Engine MII MAC GMII/PCS or MII control of packet rate CLKo[0] CLKo[1] CLKo[2] CLKo[3] Clock Synthesis Packet Engine CLKi[0] CLKi[1] CLKi[2] CLKi[3] JTAG EXT_CLKo_REF TS_CLKi TCK TDI TDO TMS TRST Figure 7 - ZL30301 Timing Repeater Mode 28 Zarlink Semiconductor Inc. ZL30301 5.2 Data Sheet Timing Redundancy The ZL30301 can recover clocks from up to four separate packet timing sources. The on-chip multiplexer can be used to select the required clock, routing this to the common “EXT_CLKo_REF” pin. There is also a second internal multiplexer which can select the clock to be used as the timestamp source in the case of a repeater function. Various statistics on the status or the quality of the recovered clocks are available on which to base the choice of clock (see Section 5.7). However, it should be noted that a phase transient may be generated when switching over between recovered clocks. An external PLL with hitless reference switching should be used if it is important to avoid the phase hit. 5.3 Clock Recovery The ZL30301 supports clock recovery from up to four individual timing packet streams. There are two clock recovery schemes which can employed, depending on the availability of a common reference clock at both master and slave nodes - adaptive and differential. In some applications these schemes may be used in combination, where a ToP stream itself is used to distribute the common reference clock to the slave node. The clock recovery algorithm is performed by software in the external processor, with support from on-chip hardware to gather the required statistics. 5.3.1 Adaptive Clock Recovery For applications where there is no common reference clock available at both master and slave nodes, an adaptive clock recovery technique is used. This infers the clock rate of the original service clock from information about the arrival times of the timing packets at the slave, and the original launch times of the timing packets from the master. The advantage of this scheme is that there is no need for a common reference clock at both end of the network. Typical adaptive clock recovery algorithms use averaging to calculate the frequency of the original clock source. However, low frequency variations in the delay of packets through the network may be fed through as wander in the recovered clock. Zarlink has developed a superior method of adaptive clock recovery using patent-pending algorithms and heuristics to overcome the issue, and identify other disruptive events seen in typical packet networks. 29 Zarlink Semiconductor Inc. ZL30301 Data Sheet ZL30301/2 source node Source Clock Transmission timestamp generation ZL30301 destination node Packets Packet Switched Network Packets Arrival timestamp association DCO ~ Recovered Clock Host CPU Timing Recovery Algorithm Figure 8 - Adaptive Clock Recovery Incoming data traffic on the packet interface is received by the MACs, and forwarded to the packet classifier to determine the destination. Those packets identified as timing packets are timestamped on arrival, and this is compared to the timestamp data in the received packet. Where there is no explicit timestamp in the packet (such as in the case of CES data streams), an “effective timestamp” from the sequence number may be calculated, provided the packets are generated at a known, stable and unchanging rate. For CES data packets this is normally the case, since they are made up of a fixed number of bits from a constant-bit-rate data stream. The host processor filters the results to determine the frequency and phase of the master time-stamping clock, and to compare it to the frequency of the recovered clock. The filtering uses Zarlink’s patent-pending intelligent algorithms and heuristics to take into account any disruptive events in the packet network such as changes in routing, congestion and packet loss. It is also able to compensate for long-term changes in packet delay variation, such as may be exhibited by change in network usage patterns over a 24 hour period. The output of the filter is used to control the frequency of the output clock, which is generated using Zarlink’s precision, low-jitter DCO technology. The algorithm follows a simple state-machine design, shown in Figure 9. When the device starts up, the clock is in “free run” mode, and may be set to a pre-determined frequency. When it starts to receive timing packets, the algorithm will attempt to lock onto the stream of packets, and moves into the “acquiring” state. The “acquired” state is obtained when the device is locked to the frequency and phase of the source. Should a network event compromise the delivery of timing packets such that the slave is not able to make a valid assessment of the master clock frequency or phase for a period of time, it will drop back to the “acquiring” state. During this period, it will cease updating the clock frequency to avoid making an adjustment based on bad information, and sending the clock out of specification. If it is still unable to make a good estimation of the master clock then it will move into the “holdover” mode, and generate an interrupt to indicate to the management system that it has lost lock to the master source. The “holdover” state is typically entered for short durations while network is temporarily disrupted.While in holdover, the drift of the system clock directly affects the accuracy of the clock frequency. The device continues to monitor the incoming packets while in holdover, and on receipt of good packets will move back into the “acquiring” state and attempt to lock back onto the master clock source. 30 Zarlink Semiconductor Inc. ZL30301 Data Sheet Free Run Acquiring Holdover Acquired Figure 9 - Adaptive Clock Recovery State Machine 5.3.2 Differential Clock Recovery For applications where the wander characteristics of the recovered clock are very important, such as when an emulated circuit must be connected into the plesiochronous digital hierarchy (PDH), the ZL30301 also offers a differential clock recovery technique. This relies on having a common reference clock available at each provider edge point. Figure 10 illustrates this concept with a common Primary Reference Source (PRS) clock being present at both the source and destination equipment. In a differential technique, the timing of the service clock is sent relative to the common reference clock. Since the same reference is available at the packet egress point and the packet size is fixed, the original service clock frequency can be recovered. This technique is unaffected by any low frequency components in the packet delay variation. The disadvantage is the requirement for a common reference clock at each end of the packet network. 31 Zarlink Semiconductor Inc. ZL30301 Data Sheet PRS Clock ZL30301 destination node ZL30301/2 source node Source Clock Differential timestamp generation Packets Packet Switched Network Packets Timestamp extraction DCO ~ Recovered Clock Host CPU Timing Recovery Algorithm Figure 10 - Differential Clock Recovery 5.3.3 Combination of Adaptive and Differential Clock Recovery It is possible to combine the two techniques to gain the advantages of differential recovery without the need for a common reference clock. In this scenario, the reference clock is distributed between the two (or more) nodes using the “ToP” adaptive technique, and then several further clocks may be recovered differentially by reference to it. Figure 11 shows how this works in practice. An example of this kind of application is circuit emulation, where the central office reference may be distributed to several slave nodes, and the plesiochronous clocks associated with the TDM streams differentially encoded with respect to that reference (see Figure 12). The advantage of this is that the single “ToP” stream may achieve much better quality than adaptive recovery from the circuit emulation streams. This is because the packet formation process is freed from the necessity to transport regular, constant bit rate data, and can be optimized for timing transfer only. The result is a more robust, reliable and accurate recovery of the reference clock. 32 Zarlink Semiconductor Inc. ZL30301 Data Sheet PRS Clock ZL30301 destination node ZL30301/2 source node Transmission timestamp generation ToP Packets ToP Packets Packet Switched Network Source Clock Differential timestamp generation Diff. Packets Arrival timestamp association DCO Diff. Packets ~ Recovered PRS Timestamp extraction DCO ~ Recovered Clock Host CPU Timing Recovery Algorithms Figure 11 - Combination of Adaptive and Differential Clock Recovery CE1 CE1 Differential Clock Recovery CES IWF CE2 CE3 Packet Switched Network Adaptive Clock Recovery using ToP TDM Attachment Circuits e.g. T1, E1 CES IWF CE2 CE4 TDM Attachment Circuits e.g. T1, E1 Primary Reference Clock Figure 12 - Application to Circuit Emulation 33 Zarlink Semiconductor Inc. ZL30301 5.4 Data Sheet Handling of Non-Timing Packets Typically, a ZL30301 sits as close as possible to the customer interface, to avoid degradation of timing through the customer LAN. The devices may be connected in one of three ways: 1. snoop mode 2. pass-through mode 3. standalone mode 5.4.1 Snoop Mode This is where the device “listens” as packets fly past on the MII interface, ignoring all non-timing packets, as shown in Figure 13. Timing packets are passed to the clock synthesis function, and the embedded clocks recovered. This techniques is useful in a CES application, where packets are simultaneously passed to a CES interworking function to recover the data, while the timing is recovered by the ZL30301. The technique prevents any transmission by the ZL30301, and hence by implication, the use of a repeater stage. . Customer Premises ZL30302 ~ clock synth. PRS recovered clocks timing packets Timeserver classification timing packets Service Provider Network Ethernet P H Y Customer Edge Router MII "listens" on the line for timing packets, non-timing packets ignored Figure 13 - Snoop or Listen-only Mode 5.4.2 Pass-through Mode Pass-through mode is where the device forwards all non-timing packets onto the opposite packet interface (e.g. packets from MII1 to MII2 and vice versa). The devices on either side take care of any standard IP protocol control messages. This is the typical expected usage mode for the ZL30301 in slave and repeater applications. In this mode, the device is situated as near the customer/provider interface as possible (see Figure 14), with one port connected to the service provider network, and the second port connected to the customer network (normally the customer’s edge router or switch). All packets intended for the customer pass through the ZL30301 device. The ZL30301 classifies packets as they arrive to determine if they are timing packets or not. Timing packets are stripped out and processed, while all non-timing packets are forwarded to the customer edge router. 34 Zarlink Semiconductor Inc. ZL30301 Data Sheet In the reverse direction, packets from the customer edge router into the network are forwarded straight on into the service provider network. Timing packets (such as those generated by a repeater function) may also be forwarded into the network. Customer Premises ZL30302 recovered clocks clock synth. ~ PRS timing packets Timeserver classification timing packets Service Provider Network Ethernet non-timing packets Ethernet Customer Edge Router "non-timing" packets passed through from port to port Figure 14 - “Pass-Through” Mode 5.4.3 Standalone Mode In standalone mode, the ZL30301 is connected on its own port to a switch or router. For example, a standalone time-server or timing master device may use this configuration. The classifier must still identify timing packets for processing, but in this mode all non-timing packets are forwarded to the host CPU controlling the device. Packet forwarding may be done in two ways: • via the ZL30301 CPU interface, using the DMA queues internal to the device • forwarding non-timing packets to the second Ethernet port, and connecting this to the CPU’s own Ethernet port The second case is essentially identical to pass-through mode. 35 Zarlink Semiconductor Inc. ZL30301 5.5 Data Sheet Contribution of the Network and Local Oscillator on the Performance The ZL30301 uses a local oscillator to feed the system clock. The ZL30301 uses the system clock for internal operations and relies on the system clock during holdover of the recovered reference clock. The precision of timing recovery depends on statistical properties of the propagation delay of timing packets through the network and the stability of the local oscillator. The precision timing recovery through a switched network depends on several factors, including: • The accuracy and stability of the Local Oscillator • The timing packet rate • The delay profile of the timing packet stream This is in turn dependent on: • The length of the timing packet • The number of switches or routers in the network • The relative data load at the inter-switch links • The internal timing granularity of the switches or routers The accuracy and stability of the regenerated clock at the slaves depends on the combination of the clock recovery methodology and the accuracy and stability of the LO's in the system. The stability of the LO at the slave determines the packet rate that is required to sample its wander fast enough. The target precision for the average frequency accuracy at the slave is within 15 parts per billion. The performance that the ZL30301 achieves is dependent of the network that connects the master to the slave nodes. A sustained high network load affects the ZL30301 performance. The packet delay profile and the stability of the Local Oscillator are critical factors that are related to each other and suggest that several combinations are possible. A trade off must be made for the application between: 1. The accuracy and the stability of the LO 2. The maximum allowable timing packet rate 3. The dimensions of the network (number of inter-switch links and long-term average network load) 5.6 CPU Interface Figure 15 on page 37 gives an example on how to connect the CPU interface pin son the ZL30301 to an MPC8260. The intention is to help board designers understand the function of each of the CPU interface signals. Timing and other important issues are not considered in these examples. For a real interface design, it may be useful to have all CPU control signals connected through a PLD or FPGA logic, so that any tweaking on signals or timing can be easily implemented. As most of the microprocessors have multiple interrupts and DMA controllers, the choices made are discretionary. A “TA Stretch Circuit” is recommended for host interfaces operating above 40 MHz. Refer to section “CPU TA Output” on page 60 for more details. 36 Zarlink Semiconductor Inc. ZL30301 Data Sheet MPC8260 ZL30300 A[8:29] CPU_ADDR[23:2] D[0:31] CPU_DATA[31:0] CS[x] CPU_CS ALE CPU_ALE BCTL0 CPU_WE POE/PSDRAS CPU_OE PGTA/PGPL4 CPU_TA TA Stretch Circuit DREQ1/PC0 CPU_DREQ0 DREQ2/PC1 CPU_DREQ1 DACK1/PC23 CPU_SDACK1 DACK2/PC3 CPU_SDACK2 IRQ[x] CPU_IREQ0 IRQ[x] CPU_IREQ1 CLKIN CPU_CLK Figure 15 - Block Diagram of ZL30301 to MPC8260 Connection 5.7 Management and Clock Quality Statistics The ZL30301 can generate both network management and clock quality statistics, partially satisfying the requirements of the following protocols: • RTCP (RFC3550, section 6) - RTP is used as the protocol for the transfer of timing information • Pseudo-wire MIB (draft-ietf-pwe3-pw-mib-05) - this is important because timing packets could be distributed via a “timing pseudo-wire”, similar to that used for circuit emulation packets. 5.7.1 Statistics on Received Timing Packets (Slave mode) Statistic Value Required by Notes Number of packets received 32 bit count PW MIB PW MIB specifies both a 32 and 64 bit counter. For typical timing packet rates the 32 bit counter will never overflow within the 15 minute reporting interval. Number of payload octets received 32 bit count PW MIB PW MIB specifies both a 32 and 64 bit counter. For typical timing packet rates the 32 bit counter will never overflow within the 15 minute reporting interval. Table 17 - Management Statistics on Received Timing Packets 37 Zarlink Semiconductor Inc. ZL30301 Statistic Data Sheet Value Required by Notes Cumulative number of packets lost 32 bit count RTCP RTCP specifies an 8-bit “fraction lost since last report” parameter. If required, this may be implemented by periodically monitoring the cumulative value. Extended highest sequence number received 32 bit value RTCP The 16-bit extension may lose accuracy during extended periods of packet loss due to multiple wraparounds. Minimum and maximum values over a period RTCP (inter-arrival jitter) Reported in units of 125 us periods, although accuracy is approximately 1 ms. RTCP requests a measure of inter-arrival jitter rather than packet delay variation. The PDV figure may be used to obtain a rough estimate of inter-arrival jitter. Estimate of Packet Delay Variation Table 17 - Management Statistics on Received Timing Packets (continued) 5.7.2 Statistics on Transmitted Timing Packets (Master mode) Statistic Value Required by Notes Number of packets transmitted 32 bit count PW MIB, RTCP PW MIB specifies both a 32 and 64 bit counter. For typical timing packet rates the 32 bit counter will never overflow within the 15 minute reporting interval. Number of payload octets transmitted 32 bit count PW MIB, RTCP PW MIB specifies both a 32 and 64 bit counter. For typical timing packet rates the 32 bit counter will never overflow within the 15 minute reporting interval. Table 18 - Management Statistics on Transmitted Timing Packets 5.7.3 Status Information on Recovered Clocks Status Value Notes Slave state information Free running, Acquiring, Acquired, Holdover Master state information Boolean Clock Quality factor 8 bit value Indication of the current state of the clock recovery algorithm. An interrupt is generated on entry into/exit from holdover. Boolean value indicating loss of signal or reference at the master device. This may indicate either an absence of a master clock, or that the master clock has gone into holdover. An interrupt is generated on change of state. Value indicates a notional “quality value” of the recovered clock, based on how well disciplined the output frequency is. Values range from 0 (poor) - 255 (good), and are both normalised depending on the local oscillator type, and smoothed with a configurable time constant. Table 19 - Status Information on the Recovered Clocks 38 Zarlink Semiconductor Inc. ZL30301 5.8 Data Sheet Processing of Incoming Packets The incoming packets are classified into different packet timing connections. A connection is a mechanism used by the device to keep track of each data is extracted from each packet. The contents of the packet header of the incoming packets are examined to differentiate which connection should receive the packets. This is achieved using a multi-stage filter/comparator engine called the Packet Classifier. The first stage of the Packet Classifier is the Rx Filter or Pre-processor which looks at the destination MAC field and the ethertype field to allow packet to be quickly discarded. Additionally this stage also converts any IEEE 802.3 frames into standard Ethernet II frames. Packets that are not discarded will be passed on to the second stage. The second stage of the Packet Classifier is the Protocol Match or Pre-Classifier stage. This looks for specified fixed bytes in particular byte positions in order to confirm that the incoming packet is of the required protocol. There are four of these matches so allowing four different protocols to be identified. Packets that do not match any of the protocols are discarded. For packets that satisfy one of these protocol matches, certain bytes will then be extracted from the packet header and passed onto various other processing blocks. The third stage of interest is the Connection Match or Classifier stage. This receives from the protocol match 12 bytes from specified positions assembled into a contiguous array. The Connection Match compares this array of 12 bytes against user definable reference arrays contained within a number of “rules”. If no match is found the packet will be discarded. If however, a match is declared then the matched rule specifies which connection will be used to receive and process the packet as well as specifying the route for the packet through the device. The Protocol Match also extracts several fields of interest from the packet header. These are the sequence number, timestamp and length fields which are all passed on to other device blocks. One final field that is extracted is a number of “check bytes”. For packets which pass the Connection Match stage these check bytes provide a final check on the authenticity of the required packet. The output of all these stages is that packets that are accepted will be directed to the appropriate packet timing connection for further processing. The API provides facilities to program each of these stages independently (see API User Guide for details). 39 Zarlink Semiconductor Inc. ZL30301 6.0 System Features 6.1 Loopback Modes Data Sheet The ZL30301 devices support loopback of the clocks from CLKi[3:0] to its respectively CLKo[3:0] on a per port basis. That is to say that CLKo[3:0] may either be sourced from the packet network clock recovery or from CLKi[3:0]. Loopback of the ingress packets on the packet interface is achieved by redirecting classified packets from the Packet Receive blocks, back to the packet network. The Packet Transmit blocks are setup to strip the original header and add a new header directing the packets back to the source. 6.2 Host Packet Generation The control processor can generate packets directly, allowing it to use the network for out-of-band communications. This can be used for transmission of control data or network setup information, e.g., routing information. The host interface can also be used by a local resource for network transmission of processed data. The device supports dual address DMA transfers of packets to and from the CPU memory, using the host's own DMA controller. Table 20 illustrates the maximum bandwidths achievable by an external DMA master. Max Bandwidth Mbps1 DMA Path Packet Size ZL30301 to CPU only >1000 bytes 50 ZL30301 to CPU only 60 bytes 6.7 CPU to ZL30301 only >1000 bytes 60 CPU to ZL30301 only 60 bytes 43 Combined2 >1000 bytes 58 (29 each way) Combined2 60 bytes 11 (5.5 each way) Table 20 - DMA Maximum Bandwidths Note 1: Maximum bandwidths are the maximum the ZL30301 devices can transfer under host control, and assumes only minimal packet processing by the host. Note 2: Combined figures assume the same amount of data is to be transferred each way. 6.3 Power Up Sequence To power up the ZL30301 the following procedure must be used: • The Core supply must never exceed the I/O supply by more than 0.5 VDC • Both the Core supply and the I/O supply must be brought up together • The System Reset and, if used, the JTAG Reset must remain low until at least 100 µs after the 100 MHz system clock has stabilised. Note that if JTAG Reset is not used it must be tied low This is illustrated in the diagram shown in Figure 16. 40 Zarlink Semiconductor Inc. ZL30301 Data Sheet I/O supply (3.3 V) VDD 100 µs SCLK t 10 ns Figure 16 - Powering Up the ZL30301 6.4 JTAG Interface and Board Level Test Features The JTAG interface is used to access the boundary scan logic for board level production testing. 6.5 External Component Requirements • Direct connection to PowerQUICC™ II (MPC8260) host processor and associated memory, but can support other processors with appropriate glue logic • Ethernet PHY for each MAC port 6.6 Miscellaneous Features • System clock speed of 100 MHz • Host clock speed of up to 66 MHz • Debug option to freeze all internal state machines • JTAG (IEEE1149) Test Access Port • 3.3 V I/O Supply rail with 5 V tolerance • 1.8 V Core Supply rail 41 Zarlink Semiconductor Inc. ZL30301 6.7 Data Sheet Test Modes Operation 6.7.1 Overview The ZL30301 supports the following modes of operation. 6.7.1.1 System Normal Mode This mode is the device's normal operating mode. Boundary scan testing of the peripheral ring is accessible in this mode via the dedicated JTAG pins. The JTAG interface is compliant with the IEEE Std. 1149.1-2001; Test Access Port and Boundary Scan Architecture. Each variant has it's own dedicated.bsdl file which fully describes it's boundary scan architecture. 6.7.1.2 System Tri-State Mode All output and I/O output drivers are tri-stated allowing the device to be isolated when testing or debugging the development board. 6.7.2 Test Mode Control The System Test Mode is selected using the dedicated device input bus TEST_MODE[2:0] as follows in Table 21. System Test Mode test_mode[2:0] SYS_NORMAL_MODE 3’b000 SYS_TRI_STATE_MODE 3’b011 Table 21 - Test Mode Control 6.7.3 System Normal Mode Selected by TEST_MODE[2:0] = 3'b000. As the test_mode[2:0] inputs have internal pull-downs this is the default mode of operation if no external pull-up/downs are connected. The GPIO[15:0] bus is captured on the rising edge of the external reset to provide internal bootstrap options. After the internal reset has been de-asserted the GPIO pins may be configured by the ADM module as either inputs or outputs. 6.7.4 System Tri-state Mode Selected by TEST_MODE[2:0] = 3'b011. All device output and I/O output drivers are tri-stated. 42 Zarlink Semiconductor Inc. ZL30301 7.0 Data Sheet DC Characteristics Absolute Maximum Ratings* Parameter Symbol Min. Max. Units VDD_IO -0.5 5.0 V Core Supply Voltage VDD_CORE -0.5 2.5 V PLL Supply Voltage VDD_PLL -0.5 2.5 V VI -0.5 VDD + 0.5 V Input Voltage (5 V tolerant inputs) VI_5V -0.5 7.0 V Continuous current at digital inputs IIN - ±10 mA Continuous current at digital outputs IO - ±15 mA Package power dissipation PD - 4 W Storage Temperature TS -55 +125 °C I/O Supply Voltage Input Voltage * Exceeding these figures may cause permanent damage. Functional operation under these conditions is not guaranteed. Voltage measurements are with respect to ground (VSS) unless otherwise stated. * The core and PLL supply voltages must never be allowed to exceed the I/O supply voltage by more than 0.5 V during power-up. Failure to observe this rule could lead to a high-current latch-up state, possibly leading to chip failure, if sufficient cross-supply current is available. To be safe ensure the I/O supply voltage supply always rises earlier than the core and PLL supply voltages. Recommended Operating Conditions Characteristics Symbol Min. Typ. Max. Units TOP -40 25 +85 °C TJ -40 - 125 °C VDD_IO 3.0 3.3 3.6 V Positive Supply Voltage, Core VDD_CORE 1.65 1.8 1.95 V Positive Supply Voltage, Core VDD_PLL 1.65 1.8 1.95 V Input Voltage Low - all inputs VIL - - 0.8 V Input Voltage High VIH 2.0 - VDD_IO V VIH_5V 2.0 - 5.5 V Operating Temperature Junction temperature Positive Supply Voltage, I/O Input Voltage High, 5 V tolerant inputs Test Condition Typical figures are at 25°C and are for design aid only, they are not guaranteed and not subject to production testing. Voltage measurements are with respect to ground (VSS) unless otherwise stated. 43 Zarlink Semiconductor Inc. ZL30301 Data Sheet DC Electrical Characteristics- Typical characteristics are at 1.8 V core, 3.3 V I/O, 25°C and typical processing. The min. and max. values are defined over all process conditions, from -40 to 125°C junction temperature, core voltage 1.65 to 1.95 V and I/O voltage 3.0 and 3.6 V unless otherwise stated. Characteristics Symbol Min. Typ. Max. Units. Test Condition Input Leakage ILEIP ±1 µA No pull up/down VDD_IO = 3.6 V Output (High impedance) Leakage ILEOP 2 µA No pull up/down VDD_IO = 3.6 V Input Capacitance CIP 1 pF Output Capacitance COP 4 pF Pullup Current IPU -27 µA Input at 0 V IPU_5V -110 µA Input at 0 V IPD 27 µA Input at VDD_IO IPD_5V 110 µA Input at VDD_IO Core 1.8 V supply current IDD_CORE 720 950 mA Note 1,2 PLL 1.8 V supply current IDD_PLL 1.30 mA I/O 3.3 V supply current IDD_IO 120 mA Note 1,2 Max. Units 0.8 V Pullup Current, 5 V tolerant inputs Pulldown Current Pulldown Current, 5 V tolerant inputs 32 Note 1: Worst case assumes the maximum number of active connections. Note 2: Typical assumes four active E1 connections, and two 100 Mbps MII ports. Input Levels Characteristics Symbol Min. Typ. Input Low Voltage VIL Input High Voltage VIH Positive Schmitt Threshold VT+ 1.6 V Negative Schmitt Threshold VT- 1.2 V 2.0 Test Condition V Output Levels Characteristics Symbol Output Low Voltage VOL Output High Voltage VOH Min. Typ. Max. Units Test Condition 0.4 V IOL = 6 mA IOL = 12 mA for packet interface (m*) pins and GPIO pins IOL = 24 mA for LED pins V IOH = 6 mA IOH = 12 mA for packet interface (m*) pins and GPIO pins IOH = 24 mA for LED pins 2.4 44 Zarlink Semiconductor Inc. ZL30301 8.0 AC Characteristics 8.1 Clock Interface Timing Data Sheet The clock signals can generate a wide range of clock frequencies including standard Telecom frequencies for E1, DS1, J2, E3 and DS3. Table 22 shows timing for DS3, which would be the most stringent requirement. Parameter Symbol Min. Typ. Max. Units 22.353 ns CLKo Period tCTP CLKo High tCTH 6.7 ns CLKo Low tCTL 6.7 ns CLKi Period tCRP CLKi High tCRH 9.0 ns CLKi Low tCRL 9.0 ns 22.353 ns Table 22 - Clock Interface Timing tCTP tCTH tCTL CLKo tCRH tCRP CLKi Figure 17 - Clock Interface Timing 45 Zarlink Semiconductor Inc. tCRL Notes DS3 clock DS3 clock ZL30301 8.2 Data Sheet Timestamp Reference Timing Parameter TS_CLKi High / Low Pulsewidth Symbol Min. Typ. Max. Units tCPP 10 - - ns Notes Table 23 - Timestamp Reference Timing Specification 8.3 Packet Interface Timing Data for the MII/GMII/TBI packet switching is based on Specification IEEE Std. 802.3 - 2000. 8.3.1 MII Transmit Timing 100 Mbps Parameter Symbol Units Min. Typ. Max. Notes TXCLK period tCC - 40 - ns TXCLK high time tCHI 14 - 26 ns TXCLK low time tCLO 14 - 26 ns TXCLK rise time tCR - - 5 ns TXCLK fall time tCF - - 5 ns TXCLK rise to TXD[3:0] active delay (TXCLK rising edge) tDV 1 - 25 ns Load = 25 pF TXCLK to TXEN active delay (TXCLK rising edge) tEV 1 - 25 ns Load = 25 pF TXCLK to TXER active delay (TXCLK rising edge) tER 1 - 25 ns Load = 25 pF Table 24 - MII Transmit Timing - 100 Mbps tCL tCC tCH TXCLK tEV tEV TXEN tDV TXD[3:0] tER tER TXER Figure 18 - MII Transmit Timing Diagram 46 Zarlink Semiconductor Inc. ZL30301 8.3.2 Data Sheet MII Receive Timing 100 Mbps Parameter Symbol Units Min. Typ. Max. RXCLK period tCC - 40 - ns RXCLK high wide time tCH 14 20 26 ns RXCLK low wide time tCL 14 20 26 ns RXCLK rise time tCR - - 5 ns RXCLK fall time tCF - - 5 ns RXD[3:0] setup time (RXCLK rising edge) tDS 10 - - ns RXD[3:0] hold time (RXCLK rising edge) tDH 5 - - ns RXDV input setup time (RXCLK rising edge) tDVS 10 - - ns RXDV input hold time (RXCLK rising edge) tDVH 5 - - ns RXER input setup time (RXCL edge) tERS 10 - - ns RXER input hold time (RXCLK rising edge) tERH 5 - - ns Table 25 - MII Receive Timing - 100 Mbps tCC tCLO tCHI RXCLK tDVS tDVH RXDV tDH tDS RXD[3:0] tERH tERS RXER Figure 19 - MII Receive Timing Diagram 47 Zarlink Semiconductor Inc. Notes ZL30301 8.3.3 Data Sheet GMII Transmit Timing 1000 Mbps Parameter Symbol Units Min. Typ. Max. Notes GTXCLK period tGC 7.5 - 8.5 ns GTXCLK high time tGCH 2.5 - - ns GTXCLK low time tGCL 2.5 - - ns GTXCLK rise time tGCR - - 1 ns GTXCLK fall time tGCF - - 1 ns GTXCLK rise to TXD[7:0] active delay tDV 1.5 - 6 ns Load = 25 pF GTXCLK rise to TXEN active delay tEV 2 - 6 ns Load = 25 pF GTXCLK rise to TXER active delay tER 1 - 6 ns Load = 25 pF Table 26 - GMII Transmit Timing - 1000 Mbps tCC tCL tCH GTXCLK tEV tEV TXEN tDV TXD[3:0] tER tER TXER Figure 20 - GMII Transmit Timing Diagram 48 Zarlink Semiconductor Inc. ZL30301 8.3.4 Data Sheet GMII Receive Timing 1000 Mbps Parameter Symbol Units Min. Typ. Max. RXCLK period tCC 7.5 - 8.5 ns RXCLK high wide time tCH 2.5 - - ns RXCLK low wide time tCL 2.5 - - ns RXCLK rise time tCR - - 1 ns RXCLK fall time tCF - - 1 ns RXD[7:0] setup time (RXCLK rising edge) tDS 2 - - ns RXD[7:0] hold time (RXCLK rising edge) tDH 1 - - ns RXDV setup time (RXCLK rising edge) tDVS 2 - - ns RXDV hold time (RXCLK rising edge) tDVH 1 - - ns RXER setup time (RXCLK rising edge) tERS 2 - - ns RXER hold time (RXCLK rising edge) tERH 1 - - ns Table 27 - GMII Receive Timing - 1000 Mbps tCC tCLO tCHI RXCLK tDVS tDVH RXDV tDH tDS RXD[7:0] tERH tERS RXER Figure 21 - GMII Receive Timing Diagram 49 Zarlink Semiconductor Inc. Notes ZL30301 8.3.5 Data Sheet TBI Interface Timing 1000 Mbps Parameter Symbol Units Min. Typ. Max. GTXCLK period tGC 7.5 - 8.5 ns GTXCLK high wide time tGH 2.5 - - ns GTXCLK low wide time tGL 2.5 - - ns TXD[9:0] Output Delay (GTXCLK rising edge) tDV 1 - 6 RCB0/RBC1 period tRC 15 16 17 ns RCB0/RBC1 high wide time tRH 5 - - ns RCB0/RBC1 low wide time tRL 5 - - ns RCB0/RBC1 rise time tRR - - 2 ns RCB0/RBC1 fall time tRF - - 2 ns RXD[9:0] setup time (RCB0 rising edge) tDS 2 - - ns RXD[9:0] hold time (RCB0 rising edge) tDH 1 - - ns REFCLK period tFC 7.5 - 8.5 ns REFCLK high wide time tFH 2.5 - - ns REFCLK low wide time tFL 2.5 - - ns Notes Load = 25 pF Table 28 - TBI Timing - 1000 Mbps tGC GTXCLK TXD[9:0] /I/ tDV /S/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /D/ /T/ /R/ /I/ Signal_Detect Figure 22 - TBI Transmit Timing Diagram tRC RBC1 tRC RBC0 tDH RXD[9:0] /I/ /S/ /D/ /D/ /D/ tDS /D/ /D/ /D/ /D/ tDH /D/ tDS /D/ /D/ /D/ Signal_Detect Figure 23 - TBI Receive Timing Diagram 50 Zarlink Semiconductor Inc. /D/ /T/ /R/ /I/ ZL30301 8.3.6 Data Sheet Management Interface Timing The management interface is common for all inputs and consists of a serial data I/O line and a clock line. Parameter M_MDC Clock Output period Symbol Min. Typ. Max. Units Notes tMP 1990 2000 2010 ns Note 1 M_MDC high tMHI 900 1000 1100 ns M_MDC low tMLO 900 1000 1100 ns M_MDC rise time tMR - - 5 ns M_MDC fall time tMF - - 5 ns M_MDIO setup time (MDC rising edge) tMS 10 - - ns Note 1 M_MDIO hold time (M_MDC rising edge) tMH 10 - - ns Note 1 M_MDIO Output Delay (M_MDC rising edge) tMD 1 - 300 ns Note 2 Table 29 - MAC Management Timing Specification Note 1: Refer to Clause 22 in IEEE802.3 (2000) Standard for input/output signal timing characteristics. Note 2: Refer to Clause 22C.4 in IEEE802.3 (2000) Standard for output load description of MDIO. tMHI tMLO M_MDC tMS tMH M_MDIO Figure 24 - Management Interface Timing for Ethernet Port - Read tMP M_MDC tMD M_MDIO Figure 25 - Management Interface Timing for Ethernet Port - Write 51 Zarlink Semiconductor Inc. ZL30301 8.4 Data Sheet CPU Interface Timing Parameter Symbol Min. Typ. Max. 15.152 Units Notes ns CPU_CLK Period tCC CPU_CLK High Time tCCH 6 ns CPU_CLK Low Time tCCL 6 ns CPU_CLK Rise Time tCCR 4 ns CPU_CLK Fall Time tCCF 4 ns CPU_ADDR[23:2] Setup Time tCAS 4 ns CPU_ADDR[23:2] Hold Time tCAH 2 ns CPU_DATA[31:0] Setup Time tCDS 4 ns CPU_DATA[31:0] Hold Time tCDH 2 ns CPU_CS Setup Time tCSS 4 ns CPU_CS Hold Time tCSH 2 ns CPU_WE/CPU_OE Setup Time tCES 5 ns CPU_WE/CPU_OE Hold Time tCEH 2 ns CPU_TS_ALE Setup Time tCTS 4 ns CPU_TS_ALE Hold Time tCTH 2 ns CPU_SDACK1/CPU_SDACK2 Setup Time tCKS 2 ns CPU_SDACK1/CPU_SDACK2 Hold Time tCKH 2 ns Note 1 CPU_TA Output Valid Delay tCTV 2 11.3 ns Note 1, 2 CPU_DREQ0/CPU_DREQ1 Output Valid Delay tCWV 2 6 ns Note 1 CPU_IREQ0/CPU_IREQ1 Output Valid Delay tCRV 2 6 ns Note 1 CPU_DATA[31:0] Output Valid Delay tCDV 2 7 ns Note 1 CPU_CS to Output Data Valid tSDV 3.2 10.4 ns CPU_OE to Output Data Valid tODV 3.3 10.4 ns CPU_CLK(falling) to CPU_TA Valid tOTV 3.2 9.5 ns Table 30 - CPU Timing Specification Note 1: Note 2: Load = 50 pF maximum The maximum value of tCTV may cause setup violations if directly connected to the MPC8260. See Section 9.2 for details of how to accommodate this during board design. 52 Zarlink Semiconductor Inc. ZL30301 Data Sheet The actual point where read/write data is transferred occurs at the positive clock edge following the assertion of CPU_TA, not at the positive clock edge during the assertion of CPU_TA. tCC 0 or more cycles CPU_CLK tCAH tCAS CPU_ADDR[23:2] tCSS tCSH CPU_CS tCES tCEH CPU_OE CPU_WE tCTS tCTH CPU_TS_ALE tODV tSDV tODV tSDV tCDV CPU_DATA[31:0] tOTV tCTV tCTV tOTV CPU_TA NOTE: CPU_DATA is valid when CPU_TA is asserted. CPU_DATA will remain valid while both CPU_CS and CPU_OE are asserted. CPU_TA will continue to be driven until CPU_CS is deasserted. CPU_CS and CPU_OE must BOTH be asserted to enable the CPU_DATA output. Figure 26 - CPU Read - MPC8260 tCC 0 or more cycles 0 or more cycles CPU_CLK tCAS tCAH CPU_ADDR[23:2] tCSS tCSH CPU_CS CPU_OE tCES tCEH CPU_WE tCTH tCTS CPU_TS_ALE tCDS tCDH CPU_DATA[31:0] tOTV tCTV tCTV tOTV CPU_TA NOTE: Following assertion of CPU_TA, CPU_CS may be deasserted. The MPC8260 will continue to assert CPU_CS until CPU_TA has been synchronized internally. CPU_TA will continue to be driven until CPU_CS is finally deasserted. During continued assertion of CPU_CS, CPU_WE and CPU_DATA may be removed. Figure 27 - CPU Write - MPC8260 53 Zarlink Semiconductor Inc. ZL30301 Data Sheet tCC 0 or more cycles CPU_CLK tCWV tCWV CPU_DREQ1 tCKH tCKS CPU_SDACK2 tCSS tCSH CPU_CS tCES tCEH CPU_OE CPU_WE tCTH tCTS CPU_TS_ALE tODV tSDV tODV tSDV tCDV CPU_DATA[31:0] tCTV tOTV tCTV tOTV CPU_TA NOTE: CPU_SDACK2 must be asserted during the cycle shown. It may then be deasserted at any time. CPU_DATA is valid when CPU_TA is asserted (always timed as shown). CPU_DATA will remain valid while CPU_CS and CPU_OE are asserted. CPU_TA will continue to be driven until CPU_CS is deasserted. CPU_CS and CPU_OE must BOTH be asserted to enable the CPU_DATA output. Figure 28 - CPU DMA Read - MPC8260 tCC 0 or more cycles CPU_CLK tCWV tCWV CPU_DREQ0 tCKH tCKS CPU_SDACK1 tCSS tCSH CPU_CS CPU_OE tCES tCEH CPU_WE tCTH tCTS CPU_TS_ALE tCDS tCDH CPU_DATA[31:0] tOTV tCTV tCTV CPU_TA NOTE: CPU_SDACK1 must be asserted during the cycle shown. It may then be deasserted at any time. Following assertion of CPU_TA (always timed as shown), CPU_CS may be deasserted. The MPC8260 will continue to assert CPU_CS until CPU_TA has been synchronized internally. CPU_TA will continue to be driven until CPU_CS is finally deasserted. During continued assertion of CPU_CS, CPU_WE and CPU_DATA may be removed. Figure 29 - CPU DMA Write - MPC8260 54 Zarlink Semiconductor Inc. tOTV ZL30301 8.5 Data Sheet System Function Port Parameter Symbol Min. Typ. Max. Units Notes SYSTEM_CLK Frequency CLKFR - 100 - MHz Note 1, Note 2 and Note 3 SYSTEM_CLK accuracy ( CLKACA - - ±200 ppm Note 4 Table 31 - System Clock Timing Note 1: The system clock frequency stability affects the holdover-operating mode. Holdover Mode is typically used for a short duration while network synchronisation is temporarily disrupted. Drift on the system clock directly affects the Holdover Mode accuracy. Note that the absolute system clock accuracy does not affect the Holdover accuracy, only the change in the system clock (SYSTEM_CLK) accuracy while in Holdover. For example, if the system clock oscillator has a temperature coefficient of 0.1 ppm/ºC, a 10ºC change in temperature while the DCO is in holdover will result in a frequency accuracy offset of 1 ppm. Note 2: The system clock frequency affects the operation of the DCO in free-run mode. In this mode, the DCO provides timing and synchronisation signals which are based on the frequency of the accuracy of the master clock (i.e., frequency of clock output equals 8.192 MHz ± SYSTEM_CLK accuracy ± 0.005 ppm). Note 3: The absolute SYSTEM_CLK accuracy must be controlled to ± 30 ppm in to enable the internal DCO to meet T1/E1 specification. Note 4: Maximum system clock accuracy for the proper operation of the device. 55 Zarlink Semiconductor Inc. ZL30301 8.6 Data Sheet JTAG Interface Timing Parameter Symbol Min. Typ. JTAG_CLK period tJCP 40 100 JTAG_CLK clock pulse width tLOW, tHIGH 20 - - ns JTAG_CLK rise and fall time tJRF 0 - 3 ns JTAG_TRST setup time tRSTSU 10 - - ns JTAG_TRST assert time tRST 10 - - ns Input data setup time tJSU 5 - - ns Note 2 Input Data hold time tJH 15 - - ns Note 2 JTAG_CLK to Output data valid tJDV 0 - 20 ns Note 3 JTAG_CLK to Output data high impedance tJZ 0 - 20 ns Note 3 JTAG_TMS, JTAG_TDI setup time tTPSU 5 - - ns JTAG_TMS, JTAG_TDI hold time tTPH 15 - - ns tTOPDV 0 - 15 ns tTPZ 0 - 15 ns JTAG_TDO delay JTAG_TDO delay to high impedance Max. Units ns Table 32 - JTAG Interface Timing Note 1: JTAG_TRST is an asynchronous signal. The setup time is for test purposes only. Note 2: Non Test (other than JTAG_TDI and JTAG_TMS) signal input timing with respect to JTAG_CLK. Note 3: Non Test (other than JTAG_TDO) signal output with respect to JTAG_CLK. 56 Zarlink Semiconductor Inc. Notes With respect to JTAG_CLK falling edge. Note 1 ZL30301 Data Sheet tLOW tHIGH tJCP JTAG_TCK tTPH tTPSU JTAG_TMS tTPSU JTAG_TDI tTPH Don't Care DC tTPZ tTOPDV JTAG_TDO HiZ HiZ Figure 30 - JTAG Signal Timing tLOW tHIGH JTAG_TCK tRST tRSTSU JTAG_TRST Figure 31 - JTAG Clock and Reset Timing 57 Zarlink Semiconductor Inc. ZL30301 9.0 Data Sheet Design and Layout Guidelines This guide will provide information and guidance for PCB layouts when using the ZL30301. Specific areas of guidance are: • High Speed Clock and Data, Outputs and Inputs • CPU_TA Output 9.1 High Speed Clock & Data Interfaces On the ZL30301 series of devices there are four high-speed data interfaces that need consideration when laying out a PCB to ensure correct termination of traces and the reduction of crosstalk noise. The interfaces being: • GMAC Interfaces • Clock Interface • CPU Interface It is recommended that the outputs are suitably terminated using a series termination through a resistor as close to the output pin as possible. The purpose of the series termination resistor is to reduce reflections on the line. The value of the series termination and the length of trace the output can drive will depend on the driver output impedance, the characteristic impedance of the PCB trace (recommend 50 ohm), the distributed trace capacitance and the load capacitance. As a general rule of thumb, if the trace length is less than 1/6th of the equivalent length of the rise and fall times, then a series termination may not be required. the equivalent length of rise time = rise time (ps) / delay (ps/mm) For example: Typical FR4 board delay = 6.8 ps/mm Typical rise/fall time for a ZL30301 output = 2.5 ns critical track length = (1/6) x (2500/6.8) = 61 mm Therefore tracks longer than 61 mm will require termination. As a signal travels along a trace it creates a magnetic field, which induces noise voltages in adjacent traces, this is crosstalk. If the crosstalk is of sufficiently strong amplitude, false data can be induced in the trace and therefore it should be minimized in the layout. The voltage that the external fields cause is proportional to the strength of the field and the length of the trace exposed to the field. Therefore to minimize the effect of crosstalk some basic guidelines should be followed. First, increase separation of sensitive signals, a rough rule of thumb is that doubling the separation reduces the coupling by a factor of four. Alternatively, shield the victim traces from the aggressor by either routing on another layer separated by a power plane (in a correctly decoupled design the power planes have the same AC potential) or by placing guard traces between the signals usually held ground potential. 9.1.1 GMAC Interface - Special Considerations During Layout The GMII interface passes data to and from the ZL30301 with their related transmit and receive clocks. It is therefore recommended that the trace lengths for transmit related signals and their clock and the receive related signals and their clock are kept to the same length. By doing this the skew between individual signals and their related clock will be minimized. 58 Zarlink Semiconductor Inc. ZL30301 9.1.2 Data Sheet Clock Interface - Special Considerations during Layout Although the clock rates at the clock interface are typically low (1.544 MHz to 10 MHz) the outputs’ edge speeds share the characteristics of the higher data rate outputs. Therefore they should be treated with the same care extended to the other interfaces. In particular, the input clock traces to the ZL30301 devices should be treated with care. 9.1.3 Summary Particular effort should be made to minimize crosstalk from ZL30301 outputs and ensuring fast rise time to these inputs. In summary: • Place series termination resistors as close to the pins as possible • Minimize output capacitance • Keep common interface traces close to the same length to avoid skew • Protect input clocks and signals from crosstalk 59 Zarlink Semiconductor Inc. ZL30301 9.2 Data Sheet CPU TA Output The CPU_TA output signal from the ZL30301 is a critical handshake signal to the CPU that ensures the correct completion of a bus transaction between the two devices. As the signal is critical, it is recommend that the circuit shown in Figure 32 is implemented in systems operating above 40 MHz bus frequency to ensure robust operation under all conditions. The following external logic is required to implement the circuit: • 74LCX74 dual D-type flip-flop (one section of two) • 74LCX08 quad AND gate (one section of four) • 74LCX125 quad tri-state buffer (one section of four) • 4K7 resistor x2 +3V3 +3V3 R2 4K7 R1 4K7 CPU_TA from ZL30300ZL30300 CPU_TA to CPU D CPU_CLK to ZL30300 Q CPU_CS to ZL30300 Figure 32 - CPU_TA Board Circuit The function of the circuit is to extend the TA signal, to ensure the CPU correctly registers it. Resistor R2 must be fitted to ensure correct operation of the TA input to the processor. It is recommended that the logic is fitted close to the ZL30301 and that the clock to the 74LCX74 is derived from the same clock source as that input to the ZL30301. 60 Zarlink Semiconductor Inc. ZL30301 10.0 Reference Documents 10.1 External Standards/Specifications Data Sheet • IEEE Standard 1149.1-2001; Test Access Port and Boundary Scan Architecture • IEEE Standard 802.3-2000; Local and Metropolitan Networks CSMA/CD Access Method and Physical Layer • MPC8260AEC/D Revision 0.7; Motorola MPC8260 Family Hardware Specification • RFC 768; UDP • RFC 791; IPv4 • RFC2460; IPv6 • RFC 2661; L2TP • RFC 3550; RTP • RFC 1213; MIB II • RFC 1757; Remote Network Monitoring MIB (for SMIv1) • RFC 2819; Remote Network Monitoring MIB (for SMIv2) • RFC 2863; Interfaces Group MIB • G.712; TDM Timing Specification (Method 2) • G.823; Control of Jitter/Wander with digital networks based on the 2.048 Mbps hierarchy • G.824; Control of Jitter/Wander with digital networks based on the 1.544 Mbps hierarchy • ANSI T1.101 Stratum 3/4 • Telcordia GR-1244-CORE Stratum 3/4/4e • RFC 3931; L2TP Version 3 • IETF PWE3 draft-ietf-pwe3-cesopsn • IETF PWE3 draft-ietf-pwe3-satop • IETF PWE3 draft-ietf-pwe3-tdmoip • ITU-T Y.1413; TDM-MPLS Network Interworking • MEF 8; Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks • MFA 8.0.0; Emulation of TDM Circuits over MPLS Using Raw Encapsulation Implementation Agreement 61 Zarlink Semiconductor Inc. ZL30301 11.0 Data Sheet Glossary API Application Program Interface CESoP Circuit Emulation Services over Packet CESoPSN Circuit Emulation Services over Packet Switched Networks CPU Central Processing Unit DCO Digital Controlled Oscillator DMA Direct Memory Access GMII Gigabit Media Independent Interface IETF Internet Engineering Task Force IP Internet Protocol (version 4, RFC 791, version 6, RFC 2460) JTAG Joint Test Algorithms Group (refers to a boundary-scan architecture providing a board-level test facility - see IEEE1149) L2TP Layer 2 Tunneling Protocol (RFC 2661 and RFC 3931) LAN Local Area Network MAC Media Access Control MEF Metro Ethernet Forum MFA MPLS and Frame Relay Alliance MII Media Independent Interface MIB Management Information Base MPLS Multi Protocol Label Switching PDH Plesiochronous Digital Hierarchy PLL Phase Locked Loop PRS Primary Reference Source PWE3 Pseudo-Wire Emulation Edge to Edge (a working group of the IETF) RTP Real Time Protocol (RFC 3550) SAToP Structure-Agnostic TDM over Packet TDM Time Division Multiplexing UDP User Datagram Protocol (RFC 768) VLAN Virtual Local Area Network 62 Zarlink Semiconductor Inc. Package Code c Zarlink Semiconductor 2003 All rights reserved. ISSUE 1 ACN DATE APPRD. 02 June 04 Previous package codes For more information about all Zarlink products visit our Web Site at www.zarlink.com Information relating to products and services furnished herein by Zarlink Semiconductor Inc. or its subsidiaries (collectively “Zarlink”) is believed to be reliable. However, Zarlink assumes no liability for errors that may appear in this publication, or for liability otherwise arising from the application or use of any such information, product or service or for any infringement of patents or other intellectual property rights owned by third parties which may result from such application or use. Neither the supply of such information or purchase of product or service conveys any license, either express or implied, under patents or other intellectual property rights owned by Zarlink or licensed from third parties by Zarlink, whatsoever. Purchasers of products are also hereby notified that the use of product in certain ways or in combination with Zarlink, or non-Zarlink furnished goods or services may infringe patents or other intellectual property rights owned by Zarlink. This publication is issued to provide information only and (unless agreed by Zarlink in writing) may not be used, applied or reproduced for any purpose nor form part of any order or contract nor to be regarded as a representation relating to the products or services concerned. The products, their specifications, services and other information appearing in this publication are subject to change by Zarlink without notice. No warranty or guarantee express or implied is made regarding the capability, performance or suitability of any product or service. Information concerning possible methods of use is provided as a guide only and does not constitute any guarantee that such methods of use will be satisfactory in a specific piece of equipment. It is the user’s responsibility to fully determine the performance and suitability of any equipment using such information and to ensure that any publication or data used is up to date and has not been superseded. Manufacturing does not necessarily include testing of all functions or parameters. These products are not suitable for use in any medical products whose failure to perform may result in significant injury or death to the user. All products and materials are sold and services provided subject to Zarlink’s conditions of sale which are available on request. Purchase of Zarlink’s I2C components conveys a licence under the Philips I2C Patent rights to use these components in and I2C System, provided that the system conforms to the I2C Standard Specification as defined by Philips. Zarlink, ZL and the Zarlink Semiconductor logo are trademarks of Zarlink Semiconductor Inc. Copyright Zarlink Semiconductor Inc. All Rights Reserved. TECHNICAL DOCUMENTATION - NOT FOR RESALE For more information about all Zarlink products visit our Web Site at www.zarlink.com Information relating to products and services furnished herein by Zarlink Semiconductor Inc. or its subsidiaries (collectively “Zarlink”) is believed to be reliable. However, Zarlink assumes no liability for errors that may appear in this publication, or for liability otherwise arising from the application or use of any such information, product or service or for any infringement of patents or other intellectual property rights owned by third parties which may result from such application or use. Neither the supply of such information or purchase of product or service conveys any license, either express or implied, under patents or other intellectual property rights owned by Zarlink or licensed from third parties by Zarlink, whatsoever. Purchasers of products are also hereby notified that the use of product in certain ways or in combination with Zarlink, or non-Zarlink furnished goods or services may infringe patents or other intellectual property rights owned by Zarlink. This publication is issued to provide information only and (unless agreed by Zarlink in writing) may not be used, applied or reproduced for any purpose nor form part of any order or contract nor to be regarded as a representation relating to the products or services concerned. The products, their specifications, services and other information appearing in this publication are subject to change by Zarlink without notice. No warranty or guarantee express or implied is made regarding the capability, performance or suitability of any product or service. Information concerning possible methods of use is provided as a guide only and does not constitute any guarantee that such methods of use will be satisfactory in a specific piece of equipment. It is the user’s responsibility to fully determine the performance and suitability of any equipment using such information and to ensure that any publication or data used is up to date and has not been superseded. Manufacturing does not necessarily include testing of all functions or parameters. These products are not suitable for use in any medical products whose failure to perform may result in significant injury or death to the user. All products and materials are sold and services provided subject to Zarlink’s conditions of sale which are available on request. Purchase of Zarlink’s I2C components conveys a licence under the Philips I2C Patent rights to use these components in and I2C System, provided that the system conforms to the I2C Standard Specification as defined by Philips. Zarlink, ZL and the Zarlink Semiconductor logo are trademarks of Zarlink Semiconductor Inc. Copyright Zarlink Semiconductor Inc. All Rights Reserved. TECHNICAL DOCUMENTATION - NOT FOR RESALE