Page 1
Mercury+ MP1 SoC Module User Manual Purpose The purpose of this document is to present the characteristics of Mercury+ MP1 SoC module to the user, and to provide the user with a comprehensive guide to understanding and using the Mercury+ MP1 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.
Together with Mercury+ base boards, the Mercury+ MP1 SoC module allows the user to quickly build a system prototype and start with application development. A Yocto layer is available for the Mercury+ MP1 SoC module. This layer allows the user to quickly build and run linux on the Mercury+ MP1 SoC module.
1.1.7 Electromagnetic Compatibility The Mercury+ MP1 SoC module is a Class A product (as defined in IEC 61000-3-2 standard) and is not intended for use in domestic environments. The product may cause electromagnetic interference, for which appropriate measures must be taken.
1.3.2 Yocto BSP The Enclustra Yocto BSP Layer [16] enables the user to quickly set up a Yocto project and to run Linux on the Enclustra SoC module. The documentation describes the build process in detail and allows a user without Yocto knowledge to build and run a Linux reference design on the target hardware.
Please note that the available features depend on the Mercury module type and on the selected base board variant. Microchip Tool Support The SoC devices equipped on the Mercury+ MP1 SoC module are supported by the Microchip Libero SoC Design Suite software. A platinum license is required (support for S devices). Please contact Microchip for further information.
Figure 1: Hardware Block Diagram The main component of the Mercury+ MP1 SoC module is the Microchip PolarFire SoC device. Most of its I/O pins are connected to the Mercury+ module connector, making up to 215 regular user I/Os available to the user.
A real-time clock is available on the Mercury+ MP1 SoC module. All clock signals which are required for the components equipped, are generated on the module. This in- cludes a 125 MHz differential clock for the SGMII and MSS clocking and a 50 MHz FPGA fabric clock.
Figure 3: Module Label The correspondence between EN-number and product model for each revision is shown in Table 2. The revision changes and product known issues are described in the Mercury+ MP1 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-487-002 13 / 53 Version 01, 16.02.2023...
Figure 8: Module Footprint and Dimensions - Top View and Side View Warning! It is possible to mount the Mercury+ MP1 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+ MP1 SoC module.
Parameter Value Size 54 mm Component height top 3.00 mm Component height bottom 1.9 mm Weight 36 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.8.1 Pinout Information on the Mercury+ MP1 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.
Both signals have a level of VCC_CFG on the connector and are connected to the FPGA via a level shifter to 1.2 V. I/O Pins with Level Shifter There are five signals on the Mercury+ MP1 SoC module that are routed from the FPGA banks to the module connector via level shifters - these are presented in Table 7. D-0000-487-002 18 / 53 Version 01, 16.02.2023...
Additionally, there are 10 GPIOs (GPIO_B1_T3_L[1-5]_P/N) on the module connector that are connected to GPIO Bank 1. If the Mercury+ MP1 SoC module is equipped with a MPFS460 SoC device, these signals are additionally routed to HSIO Bank 0 via a 49.9 resistor.
The information regarding the length of the signal lines from the SoC device to the module connector is available in Mercury+ MP1 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.
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.
For available on-die differential termination resistors please refer to the PolarFire FPGA and SoC FPGA User I/O User Guide [25]. 2.8.7 MSS I/O Pins Table 10 gives an overview over the MSS I/O pin connections on the Mercury+ MP1 SoC module. D-0000-487-002 22 / 53 Version 01, 16.02.2023...
Table 10: MSS I/O Pins Connections Overview Multi-Gigabit Transceiver (XCVR) The multi-gigabit transceivers on the Mercury+ MP1 SoC module are referred to as XCVR which are all con- nected to the FPGA of the SoC. There are 16 XCVR transceivers available which are organized in four quads.
-1 support data rates of up to 12.7 Gbit/sec. The SoC devices equipped on the Mercury+ MP1 SoC module can support up to one integrated PCIe Gen3 4 interfaces on the FPGA fabric, implemented using XCVR transceivers. This interface is only available within quad 0.
Power Generation Overview The Mercury+ MP1 SoC module uses a 5 - 13.2 V DC power input for generating the on-board supply volt- ages (1.05/1 V, 1.2 V, 1.8 V, 2.2 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.
Power Enable/Power Good The Mercury+ MP1 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 1.05/1 V, 1.2 V, 1.8 V, 2.2 V and 2.5 V. The list of regulators that can be disabled via PWR_EN signal is provided in Section 2.10.1.
2.10.3 Voltage Supply Inputs Table 15 describes the power supply inputs on the Mercury+ MP1 SoC module. The VCC voltages used as supplies for the I/O banks are described in Section 2.8.5. Pin Name Module Connector Pins Voltage Description VCC_MOD A-1, 2, 3, 4, 5, 6, 7, 8, 9, 11 5 - 13.2 V...
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+ MP1 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.
2.11 Clock Generation A 50 MHz oscillator is used for the Mercury+ MP1 SoC module clock generation; the 50 MHz clock is fed to the HSIO bank 8 (pin AM5). A 125 MHz LVDS oscillator is connected to MSS. A 24 MHz clock and a 25 MHz clock are used for the USB PHY and Ethernet PHYs respectively.
LEDs There are four active-low user LEDs on the Mercury+ MP1 SoC module - two of them are connected to the FPGA fabric only. The other two are connected to the FPGA fabric and the MSS. This results in 6 LED control signals.
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.14.2 Signal Description Please refer to the Mercury+ MP1 SoC Module FPGA Pinout Excel Sheet [4] for detailed information on the DDR4 SDRAM connections. 2.14.3 Termination Warning! No external termination is implemented for the data signals on the Mercury+ MP1 SoC module.
SoC devices (MPFS460TS-1FCG1152I) speeds up to 1600 Mbit/s (800 MHz) are supported by the memory controller and the equipped memory devices. The maximum FPGA fabric memory bandwidth on the Mercury+ MP1 SoC module using -1 speed grade rated devices 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.15.2 Signal Description Please refer to the Mercury+ MP1 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+ MP1 SoC module.
Table 26: QSPI Flash Type Warning! Other flash memory devices may be equipped in future revisions of the Mercury+ MP1 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.
Table 27: SPI Flash Type Warning! Other flash memory devices may be equipped in future revisions of the Mercury+ MP1 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.
SD card operation. This configuration routes the SDIO signals on MSS bank 4 to the module connector A. 2.20 Dual Gigabit Ethernet Up to two 10/100/1000 Mbps Ethernet PHYs are available on the Mercury+ MP1 SoC module. Both are connected via SGMII interfaces to the Microprocessor Subsystem. 2.20.1 Ethernet PHY Characteristics Table 28 describes the equipped Ethernet PHY devices type on the Mercury+ MP1 SoC module.
Table 29: Gigabit Ethernet PHYs Configuration - Bootstraps 2.21 USB 2.0 One USB 2.0 PHY is available on the Mercury+ MP1 SoC module. Is connected to the MSS to I/O bank 2 and can be configured as device or host. D-0000-487-002 37 / 53 Version 01, 16.02.2023...
USB core. 2.22 Real-Time Clock (RTC) The Mercury+ MP1 SoC module features a real-time clock. The RTC can be accessed by the I2C bus. 2.22.1 RTC Type Table 31 describes the equipped RTC device type on the Mercury+ MP1 SoC module.
An example demonstrating how to read data from the EEPROM is included in the Mercury+ MP1 SoC module reference design [2]. 2.24 Trusted Platform Module (TPM) The Trusted Platform Module (TPM) is used to enhance the system security and enabling the implementa- tion of a Trusted Computing Platform.
3 Device Configuration Configuration Signals Table 34 describes the most important configuration pins and their location on the module connector. These signals allow the user to program the SPI flash and SoC via SPI. Please refer to Section 3.7 for details. Signal Mod.
JTAG interface. For more information on the JTAG programming mode please refer to section 3.4. For SPI configuration modes the SoC can either act as the slave or master. On the Mercury+ MP1 SoC mod- ule a third SPI programming mode can be configured, giving the user access to the SPI flash mermory by a external master and bypassing the SoC.
Enclustra Module Pin Connection Guidelines for details on JTAG interface. Warning! On Enclustra base boards, the pin assignment of the JTAG connector is different than the Microchip FlashPro Programmer. An adapter needs to be used to interface with the Microchip FlashPro Program- mer.
The internal flash of the Mercury+ MP1 SoC moduleis available to be programmed trought the SPI bus, but currently cannot be programmed with the MCT. The MCT, however, can be used to erase the contents of the internal flash starting with MCT version 2.10.
4 I2C Communication Overview The I2C bus on the Mercury+ MP1 SoC module is connected to the SoC device, the EEPROM, to the DC/DC power converters, to the 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.
The secure EEPROM is used to store the module serial number and configuration. In the future, the EEPROM will be used for copy protection and licensing features. Please contact us for further information. An example demonstrating how to read data from the EEPROM is included in the Mercury+ MP1 SoC module Linux BSP.
Module Product Information This field indicates the type of module and hardware revision. Module Product Family Reserved Revision Product Information Mercury+ MP1 SoC module 0x0339 0x[XX] 0x[YY] 0x0339 [XX][YY] Table 40: Product Information Module Configuration Addr. Bits Comment Min. Value Max.
Value SoC Device Type MPFS250T ES MPFS250TS MPFS460TS Table 42: SoC Device Types Table 43 shows the available speed grade. Value Module Speed Grade Standard Table 43: Module Speed Grade Table 44 shows the available temperature ranges. Value Module Temperature Range Industrial Extended Engineering Sample...
5 Operating Conditions Absolute Maximum Ratings Table 45 indicates the absolute maximum ratings for Mercury+ MP1 SoC module. Symbol Description Rating Unit VCC_MOD Supply voltage relative to GND -0.3 to 16 VCC_BAT Supply voltage for battery-backed RAM and battery-backed RTC -0.3 to 6...
Recommended Operating Conditions Table 46 indicates the recommended operating conditions for Mercury+ MP1 SoC module. Symbol Description Rating Unit VCC_MOD Supply voltage relative to GND 4.75 to 13.86 VCC_BAT Supply voltage for battery-backed RAM and battery- 1.8 to 5.5 backed RTC...
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-487-002 50 / 53 Version 01, 16.02.2023...
Page 51
List of Figures Hardware Block Diagram ........10 Product Model Fields .
Need help?
Do you have a question about the Mercury+ MP1 and is the answer not in the manual?
Questions and answers