CPRI IP Core
User Guide
FPGA-IPUG-02029 Version 2.8
July 2017
CPRI IP Core
User Guide
Contents
1.
Introduction .................................................................................................................................................................. 4
1.1.
Quick Facts .......................................................................................................................................................... 5
1.2.
Features ............................................................................................................................................................... 6
2. Functional Description .................................................................................................................................................. 8
2.1.
Block Diagram...................................................................................................................................................... 8
2.2.
General Description............................................................................................................................................. 9
2.3.
Functional Overview.......................................................................................................................................... 12
2.4.
Signal Descriptions ............................................................................................................................................ 13
2.5.
Timing Specifications ......................................................................................................................................... 16
2.6.
CPRI Overview ................................................................................................................................................... 16
2.7.
Interfaces........................................................................................................................................................... 19
2.7.1. User Plane IQ Data Interface ........................................................................................................................19
2.7.2. Ethernet Interface ........................................................................................................................................21
2.7.3. HDLC Interface ..............................................................................................................................................23
2.7.4. L1 Inband Protocol Interface ........................................................................................................................24
2.7.5. Vendor Specific Information .........................................................................................................................24
2.7.6. Start-up Sequence ........................................................................................................................................25
3. Parameter Settings ..................................................................................................................................................... 26
3.1.
CPRI Configuration Dialog Box .......................................................................................................................... 26
3.1.1. Generation Options ......................................................................................................................................28
3.1.2. Eval Configuration ........................................................................................................................................28
3.2.
Programmable Parameters ............................................................................................................................... 28
4. IP Core Generation ..................................................................................................................................................... 29
4.1.
Licensing the IP Core ......................................................................................................................................... 29
4.2.
Getting Started .................................................................................................................................................. 29
4.3.
IPexpress-Created Files and Top Level Directory Structure .............................................................................. 32
4.4.
Instantiating the Core........................................................................................................................................ 35
4.5.
Running Functional Simulation ......................................................................................................................... 36
4.5.1. Using Aldec Active-HDL ................................................................................................................................36
4.5.2. Using Mentor Graphics ModelSim ...............................................................................................................36
4.6.
Synthesizing and Implementing the Core in a Top-Level Design ...................................................................... 37
4.7.
Hardware Evaluation ......................................................................................................................................... 37
4.7.1. Enabling Hardware Evaluation in Diamond ..................................................................................................37
4.8.
Updating/Regenerating the IP Core .................................................................................................................. 38
4.8.1. Regenerating an IP Core in IPexpress Tool ...................................................................................................38
4.8.2. Regenerating an IP Core in Clarity Designer Tool .........................................................................................38
5. Application Support .................................................................................................................................................... 40
5.1.
CPRI IP Top-Level Reference Design .................................................................................................................. 40
5.1.1. Test Bench ....................................................................................................................................................40
5.1.2. Register Descriptions ....................................................................................................................................41
References .......................................................................................................................................................................... 46
Technical Support Assistance ............................................................................................................................................. 46
Appendix A. Resource Utilization ....................................................................................................................................... 47
LatticeECP3-FPGAs ........................................................................................................................................................ 47
ECP5 FPGAs (for 3G Version) .......................................................................................................................................... 47
ECP5 FPGAs (for 5G Version) .......................................................................................................................................... 47
Revision History .................................................................................................................................................................. 48
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
2
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Figures
Figure 2.1. CPRI IP Logic Core Block Diagram ....................................................................................................................... 8
Figure 2.2. CPRI IP Core System Block Diagram in LatticeECP3 ............................................................................................ 9
Figure 2.3. CPRI IP Core System Block Diagram in ECP5 LFE5UM ....................................................................................... 10
Figure 2.4. Top-Level Template Included with CPRI IP Core ............................................................................................... 11
Figure 2.5. CPRI Protocol Overview .................................................................................................................................... 17
Figure 2.6. CPRI Frame (Shown for 614.4 Mbps, 1228.8 Mbps, 2457.6 Mbps, and 3072 Mbps Line Rates) ...................... 17
Figure 2.7. CPRI Frame (Shown for 614.4 Mbps, 1228.8 Mbps, 2457.6 Mbps, and 3072 Mbps Line Rates) ...................... 18
Figure 2.8. Tx User IQ Interface Sync Pulse Alignment ....................................................................................................... 19
Figure 2.9. Rx IQ Interface Data and Frame Number Alignment ........................................................................................ 20
Figure 2.10. Ethernet C&M Interface ................................................................................................................................. 21
Figure 2.11. Matched Rate MII CPRI Ethernet Interface .................................................................................................... 22
Figure 2.12. 100 Mbps Fixed Rate MII CPRI Ethernet Interface ......................................................................................... 23
Figure 2.13. HDLC C&M Interface ....................................................................................................................................... 23
Figure 2.14. Timing for Vendor-Specific Information Interface .......................................................................................... 25
Figure 3.1. CPRI Configuration Dialog Box .......................................................................................................................... 26
Figure 3.2. CPRI PCS Configuration Dialog Box ................................................................................................................... 26
Figure 3.3. CPRI PCS Advanced Configuration Dialog Box .................................................................................................. 27
Figure 4.1. IPexpress Dialog Box ......................................................................................................................................... 29
Figure 4.2. Clarity Designer Dialog Box ............................................................................................................................... 30
Figure 4.3. Configuration GUI ............................................................................................................................................. 30
Figure 4.4. PCS User Interface ............................................................................................................................................ 31
Figure 4.5. LatticeECP3 CPRI IP Core Directory Structure ................................................................................................... 32
Figure 4.6. LFE5UM CPRIIP Core Directory Structure ......................................................................................................... 32
Figure 4.7. Clarity Designer Builder Window ...................................................................................................................... 38
Figure 4.8. Clarity Designer Catalog Window ..................................................................................................................... 39
Figure 5.1. Pattern Generators and Checkers Included with Delivered IP Core Testbench (One Direction Shown) .......... 41
Tables
Table 1.1. CPRI IP Core Quick Facts (3G Version) ................................................................................................................. 5
Table 1.2. CPRI IP Core Quick Facts (5G Version) ................................................................................................................. 5
Table 2.1. CPRI I/O Signal Descriptions ............................................................................................................................... 13
Table 2.2. CPRI Line Rates ................................................................................................................................................... 18
Table 2.3. HDLC Frequencies Supported ............................................................................................................................ 24
Table 3.1. IP Core Parameters ............................................................................................................................................ 26
Table 3.2. CPRI Parameters Controlled via Input Signals to the IP Core ............................................................................. 28
Table 4.1. File List ............................................................................................................................................................... 33
Table 5.1. Supported Devices for Reference Design ........................................................................................................... 40
Table 5.2. CPRI Testbench Register Map ............................................................................................................................ 41
Table A.1. Resource Utilization ........................................................................................................................................... 47
Table A.2. Resource Utilization ........................................................................................................................................... 47
Table A.3. Resource Utilization ........................................................................................................................................... 47
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
3
CPRI IP Core
User Guide
1. Introduction
This document provides technical information about the Lattice Semiconductor Common Public Radio Interface (CPRI)
IP core. This IP core together with SERDES and Physical Coding Sublayer (PCS) functionality integrated in the
LatticeECP3™ and ECP5™ LFE5UM FPGAs implements the physical layer of the CPRI specification and interleaves IQ
data with synchronization, control and management information. It can be used to connect Radio Equipment Control
(REC) and Radio Equipment (RE) modules.
The CPRI IP core implements all of the capabilities required to support the physical layer of the CPRI specification (basic
function), and also implements specific requirements related to link delay accuracy (low latency character). One CPRI
core configuration for 5G version (4.9152 Gbps) is also supported. This core configuration for 5G version is similar to
the "low latency" one for 3G version except the data rate. This document focuses on the detailed specifications
associated with implementing and using the basic function. The LatticeECP3 and ECP5 LFE5UM FPGAs optimize
PCS/SERDES architecture for low latency control. Complete details on the implementation and use of the low latency
configuration are included in CPRI IP Core Low Latency Variation Design Considerations User’s Guide (IPUG74).
The CPRI soft-core comes with the following documentation and files:
Data sheet
Protected netlist/database
Behavioral RTL simulation model
Source files for instantiating and evaluating the core
The CPRI IP core supports Lattice’s IP hardware evaluation capability, which makes it possible to create versions of the
IP core that operate in hardware for a limited period of time (approximately four hours) without requiring the purchase
of an IP license. It may also be used to evaluate the core in hardware in user-defined designs. The Hardware Evaluation
section of this document details the hardware evaluation capability.
In this document, transmit refers to data flow from the user application logic to the CPRI link. Receive refers to data
flow from the CPRI link to the user application logic. Downlink refers to the direction of data flow from REC to RE, and
uplink refers to the direction of data flow from RE to REC.
The Lattice CPRI core is compliant with the version 5.0 CPRI specification. However, the core does not directly support
requirement R-31 (line-rate autonegotiation). For the 3G version, Lattice supports dynamic switching between full and
half rate line settings (i.e., 614M/1.2G or 1.2/2.4G). However, switching dynamically between all line rates is not
supported since some PCS/SERDES bit settings need to be re-programmed through the SCI to support reliable data
transfer. It is anticipated that in most network applications, line rate negotiation will be established/managed at the
system level and there is nothing in the IP core that precludes supporting such capability.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
4
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
1.1.
Quick Facts
Table 1.1 provides quick facts about the CPRI IP core 3G version.
Table 1.1. CPRI IP Core Quick Facts (3G Version)
CPRI IP Core (3G Version)
Across All IP Configurations
Core Requirements
FPGA Families Supported
Minimal Device Supported
Resource Utilization
LatticeECP3, ECP5
LFE3-35E-6FTN256C
Data Path Width
LUTs
8-40 bits
1400-1600
sysMEM EBRs
Registers
Design Tool Support
LFE5UM-85F-7MG381C
1600-2000
2-6
1500-1700
Lattice Implementation
1500-1700
Lattice Diamond® 3.2
Synthesis
Synopsys® Synplify® Pro I-2013.09L-SP1-1
Simulation
Aldec® Active-HDLTM 9.3 Lattice Edition
Mentor Graphics® ModelSim® SE 10.1C
Table 1.2 provides quick facts about the CPRI IP core 5G version.
Table 1.2. CPRI IP Core Quick Facts (5G Version)
CPRI IP Core (5G Version)
Across All IP Configurations
Core Requirements
Resource Utilization
FPGA Families Supported
ECP5-5G
Minimal Device Supported
LFE5UM5G-45F-8BG381C
Data Path Width
LUTs
sysMEM EBRs
Registers
Design Tool Support
Lattice Implementation
64 bits
1100-1600
2~6
1000-1300
Lattice Diamond® 3.9
Synthesis
Synopsys® Synplify® Pro L-2016.09L-1
Simulation
Aldec® Active-HDLTM 10.3 Lattice Edition
Mentor Graphics® ModelSim® SE 6.6e SE
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
5
CPRI IP Core
User Guide
1.2.
Features
The following features apply to the basic CPRI core configuration for 3G version:
Supports the physical link layer (Layer 1) of the CPRI specification
Supports four standard bit rates of the CPRI specification
614.4 Mbps
1228.8 Mbps
2457.6 Mbps
3072 Mbps
Supports 8b/10b encoding/decoding performed in the PCS/SERDES
Supports code-violation detection performed in the PCS/SERDES
Performs CPRI Hyperframe Framing
Performs interleaving of IQ data, sync, C&M data, and vendor specific information
Provides an 8-, 16-, 32- or 40-bit parallel interface for IQ data
Performs subchannel mapping:
Supports a slow C&M channel based on a serial HDLC interface at standard bit rates (240 Kbps, 480 Kbps, 960
Kbps, and 1920 Kbps). The HDLC framer, if needed, must be implemented in the user logic.
Supports a fast C&M channel based on a serial Ethernet interface (84.48 Mbps max.) to the user logic, a nonstandard rate MII Ethernet interface to a MAC, or a 100 Mbps MII interface to a PHY device. Accepts a userselected pointer to the CPRI subchannel where the Ethernet link starts. The Ethernet MAC function is provided
as a separate IP core.
Performs synchronization and timing as defined in section 4.2.8 of CPRI Specification v5.0
Supports the L1 Inband Protocol
Provides a parallel interface for merging vendor specific data into the CPRI frame
Provides a start-up sequence state machine in hardware for both REC and RE nodes which performs:
Synchronization and Rate Negotiation
C&M Plane setup
Performs Link Maintenance as defined in section 4.2.10 of CPRI Specification v5.0:
LOS detection
LOF detection
RAI indication
Optional top-level template that implements user registers for control and status management
Optional 8-bit register interface through SCI bus
The low latency CPRI core configuration for 3G version supports all of the features specified for the basic core
configuration with the following key exceptions/modifications:
Supported for LatticeECP3 and ECP5 FPGA families only
Supports 1228.8 Mbps, 2457.6 Mbps, and 3072 Mbps line bit rates only.
FPGA bridge FIFOs in the SERDES/PCS (DCU in ECP5) block are bypassed in both the receive and transmit directions
Logic blocks supporting receive direction 10b word alignment, 10b/8b decoding and core-violation detection in the
SERDES/PCS (DCU in ECP5) block are bypassed and the corresponding functions are implemented in FPGA gates.
The low latency CPRI core configuration for 5G version is similar to the low latency core configuration for 3G version
with the following key exceptions/modifications:
Supported for ECP5 FPGA family only.
Supports 4915.2 Mbps only.
Provides 64-bit parallel interface for IQ data only.
Supports a slow C&M channel based on a serial HDLC interface at standard bit rates (240 Kbps, 480 Kbps, 960 Kbps,
1920 Kbps, 2400Kbps, and 3840Kbps).
No 8-bit register interface through the JTAG port
The low latency CPRI core implementation is different between LatticeECP3 and ECP5 for 3G version:
FPGA bridge FIFOs in the SERDES/PCS block are bypassed in both the receive and transmit directions for
LatticeECP3 FPGA, but enabled with synchronous WR/RD clocks for ECP5 LFE5UM FPGA
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
6
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
The latency variability from 10-bit word alignment is the key for low latency control. For LatticeECP3, CPRI
implements a PLL to eliminate the latency variation associated with the SERDES de-serializer 10-bit word alignment
function by reading word align offset status registers. (The value can be read at channel register 0x22 with the
base address.) For the LFE5UM device, the SERDES includes a new function that allows the de-serializer to slip the
location of the bits in the parallel output by one bit at a time. This is done one bit at a time under control of a
signal from the PCS and can be done multiple times as needed in order to align the data word as needed. This can
be used by the word aligner in the PCS to ensure that the parallel word is aligned on a comma character boundary
and is important to do in applications for CPRI that require that the latency variation through the SERDES block be
as small as possible.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
7
CPRI IP Core
User Guide
2. Functional Description
This section provides a functional description of the CPRI IP core.
2.1.
Block Diagram
The complete CPRI IP core includes two key components — the CPRI IP logic core and separate logic blocks that support
the interface between the logic core and the integrated PCS/SERDES block.
A block diagram of the CPRI IP logic core for 3G version is shown in Figure 2.1. For 5G version, higher HDLC rate
(hdlc_2400_en) is also supported. And 64-bit parallel interfaces (tx/rx_iq_da[63:0], tx/rx_vendor_da[63:0]) are
implemented instead.
cpri_core
tx_clk
rx_clk
sys_reset
test_md,rec_md
CPRITX
Etherne t
C&M
Transmit
Information
hdlc_(192 0,960,480,240)_en
tx_fifo
Transmit
Etherne t
Data
tx_hyp_rst_en, tx_bfn_rst_en
Us er I/O
tx_eth_pointer[5:0]
lbr[1:0], pcs_serd es_rate[1:0], force_sm_standby
rate_mode[1:0], chg_serd es_cfg
tx_hdlc_mode[2:0]
Transmit
IQ D ata
tx_cpri_da[15:0]
tx_cpri_ctl[1:0]
rectx_fe
rectx
Transmit
L1 Inband
Protocol
Transmit
HDLC Data
tx_dis, cpri_stup_state[2:0]
ver_num_err
rx_lof
rx_los
CP RI Link Status
tx_iq_data[31:0]
tx_sync
rx_hyp_num[7:0]
rx_bfn_num[11:0]
rx_frm_addr[7:0]
Us er P lane
IQ D ata
rx_iq_s1t_addr[3:0]
rx_iq_da_wr
rx_iq_da[31:0]
tx_l1_rst_rqstack
tx_l1_rai, tx_l1_sdi
CPRIRX
rx_l1_ver_num[7:0]
Re ceive
IQ D ata
rx_cpri_da[15:0]
rx_cpri_ctl[1:0]
rx_cpri_cv[1:0]
recrx_fe
Re ceive
L1 Inband
Protocol
recrx
rfe_clk
Re ceive
HDLC Data
Etherne t
C&M
Re ceive
Information
rx_l1_hdlc_mode[2:0]
rx_l1_rst_rqstack
rx_l1_rai, rx_l1_sdi
rx_l1_los, rx_l1_lof
rx_l1_eth_pointer[5:0]
tx_vendor_da[31:0]
tx_vendor_da_req
rx_vendor_da_val
rx_vendor_da[31:0]
rx_fifo
Re ceive
Etherne t
Data
L1 Inband
Protocol
Vendor
Specific
Data
tx_eth_clk, rx_eth_clk
tx_eth_da[3:0], tx_eth_en, tx_eth_er
rx_eth_da[3:0], rx_eth_en, rx_eth_er
tx_eth_full, tx_eth_empty
rx_eth_full, rx_eth_empty
C&M
Etherne t
Interface
tx_hdlc_da
tx_hdlc_clk,rx_hdlc_clk
rx_hdlc_wr, rx_hd lc_da
C&M
HDLC
Interface
Figure 2.1. CPRI IP Logic Core Block Diagram
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
8
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
2.2.
General Description
The complete CPRI IP core includes two key components, the CPRI IP logic core and separate logic blocks that support
the interface between the logic core and the SERDES/PCS (DCU for LFE5UM) functions integrated in the FPGA. Figure
2.1 shows a block diagram of the CPRI IP logic core. For 3G version, control and status parameters specifying core
functionality are managed via bit-mapped I/O that may be hard-wired or interfaced to programmable registers,
providing users with optimal flexibility in defining static and/or dynamic management of the various functional
parameters needed for their particular applications.
The CPRI IP Core supports a parallel user IQ data interface, a serial HDLC interface, a serial Ethernet interface, a parallel
interface for vendor specific information, and provides individual signals which allow the user to insert/receive L1
Inband Protocol information to/from the CPRI link. The interfaces to the user application are by design very simple to
allow the CPRI IP Core to be as flexible as possible. All higher-level functions such as Ethernet MAC functions, HDLC
framing, etc. are all intended to be done outside of the CPRI IP Core in user logic or in other Lattice IP Modules.
Figure 2.2 and Figure 2.3 show a system level block diagram of CPRI IP core instantiated in a LatticeECP3 or LFE5UM
series FPGA. As indicated in Figure 2.2 and Figure 2.3, additional IP cores may be instantiated to support multiple RP3
data links. Also shown in Figure 2.2 and Figure 2.3 are RXFE and TXFE logic blocks that support the interface between IP
logic core and the integrated SERDES/PCS (DCU for LFE5UM) block.
LatticeECP3 FPGA in REC / RE Module
LatticeECP3
FPGA Fabric
PCS QUAD
QUAD0
CPRI
(soft IP core)
CPRI
TX
P, N
CPRI
CPRI
RX
P, N
CH0
IQ
CPRI TX
Data&Ctrl
TX
SERDES
RX
RE or REC
Module
TXFE
P
C
S
CPRI
TX
C&M
Others
IQ
CPRI RX
Data&Ctrl
RXFE
CPRI
RX
User Logic
(CPRI
Transport
Layer
Function)
C&M
Others
CH1
CH2
CH3
Figure 2.2. CPRI IP Core System Block Diagram in LatticeECP3
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
9
CPRI IP Core
User Guide
LatticeECP3 FPGA in REC / RE Module
LFE5UM DCU
FPGA Fabric
DCU0
CPRI PHY
CPRI
TX
P, N
CPRI
CPRI
RX
P, N
CPRI
CORE
CH0
IQ
CPRI TX
Data&Ctrl
TX
SERDES
RX
RE or REC
Module
TXFE
P
C
S
CPRI
TX
C&M
Others
IQ
CPRI RX
Data&Ctrl
RXFE
CPRI
RX
User Logic
(CPRI
Transport
Layer
Function)
C&M
Others
CH1
Figure 2.3. CPRI IP Core System Block Diagram in ECP5 LFE5UM
Included in the CPRI IP core evaluation package is a reference module that provides an example of how the IP core is
instantiated at the top level, as shown in Figure 2.4. This top-level template is provided in RTL format and provides a
good starting point from which the user can begin to add custom logic to a design. Figure 2.4 includes example
connections for using the IP core in REC and RE modes.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
10
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Figure 2.4. Top-Level Template Included with CPRI IP Core
The CPRI IP logic core is provided in NGO format. For LatticeECP3 CPRI IP core, the RXFE and TXFE blocks are RTL
templates. For LFE5UM, PCS/SERDES, the rxfe and txfe blocks are packaged as CPRI PHY. Also included in the reference
top file is a user side driver/monitor module and register implementation module for optional use. These modules are
used in the evaluation simulation capability. The driver/monitor module is used to provide data in the transmit
direction and verify data in the receive direction. The register implementation module is used to control the IP core.
The overall top-level design can be used without modification in the debugging phase on physical hardware needing
only a CPRI source/sink capability to verify IP core operation.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
11
CPRI IP Core
User Guide
2.3.
Functional Overview
A block diagram of a typical LatticeECP3 CPRI application is shown in Figure 2.2 on page 9 and a block diagram of a
typical LFE5UM CPRI application is shown in Figure 2.3 on page 10. These examples show four CPRI link transceivers
implemented in a LatticeECP3 and an LFE5UM device. The major functional blocks in the example are the CPRI Soft IP
core, the PCS/SERDES block, and the user application logic. The CPRI IP Core (cpri_core), shown in Figure 2.1 on page 9,
consists of two major functional blocks, the transmitter (CPRITX) and the receiver (CPRIRX). One side of each of these
two blocks interfaces to the PCS/SERDES module, and the other side interfaces to the user logic that implements the
data link and higher layers of the CPRI protocol.
The CPRI IP Core multiplexes user IQ data with synchronization and C&M data. The IP core is being designed with very
simple and versatile interfaces for transferring data to the user application logic.
IQ data is transferred between the IP core and the user logic using a parallel data interface. In the transmit direction,
the user application provides a sync pulse which determines the start of a CPRI BFN (every 150 hyperframes) frame. In
the receive direction, the IP core transfers IQ data to the user application along with framing information recovered
from the CPRI link.
In the transmit direction, the CPRI IP core accepts user C&M data at either the HDLC and/or the Ethernet interface and
interleaves that data with the user IQ data into the CPRI frame. In the receive direction, C&M data received on the CPRI
link is disinterleaved from the user IQ data, and the HDLC or Ethernet encapsulated data is presented to the user at
either the HDLC or Ethernet interfaces of the CPRI IP core.
The C&M data can be encapsulated in either HDLC (slow channel) or Ethernet (fast channel) as desired by the user. For
HDLC, the CPRI IP Core only performs the interleaving of the C&M data with user IQ data. It does not provide any of the
HDLC Level 2 functions such as framing and serial to parallel conversion. These functions must be done in the user
application logic or in another IP module. For Ethernet, three modes are provided. In mode 1, the core does not
provide the serial to parallel and 4B/5B conversion. The interface is a serial bitstream that contains 5B encoded nibbles.
In mode 2, the core provides a standard MII interface that can be connected to a standard Ethernet MAC. In mode 3,
the core provides an MII like interface that has the clocks as inputs instead of outputs. This interface can be connected
to a PHY that is operating at the 100 Mbps standard rate.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
12
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
2.4.
Signal Descriptions
Table 2.1. CPRI I/O Signal Descriptions
Direction
Input/Output
Width (Bits)
tx_clk
I
1
61 MHz system clock input
rx_clk
I
1
61 MHz receive side clock input
sys_reset
I
1
Active low reset
txrst
I
1
Active high Ethernet FIFO reset (in TX CPRI)
rxrst
I
1
Active high Ethernet FIFO reset (in RX CPRI)
rec_md
I
1
Select between REC or RE mode, REC = 1
test_md
I
1
test_mod = 1, speed up the timer for simulation
hdlc_240_en
I
1
240 KHz HDLC frequency enable
hdlc_480_en
I
1
480 KHz HDLC frequency enable
hdlc_960_en
I
1
960 KHz HDLC frequency enable
hdlc_1920_en
I
1
1920 KHz HDLC frequency enable
hdlc_2400_en
I
1
2400 KHz HDLC frequency enable (only available in 3G)
auto_cnt
I
1
For master CPRI TX only, update Z64, Z128, Z192 with hyp_cnt_init
and bfn_cnt_init when low. When it is high, control words are
updated by internal counter.
hyn_cnt_init
I
8
For master CPRI TX only, used for two purposes: Auto_cnt = 0:
update Z64
Auto_cnt = 1: update internal hfn counter when tx_sync = 1 and
tx_hyp_rst_en = 1
bfn_cnt_init
I
12
For master CPRI TX only, used for two purposes: Auto_cnt = 0:
update Z128, Z192
Auto_cnt = 1: update internal bfn counter when tx_sync = 1 and
tx_bfn_rst_en = 1
tx_hyp_rst_en
I
1
Transmit side hype frame counter reset enable during tx_sync
active
tx_bfn_rst_en
I
1
Transmit side bfn counter reset enable during tx_sync active
tx_eth_pointer
I
6
Transmit Ethernet pointer value, the value is 0, 20~63.
lbr_en
I
2 (3 for 5G)
force_sm_standby
I
1
Force startup state machine to standby
pcs_serdes_rate
I
2 (3 for 5G)
CPRI line rate supported by PCS/SERDES
Pin Name
Description
System Clock and Reset
User Interface
Maximum CPRI Line bit rate enabled by user
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
13
CPRI IP Core
User Guide
Table 2.1. CPRI I/O Signal Descriptions (continued)
Pin Name
Direction
Input/Output
Width (Bits)
Description
rate_mode
O
2 (3 for 5G)
Final negotiated CPRI Line bit rate after start-up sequence
completes
chg_serdes_cfg
O
1
Indicator to program the SERDES for different rate
tx_hdlc_mode
O
3
Transmit side HDLC negotiated bit rate
tx_dis
O
1
For RE mode disable transmit side active high
cpri_stup_stat
O
3
Startup sequence state 1 = synchronization state 2 = protocol
setup state 3 = c/m plane setup state 4 = interface and vendor
negotiation state 5 = operation
ver_num_err
O
1
Version number error
rx_lof
O
1
Receive side Loss of Frame
rx_los
O
1
Receive side Loss of Signal
tx_iq_da
I
32 (40 for 3G, 64
for 5G)
tx_sync
I
1
Transmit side IQ data sync
rx_hyp_num
O
8
Receive side hyper frame number
rx_bfn_num
O
12
Receive side basic frame number
rx_frm_addr
O
8
Receive side frame address
rx_iq_slt_addr
O
4
Receive side IQ data slot address
rx_iq_da_wr
O
1
Receive side IQ data write enable
rx_iq_da
O
32 (40 for 3G, 64
for 5G)
tx_l1_rst_rqstack
I
1
Transmit reset request or acknowledge
tx_l1_rai
I
1
Transmit Remote Alarm indication
tx_l1_sdi
I
1
Transmit SAP Defect Indication
rx_l1_ver_num
O
8
Received version number
rx_l1_hdlc_mode
O
3
Receive side HDLC negotiated bit rate
rx_l1_rst_rqstack
O
1
Receive reset request or acknowledge
CPRI Link Status
User Plane IQ Data Signals
Transmit side IQ data
Receive side IQ data
L1 Inband Protocol Signals
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
14
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Table 2.1. CPRI I/O Signal Descriptions (continued)
Pin Name
Direction
Input/Output
Width (Bits)
rx_l1_rai
O
1
Receive Remote Action Indication
rx_l1_sdi
O
1
Receive SAP Defect Indication
rx_l1_los
O
1
Receive Loss of Signal
rx_li_lof
O
1
Receive Loss of Frame
rx_l1_eth_pointer
O
6
Receive side Ethernet pointer value
Description
Vendor-Specific Data Interface Signals
tx_vendor_da
I
32 (40 for 3G, 64
for 5G)
tx_vendor_da_req
O
1
Vendor-specific transmit data request
rx_vendor_da_val
O
1
Vendor-specific receive data valid
rx_vendor_da
O
32 (40 for 3G, 64
for 5G)
tx_cpri_ctl
O
2
tx_cpri_da
O
16 (40 for 3G and
64 for 5G, applies
to tx-cpri_da
andrx_cpri_da)
Vendor-specific transmit data
Vendor-specific receive data
CPRI to SERDES Signals
Transmit side CPRI control to SERDES
Transmit side CPRI data to SERDES
(5 for 3G and 8
for 5G, applies to
tx_cpri_ctl,
rx_cpri_ctl and
rx_cpri_cv)
rx_cpri_ctl
I
2
Receive side CPRI control from SERDES
rx_cpri_da
I
16
Receive side CPRI data from SERDES
rx_cpri_cv
I
2
Receive side CPRI code violation from SERDES
slip_rxfe
O
1
Receive side slip to get “BC” in low byte
tx_eth_clk, rx_eth_clk
I
1
Transmit Ethernet clock, Receive Ethernet clock
tx_eth_da
I
4
Transmit Ethernet data (1 bit wide in Serial mode)
tx_eth_en
I
1
Transmit Ethernet data enable (not equipped in Serial mode)
tx_eth_er
I
1
Transmit Ethernet error (not equipped in Serial mode)
rx_eth_da
O
4
Receive Ethernet data (1 bit wide in Serial mode)
C&M Ethernet Interface Signals
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
15
CPRI IP Core
User Guide
Table 2.1. CPRI I/O Signal Descriptions (continued)
Pin Name
Direction
Input/Output
Width (Bits)
rx_eth_en
I
1
Receive Ethernet data enable (not equipped in Serial mode)
rx_eth_er
I
1
Receive Ethernet error (not equipped in Serial mode)
tx_eth_almost_full
O
1
Transmit Ethernet FIFO almost full. This is for user flow control.
tx_eth_empty
O
1
Transmit Ethernet FIFO empty
rx_eth_full
O
1
Receive Ethernet FIFO full
rx_eth_empty
O
1
Receive Ethernet FIFO empty
rx_eth_fifo_err
O
2
Receive Ethernet FIFO error flag (only for Fixed mode)
tx_hdlc_da
I
1
Transmit HDLC data
tx_hdlc_clk
O
1
Transmit HDLC clock
rx_hdlc_clk
O
1
Receive HDLC clock
rx_hdlc_wr
O
1
Receive HDLC write
rx_hdlc_da
O
1
Receive HDLC data
Description
C&M HDLC Interface Signals
2.5.
Timing Specifications
Refer to LatticeECP3 Family Data Sheet (DS1021) and ECP5 and ECP5-5G Family Data Sheet (FPGA-DS-02012, previously
DS1044) for detailed SERDES and FPGA interface timing and electrical specifications.
2.6.
CPRI Overview
Figure 2.5 shows the CPRI layer 1 and layer 2 protocols. The CPRI IP core interleaves user IQ (in-phase and quadrature)
data with control and management (C&M) data into the frame and hyperframe formats specified by the CPRI
Specification and shown in Figure 2.6 and Figure 2.7, respectively.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
16
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Figure 2.5. CPRI Protocol Overview
Figure 2.6. CPRI Frame (Shown for 614.4 Mbps, 1228.8 Mbps, 2457.6 Mbps, and 3072 Mbps Line Rates)
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
17
CPRI IP Core
User Guide
Xs=0
1
Ns=0
0
64
1
1
65
2
2
66
3
3
67
4
4
2
Comma Byte, Synchronization and Timing
Slow C&M Link
p
L1 Inband Protocol
Reserved
Reserved
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
Reserved
10
Reserved
11
Reserved
12
Reserved
13
Reserved
14
14
15
15
79
143
207
Reserved
Reserved
16
16
80
144
208
Ve ndor-specific
17
17
Ve ndor-specific
18
Ve ndor-specific
.
.
.
Ve ndor-specific
Pointer p ->
Fa st C&M Link
.
.
.
61
61
62
62
126
190
254
63
63
127
191
255
Figure 2.7. CPRI Frame (Shown for 614.4 Mbps, 1228.8 Mbps, 2457.6 Mbps, and 3072 Mbps Line Rates)
Four possible line rates for the CPRI frame are supported, as shown in Table 2.2. The maximum line bit rate that the
core must support is selected by setting the lbr_en input signals. Once the maximum line bit rate has been selected, all
lower line bit rates are automatically enabled. The bit rate between the REC and RE is then negotiated between the
transmitting and receiving ends by the start-up sequence state machine within the CPRI IP core.
Table 2.2. CPRI Line Rates
CPRI Line Bit Rate
Rate (Mbps)
lbr_en[1:0] (lbr_en[2:0] for 5G)
Option 1
614.4
00
Option 2
1228.8
01
Option 3
2457.6
1X or 10 (LatticeECP3 only)
Option 4
3072
11 (LatticeECP3 only)
Option 5 (for 5G version)
4915.2
100 (LatticeECP5 only)
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
18
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
2.7.
Interfaces
The following sections discuss the interfaces of the IQ data, HDLC, Ethernet, and vendor information interfaces of the
CPRI IP core.
2.7.1. User Plane IQ Data Interface
The user IQ data interface supports the five line rates shown in Table 2.2. For 3G version, both the transmit and receive
directions provide a 40-bit IQ data bus. However, the number of bits used depends on the line rate selected by the
user. For the 614.4 Mbps line rate, 8 of the 32 bits on the IQ data interface are used (bits 7:0). For 1228.8 Mbps, bits
15:0 are used, and for a line rate of 2457.6 Mbps, 32 bits are used. For a line rate of 3072 Mbps, all 40 bits are used. For
5G version (4.9152 Gbps line rate), 64-bit IQ data bus is used for both the transmitter and the receiver.
In the transmit direction, the user application must provide a sync pulse to the CPRI IP core to indicate the start of each
CPRI BFN (every 150 hyperframes) frame. This sync pulse must be aligned with the IQ data, as shown in Figure 2.8.
Logic external to the IP core will be needed to assemble the octets of the aligned data from the Rx IP core into the
samples and control bits according to the user’s sample stream mapping. This is the reason it is necessary for the Rx IP
core to provide the boundary signals.
Clk
Sync (tx_sync)
Word15
Unused
Word1
Word2
W (user framing, not
passed to IP core)
15
0
1
2
X (user framing, not
passed to IP core)
255
Data (tx_iq_da)
0
Figure 2.8. Tx User IQ Interface Sync Pulse Alignment
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
19
CPRI IP Core
User Guide
In the receive direction, the CPRI IP Core provides IQ data to the user interface along with a word number (W), frame
number (X), hyperframe number (Z), and a BFN number, as shown in Figure 2.9.
Clk
BFN (rx_bfn_num)
Word2
Z (rx_hfrm_num)
Word1
X (rx_frm_addr)
Unused
W (rxwrdnum)
Word15
Data (rx_iq_da)
15
0
1
2
63
64
previous
#Z.64.0 (new)
#Z.192.0 #Z.128.0
Figure 2.9. Rx IQ Interface Data and Frame Number Alignment
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
20
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
2.7.2. Ethernet Interface
2.7.2.1. Mode 1 (Serial)
The CPRI IP Core Ethernet Interface transmits and receives Ethernet data to/from the user application logic using a
simple serial data connection. The amount of bandwidth on the CPRI link which is allocated to Ethernet (fast C&M) data
is determined by the pointer value (Z.194.0) which in turn determines which subchannel number the Ethernet data
starts at within the CPRI hyperframe. The pointer value is set by the user using the tx_eth_pointer[7:0] inputs to the IP
core. The transmitter and receiver of the REC and RE ends must be able to use the same pointer value.
Since a buffer is provided within the IP core for Ethernet data, the Ethernet interface clock between the IP core and the
user application logic must be chosen such that the correct number of words are transferred between the IP core and
the user's logic each frame or else the internal buffer may overrun or underrun. Due to the large number of possible
pointer values available it is not practical for the IP core to generate the Ethernet interface clock. Instead, the IP core is
designed such that the pointer value and the Ethernet interface clock are provided as inputs to the Core, giving the
user the maximum flexibility. The template logic (cpri_top) shown in Figure 2.10, which will be delivered with the IP
core, will include an example of how to generate and connect an Ethernet interface clock frequency of 61.44 MHz.
Additional clock frequencies and pointer values may be set by the user by modifying the template logic. The difficulty
which will be encountered in generating various Ethernet clock frequencies and pointer values will be entirely
dependent on the clock frequencies available in the user's system. This is why the generation of the Ethernet clock
frequency, and the assignment of the pointer value, must be done in the template logic and not within the IP core.
Figure 2.10. Ethernet C&M Interface
2.7.2.2. Mode 2 (Matched Rate MII)
The CPRI IP Core Ethernet Interface transmits and receives Ethernet data to/from the user application logic using a
non-standard rate MII interface. The amount of bandwidth on the CPRI link which is allocated to Ethernet (fast C&M)
data is determined by the pointer value (Z.194.0) which in turn determines which subchannel number the Ethernet
data starts at within the CPRI hyperframe. The pointer value is set by the user using the tx_eth_pointer[7:0] inputs to
the IP core.
Since a buffer is provided within the IP core for Ethernet data, the Ethernet interface clock between the IP core and the
user application logic must be chosen such that the correct number of words are transferred between the IP core and
the user's logic each frame or else the internal buffer may overrun or underrun. Due to the large number of possible
pointer values available it is not practical for the IP Core to generate a periodic interface clock. Instead, the IP core is
designed to produce a gapped clock. The Ethernet pointer and CPRI line rate are used to index a two parameter table
that specifies the frequency and number of pulses contained in the gapped clock. The transmit Ethernet clock is based
on the negotiated rate and transmit pointer. The receive Ethernet clock is based on the negotiated rate and the
received L1 inband pointer in Z.194.0.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
21
CPRI IP Core
User Guide
The core provides the 4B/5B code conversion required by the CPRI specification. The logic that interfaces the MII to
CPRI byte mux/demux is shown in Figure 2.11.
Lattice CPRI IP Core
TX
CPRI
BYTE
MUX
5-Bit to
85
8-Bit
Width
Translator
4b/5b
Encoder
18
(Invoked 3
times per
FIFO Read)
FIFO
(512x18
3 Nibbles
per Word)
1 nib
to
3 nib
TXD[3:0 ]
TX_EN
TX_ER
TX_CLK
MII
Ethernet
MAC
Core
Client Side
Interface
(Lattice IP
or userspecified)
RX
5-Bit to
CPRI 85
8-Bit
Width
BYTE
Translator
DEMUX
5b/4b
Decoder 18
(Invoked 3
times per
FIFO Write)
FIFO
(512x18
3 Nibbles
per Word)
3 nib
to
1 nib
RXD[3:0 ]
RX_DV
RX_ER
RX_CLK
Notes:
1. TX_CLK and RX_CLK are gapped clocks with transition rates matching the effective data rate of the
Fast C&M Channel specified by the pointer value in control byte #Z.194.0 and the CPRI line rate.
2. Both FIFOs are read and written as needed to source and sink data/control from/to the MII and CPRI
mux/demux.
Figure 2.11. Matched Rate MII CPRI Ethernet Interface
2.7.2.3. Mode 3 (100 Mb/s Fixed Rate MII)
The CPRI IP Core Ethernet Interface transmits and receives Ethernet data to/from the user application logic using a 100
Mbps rate MII interface. The amount of bandwidth on the CPRI link which is allocated to Ethernet (fast C&M) data is
determined by the pointer value (Z.194.0) which in turn determines which subchannel number the Ethernet data starts
at within the CPRI hyperframe. The pointer value is set by the user using the tx_eth_pointer[7:0] inputs to the IP core.
The logic needed to support mode 3 is similar to that required for mode 2 with the exception of handling the reading
and writing of the FIFOs. On the transmit side, the FIFO is always written at a faster rate than it is read. This means that
the reading of this FIFO is the same as mode 2. Interframe gap is only written into the FIFO if the almost empty
threshold is not maintained. This prevents the FIFO from being filled with idle information. It is the responsibility of the
driver of the 100 Mbps link to not overrun the FIFO. There is no flow control provided to accommodate the rate
mismatch between the 100 Mbps link and the CPRI link. Packets must be spaced to allow enough time for the CPRI to
transmit packets.
On the receive side, the FIFO is always read at a faster rate than it is written. When the FIFO input data is not idle and
passes basic SSD and ESD checks, it is written to the FIFO. When idle is detected on the FIFO input the FIFO is not
written. When an end of packet is detected, a request is sent to the FIFO Read Control to send the packet on to the MII.
A complete packet is received before it is read from the FIFO. FIFO reads begin when a request is received from the
FIFO Write Control. FIFO reads continue until an end of packet is detected.
When an end of packet is detected, FIFO reads stop and a minimum of 24 nibble IDLEs are supplied to the MII interface.
For 3.072 Gbps CPRI link, the MAC Ethernet MAX bandwidth is 3.84M/64*(64-20)*40, that is 105.6 Mbps (when
Ethernet pointer p is set to 20), and MIN bandwidth is 2.4 Mbps (when Ethernet pointer p is set to 63). For example, if
your Ethernet bandwidth requirement is 10 Mbps, please set Ethernet pointer p as 60~61, the corresponding
bandwidth is 7.2~9.6 Mbps. If Ethernet pointer p is set too small, the TX FIFO for Ethernet may be empty, and the
Ethernet package may be inserted by duplicated data of the partial package. If Ethernet pointer p is set too large, the
TX FIFO for Ethernet may be full. If no Ethernet bandwidth is needed, please set Ethernet pointer p to 0.
The core provides the 4B/5B code conversion required by the CPRI specification. The logic that interfaces the MII to
CPRI byte mux/demux is shown in Figure 2.12.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
22
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Lattice CPRI IP Core
FIFO
(2048x18
3 Nibbles
per word)
TX
CPRI
BYTE
MUX
5-Bit to
8-Bit
Width
Translator
4b/5b
Encoder
(Invoked
3 times
per FIFO
Read)
FIFO
(2048x18
3 Nibbles
per Word)
UTP
Line
MII
RX
CPRI
BYTE
MUX
8-Bit to
5-Bit
Width
Translator
5b/4b
Decoder
(Invoked 3
times per
FIFO
Write)
FIFO
(8129x7
1 Nibble
per Read)
Notes:
1. TX_CLK and RX_CLK are supplied by the external PHY device and assumed to be 25MHz.
2. The transmit FIFO is read as needed to supply data/control to the CPRI mux.
3. The transmit FIFO is written as needed to sink packets from the MII and supply idle.
4. The receive FIFO is read and written as needed to source and sink packets from/to the MII and CPRI
demux. Idle is supplied separately.
Figure 2.12. 100 Mbps Fixed Rate MII CPRI Ethernet Interface
2.7.3. HDLC Interface
A timing diagram for the Ethernet C&M interface is given in Figure 2.13. The CPRI IP Core HDLC interface transmits and
receives HDLC data to/from the user application logic using a serial data connection. The user selects the desired
frequencies which the IP core will support by setting the hdlc_(240,480,960,1920,2400)_en input signals. The HDLC
data rates shown in Table 2.3 are supported.
The CPRI IP core HDLC Interface does not perform any HDLC framing or processing. This must be performed in the user
application logic or in another IP module. The transmitter of the IP core will negotiate with the receiver of the end of
the CPRI link to achieve the maximum HDLC rate possible.
Figure 2.13. HDLC C&M Interface
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
23
CPRI IP Core
User Guide
Table 2.3. HDLC Frequencies Supported
HDLC Option
Input Signal
HDLC Data Rate (Kbps)
0
None selected
HDLC disabled
1
hdlc_240_en = 1
240
2
hdlc_480_en = 1
480
3
hdlc_960_en = 1
960
4
hdlc_1920_en = 1
1920
5
hdlc_2400_en = 1
2400
2.7.4. L1 Inband Protocol Interface
The L1 Inband Protocol Interface provides signals that allow the user application logic to populate the control words
listed in the CPRI specification, and to read the value of the L1 Inband Protocol control words that are received from
the CPRI link.
2.7.5. Vendor Specific Information
Figure 2.14 illustrates the timing of the vendor-specific information interface between the IP core and the user
application logic. The IP core provides a simple parallel interface for merging vendor-specific information into the CPRI
frame. The number of bytes available in the CPRI frame for vendor-specific information is dependent on the pointer
value chosen. Any FIFOs required to support the bandwidth allocated to vendor-specific information must be
implemented in the user logic.
The IP core provides a data request signal to the user application logic called tx_vendor_data_req. When this signal
goes high, the user logic must return the vendor-specific data to the IP core within six clock cycles. The user logic must
continue to provide vendor-specific data until the tx_vendor_data_req signal is once again asserted. If the user does
not have any data to send in the vendor-specific bytes, then it must insert idle code.
In the receive direction, incoming vendor-specific information which is recovered from the CPRI link is presented to the
user application logic along with an rx_vendor_da_val signal. The vendor-specific information interface uses either 8,
16, or 32 (40 for 3G, 64 for 5G) of the available data bits, depending on which CPRI line bit rate has been selected. This
is similar to the IQ data interface described previously.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
24
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Clk
Vendor-specific data
request from IP core
(tx_vendor_data_req)
Data from user logic
(tx_vendor_data)
User data
Figure 2.14. Timing for Vendor-Specific Information Interface
2.7.6. Start-up Sequence
The CPRI IP Core provides a start-up state machine which executes the startup state transitions as shown in Figure 30 in
the CPRI Specification (Reference 2). This state machine will automatically perform the synchronization of Layer 1, and
it will align the capabilities of the REC and the RE (line bit rate, protocol, C&M link speed, C&M protocol, and vendor
specific signaling). For 3G version, the CPRI IP Core depends on software to program the correct data bus width into the
LatticeECP3/LFE5UM SERDES through the SCI Bus. For a 1228.8 or 2457.6 Mbps CPRI line bit rate, the SERDES must be
provisioned for a 16-bit interface to the FPGA logic. For all CPRI line bit rate, the SERDES must be provisioned for an 8bit interface to the FPGA logic to achieve low latency purpose. Since the provisioned mode of the SERDES may need to
change while the start-up sequence is negotiating the CPRI line rate, a signal (chg_serdes_cfg) is provided to the user
application logic indicating that the mode the SERDES should be programmed for needs to be changed. The user
application must monitor this signal and program the SERDES to the correct mode while the REC and RE are attempting
to match line bit rates. When the application has finished programming the PCS/SERDES it writes the rate that is being
supported to lbr_en[4:3]. For 5G version, there is not JTAG interface to update parameters.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
25
CPRI IP Core
User Guide
3. Parameter Settings
The IPexpress ™ and the Clarity Designer tools are used to create IP and architectural modules in the Diamond
software. IPexpress is for LatticeECP3 CPRI IP Core and Clarity Designer is for LFE5UM CPRI IP Core. Refer to the IP Core
Generation section for a description on how to generate the IP.
Table 3.1 provides the list of user configurable parameters for the CPRI IP core for 3G version. The parameter settings
are specified using the CPRI IP core Configuration GUI in IPexpress.
Table 3.1. IP Core Parameters
Parameter
Range/Options
Default
Design Entry
Design Entry
Design Entry
Ethernet Mode
Ethernet Mode
Ethernet Mode
Synthesis Tool
Synthesis Tool
General Options
Eval Configuration
Synthesis Tool
3.1.
CPRI Configuration Dialog Box
Figure 3.1 shows the CPRI Configuration dialog box.
Figure 3.1. CPRI Configuration Dialog Box
Figure 3.2 shows the CPRI PCS Configuration dialog box, it is for LFE5UM CPRI IP Core only. The page ‘PCS’ is for
ECP5UM PCS/SERDES settings. If the PCS in debug mode option is selected, the LFE5UM DCU interface is displayed in
_phy_bb.v for debug. For further PCS configuration, click the Advanced button.
Figure 3.2. CPRI PCS Configuration Dialog Box
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
26
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Clicking the Advanced button opens the CPRI PCS Advanced Configuration Dialog Box shown in Figure 3.3.
If only one PCS is used in the project, it is recommended to select the Reset Sequence Select option in Control Setup
tab.
If you want to revise the SERDES electric character, change the parameters on the SerDes Setup tab. Refer to ECP5
SERDES/PCS Usage Guide (TN1261).
Figure 3.3. CPRI PCS Advanced Configuration Dialog Box
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
27
CPRI IP Core
User Guide
3.1.1. Generation Options
3.1.1.1. Design Entry
Lattice CPRI IP core only supports low latency character. The 'basic' option is not supported.
3.1.1.2. Ethernet Mode
This option allows the user to specify the Ethernet mode supported by the IP core, either Serial, Matched Rate MII or
100Mb/s Fixed Rate MII. See Ethernet Interface for a detailed description of these different modes.
3.1.2. Eval Configuration
3.1.2.1. Synthesis Tool
This option specifies evaluation configuration synthesis tool support for Synplify.
3.2.
Programmable Parameters
The configuration settings listed in Table 3.2 are controlled via user-specified input signals to the IP core.
Table 3.2. CPRI Parameters Controlled via Input Signals to the IP Core
Input Signal
Values
Function
lbr_en[1:0](for 3G)
lbr_en[2:0](for 5G)
0, 1, 2, 3, 4
force_sm_standby
0, 1
Selects the maximum line bit rate which the IP core will support:
0 – 614.4 Mbps maximum
1 – 1228.8 Mbps maximum
2, 3 – 2457.6 Mbps maximum
3 – 3072 Mbps in 3G version
4
4915.2 Mbps
in 5G version
A -zero-to-one
transition
forces the startup state machine to the Standby state.
pcs_serdes_rate[1:0]
(for 3G)
pcs_serdes_rate[2:0]
(for 5G)
0, 1, 2, 3, 4
tx_eth_pointer[7:0]
0-63
Selects the line bit rate which the PCS/SERDES will support:
0 – 614.4 Mbps maximum
1 – 1228.8 Mbps maximum
2 – 2457.6 Mbps maximum
3 – 3072 Mbps in 3G version
4
- 4915.2
5G version
Selects
fastMbps
C&Minpointer
value
hdlc_240_en
0, 1
Enables 240 KHz as the maximum HDLC interface frequency
hdlc_480_en
0, 1
Enables 480 KHz as the maximum HDLC interface frequency
hdlc_960_en
0, 1
Enables 960 KHz as the maximum HDLC interface frequency
hdlc_1920_en
0, 1
Enables 1920 KHz as the maximum HDLC interface frequency
hdlc_2400_en
0, 1
Enables 2400 KHz as the maximum HDLC interface frequency
auto_cnt
0, 1
Enable master CPRI tx hfn and bfn updating. Default 1.
hyp_cnt_init
0-255
bfn_cnt_init
0-4095
hfn used to update the control words or initialize the internal hfn counter. Default
0.
bfn used to update the control words or initialize the internal bfn counter. Default
tx_hyp_rst_en
0, 1
0.
Enables
tx_sync to reset tx_hyp_num
tx_bfn_rst_en
0, 1
Enables tx_sync to reset tx_bfn_num
test_md
0, 1
Speeds up timer to reduce test time:
0 – Normal
1 – Test
rec_md
0, 1
Sets core to REC or RE:
0 – RE
1 – REC
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
28
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
4. IP Core Generation
This section provides information on how to generate the CPRI IP core using the Diamond or ispLEVER software
IPexpress tool, and how to include the core in a top-level design.
4.1.
Licensing the IP Core
An IP core- and device-specific license is required to enable full, unrestricted use of the CPRI IP core in a complete, top
level design. Instructions on how to obtain licenses for Lattice IP cores are given at:
http://www.latticesemi.com/Products/DesignSoftwareAndIP.aspx
Users may download and generate the CPRI IP core and fully evaluate the core through functional simulation and
implementation (synthesis, map, place and route) without an IP license. The CPRI IP core also supports Lattice’s IP
hardware evaluation capability, which makes it possible to create versions of the IP core that operate in hardware for a
limited time (approximately four hours) without requiring an IP license. See the Hardware Evaluation section for
further details. However, a license is required to enable timing simulation, to open the design in the Diamond EPIC tool,
and to generate bitstreams that do not include the hardware evaluation timeout limitation.
4.2.
Getting Started
The CPRI IP core is available for download from the Lattice IP Server using the IPexpress tool. The IP files are
automatically installed using ispUPDATE technology in any customer-specified directory. After the IP core has been
installed, the IP core will be available in the IPexpress GUI dialog box shown in Figure 4.1.
The IPexpress tool GUI dialog box for the CPRI IP core is shown in Figure 4.1. To generate a specific IP core
configuration the user specifies:
Project Path – Path to the directory where the generated IP files will be loaded.
File Name – “username” designation given to the generated IP core and corresponding folders and files.
(Diamond) Module Output – Verilog or VHDL.
(ispLEVER) Design Entry Type – Verilog HDL or VHDL.
Device Family – Device family to which IP is to be targeted (e.g. LFE5UM, LatticeECP3, etc.). Only families that
support the particular IP core are listed.
Part Name – Specific targeted part within the selected device family.
Figure 4.1. IPexpress Dialog Box
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
29
CPRI IP Core
User Guide
Figure 4.2. Clarity Designer Dialog Box
Note that if the IPexpress for LatticeECP3 or the Clarity Designer for LFE5UM is called from within an existing project,
Project Path, Module Output, Device Family and Part Name default to the specified project parameters. Refer to the
IPexpress tool online help for further information.
Figure 4.3. Configuration GUI
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
30
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
For LFE5UM CPRI IP core, the core should be generated using Diamond Clarity Designer.
To generate the LFE5UM CPRI IP Core in System Planner:
1.
Create a new project with an LFE5UM device.
2.
Open Clarity Designer and double-click CPRI IP core to open the CPRI IP GUI.
3.
Configure the parameters. Note that there is one more package PCS.
4.
Locate the DCU Channel into FPGA in the Clarity Designer Planner.
5.
Click the Generate button.
The PCS page is shown in Figure 4.4.
Figure 4.4. PCS User Interface
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
31
CPRI IP Core
User Guide
4.3.
IPexpress-Created Files and Top Level Directory Structure
When the user clicks the Generate button in the IP Configuration dialog box, the IP core and supporting files are
generated in the specified “Project Path” directory. The directory structure of the generated files is shown in Figure 4.5.
Figure 4.5. LatticeECP3 CPRI IP Core Directory Structure
The directory structure of LFE5UM CPRI IP core, as shown in Figure 4.6, is different from LatticeECP3.
Figure 4.6. LFE5UM CPRIIP Core Directory Structure
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
32
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Table 4.1 provides a list of key files created by the IPexpress tool and how they are used. The IPexpress tool creates
several files that are used throughout the design cycle. The names of most of the created files are customized to the
user’s module name specified in the IPexpress tool.
Table 4.1. File List
File
Simulation Synthesis
Description
IP Configuration Files
.lpc
This file contains the IPexpress tool options
used to recreate or modify the core in the
IPexpress tool.
.ipx
This file is a container that holds references
to all of the elements of the generated IP
core required to support simulation,
synthesis and implementation. The file is
used to bring in the appropriate files during
the design implementation and analysis. It
is also used to re-load parameter settings
into the IP/Module generation GUI when an
IP/Module is being regenerated.
LatticeECP3 CPRI Core Files
\cpri_lowlatency_eval\cpri_c0\src\params\cpri_defines.v
Yes
This file provides user options of the IP for
the simulation models.
cpri_core_3g_beh.v
Yes
This file provides CPRI core obfuscated file
for RTL simulation.
.v/.vhd
Yes
This file provides CPRI core wrapper file for
RTL simulation.
(.v file if Verilog is selected or .vhd file if
VHDL is selected).
_bb.v
Yes
This file has black-box instantiations of the
core and I/O modules and also source
instantiation of clock synchronization
module.
This file provides the core instance for user
project example.
_inst.v
.ngo
Yes
This file provides the synthesized IP core.
pmi_ram_*.ngo
Yes
This file provides the synthesized RAM files.
cpri_lowlatency_eval\models\ecp3\frm_ram_256x40.v
Yes
cpri_lowlatency_eval\models\ecp3\pcs_serdes.v
Yes
cpri_lowlatency_eval\testbench\*
Yes
This is a ram RTL file.
Yes
This is a PCS/SERDES RTL file.
All files in the folder are test bench files for
evaluation simulation.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
33
CPRI IP Core
User Guide
Table 4.1. File List (continued)
File
cpri_lowlatency_eval\\sim\*
Simulation Synthesis
All files in the folder are simulation script
files (*.do) for RTL level evaluation
simulation and gate level evaluation
simulation. The .do files can be launched in
Modelsim or ActiveHDL tools.
Yes
cpri_lowlatency_eval\\impl\*
Description
Yes
All files in the folder are evaluation
implementation Diamond project files for
core only project and reference top project.
*.lpf files are for evaluation project timing
constraint.
LFE5UM CPRI Core Files
This is for CPRI PCS/SERDES model
generation.
\cpri_lowlatency_eval\cpri_c0\src\params\cpri_defines.v
Yes
This file provides user options of the IP for
the simulation models.
phy_wrap.v
Yes
This file provides CPRI PHY obfuscated file
for RTL simulation.
cpri_core_3g_beh.v
Yes
This file provides CPRI core obfuscated file
for RTL simulation.
.v/.vhd
Yes
_phy.v
Yes
Yes
This file provides CPRI core top wrapper file
for RTL simulation and implementation. (.v
file if Verilog is selected or .vhd file if VHDL
is selected.) The module
includes CPRI PHY and CPRI core.
This file provides CPRI PHY wrapper file for
RTL simulation.
_phy_bb.v
Yes
This file has black-box instantiation of the
CPRI PHY.
_phy.ngo
Yes
This file provides the synthesized CPRI PHY.
_core.v
This file provides CPRI core wrapper file for
RTL simulation.
Yes
_core_bb.v
Yes
This file has black-box instantiation of the
CPRI core.
_core.ngo
Yes
This file provides the synthesized CPRI core.
pmi_ram_*.ngo
Yes
This file provides the synthesized RAM files.
cpri_lowlatency_eval\models\ecp5u\frm_ram_256x40.v
Yes
This is a ram RTL file.
cpri_lowlatency_eval\models\ecp5u\_PCS.v
Yes
This is a PCS/SERDES RTL file.
cpri_lowlatency_eval\models\ecp5u\rsl_core.v
Yes
Yes
This is a PCS/SERDES reset sequence logic
RTL file.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
34
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Table 4.1. File List (continued)
File
Simulation Synthesis
Description
cpri_lowlatency_eval\testbench\*
Yes
All files in the folder are test bench files for
evaluation simulation.
cpri_lowlatency_eval\\sim\*
Yes
All files in the folder are simulation script
files (*.do) for RTL level evaluation
simulation and gate level evaluation
simulation. The .do files can be launched in
Modelsim or ActiveHDL tools.
cpri_lowlatency_eval\\impl\*
Yes
All files in the folder are evaluation
implementation Diamond project files for
core only project and reference top project.
*.lpf files are for evaluation project timing
constraint.
These are all of the files necessary to implement and verify the CPRI IP core in your own top-level design. The following
additional files providing IP core generation status information are also generated in the “Project Path” directory:
_generate.log – Diamond or ispLEVER synthesis and map log file.
_gen.log – IPexpress IP generation log file.
The
CPRI IP core. The
and subtending directories provide files supporting the CPRI IP core evaluation. The
directory contains files/folders with content that is constant for all configurations of the
subfolder contains files/folders with content specific to the username configuration.
The
directory is created by IPexpress the first time the core is generated and updated each
time the core is regenerated. A
directory is created by IPexpress each time the core is generated and
regenerated each time the core with the same file name is regenerated. A separate
directory is
generated for cores with different names, e.g.
, etc.
4.4.
Instantiating the Core
For ECP3 CPRI, the generated CPRI IP core package includes black-box (_bb.v) and instance
(_inst.v) templates that can be used to instantiate the core in a top-level design. For LFE5UM CPRI, the
generated CPRI IP core package includes a top file (), black-box (_phy_bb.v and
_core_bb.v) that can be used to instantiate the core in a top-level design. Two example RTL top level
reference source files are provided in
.
The top-level file cpri_reference_top.v is the same top-level that is used in the simulation model described in the next
section. Users may use this top-level reference as the starting template for the top level for their complete design.
Included in cpri_reference_top.v are logic, memory and clock modules supporting a driver/monitor module capability,
a register module supporting programmable control of the CPRI core and system processor interface via SCI bus.
Verilog source RTL for these modules are provided in
. The top-level configuration is
specified via the parameters defined in the cpri_defines.v file in
. A description of the CPRI register layout
for this reference design is provided in the Register Descriptions section.
The top-level file cpri_CORE_ONLY_top.v supports the ability to implement just the CPRI core itself. This design is
intended only to provide an accurate indication of the device utilization associated with the CPRI core and should not
be used as an actual implementation example.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
35
CPRI IP Core
User Guide
4.5.
Running Functional Simulation
The functional simulation includes a configuration-specific behavioral model of the CPRI IP Core that is instantiated in
an FPGA top level along with a user-side driver/monitor module and register implementation module. The top- level
file supporting ModelSim evaluation simulation is provided in
. This FPGA top is instantiated in an evalulation
testbench provided in
that configures FPGA test logic
registers and CPRI IP core control and status registers via an included test file testcase.v provided in
. Note the user can edit the testcase.v file to
configure and monitor whatever registers they desire.
Users may run the evaluation simulation by doing the following.
4.5.1. Using Aldec Active-HDL
To run the evalualtion simulation using Active HDL:
1.
Open Active-HDL.
2.
Under the Tools tab, select Execute Macro.
3.
Browse to folder
“do” scripts shown.
and execute on of the
4.5.2. Using Mentor Graphics ModelSim
To run the evaluation simulation using ModelSim:
1.
Open ModelSim.
2.
Under the File tab, select Change Directory and choose folder
.
3.
Under the Tools tab, select Execute Macro and execute one of the “do” scripts shown.
The simulation waveform results will be displayed in the simulator Wave window.
For 5G version, only 4915.2 MHz line rate is supported for evaluation simulation. For 3G version, four different
evaluation simulations are provided with the CPRI IP core:
Evaluation simulation using rate 614.4 MHz as the line rate
Evaluation simulation using rate 1228.8 MHz as the line rate.
Evaluation simulation using rate 2457.6 MHz as the line rate.
Evaluation simulation using rate 3072 MHz as the line rate.
All of the simulations configure the CPRI and PCS/SERDES registers and wait for the receiver to synchronize with the
incoming link. The following tests are then run:
Verify that the receiver has no IQ data errors for one frame.
Verify that the receiver has no vendor specific data errors for one frame.
Verify that the receiver has no Ethernet data errors for one frame.
Verify that the receiver has no HDLC data errors for one frame.
The procedure for running gate-level timing simulation is equivalent to that for running RTL functional simulation. After
opening Active-HDL or ModelSim, the user executes one of the “do” scripts in the corresponding
\sim\aldec\gate or \sim\modelsim\gate directory. Note that for VHDL gate netlist simulation, it is recommended to
start with an empty work library.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
36
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
4.6.
Synthesizing and Implementing the Core in a Top-Level Design
The CPRI IP core itself is synthesized and provided in NGO format when the core is generated. Users may synthesize the
core in their own top-level design by instantiating the core in their top level as described previously and then
synthesizing the entire design with Synplicity or RTL Synthesis.
Two example RTL top-level configurations supporting CPRI core top-level synthesis and implementation are provided
with the CPRI IP core in
.
The top-level file cpri_core_only_top.v provided in
supports the ability to implement just the
CPRI core. This design is intended only to provide an accurate indication of the device utilization associated with the
core itself and should not be used as an actual implementation example. The top-level file cpri_reference_top.v
provided in
supports the ability to
instantiate, simulate, map, place and route the Lattice CPRI IP core in a complete example design. This reference design
basically provides a CPRI driver/monitor on the client side of the core in an FPGA top-level file that contains the CPRI IP
core and the driver/monitor. This is the same configuration that is used in the evaluation simulation capability
described previously.
Note that implementation of the reference evaluation configuration is targeted to a specific device and package type
for each device family (LatticeECP3 and ECP5). Specifically:
LatticeECP3: LFE3-95E-7FN1156CES
ECP5: LFE5UM-85F-7MG381C (for 3G version)
ECP5: LFE5UM5G-45F-8BG381C (for 5G version)
Push-button implementation of both top-level configurations is supported via the ispLEVER project files,
. These files are located in
.
To use this project file in Diamond:
1.
Choose File > Open > Project.
2.
Browse to
(or precision) in the
Open Project dialog box.
3.
Select and open .ldf. At this point, all of the files needed to support top-level synthesis and
implementation will be imported to the project.
4.
Select the Process tab in the left-hand GUI window.
5.
Implement the complete design via the standard Diamond GUI flow.
4.7.
Hardware Evaluation
The CPRI IP core supports Lattice’s IP hardware evaluation capability, which makes it possible to create versions of the
IP core that operate in hardware for a limited period of time (approximately four hours) without requiring the purchase
of an IP license. It may also be used to evaluate the core in hardware in user-defined designs.
4.7.1. Enabling Hardware Evaluation in Diamond
Choose Project > Active Strategy > Translate Design Settings. The hardware evaluation capability may be
enabled/disabled in the Strategy dialog box. It is enabled by default.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
37
CPRI IP Core
User Guide
4.8.
Updating/Regenerating the IP Core
By regenerating an IP core with the IPexpress tool, you can modify any of its settings including device type, design entry
method, and any of the options specific to the IP core. Regenerating can be done to modify an existing IP core or to
create a new but similar one.
4.8.1. Regenerating an IP Core in IPexpress Tool
To regenerate an IP core in IPexpress:
1.
In IPexpress, choose Tools > Regenerate IP/Module.
2.
In the Select a Parameter File dialog box, choose the Lattice Parameter Configuration (.lpc) file of the IP core to
regenerate, and click Open.
3.
The Select Target Core Version, Design Entry, and Device dialog box shows the current settings for the IP core in the
Source Value box. Make your new settings in the Target Value box.
4.
If you want to generate a new set of files in a new location, set the location in the LPC Target File box. The base of
the .lpc file name will be the base of all the new file names. The LPC Target File must end with an .lpc extension.
5.
Click Next. The IP core’s dialog box opens showing the current option settings.
6.
In the dialog box, choose desired options. To get information about the options, click Help. Also, check the About
tab in the IPexpress tool for links to technical notes and user guides. The IP core might come with additional
information. As the options change, the schematic diagram of the IP core changes to show the I/O and the device
resources the IP core will need.
7.
Click Generate.
8.
Click the Generate Log tab to check for warnings and error messages.
4.8.2. Regenerating an IP Core in Clarity Designer Tool
To regenerate an IP core in Clarity Designer:
Option 1
1.
In the Clarity Designer Builder window, right-click on the existing IP instance and choose Config.
Figure 4.7. Clarity Designer Builder Window
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
38
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
2.
In the dialog box, choose the desired options.
For more information about the options, click Help. You may also click the About tab in the Clarity Designer
window for links to technical notes and user guides. The IP may come with additional information. As the options
change, the schematic diagram of the module changes to show the I/O and the device resources the module will
need.
3.
Click Configure.
Option 2
1.
In the Clarity Designer Catalog window, click the Import IP tab at the bottom.
2.
In the Import IP tab, click Browse to choose the IPX/LPC source file of the module or IP to regenerate.
Figure 4.8. Clarity Designer Catalog Window
3.
Specify the instance name in Target Instance. Note that this instance name should not be the same as any of the
existing IP instances in the current Clarity Design project.
4.
Click Import. The module's dialog box opens showing the option settings.
5.
In the dialog box, choose the desired options.
For more information about the options, click Help. You may also click the About tab in the Clarity Designer window
for links to technical notes and user guides. The IP may come with additional information. As the options change,
the schematic diagram of the module changes to show the I/O and the device resources the module will need.
6.
Click Configure.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
39
CPRI IP Core
User Guide
5. Application Support
This section provides application support information for the CPRI IP core.
5.1.
CPRI IP Top-Level Reference Design
Note: A top-level reference design is available for user evaluation. This reference design is also described in detail in
CPRI IP Core Low Latency Variation Design Considerations User’s Guide (IPUG74).
Included with the CPRI IP core is a reference top-level file, cpri_reference_top.v, which designers may use as the
starting template for the top-level for their complete design. Included in cpri_reference_top.v are logic, memory and
clock modules supporting a driver/monitor module capability, a register module supporting programmable control of
the system processor interface. Verilog source RTL for these modules are provided in
. The top-level configuration is
specified via the parameters defined in the cpri_defines.v file in
.
The constraints files provided are for a specific device, package type, and minimum speed grade for each device family
supported. These values are shown in Table 5.1.
Table 5.1. Supported Devices for Reference Design
Device Family
Device
Package
Minimum Speed Grade
LatticeECP3
LFE3-95EA
1156-ball fpBGA
–7
ECP5(for 3G)
LFE5UM-85F
756-ball fpBGA
–7
ECP5(for 5G)
LFE5UM5G-45F
381-ball CABGA
–8
5.1.1. Test Bench
The template logic shown in Figure 2.4 on page 11 which is delivered with the IP core, contains the REC configuration. A
sample user application (to be removed and replaced with your own application) is included along with the sample toplevel. The user application logic, which is delivered in the template, includes circuitry which can be used to test the CPRI
IP core. This circuitry consists of pseudo-random number generators for the fast and slow C&M channels, as well as
circuits which insert numbered words into the user IQ data and the vendor specific channels. The delivery also includes
a testbench that connects the top-level template logic as an REC interface, and has test data being sent from the
transmitter to the receiver, as shown in Figure 5.1.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
40
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Sample User
Application Logic
Included with
Delivery
Fast C&M
Random
Data Gen
Slow C&M
Random
Data Gen
ch 1 - REC
PCS/SERDES
IQ Data
Numbered
Word Gen
Tx
Rx
VendorSpecific
Data Num
Pattern
Checkers
Figure 5.1. Pattern Generators and Checkers Included with Delivered IP Core Testbench (One Direction Shown)
5.1.2. Register Descriptions
There are no user accessible registers within the core. All control and status appear as internal I/O at the core
boundary. For none-5G version, registers are provided at the top (template) level to drive and monitor all the control
and status that interfaces with the core. These registers are shown in Table 5.2. Additional registers supporting the low
latency core configuration are described in IPUG74, CPRI IP Core Low Latency Variation Design Considerations User’s
Guide.
Table 5.2. CPRI Testbench Register Map
Register Name
Register
Address
Bit Position
Bit Name
Description
CPRI Control 0
0x800
4:0
lbr[1:0] – Line Bit Rate
Control
For maximum CPRI line
rate enabled by user
00 = 614.4 MHz
01 = 1228.8 MHz
10 = 2457.6 MHz
11 = 2457.6 MHz
FORCE_SM_STANDBY –
Forces startup state
machine to standby
zero to one transition
PCS_SERDES_RATE[1:0] –
Line rate supported by
PCS/SERDES
00 = 614.4 MHz
01 = 1228.8 MHz
10 = 2457.6 MHz
11 = 2457.6 MHz
CPRI Control 1
0x801
1:0
TX_L1_SDI TX_L1_RAI
SAP defect indication and remote action
indication
CPRI Control 2
0x802
5:0
TX_BFN_RST_EN
TX_HYP_RST_EN
HDLC_1920_EN
HDLC_960_EN
HDLC_480_EN
HDLC_240_EN
Enable = 1
Disable = 0
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
41
CPRI IP Core
User Guide
Table 5.2. CPRI Testbench Register Map (continued)
Register Name
Register
Address
Bit Position
Bit Name
Description
CPRI Control 3
0x803
5:0
TX_ETH_POINTER
Tx Ethernet pointer value
CPRI Control 4
0x804
0
TX_L1_RST_RQSTACK
Source for down link reset request or up
link reset acknowledge
CPRI Error Reg 0
0x805
7:5,3:0
RX_LOF RX_LOS
VER_NUM_ERR
PRO_INTRUPT
RX_ETH_FULL
RX_ETH_EMPTY
TX_ETH_FULL
TX_ETH_EMPTY
Rx loss of frame
Rx loss of signal
Version number error bit
Processor interrupt
Ethernet FIFO error bits
CPRI Status Reg 0
0x806
1:0
RATE_MODE
Final negotiated line bit rate
CPRI Status Reg 1
0x807
7:0
RX_LOF RX_LOS
VER_NUM_ERR RX_L1_LOF
RX_L1_LOS RX_L1_SDI
RX_L1_RAI
RX_L1_RST_RQSTACK
Rx loss of frame
Rx loss of signal
Version number error bit Received L1
inband protocol bits of byte Z.130.0
VERSION Reg
0x808
7:0
RX_L1_VER_NUM
Received L1 inband protocol bits of byte
Z.2.0
CPRI Status Reg 2
0x809
5:0
RX_L1_ETH_POINTER
Received L1 inband protocol bits of byte
Z.194.0
CPRI Status Reg 3
0x80a
6:4, 2:0
RX_L1_HDLC_MODE[2:0]
TX_HDLC_MODE[2:0]
Received L1 inband protocol bits of byte
Z.66.0
Final negotiated HDLC bit rate
CPRI Status Reg 4
0x80b
2:0
CPRI_STUP_STATE
CPRI start up state
Test Control
0x80c
1:0
7 – Core reset, used if core
reset port is not connected
to GSR
1 – TEST_MD Test mode,
1 = short time
0 – REC_MD, REC mode,
1 = REC, 0 = RE
Test Loop Data Error Reg
0x80d
3:0
Rx_hdlc_pdo_da_err
Vendor_pdo_da_err
Rx_iq_da_err
Rx_eth_pdo_da_err
Test bench check loop back data errors
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
42
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Table 5.2. CPRI Testbench Register Map (continued)
Register Name
Register
Address
Bit Position
Bit Name
Description
TB_CNTRL
0x80E
0
TB_CNTRL [0]
If 0: Check IQ data based on Numbered
Word Gen. If 1: Fill data message with
value in register TB_RXIQ
1
TB_CNTRL [1]
If 0: Check VENDOR Data based on Data
Num. If 1: Fill data message with value in
register TB_RXVEND
2
TB_CNTRL [2]
If 0: Check ETHR C/M based on random
Data Gen. If 1: Fill ETHR C/M with value in
register TB_RXETHR
3
TB_CNTRL [3]
If 0: Check HDLC C/M based on random
Data Gen. If 1: Fill HDLC C/M with value in
register TB_RXHDLC
4
TB_CNTRL [4]
If 0: Generate IQ data based on
Numbered Word Gen. If 1: Fill data
message with value in register TB_TXIQ
5
TB_CNTRL [5]
If 0: Generate VENDOR data based on
Data Num. If 1: Fill data message with
value in register TB_TXVEND
6
TB_CNTRL [6]
If 0: Generate ETHR C/M based on
random Data Gen. If 1: Fill ETHR C/M with
value in register TB_TXETHR
7
TB_CNTRL [7]
If 0: Generate HDLC C/M based on
random Data Gen. If 1: Fill HDLC C/M with
value in register TB_TXHDLC
TB_TXHDLC
0x80F
7:0
TB_TXHDLC
This byte is used to fill HDLC messages
when TB_CNTRL [7] is set to 1.
TB_TXETHR
0x810
7:0
TB_TXETHR
This byte is used to fill ETHR messages
when TB_CNTRL [6] is set to 1.
TB_TXVEND
0x811
7:0
TB_TXVEND
This byte is used to fill VEND messages
when TB_CNTRL [5] is set to 1.
TB_TXIQ
0x812
7:0
TB_TXIQ
This byte is used to fill IQ messages when
TB_CNTRL [4] is set to 1.
TB_RXHDLC
0x813
7:0
TB_RXHDLC
This byte is used to check HDLC messages
when TB_CNTRL [3] is set to 1.
TB_RXETHR
0x814
7:0
TB_RXETHR
This byte is used to check ETHR messages
when TB_CNTRL [2] is set to 1.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
43
CPRI IP Core
User Guide
Table 5.2. CPRI Testbench Register Map (continued)
Register Name
Register
Address
Bit Position
Bit Name
Description
TB_RXVEND
0x815
7:0
TB_RXVEND
This byte is used to check VEND messages
when TB_CNTRL [1] is set to 1.
TB_RXIQ
0x816
7:0
TB_RXIQ
This byte is used to check IQ messages
when TB_CNTRL [0] is set to 1.
TB_HDLC_CNT_HB
0x900
7:0
TB_HDLC_CNT [15:8]
HDLC message bit error counter, high
byte. A read of this register latches both
bytes and clears the internal counter. The
internal counter freezes at maximum
count.
TB_HDLC_CNT_LB
0x901
7:0
TB_HDLC_CNT [7:0]
HDLC message bit error counter, low
byte.
TB_ETHR_CNT_HB
0x902
7:0
TB_ETHR_CNT [15:8]
ETHR message bit error counter, high
byte. A read of this register latches both
bytes and clears the internal counter. The
internal counter freezes at maximum
count.
TB_ETHR_CNT_LB
0x903
7:0
TB_ETHR_CNT [7:0]
ETHR message bit error counter, low byte.
TB_VEND_CNT_HB
0x904
7:0
TB_VEND_CNT [15:8]
TB_VEND_CNT_LB
0x905
7:0
TB_VEND_CNT [7:0]
TB_IQ_CNT_HB
0x906
7:0
TB_IQ_CNT [15:8]
VEND message bit error counter, high
byte. A read of this register latches both
bytes and clears the internal counter. The
internal counter freezes at maximum
count.message bit error counter, low
VEND
byte.
IQ message bit error counter, high byte. A
read of this register latches both bytes
and clears the internal counter. The
internal counter freezes at maximum
count.
IQ
message bit error counter, low byte.
TB_IQ_CNT_LB
0x907
7:0
TB_IQ_CNT [7:0]
TB_ERRINJ
0x817
0
TB_ERRINJ [0]
1
TB_ERRINJ [1]
2
TB_ERRINJ [2]
3
TB_ERRINJ [3]
7:4
UNUSED
7:0
SUBCH_SAMPLE
SUBCH_SAMPLE
0x818
Inject an IQ message bit error each time
this bit is changed from 0 to 1
Inject an VEND message bit error each
time this bit is changed from 0 to 1
Inject an ETHR message bit error each
time this bit is changed from 0 to 1
Inject an HDLC message bit error each
time this bit is changed from 0 to 1.
UNUSED
The CPRI Design will sample bit 0 of
0x00818 and initiate a memory sample of
all the 64 subchannels when that bit is 1.
When the CPRI Design memory sample is
done, the CPRI Design will clear 0x00818.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
44
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Table 5.2. CPRI Testbench Register Map (continued)
Register Name
Register
Address
Bit Position
Bit Name
Description
SUBCH_MEM
0x819
7:0
SUBCH_MEM
When the CPRI Design clears 0x00818,
the first byte (OFFSET=0) of the sampled
1024 SUBCHANNEL BYTES will be available
at 0x819. Once a read access is performed on 0x819 to sample OFFSET Byte
0, the next available byte (OFFSET=1) will
be available at 0x819 for the subsequent
read access. Subsequent read accesses
will access the subsequent bytes of
SUBCH_MEM.
TB_ETH_IDLE_HB
0x81A
5:0
TB_ETH_IDLE_SIZE_HB
Testbench Ethernet Idle size High Byte This is the upper 6 bits of a constant used
to set the number of nibbles of idle in the
ethernet message generated by the testbench.
TB_ETH_IDLE_LB
0x81B
7:0
TB_ETH_IDLE_SIZE_LB
Testbench Ethernet Idle size Low Byte This is the lower 8 bits of a constant used
to set the number of nibbles of idle in the
ethernet message generated by the testbench.
TB_ETH_DATA_HB
0x81C
5:0
TB_ETH_DATA_SIZE_HB
Testbench Ethernet Data size High Byte This is the upper 6 bits of a constant used
to set the number of nibbles of data in the
ethernet message generated by the testbench.
TB_ETH_DATA_LB
0x81D
7:0
TB_ETH_DATA_SIZE_LB
Testbench Ethernet Data size Low Byte This is the lower 8 bits of a constant used
to set the number of nibbles of data in the
ethernet message generated by the testbench.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
45
CPRI IP Core
User Guide
References
Complete details on the CPRI IP core low latency configuration are provided in IPUG74, CPRI IP Core Low Latency
Variation Design Considerations User's Guide.
For additional information, refer to:
DS1021, LatticeECP3 Family Data Sheet
FPGA-DS-02012 (previously DS1044), ECP5 and ECP5-5G Family Data Sheet
JEDEC Standard, Serial Interface for Data Converters, JESD204B.01, July 2012, www.jedec.org
Technical Support Assistance
Submit a technical support case through www.latticesemi.com/techsupport.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
46
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
Appendix A. Resource Utilization
This appendix provides resource utilization information for Lattice FPGAs using the CPRI IP core.
IPexpress is the Lattice IP configuration utility, and is included as a standard feature of the Diamond and ispLEVER
design tools. Details regarding the usage of IPexpress can be found in the IPexpress and Diamond or ispLEVER help
system. For more information on the Diamond design tools, visit the Lattice website at
www.latticesemi.com//Products/DesignSoftware.
LatticeECP3-FPGAs
Table A.1. Resource Utilization*
Mode
Slices
LUTs
Registers
sysMEM EBRs
Serial
1139
1359
1522
4
Matched
1342
1714
1632
2
Fixed
1433
1848
1691
6
*Note: Performance and utilization data are generated targeting an LFE3-95E-7FN1156CES device using Lattice Diamond 3.2 and
Synplify Pro for Lattice I-2013.09L-SP1-1 software. Performance may vary when using a different software version or targeting a
different device density or speed grade within the LatticeECP3 family.
Ordering Part Number
The Ordering Part Number (OPN) for the CPRI IP core targeting LatticeECP3 devices is CPRI-E3-U4.
ECP5 FPGAs (for 3G Version)
Table A.2. Resource Utilization*
Mode
Slices
LUTs
Registers
sysMEM EBRs
Serial
1235
1517
1480
4
Matched
1452
1861
1590
2
Fixed
1473
1980
1646
6
*Note: Performance and utilization data are generated targeting an LFE5UM-85F-7BG756C device using Lattice Diamond 3.2 and
Synplify Pro for Lattice I-2013.09L-SP1-1 software. Performance may vary when using a different software version or targeting a
different device density or speed grade within theECP5UM family.
Ordering Part Number
The Ordering Part Number (OPN) for the CPRI IP core targeting LFE5UM devices is CPRI-E5-U and CPRI-E5-UT.
ECP5 FPGAs (for 5G Version)
Table A.3. Resource Utilization*
Mode
Slices
LUTs
Registers
sysMEM EBRs
Serial
952
1033
1036
4
Matched
1150
1314
1162
2
Fixed
1315
1548
1224
6
Ordering Part Number
The Ordering Part Number (OPN) for the CPRI IP core targeting LFE5UM devices is CPRI-E5G-U and CPRI-E5G- UT.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
47
CPRI IP Core
User Guide
Revision History
Date
July 2017
Document
Version
2.8
IP Core
Version
1.0 (for 5G version)
Change Summary
Changed document number from IPUG56 to
FPGA-IPUG-02029.
Updated document template.
Updated supported Diamond version in Table 1.2,
CPRI IP Core Quick Facts (5G Version)
Updated Table 2.1, CPRI I/O Signal Descriptions.
Revised lbr_en description
Revised pcs_serdes_rate and rate_mode
Width (Bits)
Corrected LatticeECP3 device in Table 5.1,
Supported Devices for Reference Design.
October 2016
2.7
Beta (for 5G
version)
Updated Table 1.2, CPRI IP Core Quick Facts (5G
Version). Changed the FPGA family to ECP5-5G
and the Diamond version to 3.8.
Changed heading to ECP5/ECP5-5G in the
References section.
Corrected IP Core Version in Revision History.
2.6
April 2014
Beta (for 5G
version)
Added support for 4.9152 Gbps line rate.
General updates in all chapters.
02.5
5.0asr
General updates in all chapters.
02.4
5.0asr
Added support for Diamond 3.2.
Added support for ECP5 device family.
Updated document with new corporate logo.
Updated Lattice Technical Support information.
September 2010
02.3
3.3
Added support for Diamond software throughout.
Added new content in IP Core Generation.
June 2010
02.2
3.2
Divided the document into chapters and added
table of contents.
Added Quick Facts tables in Introduction.
Added new content in IP Core Generation.
November 2009
02.1
3.2
Updated LatticeECP3 3G line rate TX HDLC
support.
Updated utilization tables with ispLEVER 8.0.
May 2009
02.0
3.0
Updated to include LatticeECP3 and 3G line rate
support.
Updated for enhanced fast C&M packet check for
Fixed Ethernet mode, and support for back-toback Ethernet packet in the CPRI link.
September 2008
01.9
2.7
Updated Introduction text section.
August 2008
01.8
2.7
Updated Figure 2.9, Rx IQ Interface Data and
Frame Number Alignment diagram.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
48
FPGA-IPUG-02029-2.8
CPRI IP Core
User Guide
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
FPGA-IPUG-02029-2.8
49
CPRI IP Core
User Guide
Revision History (continued)
Date
August 2008
Document
Version
01.7
IP Core
Version
2.7
Change Summary
Updated Introduction section to include
information regarding the v3.0
CPRI specification, requirement R-31 (line rate
auto-negotiation).
Removed the Core Generation text section.
Removed the Instantiating the Core text section.
Removed the Running Functional Simulation text
section.
Removed the Synthesizing and Implementing the
Core in a Top-Level
Design text section.
Removed the Hardware Evaluation text section.
June 2008
01.6
2.7
Included information for Aldec, ModelSim, mixed
mode, and rtl/gate simulation.
Added information for low latency variation IP
configuration.
May 2008
01.5
2.7
Added information for txrst and rxrst to Signal
Descriptions table.
Added information about using this IP core with
the Linux operating system.
September 2007
01.4
2.4
References to tx_eth_pointer[7:0] replaced with
tx_eth_pointer[5:0].
July 2007
01.3
2.3
Updated LatticeSC/M and LatticeECP2M/S
appendices.
Added support for LatticeECP2MS.
April 2007
01.2
2.2
Input lbr_en was expanded from 2 bits to 4 bits.
The additional three bits provide two functions.
Function 1: Adds the ability to force the Startup
state machine to the standby state.
Function 2: Adds the ability to tell the core which
rate the PCS/SERDES supports.
These functions were added to make the rate
selection process work properly.
January 2007
01.1
2.0
Updated to include LatticeECP2M.
September 2006
01.0
1.0
Initial release.
© 2006-2017 Lattice Semiconductor Corp. All Lattice trademarks, registered trademarks, patents, and disclaimers are as listed at www.latticesemi.com/legal. All other brand or product names are
trademarks or registered trademarks of their respective holders. The specifications and information herein are subject to change without notice.
50
FPGA-IPUG-02029-2.8
7th Floor, 111 SW 5th Avenue
Portland, OR 97204, USA
T 503.268.8000
www.latticesemi.com
工商网监
湘ICP备2023018690号
