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

Compare with Current View Page History

« Previous Version 3 Next »

Table of contents

Overview

CR00140 SC CPLD design for MAX10 with designator U25:  10M08SAU169C8G.

Feature Summary

  • Receiving, levelshifting and forwarding of
    • control,
    • sensor,
    • measurement and
    • status signals
  • Push Buttons
  • USR LED

Firmware Revision and supported PCB Revision

See Document Change History.

Product Specification

Port Description

VHDL Port nameDirectionSC CPLD PinCPLD BankConnected toFunctionNotes

X0


B98J11-3CPLD to CRUVI communicationcurrently not used
X1
A88J11-5
X2
A78J11-7

X3


A68J11-9
X4
D88J11-4
X5
B68J11-10
X6
C98J11-1
X7
E88J11-2
A0_PinJ83J9-14

A0_NinK83J9-16

A1_PinM133

J9-20



A1_NinM123J9-22

A2_PinM93J9-26

A2_NinM83J9-28

A3_PinN83J9-32

A3_NinN73J9-34

A4_PoutM73J9-38

A4_NoutN63J9-40

A5_PoutK53J9-44

A5_N
J53J9-46CPLD to CRUVI communicationcurrently not used
B0_P
N53J9-15CPLD to CRUVI communicationcurrently not used
B0_NinN43J9-17

B1_P
J73J9-21CPLD to CRUVI communicationcurrently not used
B1_NinK73J9-23

B2_PoutL113J9-27

B2_NoutM113J9-29

B3_PoutL103J9-33

B3_NoutM103J9-35

B4_PoutJ63J9-398

B4_NoutK63J9-41

B5_PoutL53J9-45

B5_NoutL43J9-47

HSIO
N93J9-2CPLD to CRUVI I/O communicationcurrently not used
HSO
N103J9-6
RESET
M53J9-8
HSI
N123J9-10

TDI


F51BJ9-51, J10-9JTAG / user IO CPLD firmware dependentJTAG pinsharing currently not enabled
TDO
F61BJ9-53, J10-3JTAG / user IO CPLD firmware dependent
TMS
G11BJ9-55, J10-5JTAG / user IO CPLD firmware dependent
JTAGEN
E51BJ9-57JTAG enable CPLD firmware dependent
TCK
G21BJ9-59, J10-1JTAG / user IO CPLD firmware dependent
SMB_ALERT
K22J9-3CPLD to CRUVI I/O communicationcurrently not used
SMB_SDA
H52J9-5
SMB_SCL
H42J9-7
REFCLK
M22J9-11
BUTTON1inC108S2User button forwarded to CRUVIactiv low,
BUTTON2inB108S1Motor control enable/disableactiv low
ENC_AinA108U13-13Sensor input channel A
ENC_BinA98U13-12Sensor input channel B
ENC_IinA118U13-14Sensor input channel I
LED0outD68D2User LED forwarded from CRUVI
LED1outB28D1Status LED

blinking → motor control aktiv,

static on → system ok and motor control disabled

M_BEMF_B_DinB58U15-13Back EMF signal phase B-
M_BEMF_C_DinA58U15-12Back EMF signal phase C-
M_BEMF_A_DinA48

U15-14

Back EMF signal phase A-
M_PWM_AHoutF11AU8-2Phase A half bridge high (DC_LINK) side driver signal-
M_PWM_ALoutE31AU8-3Phase A half bridge low (PGND) side driver signal-
M_PWM_BHoutE11AU9-2Phase B half bridge high (DC_LINK)side driver signal-
M_PWM_BLoutD11AU9-3Phase B half bridge low (PGND) side driver signal-
M_PWM_CHoutE41AU10-2Phase C half bridge high (DC_LINK)side driver signal-
M_PWM_CLoutC11AU10-3Phase C half bridge low (PGND) side driver signal-
M_PWM_DHoutC21AU11-2Phase D half bridge high (DC_LINK) side driver signal-
M_PWM_DLoutB11AU11-3Phase D half bridge low (PGND) side driver signal-
SD_IAinE68U3-6Current measurement phase A33 Ohm series Resistor
SCLK_AoutB38U3-7, U5-7Clock for ADC for current measurement phase A and B(5-20 MHz)
SD_VinB48U7-6Voltage measurement DC_LINK33 Ohm series Resistor
SD_IBinA28U5-6Current measurement phase B33 Ohm series Resistor
SCLK_V_AoutA38U7-7Clock for ADC for voltage measurement DC_LINK(5-20 MHz)
M_DISABLE_D_DoutJ12U11-5Halfe bridge disable phase Ddisabled when high, pull up connected, weak pull up enabled
M_DISABLE_A_DoutM12U8-5Halfe bridge disable phase Adisabled when high, pull up connected, weak pull up enabled 
M_DISABLE_B_DoutL22U9-5Halfe bridge disable phase Bdisabled when high, pull up connected, weak pull up enabled 
M_DISABLE_C_DoutK12U10-5Halfe bridge disable phase Cdisabled when high, pull up connected, weak pull up enabled
REFCLK
M22J9-11
currently not used
RST
M32J10-6
currently not used
UART_RX
N22J10-7
currently not used
UART_TX
N32J10-8

