Enclustra Mercury+ XU1 User manual

Mercury+ XU1 SoC Module
User Manual
Purpose
The purpose of this document is to present the characteristics of Mercury+ XU1 SoC module to the user,
and to provide the user with a comprehensive guide to understanding and using the Mercury+ XU1 SoC
module.
Summary
This document first gives an overview of the Mercury+ XU1 SoC module followed by a detailed description
of its features and configuration options. In addition, references to other useful documents are included.
Product Information Code Name
Product ME-XU1 Mercury+ XU1 SoC Module
Document Information Reference Version Date
Reference / Version / Date D-0000-428-001 13 15.08.2019
Approval Information Name Position Date
Written by DIUN Design Engineer 04.05.2016
Verified by GLAC Design Expert 12.05.2016
Approved by DIUN Manager, BU SP 15.08.2019
Enclustra GmbH – Räffelstrasse 28 – CH-8045 Zürich – Switzerland
Phone [phone] – www.enclustra.com

Copyright Reminder
Copyright 2019 by Enclustra GmbH, Switzerland. All rights are reserved.
Unauthorized duplication of this document, in whole or in part, by any means is prohibited without the prior
written permission of Enclustra GmbH, Switzerland.
Although Enclustra GmbH believes that the information included in this publication is correct as of the date
of publication, Enclustra GmbH reserves the right to make changes at any time without notice.
All information in this document is strictly confidential and may only be published by Enclustra GmbH,
Switzerland.
All referenced trademarks are the property of their respective owners.
Document History
Version Date Author Comment
13 15.08.2019 DIUN Added new product variant
12 25.07.2019 DIUN Added information on new variants, on power supplies, corrected
supported voltage range for VCC_BAT, corrected minimum MDIO
clock frequency, other style updates
11 08.05.2019 DIUN Corrected power synchronization frequency domain and duty cycle,
added information on Linux how-to guide
10 05.04.2019 DIUN Updated for revision 4 modules, added information on new product
variants, other style updates
09 03.01.2019 DIUN Added information on voltage monitoring, heat sink, and corrected
power synchronization frequency domain
08 12.09.2018 DIUN Updated assembly drawings for revision 3, other minor corrections
07 27.08.2018 DIUN Updated for revision 3 modules, other style updates
06 20.04.2018 DIUN Minor updates and corrections
05 13.04.2018 DIUN Updated for revision 2 modules, updated DDR timing parameters
04 04.05.2017 DIUN Updated EEPROM map, block diagram and footprint information
03 27.12.2016 DIUN Updates, corrections and additions based on revision 1 modules
02 05.07.2016 DIUN Version 02, preliminary, minor updates and corrections
01 06.06.2016 DIUN Version 01, preliminary
D-0000-428-001 2 / 66 Version 13, 15.08.2019

