Download PDF version of this document.

Overview

Trenz Electronic TEM0007 module is an industrial-grade FPGA micromodule integrating a Microsemi Polarfire SoC FPGA, Gigabit Ethernet PHY, USB 2.0 PHY, LPDDR4 SDRAM, SPI Flash memory for configuration and operation, and power supply. A large number of configurable I/Os is provided via robust board-to-board (B2B) connectors.

Refer to http://trenz.org/tem0007-info for the current online version of this manual and other available documentation.

Key Features

  • SoC/FPGA
    • Device: MPFS250T / MPFS160T / MPFS095T / MPFS025T 1)
    • Device Family: -T / -TL / -TS / -TLS 1)
    • Speedgrade: Blank / -1 1)
    • Temperature Range: Extended / Industrial 1)
    • Package: FCVG484
  • RAM/Storage
    • 1 GByte LPDDR4 SDRAM 2)
    • 64 MByte SPI Flash Memory 2)
    • EEPROM with MAC address
  • On Board
    • System Controller CPLD
    • Gigabit Ethernet PHY
    • USB 2.0 ULPI Transceiver
    • Oscillator
  • Interface
    • 3 x B2B Connector (LSHM)
      • up to 118 FPGA IOs

        • GPIO: 84
        • HSIO: 34
      • up to 14 MSSIO

      • 1 SGMII
      • 4 MGT
      • SDIO, USB, ETH, UART, I2C, JTAG, CONFIG
  • Power
    • 3.3 V power supply via B2B Connector needed 3).
  • Dimension
    • 40 mm x 50 mm
  • Notes
    1) Please, take care of the possible assembly options. Furthermore, check whether the power supply is powerful enough for your FPGA design. Attention: IO number connected to B2B connector depends on the used device!
    2) Please, take care of the possible assembly options.
    3) A higher or lower input voltage may be possible.

Block Diagram

TEM0007 block diagram

Main Components

TEM0007 main components
  1. Microsemi Polarfire SoC, U2
  2. LPDDR4 SDRAM, U6
  3. Ethernet Transceiver, U7
  4. USB Transceiver, U11
  5. System Controller CPLD, U1
  6. B2B Connector, JM1, JM2, JM3
  7. EEPROM, U10
  8. Serial NOR Flash, U3

Initial Delivery State

Storage device name

Content

Notes

LPDDR4 SDRAM

not programmed

SPI NOR Flash

not programmed
EEPROMnot programmed besides factory programmed MAC address
System Controller CPLD, U1Standard firmwareSee TEM0007 CPLD.
Initial delivery state of programmable devices on the module

Signals, Interfaces and Pins

Connectors

Connector TypeDesignatorInterfaceIO CNTNotes
B2BJM1GPIOup to 48 SE / 24 DIFFonly 40 SE / 20 DIFF for MPFS025 variants
B2BJM1MSSIO2 x MSSIO
B2BJM1I2C or MSSIOI2C or 2 x MSSIO
B2BJM1SDIO or MSSIOSDIO or 6 x MSSIO
B2BJM1UART or MSSIO2 x UART or 4 x MSSIO
B2BJM1ETH - MDIETH
B2BJM2HSIO18 SE / 9 DIFF
B2BJM2GPIOup to 36 SE / 18 DIFFonly 8 SE / 4 DIFF for MPFS025 variants
B2BJM2CFGJTAG
B2BJM3HSIO16 SE / 8 DIFF
B2BJM3SGMII1 x SGMII (RX/TX)
B2BJM3MGT FPGA4 x MGT (RX/TX)
B2BJM3MGT CLK2 x MGT CLK
B2BJM3USBUSB
Board Connectors

Test Points

Test PointSignalNotes
TP1+3.3V
TP2+2.5V
TP3+2.5V_XCVR
TP4+1.8V
TP5-Signal at U17 pin 3. See schematics.
TP6+1.1V_LPDDR4
TP7+1.0V
TP8VDDAUX1
TP9AVDD18
TP10AVDD33
TP11DVDD1V0
TP12VCCIOB_SW
TP13+2.5V_VDDA
TP14+1.0V_VDDA
TP15+2.5V_VDD
Test Points Information

On-board Peripherals

Chip/InterfaceDesignatorConnected ToNotes

System Controller CPLD

U1

B2B
DCDC
SoC
Power Monitor


Gigabit Ethernet

U7

SoC - MSS
B2B - JM1


USB PHY