CLK_25MHZinH62U26-3Clock input for accurate 25 Mhz.currently not used
On-board LEDs



Functional Description

Power Management

The M3_3VOUT rail of the attached SoM is used to power up the powerrails on TEF1002. further dependencies ar given in the table below:

Port/Signaldepends on (RGPIO not aktive)additional when RGPIO aktiveDescriptionRemark
EN_PERM3_3VOUTrgpio_out_data_i(15)Enable perepherie power 3V3_PERvia PWR_EN_Signal
FMC_PWR_setM3_3VOUTrgpio_out_data_i(16)Signal indicate FMC enable
EN_FMCFMC_PWR_set and NOT(FMC_PRSNT_M2C_L)rgpio_out_data_i(17)Enable switched 3.3V FMC power
FAN_FMC_ENFMC_PWR_set and NOT(FMC_PRSNT_M2C_L) -Enable FMC FAN
EN_FMC_VADJ(FMC_PWR_set and NOT(FMC_PRSNT_M2C_L)) or (USR0 and FMC_PRSNT_M2C_L)-Enable IO power FMC_VADJUSR0 dip switch S3-2 can be used to enable FMC_VADJ when no FMC installed
FMC_PG_C2MFMC_PWR_set and NOT(FMC_PRSNT_M2C_L) and PG_FMC_VADJ-Indicate that all FMC related powers are up
Power Management

Status LED

The Status LED D4 is utilized in the following way:

Sequenz
Description
*ooooooo1 times fast blink with a breakSOM PGOOD fail
**oooooo2 times fast blink with a breaknot used
***ooooo3 times fast blink with a breakFMC power Error
****oooo4 times fast blink with a breaknot used
*****ooo5 times fast blink with a breakUSB Power Error
******oo6 times fast blink with a breakFirefly A or B Error
*******o7 times fast blink with a breakSFPA_TX_FAULT or SFPA_LOS
ONLED ONAll OK
Status LED description

FMC VADJ Power

Three of the dip switches are linked to the voltage selection signals of FMC_VADJ:


VID0, S2-1VID1, S2-2VID2, S2-3
3.3VOFFOFFOFF
2.5V

ON

OFFOFF
1.8VOFFONOFF
1.5V

ON

ONOFF
1.25VOFFOFFON
1.2V

ON

OFFON
0.8VOFFONON
FMC_VADJ selection

SFP control

SFP control signals are handled by RGPIO:

OUTPUTINPUTFunctionNotes
rgpio_in_data_i(19)SFPA_TX_FAULTTransmitter fault'high' when fault detected
rgpio_in_data_i(18)SFPA_MDEF0Module absent'high' when absent
rgpio_in_data_i(17)SFPA_LOSSignal Loss'high' when signal loss
SFPA_TX_DISrgpio_out_data_i(22)Transmitter disableDisable transmitter when 'high'
SFPA_RS0rgpio_out_data_i(21)Select recieve signal rate
SFPA_RS1rgpio_out_data_i(20)Select transmit signal rate
Connection SFP Control

FFA & FFB control

When RGPIO is aktive the FF resets are driven low via rgpio_out_data_i(23).

For FF I2C see I2C chapter. Module Present and Interrupt signals are forwarded to SoM via RGPIO ports:

OUTPUT to SoMSignal INPUTFunctionNotes
rgpio_in_data_i(23)FFA_MPRSModule presentaktive low
rgpio_in_data_i(22)FFB_MPRSModule presentaktive low
rgpio_in_data_i(21)FFA_INTLInterrupt outputOpen collector output driven low when an Interrupt occurs.
rgpio_in_data_i(20)FFB_INTLInterrupt outputOpen collector output driven low when an Interrupt occurs.
Connection FF Control

PCIE

The PCIexpress signal "PERST#" is forwarded to the SoM using RGPIO port:  rgpio_in_data_i(11) <= PCIE_PERST;

JTAG MUX

The folowing table summarizes the JTAG MUX. Only FMC and SoM JTAG have to be handled in the CPLD explicitly. Discrimination between Module CPLD and Module SOC/FPGA are done via hard connected dip switch. Same is true for TEF1002 CPLD MAX10.

SignalJTAGEN S2-4M_JTAGEN S2-5FMC_JTAG S2-6
CPLD MAX 10

OFF

DNCDNC
4x5 SoM CPLDONOFFOFF
4x5 SoC/FPGAONONOFF
FMCONDNCON
JTAG selection

Module control

The module control signals are connected to dip switches:

Signal OUTPUT to SoMSignal INPUTFunctionNotes
EN1CM0SoM enable power"high" when Dip ON. See SoM TRM for further description.
NOSEQCM1disable SoM powerseq"high" when Dip ON. See SoM TRM for further description.
MODECM2SoM Bootmode"high" when Dip ON. See SoM TRM for further description.
Connection SoM Control

RESET

The push button signal is connected to the RESIN signal of the SoM  (low active reset).

I2C and MUX

The SEL vector is used to select different I2C devices:

