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

Compare with Current View Page History

« Previous Version 21 Next »

Table of contents

Overview

CPLD Device: LCMX02-1200HC

Feature Summary

  • Power Management
    • VADJ Configuration via DIP-Switch or I2C
  • Reset Management
  • Boot Mode Controller
  • FPGA UART routing
  • RGPIO Interface to FPGA

Firmware Revision and supported PCB Revision

See Document Change History

Product Specification

Port Description

NameDirectionPinDescription
ACBUS4                96FTDI / currently_not_used
ACBUS5                88FTDI / currently_not_used
ADBUS4               out98constant 0 / currently_not_used
ADBUS7               in97/ currently_not_used
BDBUS0               in87UART TX from FTDI
BDBUS1               out86UART RX to FTDI
C_TCKout81JTAG FTDI
C_TDIout84JTAG FTDI
C_TDOin83JTAG FTDI
C_TMSout85JTAG FTDI
CM0                  in99DIP Switch S3-M1
CM1                  in1DIP Switch S3-M2

CM2

in51REV06+ only: DIP Switch S4-1 / RGPIO Bus (powered by VIOTB (FMC VADJ))
EN_FMC               out31VADJ and 3V3V_FMC Power on
EN1                  out24Power Enable Pin for Module CPLD
FMC_PRSNT            in28FMC Card present pin (zero if not present)
FMC_SCL              out10FMC I2C
FMC_SDAinout8FMC I2C
FMC_TCK              out4JTAG FMC / currently_not_used
FMC_TDI              out12JTAG FMC / currently_not_used
FMC_TDO              in9JTAG FMC / currently_not_used
FMC_TMS              out7JTAG FMC / currently_not_used
HDMI_SCL             inout47HDMI / used also for I2C FMC control
HDMI_SDA             inout45HDMI / used also for I2C FMC control
HDMI_SPDIF           out15HDMI / currently_not_used
HDMI_SPDIFOUT        in14HDMI / currently_not_used
JTAGEN               --82

Enable JTAG access to carrier CPLD for Firmware update (zero: JTAG routed to module, one: CPLD access)

Set DIP Switch S3-JTAGEN to ON, for module access.

M_TCK                in91JTAG Module
M_TDI                in94JTAG Module
M_TDO                out95JTAG Module
M_TMS                in90JTAG Module
MIO10                inout29MIO
MIO11                inout19MIO
MIO12                inout36MIO
MIO13                inout30MIO
MIO14                inout37MIO / Module UART0.RX << BDBUS0
MIO15                in18MIO / Module UART0.TX >> BDBUS1
MODE                 out27Boot Mode for Zynq Devices (Flash or SD)
NOSEQ                inout21No Sequence, connected to Module CPLD / currently_not_used 
PG_C2M               out20Power Good for FMC
PGOOD                inout25connected to Module CPLD / currently_not_used
PHY_LED1             out42PHY LED
PHY_LED2             out43PHY LED
POK_FMC              in32FMC Power good from FMC VADJ DCDC
PX6                  inout49PMOD J2
PX7                  inout48PMOD J2 
RESIN                out13Module Reset
REVISION_DETECIONin57REV06+ only: Detection / currently_not_used
S1                   in3User Pushbutton
S2                   in2User Pushbutton / global Reset
SD_DETECT            in40SD Detection
SD_WP                in41SD
SEL_SD               out39SD Selection, MMC SD Slot or PMOD J2
ULED1                out78LED D1
ULED2                out77LED D2
ULED3                out76LED D3
ULED4                out16LED D4
ULED5                out69LED D5, powered by VIOTB (FMC VADJ)
ULED6                out68LED D6, powered by VIOTB (FMC VADJ)
ULED7                out65LED D7, powered by VIOTB (FMC VADJ)
ULED8                out64LED D8, powered by VIOTB (FMC VADJ)
USB_OC               in17USB Over Current
VID0                 out34VADJ Voltage selection (EN5335QI)
VID1                 out35VADJ Voltage selection (EN5335QI)
VID2                 out38VADJ Voltage selection (EN5335QI)
X6                   in60Module IO (powered by VIOTB (FMC VADJ))
Y0                   in75I2C SCL (powered by VIOTB (FMC VADJ))
Y1                   out66I2C SDA_OUT (powered by VIOTB (FMC VADJ))
Y2                   in67RGPIO CLK (powered by VIOTB (FMC VADJ))
Y3                   out70RGPIO TX (powered by VIOTB (FMC VADJ))
Y4                   in74RGPIO RX (powered by VIOTB (FMC VADJ))
Y5                   in71I2C SDA_IN (powered by VIOTB (FMC VADJ))
Y6                   in63Module IO (powered by VIOTB (FMC VADJ))

 

Functional Description

JTAG

JTAGEN set carrier board CPLD into the chain for firmware update. In normal mode JTAG is routed directly to Module. Set S3-ENJTAG to OFF to get access to carrier CPLD.

FMC JTAG is currently not enabled.

Power

EN1 is set to logical one .

EN_FMC is set to logical one or is controlled by I2C on I2C Mode.

PG_C2M is set to logical one or is controlled by I2C on I2C Mode.

VADJ on PCB REV06+ S4 Control

This mode is only available on PCB Revision 06 or higher.

S4 control will be enabled on power on sequence or reset (S2-Button), if one of the three S4-DIP switches is set to one.

