Table of contents

Overview

CPLD Device with designator U21: LCMX02-256HC

Feature Summary

  • JTAG routing
  • Boot Mode settings
  • Power/Status Management

Firmware Revision and supported PCB Revision

See Document Change History

Product Specification

Port Description

Name / opt. VHD NameDirectionPinBank PowerDescription
C_TCK     in303.3VINJTAG B2B
C_TDI     in323.3VINJTAG B2B
C_TDO     out13.3VINJTAG B2B
C_TMS     in293.3VINJTAG B2B
EN1       in273.3VINPower Enable from B2B Connector (Positive Enable) / Used only for PGOOD feedback
ERR_OUT   in41.8VPS_ERROR_OUT, see ug1085
ERR_STATUSin51.8VPS_ERROR_STATUS, see ug1085 / currently_not_used
JTAGEN    in263.3VINEnable JTAG access to CPLD for Firmware update (zero: JTAG routed to module, one: CPLD access)
MODE      in253.3VINBoot Mode for Zynq/ZynqMP Devices (Flash or SD)
MODE0     out121.8VZynqMP Boot Mode Pin 0
MODE1     out131.8VZynqMP Boot Mode Pin 1
MODE2     out141.8VZynqMP Boot Mode Pin 2
MODE3     out161.8VZynqMP Boot Mode Pin  3
NOSEQ     inout233.3VINusage CPLD Variant depends
PGOOD     out283.3VINModule Power Good.
PHY_LED1  in171.8VETH PHY LED1
TCK     out91.8VJTAG ZynqMP
TDI       out81.8VJTAG ZynqMP
TDO       in101.8VJTAG ZynqMP
TMS       out111.8VJTAG ZynqMP
X0        out20VCCO_65FPGA IO / Firmware Variant
X1        out21VCCO_65FPGA IO / PHY_LED1


Functional Description

JTAG

JTAG signals routed directly through the CPLD to FPGA. Access between CPLD and FPGA can be multiplexed via JTAGEN (logical one for CPLD, logical zero for FPGA) on JM1-89.

Boot Mode

Boot Modes can be selected via B2B Pin Mode. Trenz Electronic provides currently 4 Firmware variants, one for SD/JTAG, one for JTAG/QSPI, one for SD/QSPI and SD/QSPI/JTAG usage.

ModeJTAG/QSPI-VariantSD/JTAG-Variant

SD/QSPI

(default Firmware)

SD/QSPI/JTAG
lowJTAGBoot from SDBoot from SDJTAG Mode, if NOSEQ* is high otherwise boot from SD
highBoot from FlashJTAGBoot from FlashJTAG Mode, if NOSEQ* is high otherwise boot from Flash

For other UltraScale+ Boot Modes options custom firmware is needed, see also Table 11.1 Boot Modes from Xilinx UG1085.

A special FSBL is provided on 2017.4 or newer reference designs to write boot image to QSPI with Xilinx tools (Vivado or SDK) on Boot Mode unequal JTAG .

NOSEQ*: Please check the carrier board documentation, before using the SD/QSPI/JTAG  firmware variant on TE0820. In the most cases special carrier CPLD firmware is needed.

Power

PGOOD is EN1 and not ER_OUT. There is no additional power management controlled by CPLD.

Internal pullup is used for detection, ER_OUT IO powered by 1.8V. To detect power status, also B2B 1.8V or 3.3V output is usable.

X0/X1 Pin

PinDescription
X0*indicate firmware variant and NOSEQ status
X1PHY_LED1

*It's recommended to forward this signal to a carrier LED if status check is needed.

Firmware VariantBlink sequenceCondition
QSPI/JTAG*oooooooif boot mode /= JTAG otherwise const. high if NOSEQ='1' or const low if NOSEQ='0'
JTAG/SD**ooooooif boot mode /= JTAG otherwise const. high if NOSEQ='1' or const low if NOSEQ='0'
QSPI/SD****oooo/************oooo if NOSEQ='1' or ******** if NOSEQ='0'
SD/QSPI/JTAG***oooooif boot mode /= JTAG otherwise const. high if NOSEQ='1' or const low if NOSEQ='0'


Appx. A: Change History

Revision Changes

  • REV02 to REV03
    • new Boot Mode variants
    • new X0 status blink sequencing
  • REV01 to REV02
    • Boot Mode variants
    • X1
    • Remove ERR_STATUS

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

REV03REV02, REV01

Error rendering macro 'page-info'

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


  • Update Port Table
  • Rename page

v.13REV03REV02, REV01
  • Revision 03 finished
2018-01-10v.10REV02REV02, REV01John Hartfiel
  • update description - PHY LED correction
2017-08-21v.9REV02REV02, REV01John Hartfiel
  • Revision 02 finished
  • small text updates
2017-08-17v.8REV02REV02, REV01John Hartfiel
  • Revision 02 working in process
  • Boot Mode
  • X1 output
2017-06-08v.4REV01REV01John Hartfiel
  • document style update
2017-03-06v.2REV01REV01John Hartfiel
  • Revision 01 finished
2017-03-06

v.1

REV01REV01

Error rendering macro 'page-info'

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