Page 1
Mercury+ XU9 SoC Module User Manual Purpose The purpose of this document is to present the characteristics of Mercury+ XU9 SoC module to the user, and to provide the user with a comprehensive guide to understanding and using the Mercury+ XU9 SoC module.
Page 2
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.
The Enclustra Build Environment [14] is available for the Mercury+ XU9 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).
Warning! It is possible to mount the Mercury+ XU9 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+ XU9 SoC module.
Enclustra Build Environment The Enclustra Build Environment (EBE) [14] 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.
FMC interfaces, the compatibility of the Mercury+ XU9 SoC module to the Mercury+ PE1 base board is limited. It is recommended to check the FMC card pinout in detail with the Enclustra Mercury Master Pinout and with the module and base board schematics.
Block Diagram Figure 1: Hardware Block Diagram The main component of the Mercury+ XU9 SoC module is the Xilinx Zynq Ultrascale+ MPSoC device. All available I/O pins (which are not routed to on-board peripherals) are connected to the Mercury+ module connector, making 92 regular user I/Os available to the user.
Figure 2: 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. Article Numbers and Article Codes Every module is uniquely labeled, showing the article number and serial number.
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+ XU9 SoC Module Known Issues and Changes document [6].
Top and Bottom Views 2.4.1 Top View Figure 4: Module Top View 2.4.2 Bottom View Figure 5: 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-463-001 13 / 59 Version 02, 15.11.2019...
Top and Bottom Assembly Drawings 2.5.1 Top Assembly Drawing Figure 6: Module Top Assembly Drawing 2.5.2 Bottom Assembly Drawing Figure 7: 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.
Figure 8: Module Footprint - Top View Warning! It is possible to mount the Mercury+ XU9 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+ XU9 SoC module.
Symbol Value Size 54 mm Component height top 3.00 mm Component height bottom 1.35 mm Weight 32 g Table 3: Mechanical Data 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.
User I/O 2.9.1 Pinout Information on the Mercury+ XU9 SoC module pinout can be found in the Enclustra Mercury Master Pinout [11], and in the additional document Enclustra Module Pin Connection Guidelines [10]. 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.
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+ XU9 SoC module related to the PCIe reset connection. I/O Name Module Connector Pin...
MIO30/42 does not apply in this case). I/O Pins with Level Shifter There are four signals on the Mercury+ XU9 SoC module that are routed from the FPGA banks to the module connector via level shifters - these are presented in Table 7.
VCC_IO_B[x], respectively VCC_CFG_[x] pins. All VCC_IO_B[x] or VCC_CFG_[x] pins of the same bank must be connected to the same voltage. For compatibility with other Enclustra Mercury modules, it is recommended to use a single I/O voltage per module connector.
Page 21
FPGA banks which are powered by fixed voltages generated on the module. Note that the VCC_IO pins on connectors B and C are used on other Enclustra modules; for compatibility purposes it is acceptable to power these pins even if they are not used on the Mercury+ XU9 SoC module.
GPIOs; the suggested functions below are for reference only - always verify your MIO pinout with the Xilinx device handbook. Table 10 gives an overview over the MIO pin connections on the Mercury+ XU9 SoC module. Only the pins marked with “user functionality” are available on the module connector.
(connected to the PL) and GTR transceivers (connected to the PS). GTH Transceivers There are 16 GTH MGTs available on the Mercury+ XU9 SoC module organized in four FPGA banks - Table 12 describes the connections. The GTH banks are numbered differently depending on the MPSoC device equipped on the module:...
GTR Transceivers There are four GTR MGT pairs and two reference input clock differential pairs on the Mercury+ XU9 SoC module connected to I/O bank 505; these are routed to module connector B. D-0000-463-001 25 / 59 Version 02, 15.11.2019...
Power Generation Overview The Mercury+ XU9 SoC module uses a 5 - 15 V DC power input for generating the on-board supply voltages (0.72/0.85/0.9 V, 0.85/0.9 V, 0.9 V, 1.2 V, 1.8 V, 2.5 V, 3.3 V and 5.0 V). Some of these voltages (1.8 V, 2.5 V, 3.3 V) are accessible on the module connector.
-3E MPSoC device is equipped, an assembly option is available to switch the PS core operating voltage to 0.9 V. Please refer to the Enclustra Module Pin Connection Guidelines for general rules on the power pins [10]. Power Converter Synchronization All switching DC/DC converters used on the Mercury+ XU9 SoC module support synchronization of the switching frequency with an external clock.
Power Enable/Power Good The Mercury+ XU9 SoC module provides a power enable input on the module connector. This input may be used to shut down the DC/DC converters and LDOs for 0.72/0.85/0.9 V, 0.85/0.9 V, 0.9 V, 1.2 V, 1.8 V and 2.5 V.
2.11.3 Voltage Supply Inputs Table 16 describes the power supply inputs on the Mercury+ XU9 SoC module. The VCC voltages used as supplies for the I/O banks are described in Section 2.9.5. Pin Name Module Connector Pins Voltage Description VCC_MOD...
MPSoC is adequately cooled. Table 18 lists the heat sink and thermal pad part numbers that are compatible with the Mercury+ XU9 SoC module. Details on these parts and additional information that may assist in selecting a suitable heat sink for the Mercury+ XU9 SoC module can be found in the Enclustra Modules Heat Sink Application Note [17].
Clock Generation A 33.33 MHz oscillator is used for the Mercury+ XU9 SoC module clock generation; the 33.33 MHz clock is fed to the PS. A 100 MHz LVDS oscillator is connected to FPGA bank 65 and can serve as a reference for the PLL used to generate the clocks required for the PL DDR interface.
Please note that PS_POR# is automatically asserted if PWR_GOOD is low. 2.14 LEDs There are three active-low user LEDs on the Mercury+ XU9 SoC module - two of them are connected to the PS and one connected to the PL. Signal...
Please check the user manual regularly for updates. Any parts with different speed bins or temperature ranges that fulfill the requirements for the module variant may be used. 2.15.2 Signal Description Please refer to the Mercury+ XU9 SoC Module FPGA Pinout Excel Sheet [4] for detailed information on the DDR4 SDRAM connections. 2.15.3 Termination Warning! No external termination is implemented for the data signals on the Mercury+ XU9 SoC module.
The DDR4 SDRAM memory controller on the MPSoC device supports speeds up to 2666 Mbit/s (1333 MHz), however the memories equipped on the Mercury+ XU9 SoC module are rated 2400 Mbit/s (1200 MHz). The maximum PL memory bandwidth on the Mercury+ XU9 SoC module is:...
Please check the user manual regularly for updates. Any parts with different speed bins or temperature ranges that fulfill the requirements for the module variant may be used. 2.16.2 Signal Description Please refer to the Mercury+ XU9 SoC Module FPGA Pinout Excel Sheet [4] for detailed information on the DDR4 SDRAM connections. 2.16.3 Termination Warning! No external termination is implemented for the data signals on the Mercury+ XU9 SoC module.
Table 28 describes the memory availability and configuration on the Mercury+ XU9 SoC module. As there is one QSPI flash chip equipped on the Mercury+ XU9 SoC module, type “single” must be selected when programming the flash from Vivado tools.
16 GB Kingston Table 29: eMMC Flash Type Warning! Other flash memory devices may be equipped in future revisions of the Mercury+ XU9 SoC module. Please check the user manual regularly for updates. D-0000-463-001 37 / 59 Version 02, 15.11.2019...
VCC_CFG_MIO must be set to 1.8 V. Please note that this boot mode has not been tested, but it may be supported in the future. 2.20 Dual Gigabit Ethernet Two 10/100/1000 Mbit Ethernet PHYs are available on the Mercury+ XU9 SoC module, both connected to the PS via RGMII interfaces. 2.20.1 Ethernet PHY Type Table 30 describes the equipped Ethernet PHY devices type on the Mercury+ XU9 SoC module.
Ethernet PHYs is connected to the I2C interrupt line, available on MIO pin 12. 2.20.3 External Connectivity The Ethernet signal lines can be connected directly to the magnetics. Please refer to the Enclustra Module Pin Connection Guidelines [10] for details regarding the connection of Ethernet signals. 2.20.4...
USB 2.0 Two USB 2.0 PHYs are available on the Mercury+ XU9 SoC module, both connected to the PS to I/O bank 502. USB PHY 0 can be configured as host or device and USB PHY 1 can be used only as host.
PHY Type Manufacturer Type USB3320C Microchip USB 2.0 PHY Table 34: USB 2.0 PHY Type 2.21.2 Signal Description The ULPI interface for the PHY 0 is connected to MIO pins 52-63 for use with the integrated USB controller. The ULPI interface for the PHY 1 is connected to MIO pins 64-75. The MIO signals are shared between Ethernet PHY 1 and USB PHY 1, therefore only one of them can be used.
(PMU) - more information on the PMU is available in the Zynq UltraScale+ MPSoC Technical Reference Manual [18]. The RTC crystal pad input and crystal pad output are connected on the Mercury+ XU9 SoC module to a 32.768 kHz oscillator.
3 Device Configuration Configuration Signals The PS of the MPSoC needs to be configured before the FPGA logic can be used. Xilinx Zynq devices need special boot images to boot from QSPI flash, eMMC flash or SD card. For more information, please refer to the Zynq UltraScale+ MPSoC Technical Reference Manual [18].
VCC_IO pins on connector C are not used, C_PRSNT# does not influence the behavior of the module. For compatibility with other Enclustra modules, it is recommended to connect C_PRSNT# to GND on the base board if the designed base board has three connectors.
For details on the POR_OVERRIDE signal please refer to the Zynq UltraScale+ MPSoC Technical Reference Manual [18]. Boot Mode The boot mode can be selected via two signals available on the module connector. Table 37 describes the available boot modes on the Mercury+ XU9 SoC module. D-0000-463-001 45 / 59 Version 02, 15.11.2019...
BOOT BOOT Mode Description Remarks MODE1 MODE0 Straps [3:0] 0110 Boot from eMMC flash 1110 Boot from SD card (with an ex- Not supported (may be sup- ternal SD 3.0 compliant level ported in the future) shifter; only available when VCC_CFG_MIO is 1.8 V) 0010 Boot from QSPI flash...
3.6.3 JTAG Boot Mode Support for JTAG boot mode has been implemented on the Mercury+ XU9 SoC module to increase the usability of the module with Xilinx tools, for example for QSPI flash programming or FPGA bitstream loading. The following steps are required in order to boot the module in JTAG mode:...
In the SD card boot mode the PS boots from the SD card located on the base board. There are two SD card boot modes available on the Mercury+ XU9 SoC module. Please note that the SD boot mode with level shifter is currently not supported.
3.13 Enclustra Module Configuration Tool In combination with an Enclustra base board, the QSPI flash can be programmed using Enclustra Module Configuration Tool (MCT) [16]. For this method, a non-QSPI boot mode must be used during QSPI flash programming. The entire procedure is described in the reference design documentation.
4 I2C Communication Overview The I2C bus on the Mercury+ XU9 SoC module is connected to the MPSoC device and to the EEPROM, and is available on the module and debug connectors. This allows external devices to read the module type and to connect more devices to the I2C bus.
An example demonstrating how to read the module information from the EEPROM memory is included in the Mercury+ XU9 SoC module reference design. Warning! The secure EEPROM is for Enclustra use only. Any attempt to write data to the secure EEPROM causes the warranty to be rendered void. 4.4.1...
Module Product Family Reserved Revision Product Information Mercury+ XU9 SoC module 0x0336 0x[XX] 0x[YY] 0x0336 [XX][YY] Table 43: Product Information Module Configuration Addr. Bits Comment Min. Value Max. Value Comment MPSoC type See MPSoC type table (Table 45) 0x08 MPSoC device speed grade...
Value Module Temperature Range Commercial Extended Industrial Table 46: Module Temperature Range Ethernet MAC Address The Ethernet MAC address is stored using big-endian byte order (MSB on the lowest address). Each module is assigned two sequential MAC addresses; only the lower one is stored in the EEPROM. D-0000-463-001 53 / 59 Version 02, 15.11.2019...
5 Operating Conditions Absolute Maximum Ratings Table 47 indicates the absolute maximum ratings for Mercury+ XU9 SoC module. The values given are for reference only; for details please refer to the Zynq UltraScale+ MPSoC, DC and AC Switching Characteristics Datasheet [20].
Recommended Operating Conditions Table 48 indicates the recommended operating conditions for Mercury+ XU9 SoC module. The values given are for reference only; for details please refer to the Zynq UltraScale+ MPSoC, DC and AC Switching Characteristics Datasheet [20]. Symbol Description...
6 Ordering and Support Ordering Please use the Enclustra online request/order form for ordering or requesting information: http://www.enclustra.com/en/order/ Support Please follow the instructions on the Enclustra online support site: http://www.enclustra.com/en/support/ D-0000-463-001 56 / 59 Version 02, 15.11.2019...
Page 57
List of Figures Hardware Block Diagram ........10 Product Code Fields .
Need help?
Do you have a question about the Mercury+ XU9 and is the answer not in the manual?
Questions and answers