U11

SoC - MSS
B2B -JM3


LPDDR4 SDRAM

U6SoC - MSS

EEPROM

U10SoC - MSS

SPI Flash Memory

U3SoC - MSS

Oscillator

U4SoC - MSS
OscillatorU5Soc - FPGA
Oscillator
U8ETH PHY
OscillatorU12USB PHY
On board peripherals

Configuration and System Control Signals

Connector+Pin

Signal Name

Direction1)Description
JM1-7NOSEQIN/OUTSee 4 x 5 SoM Integration Guide and TEM0007 CPLD.
JM1-28SC_EN1INSee 4 x 5 SoM Integration Guide and TEM0007 CPLD.
JM1-30SC_PGOODIN/OUTSee 4 x 5 SoM Integration Guide and TEM0007 CPLD.
JM1-32SC_BOOTMODEINSee 4 x 5 SoM Integration Guide and TEM0007 CPLD.
JM1-89JTAGSELINSee 4 x 5 SoM Integration Guide and TEM0007 CPLD.
JM2-18SC_nRSTINSee 4 x 5 SoM Integration Guide and TEM0007 CPLD.
JM2-93 / JM2-95 / JM2-97 / JM2-99TMS / TDI / TDO / TCKSignal-dependent

JTAG configuration and debugging interface.

JTAG reference voltage: 3.3VIN

1) Direction:

    • IN: Input from the point of view of this board.
    • OUT: Output from the point of view of this board.
Controller signal.

Power and Power-On Sequence

Power Rails

Power Rail Name/ Schematic NameConnector + PinDirection1)Notes
VINJM1.1 / JM1.3 / JM1.5 / JM2.2 / JM2.4 / JM2.6 / JM2.8INSupply voltage from the carrier board
3.3VINJM1.13 / JM1.15INSupply voltage from the carrier board
3.3VINJM2.91OUTJTAG reference voltage

+1.8V

JM1.39OUTInternal +1.8V voltage level

VCCIOB

JM2.1 / JM2.3INGeneral purpose I/O bank voltage

VCCIOD

JM2.7 / JM2.9INHigh speed I/O bank voltage (max. +1.8 V)

+3.3V

JM2.10 / JM2.12OUTInternal +3.3 V voltage level

1) Direction:

    • IN: Input from the point of view of this board.
    • OUT: Output from the point of view of this board.
Module power rails.

Recommended Power up Sequencing

SequenceNet nameRecommended Voltage RangePull-up/downDescriptionNotes
0---Configuration signal setup.See Configuration and System Control Signals.
13.3VIN3.3 V (± 5 %)-Management and SoC power supply.Main module power supply for management and SoC. 3 A recommended. Power consumption depends mainly on design and cooling solution.
2VIN3.3 V (± 5 %) 1)-Main module power supply.Main module power supply for management and SoC. 5.5 A recommended. Power consumption depends mainly on design and cooling solution.
3+1.8V--1.8 V on-module power supply.
4

VCCIOB / VCCIOD

2)-Module bank voltages.Enable bank voltages after 1.8 V are available on carrier.

1) A higher or lower input voltage may be possible. 

2) See DS0147 for additional information.

Baseboard Design Hints

Board to Board Connectors

These connectors are hermaphroditic. Odd pin numbers on the module are connected to even pin numbers on the baseboard and vice versa.

4 x 5 modules use two or three Samtec Razor Beam LSHM connectors on the bottom side.

  • 2 x REF-189016-02 (compatible to LSHM-150-04.0-L-DV-A-S-K-TR), (100 pins, "50" per row)
  • 1 x REF-189017-02 (compatible to LSHM-130-04.0-L-DV-A-S-K-TR), (60 pins, "30" per row) (depending on module)
Connector Mating height

When using the same type on baseboard, the mating height is 8mm. Other mating heights are possible by using connectors with a different height

Order numberConnector on baseboardcompatible toMating height
23836REF-189016-01LSHM-150-02.5-L-DV-A-S-K-TR6.5 mm

LSHM-150-03.0-L-DV-A-S-K-TRLSHM-150-03.0-L-DV-A-S-K-TR7.0 mm
23838REF-189016-02LSHM-150-04.0-L-DV-A-S-K-TR8.0 mm

LSHM-150-06.0-L-DV-A-S-K-TRLSHM-150-06.0-L-DV-A-S-K-TR10.0mm
26125REF-189017-01LSHM-130-02.5-L-DV-A-S-K-TR6.5 mm

