Overview

Firmware for PCB CPLD with designator U2. CPLD Device in Chain: LCMX02-256HC

Feature Summary

  • Power Management

  • JTAG

  • Boot Mode

  • LED

  • I2C

Firmware Revision and supported PCB Revision

See Document Change History

Product Specification

Port Description

Name / opt. VHD Name

Direction

Pin

Pullup/Down

Bank Power

Description

BOOTMODE_1

out

21

None

LVCMOS18

Boot Mode Pin, connected to Zynq MIO5 (U1)

EN_PL

out

23

Up

LVCMOS33

Enable PL Power, connected to U4

F_TMS

out

9

Up

LVCMOS18

JTAG chain to Zynq TMS (W11/U1), just pass through from TMS

SLEWRATE=FAST DRIVE=8

F_TCK

out

8

Up

LVCMOS18

JTAG chain to Zynq TCK (W12/U1), just pass through from TCK

SLEWRATE=FAST DRIVE=8

F_TDI

out

10

Up

LVCMOS18

JTAG chain to Zynq TDI (V11/U1), just pass through from TDI

SLEWRATE=FAST DRIVE=8

F_TDO

in

11

None

LVCMOS18

JTAG chain to Zynq TDO (W10/U1), just pass through from TDO, maxdelay 10ns

I2C_SCL

in

17

None

LVCMOS18

I2C Bus from SoC

I2C_SDA

inout

16

None

LVCMOS18

I2C Bus from SoC

JTAG_EN

in

26

-

VCCIO 3.3 V

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

MIO0

in

14

Up

LVCMOS18

sd card detection signal coming from connected B2B, also connected to Zynq.
Depending on the firmware used, the extended boot mode JTAG can be set.

Default: Only SD/QSPI Boot mode possible

MIO8

in

13

Up

LVCMOS18

external pullup, for status of 'qspi_fbclk' from Zynq

PS_SRST

in

12

Up

LVCMOS18

system reset signal coming from connected B2B, also connected to Zynq.

PWR_PL_OK

in

27

Up

LVCMOS33

power good for PL

PWR_PS_OK

in

28

Up

LVCMOS33

power good for PS

RST_IN_N

in

25

None

LVCMOS18

Main Reset to U41 (PS_1.8V) coming from connected B2B

RTC_INT

in

4

None

LVCMOS33

RTC output interrupt signal

BOOTMODE

in

20

None

LVCMOS18

readable BOOTMODE from B2B J2-133 (MIO4)

TMS

in

29

Up

LVCMOS33

JTAG coming from connected B2B, maxdelay 10ns

TCK

in

30

Up

LVCMOS33

JTAG coming from connected B2B, maxdelay 10ns

TDI

in

32

Up

LVCMOS33

JTAG coming from connected B2B, maxdelay 10ns

TDO

out

1

None

LVCMOS33

JTAG coming from connected B2B

LED

out

5

None

LVCMOS33

used as status LED, connected to green LED (D1); SLEWRATE=SLOW


Functional Description

JTAG

JTAG signals routed directly through the CPLD to FPGA. Access between the CPLD and FPGA is realised by JTAG_EN (logical one for CPLD, logical zero for FPGA) on B2B J1-148 (JTAG_EN).

Boot Mode

The adjustable Boot Mode is depending on programmed firmware.

Default (for Boot mode QSPI/SD):

BOOTMODE_1 is set constant to 1. Boot mode can be changed between QSPI or SD with B2B J2-133 Pin (BOOTMODE/ Zynq (MIO4)). 

Boot mode

MIO5

(BOOTMODE_1 from CPLD)

MIO4

(BOOTMODE from B2B J2-133)

QSPI

1

0

SD

1

1

Optional (for Boot mode QSPI/SD/JTAG):

BOOTMODE_1 depends on MIO0 (sd card detection) connected to B2B J2-137 Pin (SD card detection/ Zynq (MIO0))

  • sd card detected --> SD/QSPI boot mode
  • no sd card detected --> JTAG/NA boot mode

Boot mode

MIO5

(BOOTMODE_1 from CPLD)

MIO4

(BOOTMODE from B2B J2-133)

comments
JTAG00SD card is not allowed to be inserted
NAND01not supported boot mode!

QSPI

1

0

inserted SD card is required

SD

1

1

inserted SD card is required

I2C interface

The CPLD firmware consists of an i2c-to-GPIO block. This subsystem provides an i2c protocol interface with several 8-bit registers (GPIO_input[8*i+7:8*i]) for reading from the CPLD as parallel general purpose inputs (I/Os). The read data is transferred to the FPGA via the i2c bus interface protocol. The chip address of this block in the firmware is 0x30, "i" is the data address in this case. The associated i2c bus is bus 1.

CPLD registers can be accessed via i2c interface in linux console with

  • i2cget -y 1 0x30 <Index> (for reading) or 
  • i2cset -y 1 0x30 <Index> <Value> (for writing)

The following table shows the register map for the CPLD interface :

IndexByteRegister NameRead/WriteDescriptionDefault
0x00

[7:0]USER_LEDR/W

User adjustable LED

  • 0x00: LED off
  • 0x01: LED on
0x01
0x01

[7:0]

BOOTMODE_VARR

Bootmode variants (depending on firmware):

  • 1 = QSPI/SD (default)
  • 2 = QSPI/SD/(NAND*)/JTAG

*no NAND flash present

0x01
0x02

[7:0]

CPLD_REVISIONRCPLD revision0x03
0x03

[7:0]

PCB_REVISIONRPCB revision0x03
0x04

[7:0]

STATUS_REGISTERR

STATUS_REGISTER(4) = RTC_INT (Pin 4)
STATUS_REGISTER(3) = 'MIO8' (Pin 13)
STATUS_REGISTER(2) = 'MIO0' (Pin 14)
STATUS_REGISTER(1) = 'BOOTMODE_1 / MIO5' (Pin 21)
STATUS_REGISTER(0) = 'BOOTMODE / MIO4' (Pin 20)

depending on BOOTMODE

Power

PL Power is enabled.

LED

The green LED D1 can be set by the user via the I2C interface, as long as the module is not in error mode. In error mode, 4 different flashing sequences are currently implemented and prioritised. The lowest number has the highest priority.

LED statePriorityDescription
Blink sequence
*ooooooo
1PWR_PS_OK not OK
Blink sequence
**oooooo
2PWR_PL_OK not OK
Blink sequence
***ooooo
3Module is in reset state
Blink sequence
****oooo
4

BOOTMODE not OK

  • no NAND flash present
USER LED5User adjustable LED (default is on)

Appx. A: Change History and Legal Notices

Firmware Revision Changes

REV02 to REV03

  • added input pin 'BOOMODE' to CPLD firmware (since REV03) 
  • added writing to I2C interface for user adjustable LED D1
  • updated LED blinking sequence for error mode 
  • update readable I2C interface

REV01 to REV02

  • added I2C interface
  • defined generic parameter
  • new Boot Mode variants (depending on firmware)

Document Change History

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

DateDocument RevisionCPLD Firmware RevisionSupported PCB RevisionAuthorsDescriptionFirmware release

Error rendering macro 'page-info'

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




 REV03REV03

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy244.$Proxy3557#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 documentation update2024-02-19
2023-02-07v.4REV02REV02, REV01Manuela StrückerREV02 documentation update2023-02-07
2018-03-08v.3REV01REV01,
REV02
John HartfielREV01 documentation update2016-05-30

All

Error rendering macro 'page-info'

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



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.$Proxy3557#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