- Created by Mohsen Chamanbaz, last modified on 05 01, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 80 Next »
Overview
A Lattice XO2-1200 CPLD (U19) is used as a System Management Controller (referred to as SC in the manual). The SC is responsible for power sequencing, reset generation and Zynq initial configuration (mode pin strapping). Moreover, some on-board ICs are connected to the SC that provides level shifting. The SC wakes up when the 3.3V input power rises above 2.1V (VIN voltage is not needed). The SC can turn on or off all of the other supplies on the module (except in no power sequencing mode when the 1.0V and 1.8 V supplies are forced to start immediately when power is applied to the module).
System Controller (SC for short) was designed to allow ZYNQ PS system to access module special functions as early as possible without reducing the number of MIO pins that are fully user configurable.This early communication channel is done using MIO52 and MIO53 pins that are used also as Ethernet PHY management interface for the on-board Gigabit PHY. In order to simplify the boot process and reduce the number of time the PS peripherals need to be configured or re-initialized SC uses the same protocol on MIO52/MIO53 as the Gigabit PHY itself. This means that FSBL Configures all peripherals to their final function, allocating MIO52 and MIO53 as Ethernet MDIO Interface. SC Controller appears as "Virtual Ethernet PHY" on the MDIO bus of PS Ethernet 0 Interface. This interface is already available when Zynq PL Fabric is not configured. It would have been possible to use I2C Protocol on MIO52/MIO53 but in such case some multiplexing would be needed to choose between two protocols, also it would be needed to change the peripheral mapping after first init by the FSBL. For use cases where Ethernet PHY on TE0720 is not used at all, it is still possible to configure SC with design that implements I2C Protocol on MIO52/MIO53 pins.For most use cases the only need to use this interface is access to MAC Address info, this is normally done by u-boot loader that fetches the MAC Address bytes and sets its environment variables accordingly. Linux image will then also be started so that the MAC Address from EEPROM is used for Ethernet 0 Physical interface.
Feature Summary
Power Management
JTAG routing
Boot Mode
User IO
LED
- MDIO interface
- Watchdog timer
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 |
---|---|---|---|---|---|
BOOT_R / BOOTMODE_R | out | N12 | NONE | 3.3V | If low then the QSPI flash can not be written. (Write protect) |
BOOT_R5 / BOOTMODE_R5 | out | M11 | DOWN | 3.3V | If low then the QSPI flash will be reset. (HOLD/RESET) |
CLK_125MHz | in | G13 | NONE | 1.8V | 125MHZ Clock Output of Ethernet transceiver chip (88E1512-A0-NNP2C000) that synchronized with the 25MHZ reference clock |
EN_3V3 | out | A2 | DOWN | 3.3V | If high then the 3.3V power will be switched ON. |
EN1 | in | A9 | UP | 3.3V | User Enable. Enables the DC-DC converters and on board supplies (Active High). (B2B JM1-28)(DIP Switch on the carrier board) . Not used if NOSEQ = '1' |
ETH-CLK-EN / EN_ETH_CLK | out | J14 | NONE | 1.8V | Enable pin for U9 oscillator chip U9 (SiT8008BI-73-18S-25.000000E) to feed a clock to Ethernet Transceiver(U8). Enabled as default. |
ETH-MDC / mdc | in | L14 | UP | 1.8V | Management Data Clock reference for the Ethernet transceiver chip. This pin is connected with MIO52 of FPGA too and can be activated in Zynq7 adjustment. |
ETH-MDIO / mdio | inout | K14 | UP | 1.8V | It is Management Data pin of Ethernet transceiver chip to transfer in and out of the device synchronously to mdc. It is connected with MIO53 of FPGA. |
ETH-RST | out | E14 | DOWN | 1.8V | Reset pin of Ethernet transceiver chip. (Active low) |
INIT | in | C9 | UP | 3.3V | INIT_B_0 pin of FPGA. (Active low). This pin must be tristate for PL configuratuion. By user or device held low until is ready to be configured. |
INT1 / INT2 | in | P4 | UP | 3.3V | MEMS Interrupt 1 of 3D accelerometer and 3D magnetometer chip U22 (LSM303DTR) (Active High) |
INT2 / INT1 | in | P6 | UP | 3.3V | MEMS Interrupt 2 of 3D accelerometer and 3D magnetometer chip U22 (LSM303DTR) (Active High) |
JTAGMODE | in | B9 | 3.3V | JTAGENB pin of CPLD. Enable JTAG access to CPLD for Firmware update (zero: JTAG routed to module, one: CPLD access) | |
LED1 | out | P2 | NONE | 3.3V | Display green LED (D2) |
LED2 | out | N3 | DOWN | 3.3V | Display red LED (D5) |
MEM-MAC / MAC_IO | inout | M14 | UP | 1.8V | Serial Clock/Data input/Output of Serial EEPROM (11AA02E48T-I/TT) U17 |
MEM-SHA / SHA_IO | inout | N14 | UP | 1.8V | SDA for CryptoAuthentication Chip (ATSHA204A-STUCZ-T) U10 |
MIO14 | inout | M4 | NONE | 3.3V | This pin is connected to Zynq PS-MIO (B6) . In firmware rev.05 is used as RX pin of UART0. |
MIO15 | inout | N4 | NONE | 3.3V | This pin is connected to Zynq PS-MIO (E6) . In firmware rev.05 is used as TX pin of UART0. |
MIO7 | in | P11 | UP | 3.3V | This pin is used as GPIO. |
MMC_RST | out | G14 | DOWN | 1.8V | Reset pin of eMMC memory (MTFC16GJVEC-2M WT) U15 |
MODE / BOOTMODE_IN | in | C8 | UP | 3.3V | Latched as BOOTMODE once at power-up, can be used later as I/O, weak pull up. Force low for boot from the SD Card. Latched at power on only, not on soft reset (B2B-JM1 pin 32) |
MODE / BOOTMODE_IN2 | in | M9 | UP | 3.3V | Latched as BOOTMODE once at power-up, can be used later as I/O, weak pull up. Force low for boot from the SD Card. Latched at power on only, not on soft reset (B2B-JM1 pin 32) |
MR / POR_B | out | P12 | UP | 3.3V | Power-on-reset pin. This pin is connected with supply voltage monitor chip (TPS3106K33DBVR) U26 and controls the PS_POR_B pin of FPGA. (Active Low) |
NetU19_B12 | B12 | / currently_not_used | |||
NetU19_B13 | B13 | / currently_not_used | |||
NetU19_B2 | B2 | / currently_not_used | |||
NetU19_B3 | B3 | / currently_not_used | |||
NetU19_B7 | B7 | / currently_not_used | |||
NetU19_C1 | C1 | / currently_not_used | |||
NetU19_C10 | C10 | / currently_not_used | |||
NetU19_C12 / Dummy | out | C12 | DOWN | 3.3V | |
NetU19_C3 | C3 | / currently_not_used | |||
NetU19_C6 / RST | in | C6 | UP | 3.3V | |
NetU19_C7 | C7 | / currently_not_used | |||
NetU19_E1 | E1 | / currently_not_used | |||
NetU19_E12 | E12 | / currently_not_used | |||
NetU19_F13 | F13 | / currently_not_used | |||
NetU19_F3 | F3 | / currently_not_used | |||
NetU19_G3 | G3 | / currently_not_used | |||
NetU19_H3 | H3 | / currently_not_used | |||
NetU19_J3 | J3 | / currently_not_used | |||
NetU19_K13 | K13 | / currently_not_used | |||
NetU19_K3 | K3 | / currently_not_used | |||
NetU19_L3 | L3 | / currently_not_used | |||
NetU19_M12 | M12 | / currently_not_used | |||
NetU19_M2 | M2 | / currently_not_used | |||
NetU19_M3 | M3 | / currently_not_used | |||
NetU19_N13 | N13 | / currently_not_used | |||
NetU19_N5 | N5 | / currently_not_used | |||
NetU19_N7 | N7 | / currently_not_used | |||
NetU19_N8 | N8 | / currently_not_used | |||
NOSEQ | inout | A3 | DOWN | 3.3V | Usage CPLD Variant depends. (B2B-NOSEQ pin 7) Forces the 1.0V and 1.8V DC-DC converters always ON when high. Can be used as an I/O after boot. |
ON_1V0 | out | A12 | NONE | 3.3V | Enable pin for 1.0 V DC-DC (Active High) |
ON_1V5 | out | M7 | NONE | 3.3V | Enable pin for 1.5 V DC-DC (Active High) |
ON_1V8 | out | A11 | NONE | 3.3V | Enable pin for 1.8 V DC-DC (Active High) |
OTG-RST | out | B14 | DOWN | 1.8V | Reset pin for high speed USB transceiver (USB3320C-EZK) U18 (Active Low) |
PG_1V0 | in | A7 | UP | 3.3V | Power OK (POK) pin of 1.0V DC-DC converter EN6347QI (U1). If High then the output voltage of regulator is within 10% of nominal value (OK). |
PG_1V5 | in | N6 | UP | 3.3V | Power OK (POK) pin of 1.5V DC-DC converter EP53F8QI (U2). If High then the output voltage of regulator is Ok. |
PG_1V8 | in | A10 | UP | 3.3V | Power OK (POK) pin of 1.8V DC-DC converter EP53F8QI (U3). If High then the output voltage of regulator is Ok. |
PG_3V3 / POR | in | C11 | UP | 3.3V | POR Reset pin. This pin is connected with PG_3V3. As long as the VCCIO34 voltage is zero, this pin will remain low. |
PGOOD | inout | B8 | UP | 3.3V | Power good output as default, can be used as I/O. (B2B JM1-Pin 30) Forced low until all on-board power supplies are working properly. |
PHY_CONFIG | inout | C14 | DOWN | 1.8V | Hardware configuration pin of Ethernet transceiver (88E1512-A0-NNP2C000). |
PHY_LED0 | inout | F14 | NONE | 1.8V | LED output 0 of Ehternet transceiver chip |
PHY_LED1 | inout | D12 | NONE | 1.8V | LED output 1 of Ehternet transceiver chip |
PHY_LED2 | inout | C13 | NONE | 1.8V | LED output 2 or interrupt output pin (Active Low) of Ehternet transceiver chip |
PJTAG_R | out | N10 | NONE | 3.3V | This pin in the schematic is connected with SPI-DQ0/M0 Pin |
PROG_B | in | A13 | UP | 3.3V | By pulsing this pin any configuration that is currently loaded is cleared and the PL prepared to load new configuration. (Active Low) |
PS-RST / SRST_B | out | M13 | UP | 1.8V | PS software reset (Active Low) |
PUDC_B | inout | E3 | DOWN | VCCIO34 | Selects the enable or disable of pull-ups during configuration on the user I/O pins. (Active Low) Enables internal pull-up resistors on the select I/O pins after power-up and during configuration. |
RESIN | in | C4 | UP | 3.3V | Master reset input (Active Low). Default mapping forces POR_B reset to Zynq PS |
RST / RST_SENSE | in | P3 | NONE | 3.3V | Reset pin that is connected with PS_PORT_B (Power-on-reset) (Active Low) |
RTC_INT | in | N2 | UP | 3.3V | Interrupt output or frequency output of RTC chip (ISL12020MIRZ) U20 (Active Low) |
SCL | inout | P8 | UP | 3.3V | I2C clock pin of MEMS chip (LSM303DTR) U22 |
SDA | inout | P7 | UP | 3.3V | I2C data pin of MEMS chip (LSM303DTR) U22 |
SPK_L | M5 | / currently_not_used | |||
SPK_R | M8 | / currently_not_used | |||
TCK / C_TCK | out | P13 | DOWN | 3.3V | Zynq JTAG clock pin |
TDI / C_TDI | out | P9 | DOWN | 3.3V | Zynq JTAG data input pin |
TDO / C_TDO | in | M10 | DOWN | 3.3V | Zynq JTAG data output pin |
TMS / C_TMS | out | N9 | DOWN | 3.3V | Zynq JTAG mode select pin |
VCCIO34 | E2 | / currently_not_used | |||
VCCIO34 | F2 | / currently_not_used | |||
VCCIO34 | H2 | / currently_not_used | |||
VCCIO34 | J2 | / currently_not_used | |||
VCCIO34 | K2 | / currently_not_used | |||
X_TCK / M_TCK | in | B6 | DOWN | 3.3V | FTDI JTAG clock pin (B2B-JM1-pin 99) |
X_TDI / M_TDI | in | B4 | DOWN | 3.3V | FTDI JTAG data input pin (B2B-JM1-pin 95) |
X_TDO / M_TDO | out | A4 | DOWN | 3.3V | FTDI JTAG data output pin (B2B-JM1-pin 97) |
X_TMS / M_TMS | in | A6 | DOWN | 3.3V | FTDI JTAG mode select pin (B2B-JM1-pin 93) |
X1 | in | F1 | UP | VCCIO34 | CPLD pin to the FPGA (L16). I2C clock from FPGA |
X2 / XIO4 | inout | C2 | UP | VCCIO34 | CPLD pin to the FPGA (M15). ETH PHY LED0 |
X3 / XIO5 | inout | B1 | UP | VCCIO34 | CPLD pin to the FPGA (N15). ETH PHY LED1 |
X4 / XIO6 | inout | D1 | UP | VCCIO34 | CPLD pin to the FPGA (P16). ETH PHY LED2 |
X5 | out | J1 | NONE | VCCIO34 | CPLD pin to the FPGA (P22). I2C data to FPGA |
X6 | H1 | / currently_not_used | |||
X7 | in | M1 | UP | VCCIO34 | CPLD pin to the FPGA (N22). I2C data from FPGA |
XCLK | out | K1 | NONE | VCCIO34 | CPLD pin to the FPGA (K19). ETH PHY clock to FPGA |
- / SIG1 | in | E13 | NONE | 1.8V | This pin is connected with VCCIO34 directly in the schematic REV03 and has no lable in the schematic. |
Functional Description
To access and control the following functions it must be accessed CR registers. For more information about how to access these registers refer to CR registers access methods
JTAG
JTAG signals routed directly through the CPLD to FPGA. Access between CPLD and FPGA can be multiplexed via JTAGENB pin of CPLD (B9) (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 JTAGENB (B2B JM1-89) | Description |
---|---|
0 | FPGA access |
1 | CPLD access |
Watchdog Timer
Watchdog timer is an added option in the CPLD code. To control and to use watchdog timer correctly , it must be written correct values in the related CR registers.
Watchdog timer signal / register | Related CPLD Register | Access in FSBL code | Access in Linux | Description |
---|---|---|---|---|
WDT input clock | CR1(14) CR1 = Register5 | XEmacPs_PhyWrite / XEmacPs_Phyread | Phytool command | |
WDT_time | CR4[7:0] CR4 = Register12 | XEmacPs_PhyWrite / XEmacPs_Phyread | Phytool command | If CR4[7:0] = 0x00 → WDT_time = 0x07 |
WDT_Enable | CR3[15:8] CR3 = Register7 | XEmacPs_PhyWrite / XEmacPs_Phyread | Phytool command | If CR3[15:8] = 0xA5 → WDT enable If CR3[15:8] /= 0xA5 → WDT disable |
For example to access these registers in FSBL code it can be used the following instruction:
Status = XEmacPs_PhyWrite(&Emac, 0x1A, 7, 0xA500); if(Status != XST_SUCCESS){ return XST_FAILURE; } → To enable WDT
Status = XEmacPs_PhyWrite(&Emac, 0x1A, 7, 0x0000); if(Status != XST_SUCCESS){ return XST_FAILURE; } → To disable WDT
Status = XEmacPs_PhyWrite(&Emac, 0x1A, 12, 0x001F); if(Status != XST_SUCCESS){ return XST_FAILURE; } → To adjust desired time for WDT
Another way to access the related registers for WDT is to use phytool command. It must be added the ethtool package in Linux. To add this package it must be chosen in petalinux configuration for rootfs this option. The path in petalinux rootfs is: Filesystem packages/console/network/ethtool
The phytool instruntion format is :
Phytool read device/addr/register
Phytool write device/addr/register <value>
To write desired value in the related WDT registers for example can be written the following instructions in Linux console:
phytool write eth0/0x1A/7 0xA500 → WDT enable
phytool write eth0/0x1A/7 0x0000 → WDT disable
phytool write eth0/0x1A/12 0x001F → Adjusted WDT time. It depends on the period of the CPLD clock.
phytool write eth0/0x1A/6 0x0200 → To set the WDT input clock high
phytool write eth0/0x1A/6 0x0000 → To set the WDT input clock low
If the WDT is activated and the generated clock is fed to WDT input clock , it will not be reset the board (WDT_RST signal low). But if the generation of this clock is stopped , the board will be reset (WDT_RST signal high) after a period of time depending on the WDT_time register value. The following shell script file generates a clock for WDT input clock. This file must be copies as init.sh to the SD card. The Boot.bin and image.ub files must be copied to the SD card too. This shell script file will be executed by bootng the board and generates the WDT input clock. As long as 1 key and enter key is not pressed, the WDT clock will be generated and subdequently the board will not be reset. Note that WDT must already be activated either in FSBL code or directly by phytool command in linux console.
#WDT test
#!/bin/sh
echo "Starting the WDT Clock"
sleep 1
while :
do
phytool read eth0/0x1A/6
phytool write eth0/0x1A/6 0x0200
sleep 1
phytool read eth0/0x1A/6
phytool write eth0/0x1A/6 0x0000
sleep 1
read -r -t 1 -p "Press 1 to exit: \n\r" b
if (( b == 1 )) ; then
break
fi
done
printf "\Quit.......................\n\n"
Reset
Zynq will be reset, when it occures one of the following conditions:
Reset name | Reset reasone | related reset pin / signal | Active |
---|---|---|---|
Reset | Reset push button | RESIN | LOW |
Reset command in software | CR1(15) | HIGH | |
WDT reset | Overflowing the WDT counter and no existance WDT input clock (For more information refer to Watchdog Timer) | WD_RST | HIGH |
Extra Reset
The board can also be reset through software.
Extra reset | related register | Access in FSBL code | Access in Linux | Description |
---|---|---|---|---|
Enable register | CR3[15:8] CR3 = Register7 | XEmacPs_PhyWrite / XEmacPs_Phyread | Phytool command | If CR3[15:8] = 0xE5 → Extra reset enable If CR3[15:8] /= 0xE5 → Extra reset disable |
Reset bit | CR1(15) | Phytool command | If CR1(15) = '1' → Reset the board |
For example the following instructions can reset the board:
phytool write eth0/0x1A/7 0xE500 → Extra reset enable
phytool write eth0/0x1A/5 0x8000 → Reset the board
It can be activated this option in FSBL code too:
Status = XEmacPs_PhyWrite(&Emac, 0x1A, 7, 0xE500); if(Status != XST_SUCCESS){ return XST_FAILURE; }
SC B2B Pins
Name | B2B | Mode | Default function | Alternative | Description |
---|---|---|---|---|---|
EN1 | JM1-Pin 28 | input, weak pull-up | Power Enable | IO | High enables the DC-DC converters and on-board supplies. Not used if NOSEQ=1 |
MODE | JM1-Pin 32 | input, weak pull-up | Boot mode | SDA or IO | Force low for boot from the SD Card. Latched at power on only, not on soft reset! |
NOSEQ | JM1-Pin 7 | input, weak pull-down | Power sequencing Control | Output | Forces the 1.0V and 1.8V DC-DC converters always ON when high. Can be used as an I/O after boot. |
PGOOD | JM1-Pin 30 | output, open drain | Power good | SCL or IO | Forced low until all on-board power supplies are working properly. Attention: During CPLD programming, this pins is high impedance. |
RESIN | JM2-Pin 18 | input, weak pull-up | Reset input | IO | Active Low Reset input, default mapping forces POR_B reset to Zynq PS |
SC Pins to the FPGA
Schematic net name | VHDL Name | Default function | Direction | SC pin | FPGA pin | Description |
---|---|---|---|---|---|---|
XCLK | XCLK | ETH PHY Clock to FPGA | to FPGA | K1 | K19 | |
X7 | X7 | I2C Data from FPGA | from FPGA | M1 | N22 | SDA from EMIO I2Cx |
X5 | X5 | I2C Data to FPGA | to FPGA | J1 | P22 | SDA to EMIO I2Cx |
X4 | XIO6 | ETH PHY LED2 | to FPGA | D1 | P16 | |
X3 | XIO5 | ETH PHY LED1 | to FPGA | B1 | N15 | RTC, MEMS Interrupt or PHY LED1 |
X2 | XIO4 | ETH PHY LED0 | to FPGA | C2 | M15 | |
X1 | X1 | I2C Clock from FPGA | from FPGA | F1 | L16 | SCL from EMIO I2Cx |
PUDC_B | PUDC_B | Enables internal pull-up resistors on the IOs | to FPGA | E3 | K16 | normally not used tied to fixed level by SC |
NOSEQ Pin
This is a dedicated input that forces the module's 1.0V and 1.8V supplies to be enabled if high. This pin has a weak pull-down on the module. If left open the module will power up in normal power sequencing enabled mode. This pin is 3.3V tolerant. This pin is also connected to the System Management Controller. The SC can read the status of this pin (it can be detected if the module is in power sequencing enabled mode). The SC can also use this pin as output after normal power on sequence.
No Sequencing mode
If the module is powered from a single 3.3V supply and power sequencing is disabled, then NOSEQ pin should be powered from the main 3.3V input. That is VIN, 3.3Vin and NOSEQ should all be tied together to the input 3.3V power rail. Sequencing mode should not be used if VIN is not 3.3V.
Normal mode
For normal operation leave NOSEQ open or pull down with a resistor.
Normal mode with user function on NOSEQ
NOSEQ can be used as an output after boot. NOSEQ must be low when 3.3V power is applied to the module. Common usage is an LED connected between NOSEQ and GND. The mapping of NOSEQ pin can be changed by CR1 register. The CR1 register is control register of MDIO slave interface that its content can be changed with u-boot functions or FSBL code or in the linux console directly.
SC registers
Most registers and functions are available via ETH PHY Management interface (MIO pins 52 and 53).
Addr | R/W | Register name | Descripion |
---|---|---|---|
0 | RO | ||
1 | RO | ||
2 | RO | ID1 | PHY Identifier Register 1 |
3 | RO | ID2 | PHY Identifier Register 2 |
4 | RW | ID3 | PHY Identifier Register 3 |
5 | RW | CR1 | Control Register 1: LED's |
6 | RW | CR2 | Control Register 2; XIO Control |
7 | RW | CR3 | Control Register 3; Reset, Interrupt |
8 | RO | SR1 | Status Register |
9 | RO | MAChi | Highest bytes of primary MAC Address |
0xA | RO | MACmi | Middle bytes of primary MAC Address |
0xB | RO | MAClo | Lowest bytes of primary MAC Address |
0xC | RO | CR4 | reserved do not use |
0xD | RW | MMD_CR | MMD Control Register |
0xE | RW | MMD_AD | MMD Address/Data |
0xF | - | reserved do no use | |
other | - | reserved do not use |
The important registers are CR1, CR2, CR3 and CR4. Each register has its own number, which is used when writing or reading.
CR register | RegisterNum |
---|---|
CR1 | 5 |
CR2 | 6 |
CR3 | 7 |
CR4 | 12 |
Register CR1
CR1 | related function |
---|---|
15 | Enable Extra_Enable |
14 | WD_HIT generation |
13 | Undefined |
12 | Undefined |
11:8 | NOSEQ Mux |
7:4 | LED1 Mux |
3:0 | LED2 Mux |
The mapping of LED1(Green) , LED2(Red) and NOSEQ pin depends on the value of CR1 register.
Value (CR1[3:0]) | LED1 Mux (Green) | Description |
---|---|---|
0001 | PHY_LED0 | LED output 0 of Ehternet transceiver chip |
0010 | PHY_LED1 | LED output 1 of Ehternet transceiver chip |
0011 | PHY_LED2 | LED output 2 or interrupt output pin (Active Low) of Ehternet transceiver chip |
0100 | MIO7 | GPIO |
0101 | RTC_INT | Interrupt output or frequency output of RTC chip |
0110 | OFF | |
0111 | ON | |
1000 | XIO4 | CPLD pin to the FPGA (M15). ETH PHY LED0 |
1001 | Not MIO14 | |
1010 | Not MIO14/Not MIO15 | |
others | MIO7 | GPIO |
Value (CR1[7:4]) | LED2 Mux (Red) | Description |
0001 | PHY_LED0 | LED output 0 of Ehternet transceiver chip |
0010 | PHY_LED1 | LED output 1 of Ehternet transceiver chip |
0011 | PHY_LED2 | LED output 2 or interrupt output pin (Active Low) of Ehternet transceiver chip |
0100 | MIO7 | GPIO |
0101 | RTC_INT | Interrupt output or frequency output of RTC chip |
0110 | OFF | |
0111 | ON | |
1000 | XIO5 | CPLD pin to the FPGA (N15). ETH PHY LED1 |
1001 | Not MIO15 | |
1010 | Not MIO14/Not MIO15 | |
others | modeblink | If SD card boot mode is selected on the carrier board (for examle for TE0703 S2-4 DIP switch ON) , LED2 flashs slow otherweise LED2 flashs fast. |
Value (CR1[11:8]) | NOSEQ Mux | Description |
0001 | PHY_LED0 | LED output 0 of Ehternet transceiver chip |
0010 | PHY_LED1 | LED output 1 of Ehternet transceiver chip |
0011 | PHY_LED2 | LED output 2 or interrupt output pin (Active Low) of Ehternet transceiver chip |
0100 | MIO7 | GPIO |
0101 | RTC_INT | Interrupt output or frequency output of RTC chip |
0110 | OFF | |
0111 | ON | |
1000 | XIO6 | CPLD pin to the FPGA (P16). ETH PHY LED2 |
1001 | uio_unidir | |
1010 | Undefined | |
others | PHY_LED0 | LED output 0 of Ehternet transceiver chip |
Register CR2
CR2 | related function |
---|---|
15:12 | XCLK Mux |
11:8 | XIO6 Mux |
7:4 | XIO5 Mux |
3:0 | XIO4 Mux |
The mapping of CPLD IOs (XIO4,XIO5,XIO6 and XCLK) that are connected directly with FPGA, can be changed using CR2 register.
Value (CR2[3:0]) | XIO4 Mux | Description |
---|---|---|
0001 | MIO7 | GPIO |
0010 | SHA_IO | SDA for CryptoAuthentication Chip |
0011 | MAC_IO | Serial Clock/Data input/Output of Serial EEPROM |
1000 | uio_unidir | |
0110 | 'Z' | |
0111 | Undefined | |
others | PHY_LED0 | Default value for CR2[3:0] is 0000. |
Value (CR2[7:4]) | XIO5 Mux | Description |
0001 | MIO14 | RX pin of UART0 (FPGA Zynq PS) |
0010 | Undefined | |
0011 | RTC_INT | Interrupt output or frequency output of RTC chip |
1000 | uio_unidir | |
0110 | 'Z' | |
0111 | Undefined | |
others | PHY_LED1 | Default value for CR2[7:4] is 0000. |
Value (CR2[11:8]) | XIO6 Mux | Description |
0001 | MIO15 | TX pin of UART0 (FPGA Zynq PS) |
0010 | Undefined | |
0011 | osc_clk | This pin is directly connected to on-chip oscillator signal. (24.18MHZ) |
1000 | uio_unidir | |
0110 | 'Z' | |
0111 | INTR | INTR signal can be depending on CR3 register value connected to one of the following interrupt signals: INT1, INT2, RTC_INT, PHY_LED2 |
others | PHY_LED2 | Default value for CR2[11:8] is 0000. |
Value (CR2[15:12]) | XCLK Mux | Description |
0001 | RTC_INT | Interrupt output or frequency output of RTC chip |
0010 | osc_clk | This pin is directly connected to on-chip oscillator signal. (24.18MHZ) |
0011 | Undefined | |
1000 | Undefined | |
0110 | Undefined | |
0111 | Undefined | |
others | CLK_125MHZ | Default value for CR2[15:12] is 0000.. This pin is connected to output clock pin of ethernet transceiver chip. |
Register CR3
CR3 bit | related port/signal | Description |
---|---|---|
0 | INT1 | MEMS interrupt 1 |
1 | INT2 | MEMS interrupt 2 |
2 | RTC_RST | Real time clock interrupt |
3 | PHY_LED2 | Interrupt output pin of ethernet transceiver |
4 | OTG_RST | Reset for high speed USB transceiver |
5 | ETH_RST | Reset for ethernet transceiver / Reset for serial for unio mac read core |
6 | MMC_RST | Reset for MMC |
7 | EN_ETH_CLK | Enable for ETH clock |
15:8 | WDT enable/ Extra enable | Enable watchdog timer (0xA5) / Enable Extra enable (0xE5) |
Register CR4
CR4 bits | related function | Description |
---|---|---|
7:0 | WDT time | if CR4[7:0]=0x00 → WDT time=0x07 |
15:8 | not used |
Register SR1
SR1 | Description |
---|---|
0 | INT1 |
1 | INT2 |
2 | RTC_INT |
3 | PHY_LED2 |
7 | BOOTMODE_LATCHED |
8 | BOOTMODE_IN2 |
9 | BOOTMODE_IN |
10 | NOSEQ |
11 | NOSEQ_LATCHED |
12 | WD_EVENT |
13 | PG_1V5 |
14 | EXTRA_ENABLED or WDOG_ENABLED |
15 | mac_valid |
SC subsystem IOs and related registers
Signal SHA_IO of CryptoAuthentication chip
Value XIO4[3:0] | Value XIO5 | SHA_IO |
---|---|---|
0010 | '0' | '0' |
else | 'Z' |
Signal MAC_IO of serial EEPROM
Value XIO4[3:0] | MAC_IO |
---|---|
0011 | '0' |
else | Connected to internal MAC read block |
Signals MIO14 (RX) and MIO15 (TX) of UART0
Value (CR2[7:4]) | MIO14 | Description |
---|---|---|
1001 | XIO5_in | XIO5_in is equal to XIO5 if VCCIO34 voltage equal to 1.8V. |
else | 'Z' | |
Value (CR2[11:8]) | MIO15 | Description |
1001 | XIO6_in | XIO6_in is equal to XIO6 if VCCIO34 voltage equal to 1.8V. |
else | 'Z' |
I2C to GPIO Subsystem
The subsystem I2C to GPIO port mapping is according the following table:
I2C to GPIO | Pin name | CPLD Pin | Direction | FPGA Pin | Description |
---|---|---|---|---|---|
sda_in (SDA) | X7 | M1 | from FPGA | N22 | |
sda_out | X5 | J1 | to FPGA | P22 | If X7 is Low, this pin will be disconnected. |
sclk (SCL) | X1 | F1 | from FPGA | L16 | |
GPIO_input | Mapping the GPIO_input bits to various ports or signals | ||||
GPIO_output | Not used |
GPIO input bit mapping:
GPIO_input bit | Connected to: |
---|---|
0 | PHY_LED0 |
1 | PHY_LED1 |
2 | MIO7 |
3 | NOSEQ |
4 | RESIN_g |
5 | EN1_g |
6 | BOOTMODE_LATCHED |
7 | BOOTMODE_IN |
8 | INT1 |
9 | INT2 |
10 | RTC_INT |
11 | PHY_LED2 |
12 | '0' |
13 | '0' |
UNI/O MAC read core IO data mapping:
Value (uio_sm_cnt[8:5]) | uio_io_data |
---|---|
0000 | MIO7 |
0001 | RTC_INT |
0010 | INT1 |
0100 | INT2 |
0011 | PHY_LED0 |
0100 | PHY_LED1 |
0101 | PHY_LED2 |
0110 | BOOTMODE_IN |
0111 | MIO14 |
1000 | MIO15 |
1001 | XIO4 |
1010 | XIO5 |
1011 | XIO6 |
1100 | WD_HIT |
1101 | '0' |
1110 | '0' |
Multiplexing uio data output between uio-id and uio-io:
Value (uio_sm_cnt[2:1]) | Value (uio_sm_cnt(4)) | uio_unidir |
---|---|---|
01 | - | '0' |
10 | '0' | uio_id_data |
10 | '1' | uio_io_data |
Pins / Functions default map
At power up the System Management Controller starts with the following default settings:
Pin/Function | Used as / Mapped to | Notes |
---|---|---|
ETH PHY LED0 | XIO to FPGA | |
ETH PHY LED1 | XIO to FPGA | |
ETH PHY LED2 | XIO to FPGA | |
ETH PHY CONFIG | Tied logic low | PHY Address set to 0 |
ETH CLK125MHz | Pass through FPGA B34 SRCC pin | |
ETH Clock Enable | Tied logic high | |
ETH PHY Reset | Internal RESET | |
MIO7 | LED1 | |
MEMS/RTC I2C | XIO to FPGA | |
RTC Interrupt | - | |
MEMS Interrupt 1 | - | |
MEMS Interrupt 2 | - | |
eMMC Reset | Internal RESET | |
USB PHY Reset | Internal RESET | |
FPGA PUDC | Tied logic low | |
FPGA PROG_B | Tied logic high | |
Zynq Cascaded JTAG | Enabled (pulled low) | |
Zynq boot mode | SPI or SD, depending on bootmode pin | |
Zynq SRST | Tied logic high | |
Zynq POR | Internal POR/Reset | |
PLL | Not used | |
LED2 | System Status LED | |
LED1 | MIO7 | |
NOSEQ Input | NOSEQ at power, LED out after boot | |
Power Good 1.5V | ||
Power Good VTT | ||
MODE Input |
On-board LEDs
There are 3 on-board LEDs, with two of them connected to the System Management Controller and one to the Zynq PL (Done pin).
Name | Color | Connected to: | Default mapping: |
---|---|---|---|
LED1 | Green | SC | PL MIO[7] |
LED2 | Red | SC | Boot Mode Blink (Fast → SPI, Slow→ SD Card) |
LED3 | Green | Zynq PL | FPGA Done - Active Low |
LED Status Codes
# | LED1 Green | LED2 Red | LED3 Green | Status | Description |
---|---|---|---|---|---|
1 | OFF | OFF | ON | Fatal power error | This combination after power up is only possible in no sequencing compatibility mode were 3.3Vout is supplied externally. The 1.0V and 1.8V DC-DC supplies are forced on (NOSEQ=1), and the SC is not able to start (3.3Vin below 2.1V). This should never happen if the external power supplies are OK. |
2 | OFF | ON | OFF | VIN missing (or EN1 low) | 3.3Vin is present, but the DC-DC supplies are not powered or 3.3Vin is below 3.05V. If the LEDs stay on in this state then 3.3Vout is not turned on, and the Zynq is kept in the POR state. |
3 | OFF | 1/2 Blink Fast 4 Hz | ON | OK | Boot mode selected is SPI Flash. This status remains after boot also if the LED settings are not changed and user is not controlling MIO7 and FPGA is not loaded. |
4 | OFF | 1/2 Blink Slow 1 Hz | ON | OK | Boot mode selected is SD Card. This status remains after boot also if the LED settings are not changed and user is not controlling MIO7 and FPGA is not loaded. |
5 | MIO7 or user function | Blink or user function | OFF | OK | LED3 goes off when the FPGA is configured. NOTE: The FPGA design can control this LED too using STARTUPE2, so it may remain ON or be flashing when the FPGA is configured. |
6 | ON | Slow blink 0.5Hz, 1/8 on, 7/8 off | OFF | Powerdown | EN1 input to the module is low. If sequencing is enabled in this mode, then all power supplies on the module are OFF. |
7 | ON | Slow blink 0.5Hz, 1/8 on, 7/8 off | ON | EN1 input to the module is low. Sequencing is disabled module is in reset state. | |
8 | ON | ON | ON | Reset | Powered, RESIN input is active low or Bank B34 Supply Voltage is missing. |
LED1 Green
This LED is mapped to MIO7 after power up. After the Zynq PS has booted it can change the mapping of this LED. If SC can not enable power to the Zynq then this LED will remain under SC control. It is available to the user only after the power supplies have stabilized and the POR reset to the Zynq is released. If watch dog timer is activated this LED will be assigned to the 7th bit of the counter of watch dog timer.
LED1(Green) | Condition | Description |
---|---|---|
WD_counter(7) | WDOG_ENABLED = '1' | |
ON | POR_B_i = '0' | POR_B_i is '0' if one of the following signals is '0' ---> EN1 or RESIN or PG_ALL or PORDONE |
Variable | else | Mapping depends on the CR1[3:0] value |
LED2 Red
This LED is used to show various signal or port states. The function of this LED can be changed by CR1 register.
LED2(Red) | Condition | Description |
---|---|---|
powerblink | EN1_g = '0' | EN1_g is delayed EN1. |
ON | POR_B_i = '0' | |
Variable | else | Mapping depending on the CR1[7:4] value |
LED3 Green (FPGA Done)
This green LED is connected to the FPGA Done pin which has an active low state. As soon as the Zynq is powered and the 3.3V I/O voltage is enabled, this LED will illuminate. This indicates that the Zynq PL is not configured. Once the Zynq PL has been configured the LED will go off.
During normal operation when the Zynq PL has been configured, the LED can be controlled from the FPGA fabric. Control of the LED in a user design requires the use of Xilinx startup primitive rather than a normal I/O primitive. If the startup primitive is not used then the LED will go off after configuration and remain off irrespectively of the user design.
This LED can not be controlled by the SC. If green LED3 does not light up at least for short time at power then there is major problem with power supplies, FPGA core and aux voltages may be missing.
CR registers access methods
System Controller can be accessed as PHY with address 0x1A on the ETH0 Management bus (MIO pins 52, 53). PHY at address 0x00 is the ETH0 onboard ethernet PHY Marvell 88E1512. PHY at address 0x1A is the System Controller. OUI 0x7201 should be decoded as Model TE0720-01. Model 0x01 is Assembly option. Rev 0x00 is the firmware major revision for the System Controller (Rev 0 is the initial version). The CR registers have individual number to be accessed in FSBL code or Linux console. These numbers are defined in mdio_slave_interface subsystem in CPLD VHDL code. Refer to SC registers to see the table of CR registers.
The CR registers can be accessed in three methods. It can be used u-boot functions , FSBL code or phytool command in linux console to access these registers.
FSBL code
It is possible to access the CR registers in FSBL code. The following functions are used to write or read these resgisters.
LONG XEmacPs_PhyWrite(XEmacPs *InstancePtr, u32 PhyAddress, u32 RegisterNum, u16 PhyData) → To write in CR registers
LONG XEmacPs_PhyRead(XEmacPs *InstancePtr, u32 PhyAddress, u32 RegisterNum, u16 *PhyDataPtr) → To read CR registers
Note that to access this registers in FSBL code it must be written the following instruction before above commands:
Mac_Config = XEmacPs_LookupConfig(XPAR_PS7_ETHERNET_0_DEVICE_ID); if(Mac_Config == NULL) { return XST_FAILURE; }
Status = XEmacPs_CfgInitialize(&Emac, Mac_Config, Mac_Config->BaseAddress); if(Status != XST_SUCCESS){ return XST_FAILURE; }
For example to write 0x0077 in CR1 register the following instruction is used:
XEmacPs_PhyWrite(&Emac, 0x1A, 5, 0x0077);
Note that the CR register names are CR1, CR2 , CR3 and CR4. But these registers are named in FSBL code register5, register6, register7 and register12 subsequently.
U-boot
Communication between Zynq and CPLD chip in mdio bus can be established anytime when ETH0 and management interface are enabled also before FPGA PL Fabric is configured too.
System Controller Firmware version and some other version info can be read with u-boot command mii info:
zynq-uboot> mii info
PHY 0x00: OUI = 0x5043, Model = 0x1D, Rev = 0x01, 100baseT, FDX
PHY 0x1A: OUI = 0x7201, Model = 0x01, Rev = 0x00, 10baseT, HDX
zynq-uboot>
To write a value into CR registers or to read one of them the following instructions can be used:
mii read <addr> <reg>
mii write <addr> <reg> <data>
For example to read CR4 register the following instruction can be written in U-Boot command console:
zynq-uboot> mii read 0x1A 0x0C
For example to write 0x0077 in CR1 can be written:
zynq-uboot> mii write 0x1A 5 0x0077
LED1 and LED2 will be switched on.
Bit Decoding
Reg Addr | Bits | U-BOOT ENV Variable | Description |
---|---|---|---|
2 | 15:0 | board | upper bits of SoM Model |
3 | 15:10 | board | lower bits of SoM Model |
4 | 15:14 | board | FPGA Speed Grade (1, 2 or 3) |
4 | 13:12 | board | FPGA Temperature Range (0=Commercial, 1=Extended, 2=Industrial, 3=Automotive) |
4 | 11:8 | - | Assembly Variant |
4 | 7:0 | scver | SC Firmware Revision Minor number |
Linux
It is possible to write into CR registers and to read these registers in Linux console directly. To access the CR registers it must be added ethtool package , while linux image file is generated. To activate this option in Petalinux this package must be chosen in configuration of rootfs in petalinux. The path for this package is: Filesystem packages/console/network/ethtool
If this package is installed , phytool command can be used to access the CR registers. Phytool command format is:
phytool read device/addr/register
phytool write device/addr/register <value>
For example to switch on LED1 and LED2 it must be written 0x0077 value in the register CR1:
phytool eth0/0x1A/5 0x0077
To switch off these LEDs execute this instruction:
phytool eth0/0x1A/5 0x0066
Reading MAC address
It can be read MAC-address automatically. Customized u-boot does read MAC Address and stores it in environment variables as required, as a result, proper MAC address is used both in u-boot as also in Linux. Setting up MAC Address for Linux involves dynamic rewrite of FDT, this is done with u-boot script that starts Linux. To read MAC address automatically, the following steps must be implemented:
In the FSBL code it must be written the following code additionally:
Mac_Config = XEmacPs_LookupConfig(XPAR_PS7_ETHERNET_0_DEVICE_ID); if(Mac_Config == NULL) { return XST_FAILURE; }
Status = XEmacPs_CfgInitialize(&Emac, Mac_Config, Mac_Config->BaseAddress); if(Status != XST_SUCCESS){ return XST_FAILURE; }
/*
* Read out MAC Address bytes
*/
Status = XEmacPs_PhyRead(&Emac, 0x1A, 9, &rval16); if(Status != XST_SUCCESS){ return XST_FAILURE; }
mac_addr[0] = (unsigned char)(rval16 >> 8);
mac_addr[1] = (unsigned char)(rval16 & 0xFF);
Status = XEmacPs_PhyRead(&Emac, 0x1A, 10, &rval16); if(Status != XST_SUCCESS){ return XST_FAILURE; }
mac_addr[2] = (unsigned char)(rval16 >> 8);
mac_addr[3] = (unsigned char)(rval16 & 0xFF);
Status = XEmacPs_PhyRead(&Emac, 0x1A, 11, &rval16); if(Status != XST_SUCCESS){ return XST_FAILURE; }
mac_addr[4] = (unsigned char)(rval16 >> 8);
mac_addr[5] = (unsigned char)(rval16 & 0xFF);
/*
* Write MAC Address to OCM memory for u-boot to import!
*
*/
//strcpy(0xFFFFFC04, "ethaddr=00:0a:35:00:00:05\n" );
#ifdef UBOOT_ENV_MAGIC
Xil_Out32(UBOOT_ENV_MAGIC_ADDR, UBOOT_ENV_MAGIC); // Magic!
MacToUbootEnvironment((char*)UBOOT_ENV_ADDR, mac_addr);
/*
* Set MAC Address in PS7 IP Core registers
*/
Status = XEmacPs_SetMacAddress(&Emac, mac_addr, 1); if(Status != XST_SUCCESS){ return XST_FAILURE; }- Add the following definition in petalinux-configuration platform-top header file:
#define CONFIG_PREBOOT "echo U-BOOT for petalinux;echo importing env from FSBL shared area at 0xFFFFFC00; if itest *0xFFFFFC00 == 0xCAFEBABE; then echo Found valid magic; env import -t 0xFFFFFC04; fi;setenv preboot; echo; dhcp"
The platform-top.h file can be found in the following path: \petalinux\project-spec\meta-user\recipes-bsp\u-boot\files
The Zynq SoC reads the MAC address from EEPROM by CPLD during power-on and copies this data in OCM (On-chip Memory). After that either in Linux or Uboot console MAC address can be accessed.
For more information refer to TE0720 test board
Appx. A: Change History and Legal Notices
Revision Changes
changes REV04 to REV05:
0.05 watchdog
changes REV03 to REV04:
NA
changes REV02 to REV03:
NA
changes REV01 to REV02:
added deglicht for EN1 and RESIN inputs
added VCORE ON when 3.3 OK signalled
Document Change History
To get content of older revision got to "Change History" of this page and select older document revision number.
Date | Document Revision | CPLD Firmware Revision | Supported PCB Revision | Authors | Description |
---|---|---|---|---|---|
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] | 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] | Work in progress | ||
2017-06-07 | 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] |
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]
Table of contents
- No labels