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

Compare with Current View Page History

« Previous Version 7 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

Dip Switch

DIP Switch S2
S2-1S2-2S2-3S2-4Description
CM1CM0JTAGENMIO0JTAGEN set carrier board CPLD into the chain for firmware update.

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). CM1 and CM0 are pulled up in CPLD.

S2-2S2-3CM0 (PROGMODE) (S2-2)JTAGEN (S2-3)Description
OFFOFF11Access to TEB2000 CPLD
OFFON10Access to CPLD of B2B Module
ONOFF01Access to TEB2000 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.

EN1

EN1 is set to one.

NOSEQ

NOSEQ pulled up to 3.3V. NOSEQ can be set or reset by i2c interface in linux console, if an i2c interface is prepared for this in linux. 

NOSEQConnected toRelated command in linux consoleDescription
'0'GPIO_output[16]
i2cset -y <related bus> 0x20 0x02 0x00
It is depends on the linux design. For example → i2cset -y 0 0x20 0x02 0x00
'1'GPIO_output[16]
i2cset -y <related bus> 0x20 0x02 0x01
It is depends on the linux design. For example → i2cset -y 0 0x20 0x02 0x01


To read the NOSEQ status, GPIO_input[16] must be read like the following instruction: 


i2cget -y <related bus> 0x20 0x02

For example --> i2cget -y 0 0x20 0x02

PGOOD

PGOOD pulled up to 3.3V. PGOOD pin can be set or reset by user. If CM1 set to high (S2-1 OFF) , PGOOD will be set to high otherwise PGOOD is set to low.

PGOODConditionDescription
'0'

CM1 = '0'

Dip switch S2-1 ON
'1'CM1 = '1'Dip switch S2-1 OFF

Reset

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

PinCPLD PinConnected toDescription
RESIN119B2B JB2 Pin 17Active-low

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

MIO14 is driven by BDBUS0 (FTDI RX). BDBUS1 (FTDI TX) is driven by MIO15 . MIO13 is driven by UART_TXD. UART_RXD is driven by MIO12.

UART 0  (HSS Console)
CPLD UART Input PinCPLD PinConnected toCPLD UART Output PinCPLD PinConnected toDescription
MIO12100B2B-JB1-100UART_RXD84U8-Pin 11
UART_TXD77U8-Pin 13MIO1399B2B-JB1-98
UART 1 (Linux Console)
CPLD UART Input PinCPLD PinConnected toCPLD UART Output PinCPLD PinConnected toDescription
FT_B_TX139FTDI Chip U4 Pin 32MIO14105B2B-JB1-91
MIO1595B2B-JB1-86FT_B_RX138FTDI Chip U4 Pin 33

SD

SD selection is set to GND (SD Card slot). MIO9 is switched to SD_CD and its status depends on SD_CD .

On-board LEDs

RJ45 Connector LEDDesignatorLED StatusConditionDescription
PHY_LED1 (Green LED Anode, Yellow LED Cathode) 

PHY_LED1R (Green LED Cathode, Yellow LED Anode)

J14B





Fast blink yellowPGOOD = '0'
Slow blink yellow greenCM0='1' → Access to CPLD of Module
GreenMIO0 = '1'
yellowMIO0 = '0'

PHY_LED2 (Green LED Cathode, Yellow LED Anode)

PHY_LED2R (Green LED Anode, Yellow LED Cathode)





J14CFast blink yellowPGOOD = '0'
Slow blink yellow greenCM0='1' → Access to CPLD of Module
GreenMIO0 = '1'
yellowMIO0 = '0'
LEDDesignatorLED StatusConditionDescription
ULED1 (Red)D1Blink, if Power Good is low

ON

FTDI UART RX

ULED2 (Green)D2Blink, if Power Good is low

ON

FTDI UART TX

FL_0 (Red)D3OFF

ON

User defined with B2B Pin JB2-99

FL_1 (Green)D4OFF

ON

User defined with B2B Pin JB2-90


I2C to GPIO

I2C to GPIO is a subsystem in firmware of CPLD that provides an i2c interface that writes received data to GPIO_output 8 bit registers or reads  8 bit GPIO_input registers and send read data to i2c bus. 

I2C to GPIO

I2C bus is connected to MIO10 ( SCL signal) and MIO11 (SDA signal). MIO10 to MIO15 are direct connection between CPLD of TEB2000 and FPGA on the module (for example TEM0007) through B2B connector. If in FPGA design exists  no i2c interface for MIO10 and MIO11, this block will be unused. More information about MIO10 to MIO15 are shown in the following table for TEM0007 modules and TEB2000 carrier board:

