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

Compare with Current View Page History

« Previous Version 2 Next »



Overview

CPLD Device with designator U5: LCMX02-1200HC.

Feature Summary

  • JTAG
  • UART
  • I2C
  • Power
  • Boot Mode
  • Reset
  • SD
  • LED

Firmware Revision and supported PCB Revision

See Document Change History

Product Specification

Port Description

Name / opt. VHD NameDirectionPinPullup/DownBank PowerDescription

UART_TXD

in77NONE3.3V

UART0 TX / Sends data to MIO13. MIO13 is connected to B2B JB1 Pin 98. ( HSS console )

UART_RXDout84NONE3.3V

UART0 RX / Recieves data from MIO12. MIO12  is connected to B2B JB1 Pin 100. ( HSS console )

CM0in76UP3.3V

DIP switch S2-2 / used as JTAG Selection/ If CM0 set to high (S2-2 OFF) → Access to CPLD of module otherwise access to FPGA of module.

CM1in75UP3.3VDIP switch S2-1 / Used to change PGOOD pin state /If CM1 set to high (S2-1 OFF) → PGOOD = '1' otherwise '0'
EN1out81NONE3.3VB2B Power Enable
FL_0inout28NONE3.3V LED (D3-red) / Status 
FL_1inout27NONE3.3VLED (D4-green) / Status
FT_B_RXout138NONE3.3VFTDI UART RX (UART1 RX)
FT_B_TX / BDBUS0in139UP3.3VFTDI UART TX (UART1 TX)
JTAGEN---120---3.3VEnable JTAG access to CPLD for Firmware update (zero: normal IOs, one: CPLD JTAG access). Selectable over S2-3
M_TCKin131NONE3.3VJTAG from/to FTDI
M_TDIin136NONE3.3VJTAG from/to FTDI
M_TDOout137NONE3.3VJTAG from/to FTDI
M_TMSin130NONE3.3VJTAG from/to FTDI
MIO0in94UP3.3VDIP-S4 and B2B JB1 Pin 88. This signal is connected to MODE signal.
MIO12in100NONE3.3VSends data to UART_RX
MIO13out99NONE3.3VRead data from UART_TX 
MIO14out105NONE3.3VReceives data from FT_B_TX of FTDI chip
MIO15in95NONE3.3VSends data to FT_B_RX of FTDI chip
MIO9 out96NONE3.3V SD_CD signal is directed to this signal in firmware. 
MODEout83NONE3.3VDip switch S2-4 is connected to MODE pin ( B2B-JB1-31)
NOSEQ inout78UP3.3VNOSEQ can be set or reset by i2c interface in linux console, if an i2c interface is prepared for this in linux. 
PGOOD inout82UP3.3VPGOOD can be set or reset via CM1 ( dip switch S2-1)
PHY_LED1 out86DOWN3.3V Shows the status of PGOOD, CM0 or MIO0 signals.
PHY_LED1R out92NONE3.3V Shows the status of PGOOD, CM0 or MIO0 signals.
PHY_LED2 out85NONE3.3VShows the status of PGOOD, CM0 or MIO0 signals.
PHY_LED2R out91NONE3.3V Shows the status of PGOOD, CM0 or MIO0 signals.   
PROGMODEout104UP3.3VEnable B2B Module JTAG access to CPLD for Firmware update
RESINout119NONE3.3VModule Reset Pin on B2B connector
S1in114UP3.3VPush Button / Used as module Reset
SD_CD in93UP3.3VForwarded to MIO9
SD_SEL out113NONE3.3VSet to GND / currently_not_used
TCK_Bout1NONE3.3VJTAG from/to Module
TDI_Bout3NONE3.3VJTAG from/to Module
TDO_B / C_TDOin2UP3.3VJTAG from/to Module
TMS_Bout4NONE3.3VJTAG from/to Module
ULED1out117NONE3.3VLED (D1-red) / Shows the status of PGOOD, CM0 or shows the UART1 RX.
ULED2out115NONE3.3VLED (D2-green) / Shows the status of PGOOD, CM0 or shows the UART1 TX.
X16in59UP3.3Vcurrently_not_used
X17out60NONE3.3Vcurrently_not_used
SDA / MIO11inout97UP3.3VI2C Data
SCL /MIO10in98UP3.3VI2C Clock (100kHz)

Functional Description

JTAG

JTAG signals routed directly through the CPLD to module in B2B connector. Access between CPLD and module can be multiplexed via JTAGEN (logical one for CPLD, logical zero for module). TEB2000 CPLD can be selected with JTAGEN (DIP-S2-3). Module FPGA/CPLD access can be switched with PROGMODE which is driven by CM0 (DIP-S2-2).CM0 is pulled up with CPLD.

