![](http://datasheet.mmic.net.cn/Lattice-Semiconductor-Corporation/ORT8850L-3BM680C_datasheet_99201/ORT8850L-3BM680C_49.png)
Lattice Semiconductor
ORCA ORT8850 Data Sheet
49
Clock and Data Timing at the FPGA/Embedded Core Interface - SONET Block
(Note: This section assumes a basic understanding of the Lattice Semiconductor ispLEVER design tool set)
This section provides examples of the clock and data timing relationships at the FPGA/Embedded Core interface
for both the parallel SONET data and the serial TOH data. The initiation of a change of data is referred to as the
"launch" time and the actual time of capture of the data is referred to as the "capture" time. Two relationships are
discussed, the relationship between data and clock at the interface itself and the relative timing constraints on the
signals in the FPGA logic between the interface and the launch/capture latch in the FPGA portion of the FPSC.
The ispLEVER place and route tool will automatically attempt to meet the timing constraints by placing a frequency
constraint on the corresponding clock and will report a non-routed condition if it is unable to do so. Trace reports
should also be generated using ispLEVER to evaluate both the setup and the hold margins.
The typical timing numbers used in the discussions are for illustration purposes and can vary due to both process
and environmental variations and to differences in the routing through the FPGA logic, especially for the data path.
Exact timing numbers should always be obtained from ispLEVER.
In all of the discussions in this section, the maximum reference clock frequency of 106 MHz is assumed. The pri-
mary clock path delay was assumed to be 3 ns - this delay is well controlled in the FPGA logic. A secondary clock
path delay can vary from 1 to 3.5 ns - a delay of 2.5 ns was used in the payload data discussions and 2 ns for the
TOH discussions.
The ve cases considered in the discussion are shown in
Table 16. The clock routing and timing congurations
shown in this section are recommended for the general user since they give the best timing margins. In the discus-
sion, if both the core and FPGA launch and latch data on the same edge, it is referred to as a "full cycle" mode. If
they launch and latch on different edges, it is referred to as a "half cycle" mode.
TOH_xx_EN
O
Indicates state of register settings for TOHxx_EN
PROT_SWITCH_AA
I
Parallel protection switch select, Channels AA and AB
PROT_SWITCH_AC
I
Parallel protection switch select, Channels AC and AD
PROT_SWITCH_BA
I
Parallel protection switch select, Channels BA and BB
PROT_SWITCH_BC
I
Parallel protection switch select, Channels BC and BD
LVDS_PROT_AA
I
LVDS protection switch select, Channel AA
LVSD_PROT_AB
I
LVDS protection switch select, Channel AB
LVDS_PROT_AC
I
LVDS protection switch select, Channel AC
LVDS_PROT_AD
I
LVDS protection switch select, Channel AD
LVDS_PROT_BA
I
LVDS protection switch select, Channel BA
LVDS_PROT_BB
I
LVDS protection switch select, Channel BB
LVDS_PROT_BC
I
LVDS protection switch select, Channel BC
LVDS_PROT_BD
I
LVDS protection switch select, Channel BD
Table 15. FPGA/Embedded Core Interface Signals (Continued)
ORT8850 FPGA/Embedded Core Interface Signals - SONET Blocks
FPGA/Embedded Core
Interface Signal Name
xx=[AA,…,BD]
Input (I) to or Output (O)
from Core
Signal Description