B2B PinB2B JB1-96B2B JB1-94B2B JB1-100B2B JB1-98B2B JB1-91B2B JB1-86
Carrier boardLabel / Firmware functionLabel / Firmware functionLabel / Firmware functionLabel / Firmware functionLabel / Firmware functionLabel / Firmware functionDescription
TEB2000MIO10 / I2C-SCLMIO11 / I2C-SDAMIO12 / GPIOMIO13 / GPIOMIO14 / UART0-RXMIO15 / USRT0-TXMIO10 and MIO11 are used in CPLD firmware as I2C SCL and SDA  respectively.
B2B PinB2B JM1-95B2B JM1-93B2B JM1-99B2B JM1-97B2B JM1-92B2B JM1-85
Module Label / Chip pinLabel / Chip pinLabel / Chip pinLabel / Chip pinLabel / Chip pinLabel / Chip pinDescription
TEM0007I2C_CON_SCL / A3I2C_CON_SDA / E3UART_CON_TX / C2USRT_CON_RX / D3UART_RX / H2UART_TX / H5MIO10 and MIO11 are already set in test_design of

There are more additional connections between CPLD and FPGA on the module , that are listed in the following table:

CPLD PinCarrier board B2B PinModule B2B PinIn firmware used asDescription
X6B2B JB1-84B2B JM1-83No specific function. It can only be read by GPIO_input. It can be read via i2c to GPIO.  ( GPIO_input(31) )
Y0B2B JB2-76B2B JM2-75No specific function. It can only be read by GPIO_input.It can be read via i2c to GPIO.  ( GPIO_input(24) )
Y1B2B JB2-78B2B JM2-77No specific function. It can only be read by GPIO_input. It can be read via i2c to GPIO.  ( GPIO_input(25) )
Y2B2B JB2-82B2B JM2-81No specific function. It can only be read by GPIO_input. It can be read via i2c to GPIO.  ( GPIO_input(26) )
Y3B2B JB2-84B2B JM2-83No specific function. It can only be read by GPIO_input. It can be read via i2c to GPIO.  ( GPIO_input(27) )
Y4B2B JB2-86B2B JM2-85No specific function. It can only be read by GPIO_input. It can be read via i2c to GPIO.  ( GPIO_input(28) )
Y5B2B JB2-88B2B JM2-87No specific function. It can only be read by GPIO_input. It can be read via i2c to GPIO.  ( GPIO_input(29) )
Y6B2B JB2-90B2B JM2-89No specific function. It can only be read by GPIO_input. It can be read via i2c to GPIO.  ( GPIO_input(30) )

I2C to GPIO registers access methods

I2C to GPIO subsystem has 4 output and 4 input 8 bit registers. These registers can be written or read in linux  as shown in the following tables:

GPIO input registerAddressRead command in LinuxDescription
GPIO_input[7:0]0x00
i2cget -y 0 0x20 0x00
0x20 is device address. ( I2C to GPIO address).
GPIO_input[15:8]0x01
i2cget -y 0 0x20 0x01
0x20 is device address. ( I2C to GPIO address).
GPIO_input[23:16]0x02
i2cget -y 0 0x20 0x02
0x20 is device address. ( I2C to GPIO address).
GPIO_input[31:24]0x03
i2cget -y 0 0x20 0x03
0x20 is device address. ( I2C to GPIO address).
GPIO output registerAddressWrite command in LinuxDescription
GPIO_output[7:0]0x00
i2cset -y 0 0x20 0x00 <data>
0x20 is device address. ( I2C to GPIO address). 0x00 is register address.
GPIO_output[15:8]0x01
i2cset -y 0 0x20 0x01 <data>
0x20 is device address. ( I2C to GPIO address). 0x01 is register address.
GPIO_output[23:16]0x02
i2cset -y 0 0x20 0x02 <data>
0x20 is device address. ( I2C to GPIO address). 0x02 is register address.
GPIO_output[31:24]0x03
i2cset -y 0 0x20 0x03 <data>
0x20 is device address. ( I2C to GPIO address). 0x03 is register address.

I2C to GPIO registers

GPIO input registers

The following port or signals can be read via GPIO_input[ ] registers. 

GPIO input bitPort/SignalDescription
0CPLD_REVISION [0]
1CPLD_REVISION [1]
2CPLD_REVISION [2]
3CPLD_REVISION [3]
4CPLD_REVISION [4]
5CPLD_REVISION [5]
6CPLD_REVISION [6]
7CPLD_REVISION [7]
GPIO input bitPort/SignalDescription
8X0
9X1
10X2
11X3
12X4
13X5
14X6
15X7
GPIO input bitPort/SignalDescription
16NOSEQ
17X8
18X9
19X10
20X11
21X12
22X13
23X14
GPIO input bitPort/SignalDescription
24X15
25X16
26X17
27CM0
28CM1
29PGOOD
30S1
31USB_OC
GPIO output registers

 The following port or signals can be written via GPIO_output[ ] registers.

GPIO output bitPort/SignalDescription
0Reserved
1Reserved
2Reserved
3Reserved
4Reserved
5Reserved
6Reserved
7Reserved
GPIO output bitPort/SignalDescription
8X0
9X1
10X2
11X3
12X4
13X5
14X6
15X7
GPIO output bitPort/SignalDescription
16NOSEQ
17X8
18X9
19X10
20X11
21X12
22X13
23X14
GPIO output bitPort/SignalDescription
24X15
25X16
26X17
27Reserved
28Reserved
29Reserved
30Reserved
31Reserved

Appx. A: Change History and Legal Notices

Revision Changes

  • REV01

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]

REV01

REV01 

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]

  • REV01 release
  • Firmware release (*.zip) 

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