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

Compare with Current View Page History

« Previous Version 6 Next »

Table of contents

Overview

TEC0850 design for MAX10 FPGA U18:  10M08SAU169C8G.

Feature Summary

  • SC to HD-IO Bank Interface
  • I²C Backplane interface
  • I²C System Control interface
  • Power control
  • Power status
  • FAN Control
  • FAN Status
  • Power status indication

Firmware Revision and supported PCB Revision

See Document Change History.

Product Specification

Port Description

Name / opt. VHD NameDirectionPinBank PowerDescription
FTDI_RXDin

UART receive data from FTDI
FTDI_TXDout

UART transmit data to FTDI
MIO22out

UART receive data to FPGA
MIO23in

UART receive data from FPGA
ZYNQ_TDOin

FPGA JTAG TDO
ZYNQ_TCKout

FPGA JTAG TCK
ZYNQ_TDIout

FPGA JTAG TDI
ZYNQ_TMSout

FPGA JTAG TMS
ADBUS0in

FTDI JTAG TCK
ADBUS1in

FTDI JTAG TDI
ADBUS2out

FTDI JTAG TDO
ADBUS3in

FTDI JTAG TMS
USB_BTNin

Front panel button
LED4out

Front panel LED4
MRout

Supervisor Reset output
SRST_Bout

FPGA SRST_B
FTDI_RSTout

FPGA RST_B
PLL_RSTout

Clock chip Reset
EN_DAC1out

DAC1 Power Enable
EN_DAC2out

DAC2 Power Enable
EN_DAC3out

DAC3 Power Enable
EN_DAC4out

DAC4 Power Enable
EN_FPDout

FPD Power Enable
EN_LPDout

LPD Power Enable
EN_DDRout

DDR Power Enable
EN_PSGTout

PSGT Power Enable
ON_GT_Lout

GT_L Power Enable
ON_GT_Rout

GT_R Power Enable
PG_PSGTin

PSGT Power Good
LP_GOODin

LP Power Good
PG_GT_Lin

GT_L Power Good
PG_GT_Rin

GT_R Power Good
PG_PLin

PL Power Good
PG_DDRin

DDR Power Good
F1PWMout

FAN PWM Control
F1SENSEin

FAN Sense
DONEin

FPGA DONE
IO1in

FPGA I2C SCL_t
IO2out

FPGA I2C SCL_i
IO3in

FPGA I2C SDA_t
IO4out

FPGA I2C SDA_i
IO5in

FPGA User LED control
SCL_Rout

SCL Strong Pull-Up Enable
SDA_Rout

SDA Strong Pull-Up Enable
SCLinout

I2C SCL
SDAinout

I2C SDA


Functional Description

SC to HD-IO Bank Interface

SC I/O #FunctionFPGA IO
IO1SCL OUTG18
IO2SCL ING19
IO3SDA OUTK18
IO4SDA INH19
IO5User LEDJ17Drive SC LED, if configured in "Control Register"
IO6-H17
IO7-H18
IO8-L18
IO9-L17
IO10-K17

I²C Interface

To use SC I²C interface corresponding connection should be configured in the FPGA project. There are 2 standard I²C interface controllers, which can be used AXI_IIC or Zynq UltraScale+ MPSoC integrated I²C controller.

AXI_IIC

Zynq UltraScale+ MPSoC integrated I²C controller

With this configuration, I²C device with address 0x20 should be visible on I²C bus

This device is an emulation of TCA6416 I²C GPIO Chip. GPIO input and output pins are used to get status and control the system.

AddressRegisterDescription
0Input Port 0

Power status register:

Bit 0 - LP_PGOOD

Bit 1 - PG_PL

Bit 2 - PG_PSGT

Bit 3 - PG_GT_L

Bit 4 - PG_GT_R

Bit 5 - PG_DDR

Bit 6 - Not Used "0"

Bit 7 - Not Used "0"

1Input Port 1

FAN Status register

Bits 7:0 - FAN RPM/1000

(Nominal Sepa HFB44B-12A speed is 8000 RPM)

2Output Port 0

Control register 0

Bits 1:0 - LED Control (Default "01")

Bit 2 - SMB Strong Pull-Up Enable (Default "1")

Bit 3 - Enable DAC1 Power (Default "1")

Bit 4 - Enable DAC2 Power (Default "1")

Bit 5 - Enable DAC3 Power (Default "1")

Bit 6 - Enable DAC4 Power (Default "1")

Bit 7 - Enable FPD Power (Default "1")

3Output Port 1

Control register 1

Bit 0 - Enable LPD Power (Default "1")

Bit 1 - Enable DDR Power (Default "1")

Bit 2 - Enable PSGT Power (Default "1")

Bit 3 - Enable GT_L Power (Default "1")

Bit 4 - Enable GT_R Power (Default "1")

Bit 5 - Enable FAN Power (Default "1") (Works only if 4-wire FAN is used)

Bit 6 - Not used

Bit 7 - Not used

I²C GPIO registers can be operated with  directly, using Linux i2cset and i2cget commands

root@petalinux:~# # Disable LED4
root@petalinux:~# i2cset -y 0 0x20 2 0xFC
root@petalinux:~# # Get Power status
root@petalinux:~# i2cget -y 0 0x20 0 b
0x3f
root@petalinux:~# # Get FAN RPM/1000
root@petalinux:~# i2cget -y 0 0x20 1 b
0x08

or I²C GPIO device driver can be instantiate in Linux device tree (project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi).

&i2c0 {
	tca6416: tca6416@21 {
		compatible = "ti,tca6416";
		reg = <0x20>;
		gpio-controller;
		#gpio-cells = <2>;
	};
};




Appx. A: Change History and Legal Notices

Revision Changes

RE02 to REV03

  • Add I²C GPIO core
  • FAN Control/FAN Status
  • Power control

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

REV03REV02

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]


  • initial release
  • working in process
2018-08-15v.3REV02REV02Antti Lukats
  • initial release

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]


Appx. A: Legal Notices

  • No labels