In this Mode I2C-controll is not selectable and S3-M1 and S3-M2 are available as User-DIP-Switch.

S4-3(VID2)S4-2(VID1)S4-1(VID0)Description
ONONONVADJ: 3.3V
ONONOFFVADJ: 2.5V
ONOFFONVADJ: 1.8V
ONOFFOFFVADJ: 1.5V
OFFONONVADJ: 1.25V
OFFONOFFVADJ: 1.2V
OFFOFFONVADJ: 0.8V
OFFOFFOFFused to set VADJ control to REV05- or I2C control after power up sequence

VADJ on PCB REV05- S3 Control

S4 control will be disabled on power on sequence or reset (S2-Button), if all of the three S4-DIP switches is set to OFF or older PCB revision is used.

Do not set S4-Switches to ON, if REV05- or I2C control is enabled.

S3-M1S3-M2Description
OFFOFFVADJ: 1.8V
OFFONVADJ: 2.5V
ONOFFVADJ: 3.3V
OnONI2C controlled

VADJ on I2C Control

Disable S4 Control and set S3-M1 and S3-M2 to on. I2C VADJ Control use TE0701 HDMI I2C Bus (HDMI_SCL and HDMI_SDA) connected to module FPGA PL side. I2C-GPIO controller device address is 0x22. Transmitted data will be converted to a 8-bit GPIO bus.

BitAccessDefaultDescription
7R/W0FMC - Enable
6R/W0VID2
5R/W0VID1
4R/W0VID0
3R/W0PG_C2M - Enable
2RxPOK_FMC (EN5335QI Power OK)
1Rxone: I2C Mode, zero: DIP Mode,
0RxVID Mode (zero: S4-DIP-controlled, one:  REV05-/I2C controlled)
VID2VID1VID0Description
000VADJ: 3.3V
001VADJ: 2.5V
010VADJ: 1.8V
011VADJ: 1.5V
100VADJ: 1.25V
101VADJ: 1.2V
110VADJ: 0.8V
111reserved

To read I2C with petalinux use i2cget -y 0 0x22.

  • -y: do not confirm input
  • 0: I2CBUS, use bus number, which is connected to TE0701 HDMI I2C Bus (HDMI_SCL and HDMI_SDA)
  • 0x22 I2C GPIO controller on TE0701 CPLD

To write I2C with petalinux use i2cset -y 0 0x22 0x80

  • -y: do not confirm input
  • 0: I2CBUS, use bus number, which is connected to TE0701 HDMI I2C Bus (HDMI_SCL and HDMI_SDA)
  • 0x22 I2C GPIO controller on TE0701 CPLD
  • 0x80: Enable FMC Power with VAD 3.3V, see I2C control table.

Reset

RESIN (negative Reset) to module, can be set by S2 button.

Boot Mode

Boot mode is set to SD-Boot, when SD-Card is detected.

RGPIO

RGPIO Master is a 32Bit Remote GPIO Interface to talk with FPGA over 3 lanes.

RGPIO Pin to FPGAValue
0MIO10
1MIO11
2MIO12
3MIO13
4MIO14
5MIO15
6PX6
7PX7
8S1
9CM0
10CM1
11CM2
12SD_WP
13SD_DETECT
14USB_OC
15POK_FMC
16FMC_PRSNT
17PGOOD
18NOSEQ
19unused
20X6
21Y6
22-23unused
24-27reserved
28-31Interface detection
RGPIO Pin from FPAGValue
0-7LED 1-8
8-9PHY_LED 1/2
10-23unused
24-27reserved
28-31Interface detection

LED

LEDDescription

ULED1

VADJ selection when RGPIO Bus is not active else RGPIO Bus Pin 0

VADJ selection: blink  when VCCIO(VIOTB/VADJ) is disabled else on when VADJ on PCB REV05- or I2C Control or off when VADJ on PCB REV06+ S4 Control 

ULED2I2C control mode  when RGPIO Bus is not active else RGPIO Bus Pin 1
ULED3UART to Module activity  when RGPIO Bus is not active else RGPIO Bus Pin 2
ULED4UART to FTDI activity  when RGPIO Bus is not active else RGPIO Bus Pin 3
ULED5BOOTMODE (on Flash, off SD)  when RGPIO Bus is not active else RGPIO Bus Pin 4
ULED6CM2 when RGPIO Bus is not active else RGPIO Bus Pin 5
ULED7X6 when RGPIO Bus is not active else RGPIO Bus Pin 6
ULED8Y6 when RGPIO Bus is not active else RGPIO Bus Pin 7
PHY LEDDescription
PHY_LED1Y2 when RGPIO Bus is not active else RGPIO Bus Pin 8
PHY_LED2Y4 when RGPIO Bus is not active else RGPIO Bus Pin 9

UART

ToFromDescription
MIO14BDBUS0Module UART0.RX
BDBUS1MIO15Module UART0.TX

 

Appx. A: Change History and Legal Notices

Revision Changes

Older Revisions to REV05

  • Power Management
    • three VADJ Control Modi (REV06+ S4 Control, REV05- S3 Control and I2C Control)
  • Reset Management
    • only little changes
  • RGPIO Interface to FPGA
    • RGPIO support
  • LED
    • new Order and accessible by RGPIO

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.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]


 

REV05REV03,REV04,REV05

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]


Revision 05 finished
2016-04-11

v.1

--- 

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]


Initial release
 All  
 

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.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]

 

  • No labels