LSHM-130-03.0-L-DV-A-S-K-TRLSHM-130-03.0-L-DV-A-S-K-TR7.0 mm
24903 REF-189017-02LSHM-130-04.0-L-DV-A-S-K-TR8.0 mm

LSHM-130-06.0-L-DV-A-S-K-TRLSHM-130-06.0-L-DV-A-S-K-TR10.0mm
Connectors.

The module can be manufactured using other connectors upon request.

Connector Speed Ratings

The LSHM connector speed rating depends on the stacking height; please see the following table:

Stacking heightSpeed rating
12 mm, Single-Ended7.5 GHz / 15 Gbps
12 mm, Differential

6.5 GHz / 13 Gbps

5 mm, Single-Ended11.5 GHz / 23 Gbps
5 mm, Differential7.0 GHz / 14 Gbps
Speed rating.
Current Rating

Current rating of  Samtec Razor Beam™ LSHM B2B connectors is 2.0A per pin (2 adjacent pins powered).

Connector Mechanical Ratings
  • Shock: 100G, 6 ms Sine
  • Vibration: 7.5G random, 2 hours per axis, 3 axes total


Manufacturer Documentation

  File Modified
PDF File hsc-report_lshm-lshm-05mm_web.pdf High speed test report 07 04, 2016 by Thorsten Trenz
PDF File lshm_dv.pdf LSHM catalog page 07 04, 2016 by Thorsten Trenz
PDF File LSHM-1XX-XX.X-X-DV-A-X-X-TR-FOOTPRINT(1).pdf Recommended layout and stencil drawing 07 04, 2016 by Thorsten Trenz
PDF File LSHM-1XX-XX.X-XX-DV-A-X-X-TR-MKT.pdf Technical drawing 07 04, 2016 by Thorsten Trenz
PDF File REF-189016-01.pdf Technical Drawing 07 04, 2016 by Thorsten Trenz
PDF File REF-189016-02.pdf Technical Drawing 07 04, 2016 by Thorsten Trenz
PDF File REF-189017-01.pdf Technical Drawing 07 04, 2016 by Thorsten Trenz
PDF File REF-189017-02.pdf Technical Drawing 07 04, 2016 by Thorsten Trenz
PDF File TC0923--2523_report_Rev_2_qua.pdf Design qualification test report 07 04, 2016 by Thorsten Trenz
PDF File tc0929--2611_qua(1).pdf Shock and vibration report 07 04, 2016 by Thorsten Trenz



Technical Specifications

Absolute Maximum Ratings *)

Power Rail Name/ Schematic NameDescriptionMinMaxUnit
VINSupply voltage-0.36.0V
3.3VINSupply voltage-0.33.75V

VCCIOB

I/O bank voltage-0.53.6V
VCCIODI/O bank voltage-0.52.0V
Absolute maximum ratings

*) Stresses beyond those listed under Absolute Maximum Ratings may cause permanent damage to the device. These are stress ratings only, which do not imply functional operation of the device at these
   or any other conditions beyond those indicated under Recommended Operating Condition. Exposure to absolute-maximum rated conditions for extended periods may affect device reliability.

Recommended Operating Conditions

This TRM is generic for all variants. Temperature range can be differ depending on the assembly version.  Voltage range is mostly the same during variants (exceptions are possible, depending on custom request)

Operating temperature range depends also on customer design and cooling solution. Please contact us for options.

  • Variants of modules are described here: Article Number Information
  • Modules with commercial temperature grade are equipped with components that cover at least the range of 0°C to 75°C
  • Modules with extended temperature grade are equipped with components that cover at least the range of 0°C to 85°C
  • Modules with industrial temperature grade are equipped with components that cover at least the range of -40°C to 85°C
  • The actual operating temperature range will depend on the FPGA / SoC design / usage and cooling and other variables.


ParameterMinMaxUnitsReference Document
VIN3.1353.465V
3.3VIN3.1353.465V

VCCIOB

1.143.465VSee FPGA datasheet.
VCCIOD1.141.89VSee FPGA datasheet.

1) Higher and lower values may be possible. For more information consult schematic and according datasheets.

Recommended operating conditions.

Physical Dimensions

  • Module size: 40 mm × 50 mm.  Please download the assembly diagram for exact numbers.

  • Mating height with standard connectors: 8 mm.

PCB thickness: 1.74 mm.

Physical Dimension