deviceSELNotes
SFPA00
FMC01
FFA10also used for FFA_MSEL
FFB11also used for FFB_MSEL
Connection I2C to SoM

A "three wire" I2C interface is used to connect the CPLD I2C  to the SoM:

VHDL Port nameDirectionSC CPLD PinConnected toFunctionNotes
A_00_NINJ10JB1, pin 38SDA IN "three wire" I2C
A_00_PINK10JB1, pin 36SCL IN"three wire" I2C
A_01_POUTK11JB1, pin 37SDA OUT"three wire" I2C
Connection I2C to SoM

The devices SDA are driven in the following way: DEVICE_XY_SDA <= '0' when SEL= "XY" and A_00_N='0' else 'Z';

The SDA to the SoM is generated by the logical AND connection of all devices:  SDAs <= (SFPA_SDA AND FMC_SDA AND FFA_SDA AND FFB_SDA )


VHDL Port nameDirectionSC CPLD PinConnected toFunctionNotes
FMC_SCLOUTJ8J1, pin C31I2C 2-wire serial busMUX in CPLD
FMC_SDAINOUTF9J1, pin C30
FFA_MSELOUTC9J13, pin 4Select attached FF ModulePull low to use I2C
FFA_SCLOUTD6J13, pin 8I2C 2-wire serial busMUX in CPLD
FFA_SDAINOUTE6J13, pin 7
FFB_MSELOUTB10J18, pin 4Select attached FF ModulePull low to use I2C
FFB_SCLOUTD8J18, pin 8I2C 2-wire serial busMUX in CPLD
FFB_SDAINOUTA9J18, pin 7
A_01_POUTK11JB1, pin 37SDA OUT"three wire" I2C
A_06_NING12JB1, pin 49I2C GPIO MUX 0I2C MUX also used for FireFlys MSEL
A_07INL13JB1, pin 34I2C GPIO MUX 1
SC I2C MUX ports

PHY LEDs

As soon as the module M3_3VOUT is ready the following signals are used to drive the PHY LEDs.

Signal VHDLnameFunctionNotes
CPLD_IO_1PHY_LED1drive LEDConnected to JB1-88
net_gndPHY_LED1Rselect coloryellow
CPLD_IO_2PHY_LED2drive LEDConnected to JB1-92
net_gndPHY_LED2Rselect colorgreen
Connection of PHY LEDs

RGPIO

The RGPIO is for communiction betweenn SoC and SC CPLD it handels the signals:

Signal VHDLnameFunctionNotes
SOC read (11)PCIE_PERSTIndication that PCIe Bus is up (power, clocks)
SoC write (17)EN_FMCEnable switched 3.3V FMC powerpulled down
SoC write (15)PWR_EN_SignalEnable perepherie power 3V3_PERused for EN_PER
SOC read (15)FMC_PRSNT_M2C_LIndicate if FMC installedLow when FMC present
SoC write (16)FMC_PWR_setTurn on FMC Powerused for EN_FMC_VADJ and FAN_FMC_EN
SOC read (14)PG_FMC_VADJIndicate FMC VADJ power is up
SoC write (23)FF_RSTLReset configurationBoth FF are resetted simultanously when pulled LOW
SOC read (21)FFA_INTLIndicate interrrupt

LOW when fault condition, pulled up

SOC read (13)FFA_MPRSIndicate FF Module installedLOW when Module present, pulled up
SOC read (20)FFB_INTLIndicate interrruptLOW when fault condition, pulled up
SOC read (22)FFB_MPRSIndicate FF Module installedLOW when Module present, pulled up
SOC read (17)SFPA_LOSSFP signal lossHIGH indicates signal loss
SOC read (18)SFPA_M-DEF0SFP modul absentHIGH when module physically absent
SoC write (21)SFPA_RS0SFP rate select RXLOW for 1000BASE-SX, HIGH for 10GBASE-SR
SoC write (20)SFPA_RS1SFP rate select TXLOW for 1000BASE-SX, HIGH for 10GBASE-SR
SoC write (22)SFPA_TX_DISSFP transmitter disableHIGH disables transmitter
SOC read (19)SFPA_TX_FAULTIndicates SFP laser faultHIGH indicates fault
SoC write (19)LED1user LEDs
SoC write (18)LED2
Signals handeld by RGPIO


VHDL Port nameDirectionSC CPLD PinConnected toFunctionNotes
A_01_NOUTL12JB1, pin 35TX data
A_02_NINJ12JB1, pin 41RX CLK
A_02_PINK12JB1, pin 39RX data
Connection RGPIO to SoM

USR LED

User LEDs are accesible via RGPIO:

Signal VHDLnameFunctionNotes
SoC write(19)LED1-user defined
SoC write(18)LED2-user defined
Connection of User LEDs

Appx. A: Change History and Legal Notices

Document Change History

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

Revision Changes

DateDocument RevisionCPLD Firmware RevisionSupported PCB RevisionAuthorsDescription

Error rendering macro 'page-info'

Ambiguous method overloading for method jdk.proxy279.$Proxy4022#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.proxy279.$Proxy4022#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.proxy279.$Proxy4022#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 version

All

Error rendering macro 'page-info'

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