Overview

Firmware for PCB CPLD with designator U1: LCMXO2-256HC-4SG32I


Feature Summary

  • Power Management

  • Power Sequencing

  • Reset

  • CPLD JTAG

  • Boot mode

Firmware Revision and supported PCB Revision

See Document Change History

Product Specification

Port Description

Name / opt. VHD NameDirectionPinPullup/DownBank PowerDescription

TDO 

out1NONE3.3VJTAG TDO signal connected to FTDI chip via B2B connector

TDI

in32UP3.3VJTAG TDI signal connected to FTDI chip via B2B connector

TCK 

in30NONE3.3VJTAG TCK signal connected to FTDI chip via B2B connector

TMS

in29UP3.3VJTAG TMS signal connected to FTDI chip via B2B connector

F_TDO

in

4NONE1.8VJTAG TDO signal connected to FPGA

F_TDI 

out20NONE1.8VJTAG TDI signal connected to FPGA

F_TCK

out5DOWN1.8VJTAG TCK signal connected to FPGA

F_TMS 

out21NONE1.8VJTAG TMS signal connected to FPGA

EN_1V8

out28NONE3.3VEnable signal for U20 DC-DC converter 3.3V/1.8V

EN_2V5

out27NONE3.3VEnable signal for U21 DC-DC converter 3.3V/2.5V

EN_3V3 

out8NONE3.3VEnable signal for U14 3.3V power switch

EN_1V0  

out9NONE3.3VEnable signal for U13 DC-DC converter 3.3V/1.0V

EN_LPDDR4  

out10NONE3.3VEnable signal for U18 DC-DC converter 3.3V/1.1V

EN_2V5_XCVR  

out23NONE3.3VEnable signal for U19 DC-DC converter 3.3V/2.5V_XCVR

PG_ALL  

in13NONE3.3VPower good input signal that is connected to all DC-DC converters U13,U18,U19,U20 and U21

SC_nRST  

in14UP3.3VReset input signal connected to reset push button on the carrier board directly or indirectly (depends on the used carrier board) via B2B connector.

SC_BOOTMODE

in25NONE3.3VBoot mode signal connected to B2B connector. This signal is connected with a dummy signal and does not have any function.

SC_EN1 

in11UP3.3VEnable signal connected to B2B connector.  This signal is connected with a dummy signal and does not have any function.

SC_PGOOD  

inout12NONE3.3VPGOOD signal connected to B2B connector

NOSEQ  

inout17UP3.3VNOSEQ signal connected to B2B connector. This signal is high as long as reset is not activated.

MR_n 

out16NONE3.3VReset output signal connected to DEVRST_N Polarfire device reset pin signal  via voltage monitor chip U15 (TPS3106K33DBVR)


Functional Description

JTAG

JTAG signals routed directly through the CPLD to FPGA. Access between CPLD and FPGA can be multiplexed via JTAGSEL pin of CPLD (pin 26) (logical one for CPLD, logical zero for FPGA). This pin is connected to B2B (JM1-pin 89) directly. On the carrier board can be this pin enabled or disabled with a dip switch.

CPLD JTAGSEL (B2B JM1-89)Description
1CPLD access
0FPGA access

Power

Power sequencing is necessary for this module. To implement a power sequencing a state machine is used. Note that the DC-DC converters do not have seperate power good output. Therefore timers will be used to created desired delay for sequencing. The state machine stages is shown in the following table:

StageEnable SignalVoltage DomainTimerDescription
IDLE---------The state machine will change its stage to PWR1 immediatly after power on.
PWR1Set EN_1V81.8VTimer1 is active.In this stage timer1 will be switched on. The stage will be changed to next stage (PWR2) after about 700 ms and timer1 will be turned off.
PWR2

Set EN_LPDDR4, EN_2V5, EN_3V3

1.1V , 2.5V, 3.3VTimer2 is active.In this stage timer2 will be switched on. The stage will be changed to next stage (PWR3) after about 700 ms and timer2 will be turned off.
PWR3

Set EN_1V0, EN_2V5_XCVR

1V , 2.5VTimer3 is active.In this stage timer3 will be switched on. The stage will be changed to next stage (READY) after about 700 ms and timer3 will be turned off.
READY---------In this stage PG_ALL signal is monitored. If PG_ALL is high, state machine staies in this stage otherwise state machine will be changed to ERROR_SYS stage and CPLD will trun all DC-DC converters off.
ERROR_SYSReset all enable signals1.8V,1V,1.1V,2.5V,3.3V---The state machine will stay in this stage and user should turn the board off and look for the cause of the error.

Boot mode

Boot Mode is independent from 4x5 Boot mode pins SC_BOOTMODE,SC_PGOOD (see: 4 x 5 SoM Integration Guide#4x5SoMIntegrationGuide-4x5ModuleControllerIOs)

The TEM0007 module supports SD card boot mode and JTAG boot mode. The selection between SD card or other boot mode will be done in HSS.

Reset

Reset pins are explained in detail in the following table:

Reset PinDirection in CPLDDescription
SC_nRSTinReset input signal connected to reset push button on the carrier board directly or undirectly (dependent on the used carrier board) via B2B connector.
MR_noutReset output signal connected to DEVRST_N pin of Polarfire SoC through a voltage monitor chip U15 (TPS3106K33DBVR)



Appx. A: Change History and Legal Notices

Revision Changes

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 RevisionAuthorsDescriptionFirmware release

Error rendering macro 'page-info'

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

REV01REV01

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy241.$Proxy3496#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
SC-PGM-TEM0007-01_SCM0007-01_20230815.zip

All

Error rendering macro 'page-info'

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