If used SoM on the carrier board is TE0715, CPLD of TE0703  must be programmed a different jed file to arrange CPLD JTAG pins correctly. This module is an exception.  For this purpose it is defined a generic parameter in VHDL code to switch JTAG pins differently as other SoM modules. There are two jed files. CPLD of TE0715 module with default jed file for CPLD of carrier board TE0703 can not be programmed. But optional jed file exists for this purpose. In both cases default or optional jed file the following table is valid:

S2-2S2-3PROGMODE (S2-2)JTAGEN (S2-3)Description
OFFOFF11Access to TE0703 CPLD
OFFON10Access to CPLD of B2B Module
ONOFF01Access to TE0703 CPLD
ONON00Access to FPGA of B2B Module

Note: LED1,2,3,4 are on and PHY LEDs blink slow, if S2-2 is set to OFF.

Power

EN1 is set to one.

NOSEQ and PGOOD pulled up to VDD. NOSEQ pin is either high impedance or is used as JTAG pin to program CPLD of TE0715 module. PGOOD pin can be set or reset by user. If CM0 or CM1 set to high (S2-2 or S2-1 OFF) , PGOOD will be set to high otherwise PGOOD is set to low.

Reset

RESIN is driven by S1 (Push Button). Button is debounced.

Boot Mode

MODE pin is sourced by MIO0. MIO0 connected DIP S2-4 and B2B connector. MIO is pulled up with CPLD and can be set to GND via DIP. PGOOD pin will be used as second select pin for boot mode selection. In this case the following table can be considered:  

S2-1S2-4PGOODMIO0Description
ONON00JTAG boot mode
OFFON10SD Card boot mode, PHY LEDs glow orange
OFFOFF11QSPI boot mode, PHY LEDs glow green

UART

Primary UART:

MIO14 is driven by BDBUS0 (FTDI RX).

BDBUS1 (FTDI TX) is driven by MIO15 .

Secondary UART:

MIO13 is driven by X16.

X17 is driven by MIO12.

SD

SD selection is set to GND (SD Card slot).

MIO9 is switched to SD_CD and its status depends on SD_CD .

LED

LED Priority is order of the description

LEDPrio 0: PowerPrio 1: Modul CPLD access*Prio 2
LED1 (D1-red)Blink, if Power Good is lowONFTDI UART RX
LED2 (D2-green)Blink, if Power Good is lowONFTDI UART TX
LED3 (D3-red)OFFONUser defined with B2B Pin JB2-99
LED4 (D4-green)OFFONUser defined with B2B Pin JB2-90
PHY LEDs (green/orange)Blink orange, if Power Good is lowBlink Green and orangeGreen: Boot Mode set  to QSPI, Orange: Boot Mode set to SD

*Attention: LED1,2,3,4 are on, if S2-2 is set to OFF. If S2-3 is OFF, TE0703 is in chain!

Appx. A: Change History and Legal Notices

Revision Changes

  • REV02 to REV03
    • Oscillator frequency is changed from 12.09 MHz to 24.18 MHZ.

    •  Access to CPLD of TE0715 with a generic parameter added. (For optional jed file to access CPLD of TE0715 module)

    • PGOOD used as second boot mode selector pin and connected to dip switch S2-1. PGOOD and MODE are boot mode selector pins.

    • S2-1 dip switch (CM1) functionality is changed.In HW PCB REV0 to REV04 is used for SD card detection but in HW PCB REV05 and REV06 is used to set or reset PGOOD.
    • MIO14 is connected to FTDI_RXD directly without depending on PGOOD.
    • CM1 (Dip switch S2-2) has no effect on MIO9 anymore. That means MIO9 is connected to SD_CD only and not to SD_CD and CM1.
  • REV02 to older REV01
    • Enable CPLD access to module CPLD over DIP
    • Add MIO0, SD_SEL, SD_CD, NOSEQ, PGOOD, 2LEDs, PHY LEDs
    • Debounce button
    • More status LED functionality

Document Change History

To get content of older revision  got to "Change History"  of this page and select older document revision number.


DateDocument RevisionCPLD Firmware RevisionSupported PCB RevisionAuthorsDescription

Error rendering macro 'page-info'

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

REV03

REV05, REV06

Error rendering macro 'page-info'

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

  • REV03 release
  • Firmware release (SC-PGM-TE0703-0506_CARRIER-03_20220815.zip)
  • PGOOD as secondboot mode select pin
  • TE0715 CPLD programming is possible
2019-11-08v.13REV02REV02*,REV03*,REV04*,REV05, REV06
*some IOs are not connected *SD_CD not available, set S2-1 to on
John Hartfiel
  • Typo
  • Note PCB REV06 support

2017-10-13

v.11




REV02

REV02*,REV03*,REV04*,REV05
*some IOs are not connected
*SD_CD not available, set S2-1 to on

  • REV 02 finished
2016-04-11

v.1

REV02

REV02*,REV03*,REV04*,REV05
*some unused IOs are not connected
*SD_CD not available, set S2-1 to on

  • Initial release

All


Appx. B: Legal Notices

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.proxy308.$Proxy4686#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

  • No labels