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

Compare with Current View Page History

« Previous Version 34 Next »

Table of contents

Overview

CPLD Device with designator U14: LCMX02-1200HC

Feature Summary

  • Power Management
  • 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

Name / opt. VHD NameDirectionPinDescription
ACBUS4          in96FTDI / currently_not_used
ACBUS5          in88FTDI / currently_not_used
ADBUS4          out98FTDI  / get M_TCK
ADBUS7          out97FTDI / currently_not_used
BDBUS0          inout87FTDI / Module UART0.RX << FTDI
BDBUS1          inout86FTDI  /Module UART0.TX >> FTDI
C_TCKout81JTAG Module
C_TDIout84JTAG Module
C_TDOin83JTAG Module
C_TMSout85JTAG Module
CM0in67DIP Switch S3-M1
CM1in66DIP Switch S3-M2
EN_FMC          out35VADJ Power on
EN1             out53Power Enable Pin for Module CPLD
JTAGEN--82Enable 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.
JTAGMODEout58Enable JTAG access to module CPLD for Firmware update (zero: JTAG routed to module FPGA, one: Module CPLD access)
M_TCK           in91JTAG FTDI
M_TDI           in94JTAG FTDI
M_TDO           out95JTAG FTDI
M_TMS           in90JTAG FTDI
MIO10           inout32 MIO / used by RGPIO Bus
MIO11           inout31MIO / used by RGPIO Bus
MIO12           inout39 MIO / used by RGPIO Bus
MIO13           inout34 MIO / used by RGPIO Bus
MIO14           inout40MIO / Module UART0.RX << BDBUS0
MIO15           inout30MIO / Module  UART0.TX >> BDBUS1
MODE            out28Boot Mode for Zynq Devices (Flash or SD)
NOSEQ           inout29/ currently_not_used
PGOOD           inout27/ currently_not_used
PHY_LED1        out45LED Ethernet
PHY_LED1_A      out49LED Ethernet / currently_not_used
PHY_LED2        out47LED Ethernet
PHY_LED2_A      out48LED  Ethernet / currently_not_used
POK_FMC         in36FMC VADJ Power Good 
RESIN           out54Module Reset
S1              in75User Button / used by RGPIO Bus
S2              in74User Button / Global Reset
SD_DETECT       in42SD Detection / used for FPGA Boot Mode
SD_WP           in43SD / RGPIO Bus
ULED1           out78LED D6
ULED2           out77LED D7
ULED3           out76LED D8
ULED4           out65LED D9
ULED5           out71LED D4
ULED6           out70LED D15
ULED7           out69LED D14
ULED8           out68LED D5
USB_OC          in99USB Over Current
USR0in64DIP Switch S4-1 / used by RGPIO Bus (PCB REV04 only)
USR1in61DIP Switch S4-2 / used by RGPIO Bus (PCB REV04 only)
USR2in60DIP Switch S4-3 / used by RGPIO Bus (PCB REV04 only)
USR3in59DIP Switch S4-4 / used by RGPIO Bus (PCB REV04 only)
VID0            out37VADJ Voltage selection (EN5335QI)
VID1            out38VADJ Voltage selection (EN5335QI)
VID2            out41VADJ Voltage selection (EN5335QI)
X6              in19RGPIO Bus
Y0               15/ currently_not_used
Y1               14/ currently_not_used
Y2              in13RGPIO CLK
Y3              out10RGPIO TX
Y4              in9RGPIO RX
Y5               8/ currently_not_used
Y6              in7RGPIO Bus

 

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.

JTAGMODE set module CPLD into the chain for firmware update. In normal mode  JTAG is routed directly to FPGA. Set S3-ENJTAG, S3-M1 and S3-M2 to ON to get access to module CPLD. Attention VADJ is set to 1.8V in this mode.

Power

EN1 is set to logical one after delay.

EN_FMC is set to logical one after delay.

VADJ Selection Table:

M1M2Description
OFFOFFVADJ: 1.8V
OFFONVADJ: 2.5V
ONOFFVADJ: 3.3V
ONONVADJ: 1.8V, Attention: Also Module CPLD JTAG access is enabled, see JTAG description.

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
6-9USR0-USR3 (S4-1...S4-4)
10-11CM0-CM1(S3-M1...S3-M2)
12SD_WP
13SD_DETECT
14USB_OC
15POK_FMC
16S1
17PGOOD
18NOSEQ
19VID0
20X6
21Y6
22VID1
23VID2
24-27reserved
28-31Interface detection
RGPIO Pin from FPGAValue
0-7LED 1-8
08-23unused
24-27reserved
28-31Interface detection

LED

LEDDescription
ULED1not external reset / RGPIO(0), when FPGA Interface is detected
ULED2(M1=off,M2=off) / RGPIO(1), when FPGA Interface is detected
ULED3Module UART0.RX / RGPIO(2), when FPGA Interface is detected
ULED4Module UART0.TX / RGPIO(3), when FPGA Interface is detected
ULED5SD_DETECT / RGPIO(4), when FPGA Interface is detected
ULED6(M1=on,M2=off) / RGPIO(5), when FPGA Interface is detected
ULED7X6 / RGPIO(6), when FPGA Interface is detected
ULED8Y6 / RGPIO(7), when FPGA Interface is detected

 

UART

ToFromDescription
MIO14BDBUS0Module UART0.RX
BDBUS1MIO15Module UART0.TX

 

Appx. A: Change History

Revision Changes

REV01 to REV02

  • Power Management
    • VADJ is switchable by S3 dip switches
  • Reset Management
    • only little changes
  • RGPIO Interface to FPGA
    • RGPIO support
  • LED
    • new Order and accessible by RGPIO
  • Module CPLD access is possible know

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

REV02REV03, REV04

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 style update
2016-11-17

v.27

 

REV02REV03, REV04John HartfielRevision 02 finished
2016-11-04

 

v.1

--- 

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]

 

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