Table of Contents
1 Overview 6
1.1 General ................................................... 6
1.1.1 Introduction ................................................ 6
1.1.2 Warranty .................................................. 6
1.1.3 RoHS .................................................... 6
1.1.4 DisposalandWEEE ............................................ 6
1.1.5 Safety Recommendations and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1.6 ElectrostaticDischarge .......................................... 7
1.1.7 Electromagnetic Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Features................................................... 7
1.3 Deliverables ................................................ 8
1.4 Accessories................................................. 8
1.4.1 ReferenceDesign ............................................. 8
1.4.2 EnclustraBuildEnvironment ....................................... 8
1.4.3 Mercury+PE1BaseBoard ........................................ 9
1.5 XilinxToolSupport ............................................ 9
2 Module Description 10
2.1 BlockDiagram............................................... 10
2.2 Module Configuration and Product Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Article Numbers and Article Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 TopandBottomViews .......................................... 15
2.4.1 TopView .................................................. 15
2.4.2 BottomView................................................ 15
2.5 Top and Bottom Assembly Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.5.1 TopAssemblyDrawing .......................................... 16
2.5.2 BottomAssemblyDrawing........................................ 16
2.6 ModuleFootprint ............................................. 17
2.7 MechanicalData.............................................. 17
2.8 ModuleConnector ............................................ 18
2.9 UserI/O................................................... 19
2.9.1 Pinout.................................................... 19
2.9.2 I/OPinExceptions............................................. 20
2.9.3 DifferentialI/Os .............................................. 23
2.9.4 I/OBanks.................................................. 23
2.9.5 VCC_IOUsage ............................................... 24
2.9.6 SignalTerminations ............................................ 25
2.9.7 MultiplexedI/O(MIO)Pins........................................ 26
2.9.8 AnalogInputs ............................................... 28
2.10 Multi-Gigabit Transceiver (MGT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.11 Power.................................................... 30
2.11.1 PowerGenerationOverview ....................................... 30
2.11.2 PowerEnable/PowerGood........................................ 32
2.11.3 VoltageSupplyInputs........................................... 33
2.11.4 VoltageSupplyOutputs ......................................... 33
2.11.5 PowerConsumption............................................ 34
2.11.6 HeatDissipation.............................................. 34
2.11.7 VoltageMonitoring ............................................ 35
2.12 ClockGeneration ............................................. 35
2.13 Reset .................................................... 36
2.14 LEDs..................................................... 36
2.15 DDR4SDRAM ............................................... 37
2.15.1 DDR4SDRAMType ............................................ 37
2.15.2 SignalDescription............................................. 38
D-0000-428-001 3 / 66 Version 13, 15.08.2019

2.15.3 Termination................................................. 38
2.15.4 Parameters................................................. 38
2.16 QSPIFlash ................................................. 39
2.16.1 QSPIFlashType .............................................. 39
2.16.2 SignalDescription............................................. 40
2.16.3 Configuration ............................................... 40
2.16.4 QSPIFlashCorruptionRisk........................................ 40
2.17 eMMCFlash ................................................ 41
2.17.1 eMMCFlashType ............................................. 41
2.17.2 SignalDescription............................................. 41
2.18 SDCard................................................... 41
2.19 DualGigabitEthernet........................................... 41
2.19.1 EthernetPHYType............................................. 41
2.19.2 SignalDescription............................................. 42
2.19.3 ExternalConnectivity ........................................... 43
2.19.4 MDIOAddress............................................... 43
2.19.5 PHYConfiguration............................................. 43
2.19.6 RGMIIDelaysConfiguration ....................................... 43
2.20 USB2.0 ................................................... 44
2.20.1 USBPHYType ............................................... 44
2.20.2 SignalDescription............................................. 44
2.21 USB3.0 ................................................... 45
2.22 DisplayPort ................................................ 45
2.23 Real-TimeClock(RTC)........................................... 46
2.24 SecureEEPROM .............................................. 46
2.24.1 EEPROMType ............................................... 46
2.25 DebugConnector............................................. 46
3 Device Configuration 49
3.1 ConfigurationSignals........................................... 49
3.2 ModuleConnectorCDetection ..................................... 50
3.3 Pull-UpDuringConfiguration ...................................... 50
3.4 Power-onResetDelayOverride ..................................... 51
3.5 BootMode................................................. 51
3.6 JTAG..................................................... 52
3.6.1 JTAGonModuleConnector ....................................... 52
3.6.2 ExternalConnectivity ........................................... 53
3.6.3 PJTAGonDebugConnector ....................................... 53
3.6.4 JTAGBootMode.............................................. 53
3.7 eMMCBootMode............................................. 54
3.8 QSPIBootMode.............................................. 54
3.9 SDCardBootMode............................................ 54
3.10 eMMCFlashProgramming........................................ 55
3.11 QSPI Flash Programming via JTAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.12 QSPI Flash Programming from an External SPI Master . . . . . . . . . . . . . . . . . . . . . . . . 55
3.13 Enclustra Module Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4 I2C Communication 57
4.1 Overview .................................................. 57
4.2 SignalDescription............................................. 57
4.3 I2CAddressMap ............................................. 57
4.4 SecureEEPROM .............................................. 58
4.4.1 MemoryMap ............................................... 58
5 Operating Conditions 61
5.1 AbsoluteMaximumRatings ....................................... 61
D-0000-428-001 4 / 66 Version 13, 15.08.2019

5.2 Recommended Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6 Ordering and Support 63
6.1 Ordering .................................................. 63
6.2 Support................................................... 63
D-0000-428-001 5 / 66 Version 13, 15.08.2019

1 Overview
1.1 General
1.1.1 Introduction
The Mercury+ XU1 SoC module combines the Xilinx Zynq® UltraScale+ MPSoC (Multiprocessor System-on-
Chip) device with USB 3.0, PCIe® Gen2 ×4, two USB 2.0 PHYs, two Gigabit Ethernet PHYs, DDR4 SDRAM
with Error Correction Code (ECC), eMMC flash, multi-gigabit transceivers, high-speed LVDS I/O, and is avail-
able in industrial temperature range, forming a complete and powerful embedded processing system.
The use of the Mercury+ XU1 SoC module, in contrast to building a custom MPSoC hardware, significantly
reduces development effort and redesign risk and improves time-to-market for the embedded system.
Together with Mercury+ base boards, the Mercury+ XU1 SoC module allows the user to quickly build a sys-
tem prototype and start with application development.
The Enclustra Build Environment [15] is available for the Mercury+ XU1 SoC module. This build system
allows the user to quickly set up and run Linux on any Enclustra SoC module. It allows the user to choose
the desired target and download all the required binaries, such as bitstream and FSBL (First Stage Boot
Loader). It downloads and compiles all required software, such as U-Boot, Linux, and BusyBox based root
file system.
1.1.2 Warranty
Please refer to the General Business Conditions, available on the Enclustra website [1].
1.1.3 RoHS
The Mercury+ XU1 SoC module is designed and produced according to the Restriction of Hazardous Sub-
stances (RoHS) Directive (2011/65/EC).
1.1.4 Disposal and WEEE
The Mercury+ XU1 SoC module must be properly disposed of at the end of its life.
The Waste Electrical and Electronic Equipment (WEEE) Directive (2002/96/EC) is not applicable for the Mer-
cury+ XU1 SoC module.
1.1.5 Safety Recommendations and Warnings
Mercury+ modules are not designed to be “ready for operation” for the end-user. These can only be used
in combination with suitable base boards. Proper configuration of the hardware before usage is required.
Ensure that the power supply is disconnected from the board before inserting or removing the Mercury+
XU1 SoC module, connecting interfaces, replacing batteries, or connecting jumpers.
Touching the capacitors of the DC-DC converters can lead to voltage peaks and permanent damage; over-
voltage on power or signal lines can also cause permanent damage to the module.
D-0000-428-001 6 / 66 Version 13, 15.08.2019

Warning!
It is possible to mount the Mercury+ XU1 SoC module the wrong way round on the base board - always
check that the mounting holes on the base board are aligned with the mounting holes of the Mercury+
XU1 SoC module.
The base board and module may be damaged if the module is mounted the wrong way round and
powered up.
1.1.6 Electrostatic Discharge
Electronic boards are sensitive to electrostatic discharge (ESD). Please ensure that the product is handled
with care and only in an ESD-protected environment.
1.1.7 Electromagnetic Compatibility
The Mercury+ XU1 SoC module is a Class A product and is not intended for use in domestic environments.
The product may cause electromagnetic interference, for which appropriate measures must be taken.
1.2 Features
•Xilinx Zynq® UltraScale+™ MPSoC
•XCZU6CG/XCZU6EG/XCZU9EG/XCZU15EG device
•FFVC900 package
•Dual-/Quad-core ARM® Cortex™-A53 MPCore™ up to 1.5 GHz
•Dual-core ARM® Cortex™-R5 MPCore™ up to 600 MHz
•Mali-400 MP2 GPU (not for CG variants)
•Xilinx 16nm FinFET+ FPGA fabric
•294 user I/Os
•14 ARM peripheral I/Os (SPI, SDIO, CAN, I2C, UART)
•200 FPGA I/Os (single-ended, differential or analog)
•152 HP I/Os (up to 1.8 V)
•148 I/Os up to 1.8 V
•4 I/Os up to 3.3 V (routed via level shifters)
•48 HD I/Os (up to 3.3 V)
•80 MGT signals (clock and data)
•60 GTH MGT signals
•20 GTR MGT signals
•Speedgrade 1 devices: 12 GTH MGTs @ 12.5 Gbit/sec and 6 reference input clock differential pairs
•Other devices: 12 GTH MGTs @ 15 Gbit/sec and 6 reference input clock differential pairs
•4 GTR MGTs @ 6 Gbit/sec and 2 reference input clock differential pairs
•PCIe Gen2 ×4 (Xilinx built-in PCIe hard block using GTR lines)
•Up to 4 GB DDR4 SDRAM with ECC
•64 MB quad SPI flash
•16 GB eMMC flash
•2×Gigabit Ethernet PHY (one PHY shared with one of the USB PHYs)
•2×USB 2.0 PHYs
•PHY0 configured as host or device
•PHY1 configured as host (shared with one of the Gigabit Ethernet PHYs)
•USB 3.0 (Xilinx built-in USB 3.0 hard block using GTR lines)
•Real-time clock
D-0000-428-001 7 / 66 Version 13, 15.08.2019

•CAN, UART, SPI, I2C, SDIO/MMC
•5 to 15 V supply voltage
Starting with revision 3 modules, 4 additional GTH transceivers and 2 differential clock pairs may be routed
to the module connector, by using the “G1” assembly variants. Please refer to Section 2.9.2 for details on
the assembly variants and MGT connectivity.
1.3 Deliverables
•Mercury+ XU1 SoC module
•Mercury+ XU1 SoC module documentation, available via download:
•Mercury+ XU1 SoC Module User Manual (this document)
•Mercury+ XU1 SoC Module Reference Design [2]
•Mercury+ XU1 SoC Module IO Net Length Excel Sheet [3]
•Mercury+ XU1 SoC Module FPGA Pinout Excel Sheet [4]
•Mercury+ XU1 SoC Module FPGA Pinout Assembly Variants Excel Sheet [5]
•Mercury+ XU1 SoC Module User Schematics (PDF) [6]
•Mercury+ XU1 SoC Module Known Issues and Changes [7]
•Mercury+ XU1 SoC Module Footprint (Altium, Eagle, Orcad and PADS) [8]
•Mercury+ XU1 SoC Module 3D Model (PDF) [9]
•Mercury+ XU1 SoC Module STEP 3D Model [10]
•Module Pin Connection Guidelines [11]
•Mercury Master Pinout [12]
•Enclustra Modules Heat Sink Application Note [18]
•Enclustra Build Environment [15] (Linux build environment; refer to Section 1.4.2 for details)
•Enclustra Build Environment How-To Guide [16]
1.4 Accessories
1.4.1 Reference Design
The Mercury+ XU1 SoC module reference design features an example configuration for the Zynq Ultrascale+
MPSoC device, together with an example top level HDL file for the user logic.
A number of software applications are available for the reference design, that show how to initialize the
peripheral controllers and how to access the external devices. Pre-compiled binaries are included in the
archive, so that the user can easily check that the hardware is functional.
The reference design can be downloaded from the Enclustra download page [2].
1.4.2 Enclustra Build Environment
The Enclustra Build Environment (EBE) [15] enables the user to quickly set up and run Linux on any Enclustra
SoC module or system board. It allows the user to choose the desired target, and download all the required
binaries, such as bitstream and FSBL. It downloads and compiles all required software, such as U-Boot, Linux,
and BusyBox based root file system.
The Enclustra Build Environment features a graphical user interface (GUI) and a command line interface (CLI)
that facilitates the automatic build flow.
The Enclustra Build Environment How-To Guide [16] describes in more detail how to use the EBE to customize
the provided software for the user application. The document provides information on the configuration
options for U-boot, Linux kernel and Buildroot, debugging possibilities for Linux applications, customization
of device trees and integration of existing or new kernel drivers.
D-0000-428-001 8 / 66 Version 13, 15.08.2019

1.4.3 Mercury+ PE1 Base Board
•168-pin Hirose FX10 module connectors (PE1-200: 2 connectors; PE1-300/400: 3 connectors)
•System controller
•Power control
•System monitor (PE1-300/400)
•Current sense (PE1-300/400)
•Low-jitter clock generator (PE1-300/400)
•Accelerometer/magnetometer/temperature sensor (PE1-300/400)
•microSD card holder
•User EEPROM
•eMMC managed NAND flash (PE1-300/400)
•PCIe ×4 interface
•USB 3.0 device connector
•USB 2.0 host connector (PE1-200: 1 connector; PE1-300/400: 4 connectors)
•Micro USB 2.0 device (UART, SPI, I2C, JTAG) connector
•2×RJ45 Gigabit Ethernet connectors
•mPCIe/mSATA card holder (USB only) (PE1-300/400)
•SIM card holder (optional, PE1-300/400 only)
•SMA clock and data in/out (optional, PE1-300/400 only)
•1×FMC LPC connector (PE1-200)
•1×FMC HPC connector (PE1-300)
•2×FMC LPC connector (PE1-400)
•2×40-pin Anios pin header
•3×12-pin Pmod™ pin header
•5 to 15 V DC supply voltage
•USB bus power (with restrictions)
Please note that the available features depend on the equipped Mercury module type and on the selected
base board variant.
1.5 Xilinx Tool Support
The MPSoC devices equipped on the Mercury+ XU1 SoC module are supported by the Vivado HL Design
Edition software, for which a paid license is required. Please contact Xilinx for further information.
D-0000-428-001 9 / 66 Version 13, 15.08.2019

2 Module Description
2.1 Block Diagram
Figure 1: Hardware Block Diagram
Figure 2: Hardware Block Diagram - G1 Variants
The main component of the Mercury+ XU1 SoC module is the Xilinx Zynq Ultrascale+ MPSoC device. Most
of its I/O pins are connected to the Mercury+ module connector, making up to 214 regular user I/Os avail-
able to the user. Further, up to twenty MGT pairs are available on the module connector, making possible the
D-0000-428-001 10 / 66 Version 13, 15.08.2019

implementation of several high-speed protocols such as PCIe Gen2 ×4 and USB 3.0 (simultaneous usage of
all the interfaces is limited to the available hardware resources i.e. number of transceivers and lane mapping).
The “G1” module variants offer 16 GTH MGT lines on the module connector at the trade-off of having only
194 regular I/Os (instead of 214). Section 2.9.2 describes in more detail the module assembly variants and
routing options around the Processing System (PS) and Programmable Logic (PL) transceivers and I/Os.
The MPSoC device can boot from the on-board QSPI flash, from the eMMC flash or from an external SD
card. For development purposes, a JTAG interface is connected to Mercury module connector.
The available standard configurations include a 16 GB eMMC flash, a 64 MB quad SPI flash and 2 GB or 4
GB DDR4 SDRAM.
Further, the module is equipped with two Gigabit Ethernet PHYs and two USB 2.0 PHYs, making it ideal for
communication applications.
A real-time clock is available on the Xilinx Zynq Ultrascale+ MPSoC device.
On-board clock generation is based on a 33.33 MHz crystal oscillator. In addition, two oscillators delivering
100 MHz and 27 MHz reference clocks for the MGT GTR lines, are equipped on the module.
The module’s internal supply voltages are generated from a single input supply of 5 - 15 V DC. Some of
these voltages are available on the Mercury module connectors to supply circuits on the base board.
Five LEDs are connected to the MPSoC pins for status signaling.
2.2 Module Configuration and Product Codes
Table 1 describes the available standard module configurations. Custom configurations are available; please
contact Enclustra for further information.
D-0000-428-001 11 / 66 Version 13, 15.08.2019

Product Code MPSoC DDR4 DDR4 GTH Temperature
SDRAM ECC MGTs Range
ME-XU1-6CG-1E-D11E-G1 XCZU6CG-1FFVC900E 2 GB 316 0 to +85◦C
ME-XU1-6CG-1E-D11E XCZU6CG-1FFVC900E 2 GB 312 0 to +85◦C
ME-XU1-6EG-1I-D11E-G1 XCZU6EG-1FFVC900I 2 GB 316 -40 to +85◦C
ME-XU1-6EG-1I-D11E XCZU6EG-1FFVC900I 2 GB 312 -40 to +85◦C
ME-XU1-9EG-1E-D11E-G1 XCZU9EG-1FFVC900E 2 GB 316 0 to +85◦C
ME-XU1-9EG-2I-D12E XCZU9EG-2FFVC900I 4 GB 312 -40 to +85◦C
ME-XU1-9EG-2I-D12E-G1 XCZU9EG-2FFVC900I 4 GB 316 -40 to +85◦C
ME-XU1-9EG-3E-D12E XCZU9EG-3FFVC900E 4 GB 312 0 to +85◦C
ME-XU1-15EG-1E-D12E-G1 XCZU15EG-1FFVC900E 4 GB 316 0 to +85◦C
ME-XU1-15EG-2I-D12E XCZU15EG-2FFVC900I 4 GB 312 -40 to +85◦C
ME-XU1-15EG-2I-D12E-G1 XCZU15EG-2FFVC900I 4 GB 316 -40 to +85◦C
Table 1: Standard Module Configurations
Starting with revision 3 modules, 4 additional GTH transceivers and 2 differential clock pairs may be routed
to the module connector, by using the “G1” assembly variants. Please refer to Section 2.9.2 for details on
the assembly variants and MGT connectivity.
The product code indicates the module type and main features. Figure 3 describes the fields within the
product code.
Figure 3: Product Code Fields
Please note that for the first revision modules or early access modules, the product code may not respect
entirely this naming convention. Please contact Enclustra for details on this aspect.
D-0000-428-001 12 / 66 Version 13, 15.08.2019

2.3 Article Numbers and Article Codes
Every module is uniquely labeled, showing the article number and serial number. An example is presented
in Figure 4.
Figure 4: Module Label
The correspondence between article number and article code is shown in Table 2. The article code repre-
sents the product code, followed by the revision; the R suffix and number represent the revision number.
The revision changes and product known issues are described in the Mercury+ XU1 SoC Module Known
Issues and Changes document [7].
D-0000-428-001 13 / 66 Version 13, 15.08.2019

Article Number Article Code
EN101846 ME-XU1-9EG-1EES-D11E-R1.3
EN101918 ME-XU1-6EG-1I-D11E-R2
EN101919 ME-XU1-9EG-2I-D12E-R2
EN101920 ME-XU1-15EG-2I-D12E-R2
EN102114 ME-XU1-6EG-1I-D11E-R3
EN102115 ME-XU1-9EG-2I-D12E-R3
EN102116 ME-XU1-9EG-3E-D12E-R3
EN102117 ME-XU1-15EG-2I-D12E-R3
EN102278 ME-XU1-6EG-1I-D11E-R4
EN102279 ME-XU1-9EG-2I-D12E-R4
EN102280 ME-XU1-9EG-3E-D12E-R4
EN102281 ME-XU1-15EG-2I-D12E-R4
EN102600 ME-XU1-6CG-1E-D11E-G1-R4.1
EN102601 ME-XU1-6CG-1E-D11E-R4.1
EN102614 ME-XU1-6EG-1I-D11E-G1-R4.1
EN102372 ME-XU1-6EG-1I-D11E-R4.1
EN102602 ME-XU1-9EG-1E-D11E-G1-R4.1
EN102373 ME-XU1-9EG-2I-D12E-R4.1
EN102603 ME-XU1-9EG-2I-D12E-G1-R4.1
EN102374 ME-XU1-9EG-3E-D12E-R4.1
EN102604 ME-XU1-15EG-1E-D12E-G1-R4.1
EN102375 ME-XU1-15EG-2I-D12E-R4.1
EN102376 ME-XU1-15EG-2I-D12E-G1-R4.1
Table 2: Article Numbers and Article Codes
D-0000-428-001 14 / 66 Version 13, 15.08.2019

2.4 Top and Bottom Views
2.4.1 Top View
Figure 5: Module Top View
2.4.2 Bottom View
Figure 6: Module Bottom View
Please note that depending on the hardware revision and configuration, the module may look slightly dif-
ferent than shown in this document.
D-0000-428-001 15 / 66 Version 13, 15.08.2019

2.5 Top and Bottom Assembly Drawings
2.5.1 Top Assembly Drawing
Figure 7: Module Top Assembly Drawing
2.5.2 Bottom Assembly Drawing
Figure 8: Module Bottom Assembly Drawing
Please note that depending on the hardware revision and configuration, the module may look slightly dif-
ferent than shown in this document.
D-0000-428-001 16 / 66 Version 13, 15.08.2019

2.6 Module Footprint
Figure 9 shows the dimensions of the module footprint on the base board.
Enclustra offers Mercury and Mercury+ modules of various geometries having widths of 56, 64, 72 or 74
mm and having different topologies for the mounting holes. If different module types shall be fixed on the
base board by screws, additional mounting holes may be required to accommodate different modules. The
footprints of the module connectors for the base board design are available for different PCB design tools
(Altium, PADS, Eagle, Orcad) [8] and include the required information on the module sizes and holes.
The maximum component height under the module is dependent on the connector type - refer to Section
2.8 for detailed connector information.
Figure 9: Module Footprint - Top View
Warning!
It is possible to mount the Mercury+ XU1 SoC module the wrong way round on the base board - always
check that the mounting holes on the base board are aligned with the mounting holes of the Mercury+
XU1 SoC module.
2.7 Mechanical Data
Table 3 describes the mechanical characteristics of the Mercury+ XU1 SoC module. A 3D model (PDF) and
a STEP 3D model are available [9], [10].
D-0000-428-001 17 / 66 Version 13, 15.08.2019

Symbol Value
Size 74 ×54 mm
Component height top 3.42 mm
Component height bottom 1.4 mm
Weight 34 g
Table 3: Mechanical Data
2.8 Module Connector
Three Hirose FX10 168-pin 0.5 mm pitch headers with a total of 504 pins have to be integrated on the base
board. Up to four M3 screws may be used to mechanically fasten the module to the base board. Do not
use excessive force to tighten the screws, as this could damage the module.
The pinout of the module connector is found in the Mercury Master Pinout Excel Sheet [12]. The connector
is available in different packaging options and different stacking heights. Some examples are presented in
Table 4. Please refer to the connector datasheet for more information.
Reference Type Description
Mercury module connector FX10A-168S-SV Hirose FX10, 168-pin, 0.5 mm pitch
Base board connector FX10A-168P-SV(71) Hirose FX10, 168-pin, 0.5 mm pitch, 4 mm stacking
height
Base board connector FX10A-168P-SV1(71) Hirose FX10, 168-pin, 0.5 mm pitch, 5 mm stacking
height
Table 4: Module Connector Types
Figure 10 indicates the pin numbering for the Mercury module connectors from the top view of the base
board. The connector pins are numbered as follows:
•Connector A: from J800-1 to J800-168
•Connector B: from J801-1 to J801-168
•Connector C: from J900-1 to J900-168
Figure 10: Pin Numbering for the Module Connector
D-0000-428-001 18 / 66 Version 13, 15.08.2019

Warning!
Do not use excessive force to latch a Mercury module into the Mercury connectors on the base board,
as this could damage the module and the base board; always make sure that the module is correctly
oriented before mounting it into the base board.
2.9 User I/O
2.9.1 Pinout
Information on the Mercury+ XU1 SoC module pinout can be found in the Enclustra Mercury Master Pinout
[12], and in the additional document Enclustra Module Pin Connection Guidelines [11].
Warning!
Please note that the pin types on the schematics symbol of the module connector and in the Master
Pinout document are for reference only. On the Mercury+ XU1 SoC module it may be possible that
the connected pins do not have the targeted functions (such as primary clocks, differential pins, MGT
signals, etc).
The naming convention for the user I/Os is:
IO_B<BANK>_L<PAIR><_SPECIAL_FUNCTION>_<PACKAGE_PIN>_<POLARITY>.
For example, IO_B64_L18_AD2_AH4_P is located on pin AH4 of I/O bank 64, pair 18, it is a System Monitor
differential auxiliary analog input capable pin and it has positive polarity, when used in a differential pair.
The global clock capable pins are marked with “GC” (HP I/O banks) or with “HDGC” (HD I/O banks) in the
signal name. For details on their function and usage, please refer to the Xilinx documentation.
Table 5 includes information related to the total number of I/Os available in each I/O bank and possible
limitations.
D-0000-428-001 19 / 66 Version 13, 15.08.2019

Signal Name Signals Pairs Differential Single-ended I/O Bank
IO_B64_<...> 52 24 In/Out In/Out 64 (HP)1
IO_B65_<...> 50 24 In/Out In/Out 65 (HP)1
IO_B66_<...> 50 24 In/Out In/Out 66 (HP)1
IO_B47_<...> 24 12 In/Out (no LVDS/LVPECL outputs sup-
ported; internal differential termina-
tion not supported)
In/Out 47 (HD)1
Refer to Section 2.9.3 for details.
IO_B48_<...> 24 12 In/Out (no LVDS/LVPECL outputs sup-
ported; internal differential termina-
tion not supported)
In/Out 48 (HD)1
Refer to Section 2.9.3 for details.
Total 200 96 - - -
Table 5: User I/Os
Please note that on the “G1” variants with 16 GTH transceivers, not all I/Os listed in Table 5 are available on
the module connector. Certain user I/Os on the module connectors can be connected to various MPSoC
I/Os, depending on the product variant. Section 2.9.2 lists and describes the connectivity for these pins for
each assembly variant. The multi-use signals on the module connector are not named according to the
naming convention described above.
The multi-gigabit transceiver (MGT) are described in section 2.10.
2.9.2 I/O Pin Exceptions
The I/O pin exceptions are pins with special functions or restrictions (for example, when used in combination
with certain Mercury boards they may have a specific role).
PCIe Reset Signal (PERST#)
Table 6 lists the I/O pin exceptions on the Mercury+ XU1 SoC module related to the PCIe reset connection.
I/O Name Module Connector Pin Description
PS_MIO42_PERST# A-104 When the pin has a low value, ETH0_TXD3_PERST# pin
(MIO30) is pulled to ground via a 1 kΩresistor for PCIe
PERST# connection implementation
Table 6: I/O Pin Exceptions - PERST#
When the Mercury+ XU1 SoC module is used in combination with a Mercury+ PE1 base board as a PCIe
device, the low value of the PERST# signal coming from the PCIe edge connector on the module connector
pin A-104 (PS_MIO42_PERST#) pulls the ETH0_TXD3_PERST# (MIO30) to ground via a 1 kΩresistor.
MIO30 is the default pin used for the reset signal of the PCIe PS built-in block, therefore it was chosen for
the reset implementation. The Ethernet controller 0 is disabled when the PCIe hard block is used; note that
any other valid position for PERST# would have resulted in having the Ethernet controller disabled.
1HD = high density pins, HP = high performance pins; Refer to the Zynq UltraScale+ MPSoC Overview [23] for details.
D-0000-428-001 20 / 66 Version 13, 15.08.2019