You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Download PDF version of this document.

Table of Contents

Overview

The Trenz Electronic TEMB0005 is an industrial-grade carrier for the module TEM00005. The carrier is equipped with a Gigabit LAN socket, a USB2.0 interface, two different Samtec B2B Connectors, three Tiger Claw Samtec Dual Sockets, a PMod Connector, a pin header and  a FTDI.  Find more information in the FTDI sections.

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

Key Features

  • Modules
    • TEM0005
  • RAM/Storage
    • 2KB EEPROM
  • On Board
    • FT2232H FTDI
    • 4x User LED
    • 2x Push Button
  • Interface
    • 1x Samtec Razor Beam (SS5) B2B Connector
    • 1x Samtec Razor Beam (SS4) B2B Connector
    • 3x Samtec  Tiger Claw Dual Socket
    • 1x PMod SMD (2x6) Connector
    • 1x SMD Header (1x6)
    • RJ45 LAN Socket
    • Micro USB2.0 Connector
  • Power
    • 5V Input Power Supply 
  • Dimension
    • 115 x 70 mm
  • Notes


Block Diagram

TEMB0005 block diagram

Main Components

TEMB0005 main components
  1. SMD Header 6x1, J3
  2. RJ45 LAN Socket, J1
  3. B2B Razor Beam Connector, J11
  4. Barrel Jack, J4
  5. Green LEDs, D1...4
  6. User Push Button, S2
  7. PMod 2x6 SMD Host Socket, J9
  8. FT2232H FTDI, U1
  9. Reset Push Button, S1
  10. Micro USB2.0 Socket, J2
  11. Red LED (PG_DCDC), D8
  12. Green LED (5VIN), D5
  13. B2B Mezzanine Connector, J5
  14. Dual Wipe Socket, J8
  15. Dual Wipe Socket, J7
  16. Dual Wipe Socket, J6

Initial Delivery State

Storage device name

Content

Notes

EEPROMProgrammedFTDI Confirguration
Initial delivery state of programmable devices on the module

Configuration Signals

Signal

B2BConnected toNote

RESET

J11- 54B2B, J5General Reset
M_RESETJ11- 11Push Button, S1Module Reset
Reset process.

Signals, Interfaces and Pins

Board to Board (B2B) I/Os

FPGA bank number and number of I/O signals connected to the B2B connector:

FPGA BankB2B ConnectorI/O Signal CountVoltage LevelNotes






























General PL I/O to B2B connectors information

USB2.0 Socket

Pin SchematicConnected toNotes
























General PL I/O to B2B connectors information

RJ45 LAN Socket

Pin SchematicConnected toNotes
























General PL I/O to B2B connectors information

Dual Sockets

Pin SchematicConnected toNotes
























General PL I/O to B2B connectors information

PMod Header

Pin SchematicConnected toNotes
























General PL I/O to B2B connectors information

Pin Header

Pin SchematicConnected toNotes
























General PL I/O to B2B connectors information

UART 

PinSchematicU?? PinNotes

UART-Tx
Driver Input

UART-Rx
Reciever Output
CAN Tranciever interface MIOs


JTAG Interface

JTAG access is provided through B2B connector J11 connected to the FTDI. For more information please refer to the FTDI section.

JTAG Signal

B2B Connector

TMSJ11-14
TDIJ11-8
TDOJ11-10
TCK

J11-12

JTAGSELJ11-9
JTAG pins connection

Test Points

Test PointSignalConnected toNotes
TP1GOLDENB2B, J11
TP2JTAGSELB2B, J11
TP3PG_DCDCB2B, J11Red LED, D8
TP4VADJRegulator, U6
TP5PROBE_BB2B, J11
TP6PROBE_AB2B, J11
Test Points Information

On-board Peripherals

Chip/InterfaceDesignatorNotes















On board peripherals

EEPROM

MIO PinSchematicU?? PinNotes








I2C EEPROM interface MIOs and pins

MIO PinI2C AddressDesignatorNotes




I2C address for EEPROM

LEDs

DesignatorColorConnected toActive LevelNote
D1...D4GreenB2B, J11Active High
D5Green5VINActive High
D6RedPG_DCDCActive Low
On-board LEDs

CAN Transceiver

BankSchematicU?? PinNotes

D-Tx
Driver Input

R-Rx
Reciever Output
CAN Tranciever interface MIOs


Clock Sources

DesignatorDescriptionFrequencyNote
U4MEMS Oscillator12 MHz
U8MEMS Oscillator30 MHz
Osillators

Programmable Clock Generator

There is a programmable clock generator on-board (U??) provided in order to generate variable clocks for the module. Programming can be done using I2C via PIN header J??.  The I2C Address is 0x??.

U?? Pin
SignalConnected toDirectionNote

IN0





IN1



IN2



IN3



XAXB





SCLK



SDA



OUT0



OUT1



OUT2



OUT3



OUT4



OUT5



OUT6



OUT7



OUT8/OUT9



Programmable Clock Generator Inputs and Outputs

Power and Power-On Sequence

Power Supply

Power supply with minimum current capability of xx A for system startup is recommended.

Power Consumption

Power Input PinTypical Current
5VINTBD*
Power Consumption

* TBD - To Be Determined

Power Distribution Dependencies

Power Distribution

Power-On Sequence

Power Sequency

Power Rails

Power Rail Name

B2B Connector

JM1 Pin

B2B Connector

JM2 Pin

B2B Connector

JM3 Pin

DirectionNotes
























Module power rails.

Bank Voltages

Bank          

Schematic Name

Voltage

Notes




























Zynq SoC bank voltages.


Board to Board Connectors

? x ? modules use two or three Samtec Micro Tiger Eye Connector on the bottom side.

  • 3 x REF-??????? (compatible to ????????), (?? pins, ?? per row)

    Operating Temperature: -??°C ~ ??°C
    Current Rating: ??A per ContactNumber of Positions: ??
    Number of Rows: ??

Technical Specifications

Absolute Maximum Ratings

SymbolsDescriptionMinMaxUnit




V




V




V










PS absolute maximum ratings

Recommended Operating Conditions

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

ParameterMinMaxUnitsReference Document



VSee ???? datasheets.



VSee Xilinx ???? datasheet.



°CSee Xilinx ???? datasheet.



°CSee Xilinx ???? datasheet.
Recommended operating conditions.

Physical Dimensions

  • Module size: 115 mm × 70 mm.  Please download the assembly diagram for exact numbers.

  • Mating height with standard connectors: 5 mm.

PCB thickness: 1.7 mm.

Physical Dimension

Currently Offered Variants 

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

Revision History

Hardware Revision History


DateRevisionChangesDocumentation Link
2020-05-20REV01Initial Release---
Hardware Revision History

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

Board hardware revision number.

Document Change History

DateRevisionContributorDescription

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3578#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.$Proxy3578#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.$Proxy3578#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]

  • Initial Release

--

all

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3578#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.$Proxy3578#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]


  • No labels