System Requirements.................................................................................................................................. 1-1
Program and File Types.............................................................................................................................. 1-3
JNEye Control Module................................................................................................................................2-1
Constructing Communication Links in the Link Designer Module........................................ 2-1
Link and Simulation Setting...........................................................................................................2-6
Setup and Initialization...............................................................................................................................3-6
Setting Up the Control Module..................................................................................................... 3-6
Constructing the Channel.............................................................................................................3-10
Completing the System................................................................................................................. 3-13
Setup and Initialization...............................................................................................................................4-3
Setting Up the Control Module..................................................................................................... 4-4
Constructing the Channel...............................................................................................................4-6
Completing the System................................................................................................................... 4-9
How to Contact Altera................................................................................................................................ 5-2
Altera Corporation
2015.05.04
www.altera.com
101 Innovation Drive, San Jose, CA 95134
System Requirements and Installation Guide
1
UG-1146
Subscribe
Send Feedback
JNEye is a high-speed transceiver link simulation. When you design high-speed, multi-gigabit transceiver
links, you must ensure the end-to-end performance from transmitter (TX) to receiver (RX) and all
interconnects in between.
JNEye's graphical user interface (GUI) and link simulator allow you to quickly and easily set up and
evaluate high-speed link performance early in your design cycle. JNEye also helps you identify possible
issues in board level design. With JNEye, you can quickly estimate optimal link equalization and other
electrical parameter settings for transmitter and receiver. You can also use JNEye to predict link perform‐
ance such as jitter and noise at a small probability level.
System Requirements
JNEye has the following minimum system requirements:
• Microsoft Windows XP, Windows 7, or Windows 8
• 4 GB RAM
• 3 GB storage space
• Microsoft .NET Framework 4
JNEye requires a Quartus® II software subscription license to perform simulations, design channels, and
view channel characteristics. Contact your Altera sales representative or your system administrator if you
have questions regarding accessing the Quartus II software subscription license.
2015 Altera Corporation. All rights reserved. ALTERA, ARRIA, CYCLONE, ENPIRION, MAX, MEGACORE, NIOS, QUARTUS and STRATIX words and logos are
trademarks of Altera Corporation and registered in the U.S. Patent and Trademark Office and in other countries. All other words and logos identified as
trademarks or service marks are the property of their respective holders as described at www.altera.com/common/legal.html. Altera warrants performance
of its semiconductor products to current specifications in accordance with Altera's standard warranty, but reserves the right to make changes to any
products and services at any time without notice. Altera assumes no responsibility or liability arising out of the application or use of any information,
product, or service described herein except as expressly agreed to in writing by Altera. Altera customers are advised to obtain the latest version of device
specifications before relying on any published information and before placing orders for products or services.
ISO
9001:2008
Registered
1-2
Installation
Installation
To install JNEye, perform the following steps:
1. Acquire the JNEye 15.0 Installation Package from the Altera Download Center.
2. Execute the installation file to install JNEye.
a. To improve the performance of the JNEye 64-bit version, the JNEye Installer asks for administra‐
b. If the installer cannot get administration-level access, the installation installs both 32-bit and 64-bit
c. If the installer can acquire the administration-level access (given user approval/acknowledge), the
3. Execute JNEye.exe to start JNEye. The JNEye 15.0 release comes with both 32-bit and 64-bit executa‐
bles. 32-bit JNEye is located in <JNEye Installation Directory>\bin and 64-bit JNEye is in <JNEye
Installation Directory>\bin64.
JNEye requires an Altera Quartus II Subscription License to perform simulations and view channel
characteristics. Contact your Altera sales/supports or your system administrator if you have questions
about obtaining an Altera Quartus II Subscription License.
UG-1146
2015.05.04
tion-level access right to install additional Microsoft .NET components.
JNEye components. You can install the additional .NET components after installation when you
can grant administration-level access to your computer.
installer automatically includes and installs the additional .NET components. The installation
process is much longer (can exceed 10 minutes) than previous JNEye releases.
JNEye automatically checks the license server specified in the system environment variable
“LM_LICENSE_FILE” for the required license. The license checking configuration can be configured by
editing the following entries in the configuration file JNEye_Config.dat:
• %% LM_License_File_Name—License file name. If a license server is used, this entry is ignored. The
default value is na. JNEye automatically checks whether a license server exists. If a valid license server
does not exist, JNEye checks the individual license file specified in this entry.
• %% LM_License_Feature_Name—The feature or type of license to be checked out for JNEye use. The
default value is quartus.
When you execute JNEye for the first time, JNEye may ask permission to create a JNEye working
directory at <JNEye Installation Directory>\GUI_Work.
Click Yes to use the default location. To use a different working directory, modify the “%% GUIWorkDir‐
ectory” entry in JNEye_Config.dat.
Altera Corporation
System Requirements and Installation Guide
Send Feedback
UG-1146
2015.05.04
Program and File Types
If you have problems running JNEye after installing the program, follow these instructions:
• Check whether the Microsoft Visual C++ 2013 library is on your system
• If you execute JNEye in a system that doesn't have the Microsoft Visual C++ 2013 library, you will
get an error message.
• Download the Visual C++ 2013 library from the Microsoft web site and install it.
Note: For 64-bit Windows operating systems, the 32-bit version of the Visual C++ 2013 library is
required for running the 32-bit version JNEye.
• Check whether Microsoft .NET Framework 4 is on your system
• If you execute JNEye Release in a system that doesn't have Microsoft .NET Framework 4, you will
get an error message.
• Download .NET Framework 4.0 from the Microsoft web site and install it.
• .jnetxdata, .jnerxdata, .jnedevdata, .jneledata, and others—JNEye internal data
When you want to share a JNEye link configuration, both .jne and .jneschm files are needed for other users
to reload the link configuration in his or her JNEye session. Make sure all other associated files, such as
channel model files and device model files, are included so that simulations can be run correctly. JNEye
provides limited backward compatibility with link configuration files saved in previous versions.
System Requirements and Installation Guide
Send Feedback
Altera Corporation
2015.05.04
www.altera.com
101 Innovation Drive, San Jose, CA 95134
Functional Description
2
UG-1146
Subscribe
JNEye Control Module
Double-click the JNEye.exe icon to launch JNEye.
Figure 2-1: JNEye Control Module
Send Feedback
Constructing Communication Links in the Link Designer Module
The Link Designer module allows you to construct communication links.
2015 Altera Corporation. All rights reserved. ALTERA, ARRIA, CYCLONE, ENPIRION, MAX, MEGACORE, NIOS, QUARTUS and STRATIX words and logos are
trademarks of Altera Corporation and registered in the U.S. Patent and Trademark Office and in other countries. All other words and logos identified as
trademarks or service marks are the property of their respective holders as described at www.altera.com/common/legal.html. Altera warrants performance
of its semiconductor products to current specifications in accordance with Altera's standard warranty, but reserves the right to make changes to any
products and services at any time without notice. Altera assumes no responsibility or liability arising out of the application or use of any information,
product, or service described herein except as expressly agreed to in writing by Altera. Altera customers are advised to obtain the latest version of device
specifications before relying on any published information and before placing orders for products or services.
ISO
9001:2008
Registered
2-2
Constructing Communication Links in the Link Designer Module
Figure 2-2: JNEye Link Designer Module
Table 2-1: Supported Transmitter, Channel, and Receiver Components
Altera Stratix V GX
Altera Arria V GZ
Altera Stratix V GT
Altera Arria 10 GX/SX
Altera Arria 10 GT
IBIS-AMI
Custom
PCI-Express 8GT
JNEye supports the following simulations:
• Altera TX to Altera RX
• Altera TX to non-Altera RX
• Non-Altera TX to Altera RX
Non-Altera to non-Altera link simulations are not supported.
Note:
A link consists of a transmitter, a receiver, and one or more channel components. Select the transmitter,
receiver, and channel components from the menus at the top of the Link Designer workspace.
After the link components are placed into the workspace, click Connect to connect the components. In
connect mode, one or two connectors are shown on each component. Connect the link components by
dragging the line from one connector to another. Two types of connections are provided in Link
Designer: Right Angled Line and Straight Line. Right Angled Line is the default connection method. Test
Altera Corporation
Functional Description
Send Feedback
UG-1146
2015.05.04
Constructing Communication Links in the Link Designer Module
points can be manually placed into the link by clicking Test Point and connecting to the desired location
in the link.
The following rules of link construction apply to the Link Designer module:
• A transmitter can only have one output port or connector
• A receiver can only have one input port or connector
• A channel component has one input and one output port
• A test point can only be connected to an input port
• A connection between two components can be established from an output port to an input port
• A transmitter cannot be connected directly to a receiver
A link establishment checking algorithm runs constantly in the background, checking whether a link is
established for simulations. When a link is established between a transmitter and receiver, the link lines
become bold and color-coded. Bold black lines indicate signal paths, green lines indicate crosstalk signal
paths, and purple lines point to test point port locations. The following figure shows an example link
topology. A table of link components is displayed in the Channel tab for reference.
Figure 2-3: JNEye Link Designer with Channel Table
2-3
When a channel component (for example, a transmission line, connector, far-end crosstalk (FEXT), nearend crosstalk (NEXT), package, AC coupling capacitor, or shunt capacitor) is chosen, the ChannelWizard helps you verify or set the channel configuration.
Functional Description
Send Feedback
Altera Corporation
2-4
Constructing Communication Links in the Link Designer Module
Figure 2-4: JNEye Channel Wizard
UG-1146
2015.05.04
The Channel Wizard displays the channel characteristics and allows you to verify the correctness of the
channel component, such as a component represented by an S-parameter. The Channel Wizard allows
you to select a channel type, port configuration, signal lanes (for multiple-lane S-parameters with eight
and more ports), crosstalk aggressor location (for multiple-lane S-parameters), aggressor, series
inductance value (in nH), AC coupling capacitor value (in nF), and shunt capacitance value (in pF). The
Channel Wizard checks the integrity of the channel component in terms of passivity and causality
characteristics. When the Channel Wizard detects passivity and causality violations, it displays messages
about the severeness of the violations in the text box on the left of the OK button. The levels of channel
integrity violation are listed in the following tables.
Table 2-2: Channel Passivity Check Results and Recommendations
Passivity Violation Check
Results
Impact on Link Simulation
Accuracy
No Passivity ViolationNo impactNo action needed
Altera Corporation
Recommendations
Functional Description
Send Feedback
UG-1146
2015.05.04
Constructing Communication Links in the Link Designer Module
2-5
Passivity Violation Check
Results
Slight Passivity ViolationThere may not be a noticeable
Impact on Link Simulation
Accuracy
effect in the simulation result
The channel model can be further
improved but the improvement in terms of
simulation results accuracy can be small.
Minor Passivity ViolationThere may be a noticeable
effect in the simulation result
The channel model can be further
improved. The differences in terms of
simulation results and accuracy are
expected.
Passivity ViolationSimulation result will be
impacted
The channel model needs to be regenerated
(by design tools) or re-taken (by
instruments). The confidence of simulation
results using this channel model is low.
Table 2-3: Channel Causality Check Results and Recommendations
Causality Violation Check
Results
Impact on Link Simulation
Accuracy
Channel is causalNo impactNo action needed
Slight non-causalThere may not be a noticeable
effect in the simulation result
The channel model can be further
improved but the improvement in terms of
simulation results accuracy can be small.
Recommendations
Recommendations
Somewhat non-causalThere may be a noticeable
effect in the simulation result
The channel model can be further
improved. The differences in terms of
simulation results and accuracy are
expected.
Non-causalSimulation result will be
impacted
The channel model needs to be regenerated
(by design tools) or re-taken (by
instruments). The confidence of simulation
results using this channel model is low.
To select another S-parameter within the Channel Wizard, click Change Channel.
Altera recommends that you replace or change a channel with one of the same channel type. Link
Note:
Designer allows channel changing with different channel types, but you might see inconsistent
channel icons in the design workspace.
An existing channel can be changed by adding a new channel component or by modifying an existing
channel component. Right-click in the Link designer module and select Properties.
When using the package channel component, follow these guidelines:
• Package models should be placed next to the devices.
• Each device can have only one package model. Therefore, the external package model can only be used
when the device’s package type is “Custom”.
• The package model type is used by the simulation engine to identify the boundary of the devices and
generate a waveform for observation and analysis.
• The package model is treated the same way as the “Transmission” channel type. Therefore, use the
“Transmission” channel type even if the model represents a physical package (in your system) but it is
not a package of the TX and RX.
Functional Description
Send Feedback
Altera Corporation
2-6
Link and Simulation Setting
Link and Simulation Setting
The Link and Simulation Setting tab sets the global link parameters and simulation configurations.
Figure 2-5: Link and Simulation Setting Tab
UG-1146
2015.05.04
The Link and Simulation Setting dialog box contains the following fields.
Data Rate
Link data rate is specified in Gbps.
Simulation Length
Simulation length is specified in the number of bits running at the specified data rate. Simulation length
should be at least 4096 bits. Altera recommends that the length is a power-of-2 factor for the best
computation efficiency. The simulation length does not apply in Statistical mode.
Simulation length is adjusted automatically to the closest power-of-2 factor.
Note:
Target BER
Target bit error rate is used to calculate the jitter and noise at low BER conditions. The methodology of
jitter and noise at low BER can be found in HST Jitter and BER Estimator Tool User Guide for Stratix IVGT and GX Devices.
Altera Corporation
Functional Description
Send Feedback
UG-1146
2015.05.04
Link and Simulation Setting
Test Pattern
Allows you to specify the test pattern used in the simulation. The following test patterns are available:
• PRBS-7, PRBS-9, PRBS-11, PRBS-15, PRBS-23, and PRBS-31
• The PRBS test patterns are generated using JNEye’s built-in pattern generator.
• If the whole PRBS pattern is shorter than the simulation length, the PRBS pattern is inverted and
repeated. The inversion is applied to achieve DC balance of the generated PRBS test pattern.
• If the PRBS patterns are longer than the simulation length, a partial test pattern of the PRBS pattern
is used. The default initial condition of PRBS test pattern generation is with logic 1s in all shift
registers for the valid PRBS patterns.
• The most commonly used PRBS test patterns are listed in the Test Pattern menu. Other PRBS test
pattern can be selected or configured in the Pattern Designer.
2-7
Functional Description
Send Feedback
Altera Corporation
2-8
Link and Simulation Setting
• Pattern Designer—Allows you to specify your own custom test patterns. The following figure shows
the Pattern Designer user interface.
Figure 2-6: JNEye Pattern Designer
UG-1146
2015.05.04
Altera Corporation
The Pattern Designer includes the following test pattern generation methods:
• PRBS—Provides an extensive list of common PRBS test patterns. You can also specify custom
PRBS polynomials and seeds. The internal linear feedback shift register (LFSR) engine uses the
information to generate the desired test pattern. Other options include selecting how the test
pattern is repeated or extracted when the simulation length is longer or shorter than the generated
test patterns. There are two options for selecting the partial test patterns:
• Use First Part of Generated PRBS Sequence
• Include Longest Run-Length Bit Sequence—The longest run-length test pattern will be located
at the ending portion of the test bit sequence.
• Consecutive Bit Patterns—Defines the test patterns with repeating patterns.
• Clock—Generates a clock-like pattern.
• All 1's—Generates an all-ones test pattern that usually feeds into a coder or scrambler.
• All 0's—Generates an all-zeros test pattern that usually feeds into a coder or scrambler.
• Encoder and Scrambler—JNEye supports the following encoders and scramblers: 8B/10B, 64B/66B, 64B/67B, and 128B/130B.
Functional Description
Send Feedback
UG-1146
2015.05.04
Link and Simulation Setting
• Custom—Click the open-file dialog button to select a custom test pattern file.
Figure 2-7: Custom Test Pattern File Browser Button
The custom pattern files are in the following formats:
• Hexadecimal—Hexadecimal strings start with 0x. For example, a PRBS-7 test pattern can be
specified by 0x8cd501fbe7ae1ba62b05e3b64a4272d0. The custom file name must have a .hex
extension.
• Binary—Binary strings have a format such as "001000111…". Blank characters and new lines/
returns are allowed in the input binary string file. The custom file name must have a .bin extension.
2-9
Note:
The custom test pattern has a maximum text length of 262,142 characters (about 1M bits with a
hexadecimal text format or about 246K bits with a binary text format). Altera recommends that
the test pattern string (hexadecimal or binary) is specified in a single row without spaces,
especially for long custom test patterns. If a custom test pattern is input with multiple lines of
text, the line returns or end-of-line control characters on each line of text are counted as an item
or entry by the text parser.
Reference Clock
Specifies the reference clock that feeds into the transmitter. The supported clock frequencies are shown in
MHz. By default, the reference is assumed to be ideal without any noise or jitter. You can configure and
specify the reference clock characteristics by clicking Reference Clock Option.
The reference clock can be fed to a transmitter with or without enabling a phase-locked loop (PLL)
module. When the transmitter PLL is disabled or not present, the reference clock noise and jitter directly
affects the serial output signal.
With integer PLLs, JNEye supports an integer divider ratio between the data rate and the reference clock
frequency. If the ratio is not an integer, the reference clock frequency is rounded to the closest integerdivided-ratio frequency. The actual reference clock frequency used in the simulation is displayed in the
message box next to the pull-down menu. With fractional-N PLLs, fractional divider ratios are allowed.
In the simulation with specific transmitter devices, such as Arria 10 GX/SX/GT, Stratix V GT, Stratix V
GX, and Arria V GZ devices, the supported data rate to reference clock divider ratios are limited. If a
specific combination of data rate, PLL divider ratio, and reference clock frequency cannot be found, the
reference clock used in the simulation can be further adjusted.
Functional Description
Send Feedback
Altera Corporation
2-10
Link and Simulation Setting
The reference clock frequencies listed are commonly used in most serial link protocols. If you cannot find
the exact reference clock frequency from the list, you can add your reference clock frequency with the
following procedure:
1. Close JNEye.
2. Navigate to the JNEye installation directory. Typically, JNEye is installed in C:\altera\15.0\jneye\.
3. Under the Database folder, find RefCLK_List.jnetxdata.
4. Edit the file by adding your desired reference clock frequencies.
5. Save the change and exit the editor.
6. Restart JNEye.
Reference Clock Option
The reference clock option user interface allows you to configure the characteristics of the reference clock
used in the simulation. The reference clock can be specified with the following methods:
• Ideal Reference Clock—With this setting, the reference clock is ideal without any noise or jitter.
Option 1 configures the reference clock with the following options:
• Random Jitter— Specify the frequency range (in ps).
UG-1146
2015.05.04
Note: Altera recommends that the maximum frequency range (f
reference clock frequency. If the f
linear extrapolation to calculate the phase noise at f
is less than the reference clock frequency, JNEye uses
MAX
MAX
) of the phase noise be set to the
MAX
, which can lead to inaccurate results.
• Periodic Jitter Type—Specify the shape profile, frequency (in Hz), and amplitude (in ps). The shape
profile can be:
• Triangle
• Hershey with programmable Hershey shape parameter
• Sharkfin with programmable Sharkfin shape parameter
• Sinusoidal
• Spurs—Specify clock spectrum spurs with individual frequency (in Hz) and amplitude (in dBc). For
example, if the reference clock has three spurs: –110 dBc at 100 KHz, –90 dBc at 1 MHz, and –80 dBc
at 10 MHz, you can input the following text into the Spurs text box:
100e3 -110
1e6 -90
10e6 -80
• Spur Phase Offset
Use the Spur Phase Offset pull-down menu to configure the initial phase of spur noises. The options
are:
• Auto—JNEye automatically selects the default initial spur noise phase. The default initial spur
phase is 0 rad.
• Random—JNEye randomly sets the initial spur noise phases.
• Zero—JNEye sets the initial spur noise phase to 0 rad.
• Specified—You can manually specify the initial spur phase individually by adding the phase value
after the amplitude value. The following example shows the initial spur noise phases are 1.0, 2.0,
and 3.0 rad.
Option 2 configures the reference clock with the following options:
• Phase Noise—Specify reference clock jitter using a phase noise profile. Reference clock phase noise is
specified with the noise power spectrum described with frequency and amplitude. The above figure
demonstrates a phase noise profile with a measured reference clock phase noise data set.
Note: Altera recommends that the maximum frequency range (f
reference clock frequency. If the f
MAX
linear extrapolation to calculate the phase noise at f
• Spurs—Specify clock spectrum spurs with individual frequency (in Hz) and amplitude (in dBc). For
example, if the reference clock has three spurs: –80 dBc at 100 KHz, –90 dBc at 1 MHz, and –96 dBc at
10 MHz, you can input the following text into the text box:
100e3 -80
1e6 -90
10e6 -96
• Spur Phase Offset—Same as in Option 1 Reference Clock Jitter.
• Periodic Jitter Type—Same as in Option 1 Reference Clock Jitter.
• Plot / Update Plot—You can plot the input phase noise and spurs in the plotting area and confirm the
reference clock characteristics.
Link Optimization Method
JNEye can find optimal transmitter and receiver equalization settings with a user-specified link configura‐
tion.
The TX/RX joint link optimization function is specific to JNEye and may not be supported by the
Note:
transmitter and receiver devices.
Table 2-4: Link Operation Modes Supported by JNEye
) of the phase noise be set to the
MAX
is less than the reference clock frequency, JNEye uses
, which can lead to inaccurate results.
MAX
Transmitter ModeReceiver ModeNotes
ManualManualBoth TX and RX equalizations are manually set.
ManualAutoTX EQ is manually set. JNEye finds optimal RX EQ
setting.
Auto /
AutoJNEye finds both TX and RX EQ settings.
Auto with Manual
Starting Point
JNEye has four link optimization methods for finding the optimal link setting, such as a transmitter preemphasis and receiver CTLE and DFE with a given link configuration.
Altera Corporation
Functional Description
Send Feedback
UG-1146
2015.05.04
Link and Simulation Setting
2-15
• FIR => CTLE => DFE— (default) Optimizes the link performance by finding the optimal transmitter
setting, receiver equalization setting, or both. This method prioritizes the transmitter equalization,
such as pre-emphasis, de-emphasis, or FIR-based, over receiver equalization schemes. However, the
optimization algorithm is also capable of detecting and utilizing optimal receiver equalization. In
practice, this usually implies that most of the "heavy-lifting" in channel compensation is performed by
the transmitter equalization.
• FIR => CTLE & DFE—Extends the FIR => CTLE =>DFE method by enabling RX DFE (Decision
Feedback Equalizer) when RX optimization is performed. This method exploits DFE capabilities by
possibly reducing the channel compensation from CTLE (depending on the channel characteristics).
• CTLE => FIR => DFE—Prioritizes the receiver's CTLE capability over the transmitter's equalization.
Most of the channel compensation is performed by the receiver's CTLE while the TX equalization
provides additional compensation if needed. RX DFE is adapted in the final stage. This method is
supported in non-IBIS-AMI devices. For Altera transmitters, you can manually set initial TX FIR
configurations so the link optimizations can yield better solutions more quickly when the initial
conditions are proper.
• CTLE => FIR & DFE—Extends the CTLE => FIR => DFE method by joint-optimizing TX pre-
emphasis/FIR and RX DFE. This method allows co-optimization between the TX FIR and RX DFE.
For Altera transmitters, you can manually set the initial TX FIR configurations so the link optimiza‐
tions can yield better solutions more quickly when the initial conditions are proper.
Use the following guidelines for choosing the best link optimization method:
• FIR => CTLE => DFE is a good choice for most applications or channels for time efficient link
optimizations. It is the default link optimization method in JNEye.
• For heavy insertion loss channels such as when insertion loss > 25 dB at Nyquist frequency, FIR =>CTLE => DFE provides good coverage.
• For strong impedance discontinuities, CTLE => FIR => DFE methods provide better performance in
general.
• For large crosstalk noises, choose FIR => CTLE & DFE for high loss channels or CTLE => FIR & DFE
for moderate loss applications.
Notes:
• JNEye supports link optimization for selected IBIS-AMI models for the link optimization modes and
the methods shown above. Refer to the IBIS-AMI model support sections for details.
• For a transmitter equalization sweep simulation, JNEye provides batch simulation capability using the
JNEye Batch Simulation Controller tool. Refer to the JNEye Batch Simulation Controller section for
details.
FOM of Link Optimization
Use this menu to select the figure of merit (FOM) for optimizing the serial link. There are three options:
Area, Width, and Height. The signal conditioning mechanisms, which include transmitter pre-emphasis,
de-emphasis, and receiver equalizers, use these selections to optimize the waveform so that it has the best
eye diagram opening in terms of area, width, or height.
Compliance Mask
JNEye plots link compliance eye diagram masks after the simulations are completed. Use a compliance
mask to examine whether the waveform or eye diagram meets the receiver's requirements at certain
conditions (such as BER target). PCI-Express 8GT receiver eye masks are provided.
Device intrinsic jitter can be included in the link simulation by using the Characterization Data
Note:
Access function in JNEye. When both transmitter and receiver jitter are extracted from the
Characterization Data Access and included in the simulation, the simulation results at the end of
Functional Description
Send Feedback
Altera Corporation
2-16
Link and Simulation Setting
the link represent the link margin at the specified bit error rate (BER) target. Link margin
simulation using transmitter and receiver jitter provides better accuracy than the conventional eye
mask method.
Eye Diagram Mask Designer
JNEye supports custom eye diagram mask definition. When the Eye Diagram Mask Designer option is
selected, the custom eye diagram mask configuration window opens. You can then specify the dimension
of the eye diagram mask. The custom eye diagram mask is used in the simulation. Two eye diagram mask
types are supported:
A custom eye diagram mask can be saved and loaded for future use.
Project Name
A user-defined name for the current task/project. Currently, the session name is the saved user configura‐
tion file name when the simulation configuration is saved.
Notes:
• The simulation results are automatically written to a directory with the same project name.
• The location of the output directory can be configured as a) the same location as the project configura‐
tion file (.jne/.jneschm) (this is the default), or b) a location you specify in the System Options. Refer to
the System Options section for details.
Simulation Mode
JNEye provides three simulation modes (statistical, full waveform, and hybrid) to meet your simulation
and link analysis preferences and needs. Hybrid mode is the default.
Simulation MethodStatistical MethodTime-domain MethodTime-domain and
Statistical Methods
UG-1146
2015.05.04
Jitter Injection and
Simulation
Statistical Domain
(PDF- based)
Time DomainMixed Domain (Time
Domain and PDFbased)
Noise Injection and
Simulation
Statistical Domain
(PDF- based)
Time DomainMixed Domain (Time
Domain and PDFbased)
Simulation Speed
FastSlowOptimal
(to meet your specified
BER target)
AccuracyLowerBestOptimal
Recommended
Simulation Length
N/A (You do not need to
specify simulation length
>500,000 bits~60,000 bits
in statistical mode.)
Further information and comparisons among the three simulation modes can be found in the following
papers:
1. Comparison of Two Statistical Methods for High-Speed Serial Link Simulation by M. Shimanouchi, M.
Li, and H. Wu. DesignCon, 2013, Santa Clara, CA.
2. Advancements in High-Speed Link Modeling and Simulation by M. Li, M. Shimanouchi, and H. Wu.
IEEE Custom Integrated Circuits Conference, 2013.
3. High-Speed Link Simulation Strategy for Meeting Ultra Long Data Pattern under Low BER Require‐
ments by H. Wu, M. Shimanouchi, and M. Li, DesignCon, 2014, Santa Clara, CA.
Output Options
• Data Viewer—When simulation is complete, a new JNEye Data Viewer opens and the results are
• Data Viewer with Image Output—When simulation is complete, all the simulation results are also
Altera Corporation
shown. The simulation results can be loaded and viewed at a later time with JNEye Data Viewer.
saved as image files that can be used in documentation. JNEye supports three image output options:
PNG, JPEG, and GIF. The saved images are located in the same directory as the simulation results for
each project.
Functional Description
Send Feedback
UG-1146
2015.05.04
Link and Simulation Setting
Test Point Options
JNEye provides the following default test point options:
• Data Latch Only—(default option) Simulation results at the data latch will be saved and displayed.
Data latch can be at DFE output, CTLE output, or input stage of receiver depending on the link or
device configuration. Custom test points will be neglected and the simulation results at test points will
not be shown.
• TX/Channel/CTLE-/DFE-Latch—JNEye automatically sets up to four test points for the link:
• Transmitter output—If a transmitter package model is present (for example, the package model is
embedded, as in Altera devices and PCI-Express 8GT) or external (for example, using the "Custom"
package option), the output appears after the package model. If no package model is present, the
output appears at the transmitter output.
• Channel output—The second test point is at the end of channels.
• CTLE output—If you enable the receiver CTLE, the third test point is at the output of the CTLE.
• DFE output—The fourth test point is at the output of the receiver DFE.
2-19
Note:
Custom test points are neglected with this test point option.
• Custom Test Point and Data Latch—JNEye plots the output at custom test points and the final data
latch point.
Probe Type
JNEye provides two type of probes:
• Ideal—With an ideal probe, the waveform, signal, or eye diagram is plotted by assuming that the link
is terminated with an ideal 50 ohms termination at the probe location.
• High-Impedance—With a high-impedance probe, the waveform, signal, or eye diagram is plotted by
emulating a high-impedance probe sensing the probe location.
Jitter Analysis Options
JNEye can perform jitter decomposition and analysis on a waveform at specified test points. The jitter
analysis feature is in the beta testing stage in the JNEye 15.0 release.
• Disable—Jitter analysis is disabled.
• Jitter Component—Using proprietary algorithms, JNEye performs a series of spectrum and
probability density function (PDF) analyses on the time-interval-error (TIE) record of the simulated
waveforms. The jitter decomposition algorithms extract various jitter components as shown in the
following figure.
Functional Description
Send Feedback
Altera Corporation
2-20
Link and Simulation Setting
Figure 2-13: Jitter Component Supported in JNEye Jitter Analysis Feature
UG-1146
2015.05.04
The jitter decomposition process (conceptual) is shown in the following figure.
Altera Corporation
Functional Description
Send Feedback
UG-1146
2015.05.04
Figure 2-14: Jitter Decomposition Process (Conceptual)
Link and Simulation Setting
2-21
In JNEye 15,0, the following jitter components are extracted and reported:
• PJ—Periodic jitter (peak-peak)
• DCD—Duty cycle distortion (peak-peak)
• ISI—Inter-symbol interference (peak-peak)
• BUJ—Bounded uncorrelated jitter (peak-peak)
• RJ-RMS—Random jitter (RMS)
Note:
Related Information
• JNEye Batch Simulation Controller on page 2-129
• HST Jitter and BER Estimator Tool User Guide for Stratix IV GT and GX Devices
Functional Description
Send Feedback
In JNEye 15.0, jitter analysis is available in Hybrid simulation mode only.
Altera Corporation
2-22
Transmitter Setting
Transmitter Setting
The transmitter generates signals based on the transmitter clock and test pattern conditions.
Figure 2-15: JNEye Transmitter Settings
UG-1146
2015.05.04
Transmitter
The following transmitter types are supported:
• Stratix V GX
• Arria V GZ
• Arria 10 GX/SX
• Arria 10 GT
• IBIS-AMI
• Custom
• PCI Express 8GT
The transmitter type determines what other transmitter settings you can select. When a transmitter is
chosen, it is automatically inserted into the Link Designer, ready to connect to other link components.
Package
Select a package type for the transmitter device. For Altera products and IBIS-AMI models, the package
models are included in the device models. For Custom devices, the package model is specified in the
channel setting. When you select the Custom package type (for any transmitter devices), the embedded
package model (if available) is disabled. You can then add a channel component (such as an S-parameter)
with type Package in the Link Designer workspace. The Custom package model must be placed next to the
transmitter module so it can be simulated and analyzed correctly. If you choose the Custom package type
but do not add a channel component with Package type to the Link Designer workspace, the transmitter is
simulated without any package model.
Altera Corporation
Functional Description
Send Feedback
UG-1146
2015.05.04
JNEye comes with the following transmitter package models:
• Stratix V GX
• Arria V GZ
• Stratix V GT
• Arria 10 GX/SX
Options: Additional package models (shown in the following figure) are available for Arria 10 devices.
The package model is specified as its trace length inside the package. These models are chosen to cover
the range of package trace lengths in Arria 10 transceiver transmitters.
• Default—The default package model is same as the 14 mm option
• 14mm
• 16.5mm
• 20mm
• 24mm
Contact your Altera’s representative if you would like to know how to pair your design with the Arria
10 package model options.
Figure 2-16: Arria 10 Transmitter Package Options
Transmitter Setting
2-23
• Arria 10 GT—Same options as Arria 10 GX/SX
• PCI-Express 8GT
VOD Selection
Select the VOD (differential output voltage) for the transmitter. VOD selections can be either by voltage
level or by index, depending on the transmitter selected. For supported devices, the target VOD value is
displayed in the Transmitter tab page. The VOD value depends on the device type, supply voltage, and
PVT.
Functional Description
Altera Corporation
Send Feedback
2-24
Transmitter Setting
Pre-Emphasis
Select or specify the transmitter pre-emphasis, de-emphasis, or TX-FIR configuration in one of the
following modes:
• Auto—JNEye uses its link optimization algorithm to find the optimal transmitter FIR settings.
• Auto with Manual Starting Point—Specify the initial TX pre-emphasis or FIR configuration. JNEye’s
link optimization engine uses the TX settings as initial conditions.
• Manual—For non-Altera devices, you can manually input the tap coefficients. For Altera devices,
select individual FIR levels from the menus for each FIR tap. The FIR selection for Altera devices is
VOD dependent. Therefore, changing the VOD or device type can reset the TX FIR menu contents.
For a generic transmitter type, a set of typical FIR coefficients is included in the pull-down menu.
• Off
Estimated TX EQ AC Gain
Select pre-tap and post-tap values to estimate the AC gain in dB scale. The TX EQ AC gain is calculated as
the gain between the DC (0 Hz) and the Nyquist frequency of the link, assuming a FIR type of transmitter
pre-emphasis scheme.
Note:
This is a rough analytical estimate of TX EQ AC gain that may differ from the actual AC gain
generated by the transmitter.
UG-1146
2015.05.04
PLL Type and Bandwidth
Select the type and bandwidth of the PLL used in the transmitter to generate the transmitter clock.
• Ideal Clock—The default PLL setting. The PLL is disabled and the clock is passed from the external
reference clock.
• For Altera transmitters, PLL models and configurations are automatically set based on the following
settings:
• Data rate
• Reference clock frequency
• Oscillator type:
• Stratix V GX and Arria V GZ—ATX (LC) or CMU
• Stratix V GT—ATX (LC)
• Arria 10 GX/SX/GT—ATX (LC), Fractional PLL, or CMU
• PLL bandwidth
• Altera transmitter PLL configurations such as internal divider ratios
Altera recommends that you follow Altera’s reference clock selection and PLL configurations
recommendations when setting up the transmitter PLL. Without following the reference clock and
PLL guidelines, you might operate and simulate an unstable PLL and see unexpected results.
• For Custom transmitters, PLL models and configuration are set automatically based on settings
similar to that of Altera PLLs while more comprehensive PLL configuration capabilities are under
development. With custom transmitters, the VCO can be either LC type or ring oscillator (Ring) type.
More PLL to reference clock divider ratios are supported in the custom PLL type. Follow Altera's PLL
and reference clock guidelines when setting up transmitter PLLs to avoid unexpected results.
• PLL is currently not supported for IBIS-AMI transmitters.
Altera Corporation
Functional Description
Send Feedback
Loading...
+ 164 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.