Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Mercury SA1 SoC Module and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Enclustra Mercury SA1 SoC Module

  • Page 1 User Manual Purpose The purpose of this document is to present the characteristics of Mercury SA1 SoC module to the user, and to provide the user with a comprehensive guide to understanding and using the Mercury SA1 SoC module. Summary This document first gives an overview of the Mercury SA1 SoC module followed by a detailed description of its features and configuration options.
  • 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.
  • Page 3: Table Of Contents

    Enclustra Build Environment ........
  • Page 4 3.11 Enclustra Module Configuration Tool ........40 I2C Communication Overview .
  • Page 5: Overview

    The Enclustra Build Environment [14] is available for the Mercury SA1 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 preloader. It downloads and compiles all required software, such as U-Boot, Linux, and BusyBox based root file system.
  • Page 6: Electrostatic Discharge

    Warning! It is possible to mount the Mercury SA1 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 SA1 SoC module.
  • Page 7: Accessories

    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 preloader/bootloader.
  • Page 8: Mercury+ St1 Base Board

    Please note that the available features depend on the equipped Mercury module type. Intel Tool Support The SoC devices equipped on the Mercury SA1 SoC module are supported by the Quartus Prime Lite Edition (or Quartus II Web Edition, for older software versions), which is available free of charge. Please contact Intel for further information.
  • Page 9: Module Description

    Figure 1: Hardware Block Diagram The main component of the Mercury SA1 SoC module is the Intel Cyclone V SoC device. Most of its I/O pins are connected to the Mercury module connectors, making 150 regular user I/Os available to the user.
  • Page 10: Module Configuration And Product Codes

    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.
  • Page 11: Article Numbers And Article Codes

    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 SA1 SoC Module Known Issues and Changes document [6].
  • Page 12: Top And Bottom Views

    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-402-002 12 / 49 Version 06, 16.02.2021...
  • Page 13: Top And Bottom Assembly Drawings

    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.
  • Page 14: Module Footprint

    Figure 8: Module Footprint - Top View Warning! It is possible to mount the Mercury SA1 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 SA1 SoC module.
  • Page 15: Mechanical Data

    Mechanical Data Table 3 describes the mechanical characteristics of the Mercury SA1 SoC module. A 3D model (PDF) and a STEP 3D model are available [8], [9]. Symbol Value Size 54 mm Component height top 5.0 mm Component height bottom 1.35 mm...
  • Page 16: User I/O

    User I/O 2.9.1 Pinout Information on the Mercury SA1 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.
  • Page 17: 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). Table 6 lists the I/O pin exceptions on the Mercury SA1 SoC module. D-0000-402-002 17 / 49 Version 06, 16.02.2021...
  • Page 18: Differential I/Os

    The information regarding the length of the signal lines from the SoC device to the module connector is available in Mercury SA1 SoC Module IO Net Length Excel Sheet [3]. This enables the user to match the total length of the differential pairs on the base board if required by the application.
  • Page 19: I/O Banks

    2.9.4 I/O Banks Table 7 describes the main attributes of the FPGA and Hard Processing System (HPS) I/O banks, and indicates which peripherals are connected to each I/O bank. All I/O pins within a particular I/O bank must use the same I/O (VCC_IO) and reference (VREF) voltages.
  • Page 20: Vcc_Io Usage

    VCC_IO_B[x] or 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: Signal Terminations

    2.9.7 HPS I/O Pins Table 9 gives an overview over the HPS pin connections on the Mercury SA1 SoC module. Only the pins marked with “user functionality” are available on the module connector. The suggested functions below are for reference only - always verify your HPS pinout with the Intel device handbook.
  • Page 22: Multi-Gigabit Transceiver (Mgt)

    The transceivers on the SoC device support a data rate of 3.125 Gbit/sec. Warning! The maximum data rate on the MGT lines on the Mercury SA1 SoC module depends on the routing path for these signals. Adequate signal integrity over the full signal path must be ensured when using MGTs at high performance rates.
  • Page 23: Power

    Power Generation Overview The Mercury SA1 SoC module uses a 5 - 15 V DC power input for generating the on-board supply voltages (1.1 V, 1.2 V, 1.35 V, 1.8 V, 2.5 V and 3.3 V). Some of these voltages (1.8 V, 2.5 V, 3.3 V) are accessible on the module connector.
  • Page 24: Voltage Supply Inputs

    Figure 10. 2.11.3 Voltage Supply Inputs Table 12 describes the power supply inputs on the Mercury SA1 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...
  • Page 25: Power Consumption

    For Mercury modules an Enclustra heat sink kit is available for purchase along with the product. It represents an optimal solution to cool the Mercury SA1 SoC module - the heat sink body is low profile and usually covers the whole module surface. The kit comes with a gap pad for the SoC device, a fan and required mounting material to attach the heat sink to the module PCB and baseboard PCB.
  • Page 26: Voltage Monitoring

    Clock Generation A 50 MHz oscillator is used for the Mercury SA1 SoC module clock generation. The 50 MHz clock is fed to the HPS and FPGA logic. The second HPS clock is provided by an external source (module connector pin A-110) in the standard module configuration.
  • Page 27: Reset

    2.14 LEDs The four LEDs on the Mercury SA1 SoC module are connected to the FPGA logic and the HPS in parallel. As the LEDs are active-low it is recommended to use the I/Os in open collector mode. Signal Name...
  • Page 28: Ddr3L Sdram

    2.15 DDR3L SDRAM There is a single DDR3 SDRAM channel on the Mercury SA1 SoC module attached directly to the HPS side and is available only as a shared resource to the FPGA side. The DDR3L SDRAM is connected to HPS I/O banks 6A and 6B, and it is always operated at 1.35 V (low power mode).
  • Page 29: Parameters

    2.15.4 Parameters Please refer to the Mercury SA1 SoC module reference design [2] for DDR3 settings guidelines. The DDR3L SDRAM parameters and the DDR3L board timing information to be set in Quartus project are presented in Tables 20 and 21.
  • Page 30: Qspi Flash

    Table 22: QSPI Flash Type Warning! Other flash memory devices may be equipped in future revisions of the Mercury SA1 SoC module. Please check the user manual regularly for updates. Any parts with different speeds and temperature ranges that fulfill the requirements for the module variant may be used.
  • Page 31: Signal Description

    Table 24: eMMC Flash Type Warning! Other flash memory devices may be equipped in future revisions of the Mercury SA1 SoC module. Please check the user manual regularly for updates. Any parts with different speeds and temperature ranges that fulfill the requirements for the module variant may be used.
  • Page 32: Signal Description

    Please note that the RGMII delays in the Ethernet PHY need to be configured before the Ethernet interface can be used. This is done in the patch for the Preloader (SPL) provided in the Mercury SA1 SoC module reference design [2].
  • Page 33: Usb 2.0

    MHz. 2.20 USB 2.0 The Mercury SA1 SoC module has an on-board USB 2.0 PHY connected to the SoC device. The USB interface can be configured for USB host, USB device and USB On-The-Go (host and device capable) operations. 2.20.1 USB PHY Type Table 27 describes the equipped USB PHY device type on the Mercury SA1 SoC module.
  • Page 34: Rtc Type

    Manufacturer ISL12020MIRZ Intersil Table 28: RTC Type An example demonstrating how to use the RTC is included in the Mercury SA1 SoC module reference design [2]. 2.22 Secure EEPROM The secure EEPROM is used to store the module type and serial number, as well as the Ethernet MAC address and other information.
  • Page 35: Device Configuration

    All configuration signals except for BOOT_MODE must be high impedance as soon as the device is released from reset. Violating this rule may damage the equipped SoC device, as well as other devices on the Mercury SA1 SoC module. D-0000-402-002 35 / 49 Version 06, 16.02.2021...
  • Page 36: Boot Mode

    HPS and FPGA Configuration Pins The BSEL and CSEL pins determine in which memory interface is the boot loader stored and how to clock the interface; details on BSEL and CSEL pins when using the HPS boot are available in the Booting and Configuration Introduction document [20].
  • Page 37: Jtag

    HPS 00010 Table 31: Boot Modes Please note that the passive serial mode is not supported on the Mercury SA1 SoC module nor has it been tested on Enclustra side. JTAG The FPGA and the HPS JTAG interfaces are connected into one single chain available on the module con- nector.
  • Page 38: Hps Jtag Connector

    It is recommended to add 22 series termination resistors between the module and the JTAG header, close to the source. Please refer to the Enclustra Module Pin Connection Guidelines for details on JTAG interface. Passive Serial Configuration In the passive serial configuration mode the FPGA bitstream is programmed from an external source into the SPI port of the FPGA.
  • Page 39: Qspi Boot Mode

    QSPI Boot Mode In the QSPI boot mode, the HPS boots from the QSPI flash and configures the FPGA logic from the HPS. The HPS configuration and the FPGA bitstream need to be stored in a boot image. For more information, please refer to the Cyclone V datasheet [18].
  • Page 40: Enclustra Module Configuration Tool

    SoC device, as well as other devices on the Mercury SA1 SoC module. 3.11 Enclustra Module Configuration Tool In combination with an Enclustra base board, the QSPI flash can be programmed using the Enclustra Module Configuration Tool (MCT) [16]. D-0000-402-002 40 / 49 Version 06, 16.02.2021...
  • Page 41: I2C Communication

    4 I2C Communication Overview The I2C bus on the Mercury SA1 SoC module is connected to the SoC device, EEPROM and RTC, and is available on the module connector. This allows external devices to read the module type and to connect more devices to the I2C bus.
  • Page 42: Secure Eeprom

    An example demonstrating how to read the module information from the EEPROM memory is included in the Mercury SA1 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...
  • Page 43: Product Information

    Module Product Family Reserved Revision Product Information Mercury SA1 SoC module 0x0326 0x[XX] 0x[YY] 0x0326 [XX][YY] Table 36: Product Information Module Configuration Addr. Bits Comment Min. Value Max. Value Comment SoC Type See SoC type table (Table 38) 0x08 SoC device speed grade...
  • Page 44 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-402-002 44 / 49 Version 06, 16.02.2021...
  • Page 45: Operating Conditions

    5 Operating Conditions Absolute Maximum Ratings Table 39 indicates the absolute maximum ratings for Mercury SA1 SoC module. The values given are for reference only; for details please refer to the Cyclone V Datasheet [18]. Symbol Description Rating Unit VCC_MOD Supply voltage relative to GND -0.5 to 16...
  • Page 46: Ordering And Support

    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-402-002 46 / 49 Version 06, 16.02.2021...
  • Page 47 List of Figures Hardware Block Diagram ........Product Code Fields .
  • Page 48 Absolute Maximum Ratings ........45 Recommended Operating Conditions .
  • Page 49 [1] Enclustra General Business Conditions http://www.enclustra.com/en/products/gbc/ [2] Mercury SA1 SoC Module Reference Design Ask Enclustra for details [3] Mercury SA1 SoC Module IO Net Length Excel Sheet Ask Enclustra for details [4] Mercury SA1 SoC Module FPGA Pinout Excel Sheet Ask Enclustra for details...

Table of Contents