Currently Offered Variants 


Trenz shop TEM0007 overview page
English pageGerman page
Trenz Electronic Shop Overview

Revision History

Hardware Revision History

Board hardware revision number.

DateRevisionChangesDocumentation Link
2020-05-2601Inital ReleaseTEM0007-01
Hardware Revision History

Hardware revision number can be found on the PCB board together with the module model number separated by the dash.

Document Change History

DateRevisionContributorDescription

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3589#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3589#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3589#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

Link fixed

2023-11-07

v.45

ED

Initial Release

--

all

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3589#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]

  • --
Document change history.

Disclaimer

Data Privacy

Please also note our data protection declaration at https://www.trenz-electronic.de/en/Data-protection-Privacy

Document Warranty

The material contained in this document is provided “as is” and is subject to being changed at any time without notice. Trenz Electronic does not warrant the accuracy and completeness of the materials in this document. Further, to the maximum extent permitted by applicable law, Trenz Electronic disclaims all warranties, either express or implied, with regard to this document and any information contained herein, including but not limited to the implied warranties of merchantability, fitness for a particular purpose or non infringement of intellectual property. Trenz Electronic shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein.

Limitation of Liability

In no event will Trenz Electronic, its suppliers, or other third parties mentioned in this document be liable for any damages whatsoever (including, without limitation, those resulting from lost profits, lost data or business interruption) arising out of the use, inability to use, or the results of use of this document, any documents linked to this document, or the materials or information contained at any or all such documents. If your use of the materials or information from this document results in the need for servicing, repair or correction of equipment or data, you assume all costs thereof.

Copyright Notice

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Trenz Electronic.

Technology Licenses

The hardware / firmware / software described in this document are furnished under a license and may be used /modified / copied only in accordance with the terms of such license.

Environmental Protection

To confront directly with the responsibility toward the environment, the global community and eventually also oneself. Such a resolution should be integral part not only of everybody's life. Also enterprises shall be conscious of their social responsibility and contribute to the preservation of our common living space. That is why Trenz Electronic invests in the protection of our Environment.

REACH, RoHS and WEEE

REACH

Trenz Electronic is a manufacturer and a distributor of electronic products. It is therefore a so called downstream user in the sense of REACH. The products we supply to you are solely non-chemical products (goods). Moreover and under normal and reasonably foreseeable circumstances of application, the goods supplied to you shall not release any substance. For that, Trenz Electronic is obliged to neither register nor to provide safety data sheet. According to present knowledge and to best of our knowledge, no SVHC (Substances of Very High Concern) on the Candidate List are contained in our products. Furthermore, we will immediately and unsolicited inform our customers in compliance with REACH - Article 33 if any substance present in our goods (above a concentration of 0,1 % weight by weight) will be classified as SVHC by the European Chemicals Agency (ECHA).

RoHS

Trenz Electronic GmbH herewith declares that all its products are developed, manufactured and distributed RoHS compliant.

WEEE

Information for users within the European Union in accordance with Directive 2002/96/EC of the European Parliament and of the Council of 27 January 2003 on waste electrical and electronic equipment (WEEE).

Users of electrical and electronic equipment in private households are required not to dispose of waste electrical and electronic equipment as unsorted municipal waste and to collect such waste electrical and electronic equipment separately. By the 13 August 2005, Member States shall have ensured that systems are set up allowing final holders and distributors to return waste electrical and electronic equipment at least free of charge. Member States shall ensure the availability and accessibility of the necessary collection facilities. Separate collection is the precondition to ensure specific treatment and recycling of waste electrical and electronic equipment and is necessary to achieve the chosen level of protection of human health and the environment in the European Union. Consumers have to actively contribute to the success of such collection and the return of waste electrical and electronic equipment. Presence of hazardous substances in electrical and electronic equipment results in potential effects on the environment and human health. The symbol consisting of the crossed-out wheeled bin indicates separate collection for waste electrical and electronic equipment.

Trenz Electronic is registered under WEEE-Reg.-Nr. DE97922676.


Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3589#hasContentLevelPermission. Cannot resolve which method to invoke for [null, class java.lang.String, class com.atlassian.confluence.pages.Page] due to overlapping prototypes between: [interface com.atlassian.confluence.user.ConfluenceUser, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject] [interface com.atlassian.user.User, class java.lang.String, class com.atlassian.confluence.core.ContentEntityObject]




Table of contents

v








  • No labels