Page 3
Preface Target Audience of this Manual This manual is intended for hardware developers who want to use the ERTEC 400 for new products. Experience working with processors and designing embedded systems and knowledge of Ethernet are required for this. It describes all ERTEC 400 function groups in detail and provides information that you must take into account when configuring your own PROFINET IO device hardware.
Contents Introduction ..........................9 1.1 Applications of the ERTEC 400 ......................9 1.2 Features of the ERTEC 400 ........................9 1.3 Structure of the ERTEC 400........................10 1.4 ERTEC 400 Package ..........................11 1.5 Signal Function Description........................12 1.5.1 GPIO 0 to 31 and Alternative Functions..................12 1.5.2...
Page 6
7.2 Page Offset Setting ..........................75 7.3 Page Control Setting ..........................76 7.3.1 LBU Read from ERTEC 400 with separate Read/Write line (LBU_RDY_N active low) ....77 7.3.2 LBU Write to ERTEC 400 with separate Read/Write line (LBU_RDY_N active low)...... 78 7.3.3...
Page 7
8.4 PCI Register Description ........................91 Memory Description.......................92 9.1 Memory Partitioning of the ERTEC 400 ....................92 9.2 Detailed Memory Description ......................... 93 Test and Debugging.......................95 10.1 ETM9 Embedded Trace Macrocell ......................95 10.1.1 Trace Modes..........................95 10.1.2 Features of the ETM9 Module ....................... 95 10.1.3 ETM9 Registers ..........................
Page 8
Table 19: Setting of Various Page Sizes ....................... 75 Table 20: Setting of Various Offset Areas ......................75 Table 21: Overview of Accesses to Address Areas of ERTEC 400 ............... 76 Table 22: LBU read access timing with seperate Read/Write line ................. 77 Table 23: LBU write access timing with seperate Read/Write line.................
By virtue of its integrated ARM946 processor, integrated 4-port realtime Ethernet switch, and available options for connecting external host processor systems to a selectable bus system (PCI or LBU), the ERTEC 400 meets all of the requirements for implementing PROFINET devices with integrated switch functionality.
ERTEC 400 Package The ERTEC 400 is supplied in an FBGA package with 304 pins. The distance between the pins is 0.8 mm. The package dimensions are 19 mm x 19 mm. Figure 2: ERTEC 400 Package Description The following documents contain the soldering instructions for the ERTEC 400: /10/ Soldering instructions for lead-based block.
Signal Function Description Pin Description for ERTEC 400 The ERTEC 400 Ethernet communication block is available in a 304-pin FBGA package: The signal names of the ERTEC 400 are described in this section. 1.5.1 GPIO 0 to 31 and Alternative Functions Various signals are multiplexed on the same pin.
ARM946E-S Processors The ARM946E-S processor is implemented in the ERTEC 400. This description is based on /1/ and /2/. Structure of ARM946E-S An ARM946E-S processor system is used. The figure below shows the structure of the processor. In addition to the processor core, the system contains one data cache, one instruction cache, a memory protection unit (MPU), a system control coprocessor, and a tightly coupled memory.
Tightly Coupled Memory (TCM) A 4-Kbyte data TCM (D-TCM) is implemented in the ARM946E-S processor of the ERTEC 400. The memory is locked after a reset. The D-TCM can be placed anywhere in the address space of the ARM946E-S and must be used together with a region of the memory protection unit.
An ETM9 module is connected at the ARM946E-S. This module permits debugging support for data and instruction traces in the ERTEC 400. The module contains all signals required by the processor for the data and instruction traces. The ETM9 module is operated by means of the JTAG interface. The trace information is provided outwards to the trace port via a FIFO memory.
Table 3: Overview of FIQ Interrupts (1) Access to non-existing addresses is detected by the individual function groups of the ERTEC 400 and triggers a pulse with duration Tp = 2/50 MHz. For evaluation of this interrupt, the connected FIQ input must be specified as an edge-triggered input.
Bus System of the ERTEC 400 The ERTEC 400 has two different buses internally. High-performance communication bus (multilayer AHB bus) I/O bus (APB bus) The following function blocks are connected directly to the multilayer AHB bus: ARM946E-S (Master/Slave) IRT switch...
32 bits and operates at a frequency of 50 MHz. I/O on APB bus The ERTEC 400 block has multiple I/O function blocks. They are connected to the 32-bit APB I/O bus. The ARM946E-S or PCI/LBU interface can access the I/O. The following I/O are available.
PCI slave macro is enabled during the boot operation in the ARM946E-S. This enables the user software to be loaded from the PCI master to the various memory areas of the ERTEC 400. At the end of the data transfer, the PCI master sets an identification bit in the SRAM in order to communicate to the ARM processor that the download is complete.
"INT_QVZ_PCI_STATE" in register "PLL_STAT_REG" at the beginning of 2nd level boot code. General Purpose I/O (GPIO) A maximum of 32 general purpose inputs/outputs are available in the ERTEC 400. After a reset, these are set as GPIO inputs. GPIOs [31, 7 : 0] are always available as I/O because no additional functions can be assigned.
Timer 0 and Timer 1 Two independent timers are integrated in the ERTEC 400. They can be used for internal monitoring of diverse software routines. Each timer has an interrupt output that is connected to the IRQ interrupt controller of the ARM946.
The maximum input frequency for the F-CLK is one-quarter of the APB clock. In the event of a quartz failure on the ERTEC 400, a minimum output frequency between 40 and 90 MHz is set at the PLL. This yields a minimum APB-CLK frequency of PLLOUT 40 MHz / 6 = 6.6666 MHz.
Watchdog Timers Two watchdog timers are integrated in the ERTEC 400. The watchdog timers are intended for stand-alone monitoring of processes. The working clock of 50 MHz is derived from the PLL the same as the processor clock. 4.5.1 Watchdog Timer 0 Watchdog timer 0 is a 32-bit down-counter to which the WDOUT0_N output is assigned.
0: Watchdog counter 0 disabled 1: Watchdog counter 0 enabled Note: If this bit = 0, the WDOUT0_n output of the ERTEC 400 is active (0), the interrupt of the watchdog (WDINT) is “0”, and the status bit of counter 0 (Bit 3) is “0”.
UART1/ UART2 Two UARTs are implemented in the ERTEC 400. The inputs and outputs of the UARTs are available as an alternative function at GPIO port [13:9] (UART1) and GPIO port [18:14] (UART2). For this purpose, the I/O must be assigned to the relevant inputs and outputs and the alternative function must be assigned (see GPIO register description).
UART 1 can also be used as a BOOT medium if, for example, functions from an external PC are to be loaded to the ERTEC 400 and executed. The BOOT medium is selected by the BOOT[2:0] inputs during the active reset phase.
Synchronous Interface SPI An SPI interface is implemented in the ERTEC 400. The inputs and outputs of the SPI interface are available as an alternative function at GPIO port [23:16]. For this purpose, the I/O must be assigned to the relevant inputs and outputs and the alternative function must be assigned (see GPIO register description).
The SPI interface can also be used as a BOOT medium if, for example, functions from a serial EEPROM are to be loaded to the ERTEC 400 and executed. The BOOT medium is selected by the BOOT[2:0] inputs during the active reset phase.
System Control Register The system control registers are ERTEC 400-specific control registers that can be read and written to from the PCI/LBU side or from the ARM946. A listing of all system control registers and their address assignments as well as a detailed description are included in the following sections.
ID_REG Addr.: 0x4000_2600 Default: 0x4026_0100 Description Identification of ERTEC 400 Bit No. Name Description 31..16 ERTEC400-ID ERTEC 400 identifier: 4026h (corresponds to the device ID of the AHB-PCI bridge) 15..8 HW-RELEASE HW release: 01h 7..0 Reserved Reserved BOOT_REG Addr.: 0x4000_2604...
Page 58
1: Last reset was via a software reset WD_RESET 1: Last reset was via a watchdog PLL_STAT_REG Addr.: 0x4000_2614 Default: 0x0007_0005 Description Status register for PLL of ERTEC 400 and interrupt control for FIQ3 Bit No. Name Description 31..19 ---- Reserved...
RMII/MII – interfacing of Ethernet MACs • 5.1.1 Clock Supply in ERTEC 400 The required clocks are generated in the ERTEC 400 by means of internal PLL and/or through direct infeed. The following table provides a detailed list of the clocks: MODULE CLOCK SOURCE...
In MII mode, the two PHYs are supplied with one 25 MHz PHY clock. The clock for the Ethernet ports of the ERTEC 400 is supplied by the MII PHYs via the RX_CLK and TX_CLK clock cables. The clock for the Ethernet ports is enabled/disabled via the clock control register in the IRT switch.
Figure 10: Clock Supply of Ethernet Interface Reset Logic of the ERTEC 400 The reset logic resets the entire circuit of the ERTEC 400 except for the PCI portion of the AHB-PCI bridge. The reset system of the ERTEC 400 is enabled by the following events: Hardware reset via external RESET_N pin •...
This register can be evaluated after a restart. 5.2.3 Software reset A software reset can be triggered in the ERTEC 400 by setting a bit in the reset control register. The XRES_SOFT bit is set in the reset status register when the reset is triggered. 5.2.4...
If one of the four memory areas that are selected via the CS_PER0_N to CS_PER3_N chip select outputs is addressed, the memory controller of the ERTEC 400 waits for the RDY_PER_N input signal. The monitoring duration is set in the ASYNC_WAIT_CYCLE_CONFIG EMIF register and is active if timeout monitoring (Bit 7) is set in the EXTENDED_CONFIG EMIF register.
External Memory Interface (EMIF) In order to access an external memory area, an External Memory Interface is incorporated in the ERTEC 400. The interface contains one SDRAM memory controller and one SRAM memory control each for asynchronous memory. Both interfaces can be assigned separately as active interfaces. That is, the data bus is driven actively to High at the end of each access.
LBU_RDY_N is a tristate output and must be pulled to his “ready” level by an external pull-down or pull-up resistor. During an access from the LBU-Interface to the ERTEC 400 (CS with RD or WR activ) , the LBU_RDY_N switched to inactiv (Wait) first. LBU_RDY_N will be active for a 50 MHz-Clock if data can be read or write.
7.3.1 LBU Read from ERTEC 400 with separate Read/Write line (LBU_RDY_N active low) LBU_CS_R_N/ LBU_CS_M_N RCSH CSRS LBU_RD_N LBU_A(20:0)A/ LBU_SEG(1:0)/ LBU_BE(1:0)_N LBU_RDY_N LBU_D(15:0) Figure 12: LBU-Read-Sequence with separate RD/WR line Parameter Description chip select asserted to read pulse asserted delay...
7.3.2 LBU Write to ERTEC 400 with separate Read/Write line (LBU_RDY_N active low) LBU_CS_R_N/ LBU_CD_M_N WCSH CSWS LBU_WR_N LBU_A(20:0)/ LBU_SEG(1:0) LBU_BE(1:0)_N LBU_RDY_N LBU_D(15:0) Figure 13: LBU-Write-Sequence with separate RD/WR line Parameter Description chip select asserted to write pulse asserted delay...
7.3.3 LBU Read from ERTEC 400 with common Read/Write line (LBU_RDY_N active low) LBU_CS_R_N/ LBU_CS_M_N LBU_WR_N LBU_A(20:0)/ LBU_SEG(1:0)/ LBU_BE(1:0)_N LBU_RDY_N LBU_D(15:0) Figure 14: LBU-Read-Sequence with common RD/WR line Parameter Description write signal deasserted to chip select asserted setup time 2 ns...
LBU unit drives the ERTEC 400 databus. The ERTEC 400 has two LBU chip select inputs. One for access to the page configuration register (LBU_CS_R_N) and one to access to the ERTEC 400 memory address space (LBU_CS_M_N). Only one of these chip select signals may be active at a time and it is not allowed to chahge the chip select during the complete access.
PCI Interface The AHB-PCI bridge of Fujitsu-Siemens is used as the PCI interface. A 2-Gbyte segment starting at address 0x80000000 (offset = 2 Gbytes) is on the AHB bus. See also “Detailed Memory Description“ in Section 9.2. The configuration area of the PCI macro is addressed here. Mapping of addresses of the AHB to the address area of the PCI bus can be set in the configuration area.
The ERTEC 400 requires the PCI clock to initiate the “PME_N” signal. If the power state of the ERTEC 400 is not D0, all PCI interrupts in the ERTEC 400 must be disabled via the software (according to the PCI specification, PCI interrupts can only be enabled in the D0 state). There is no hardware support for disabling the interrupts.
ERTEC 400 in a PC System In PC systems, the ERTEC 400 can be integrated into the system as a PC card with host and master functionality. The PC card can be operated on the 32-bit bus at a maximum of 66 MHz. Interrupt INTB_N must be disabled because the PC interface of the ERTEC 400 is only a "single function interface."...
8.2.2 ERTEC 400 as a Station on the Local PCI Bus In contrast to PC systems, the configuration can be changed during operation in local PCI systems where a host is active on the PCI system. In systems where a PCI interface is implemented only between several ERTEC 400s, one of the ERTEC 400s can also assume the host function.
10.1 ETM9 Embedded Trace Macrocell An ETM9 module is integrated in the ARM946E-S of the ERTEC 400 to enable instructions and data to be traced. The ARM946E-S supplies the ETM module with the signals needed to carry out the trace functions. The ETM9 module is operated by means of the Trace interface or JTAG interface.
10.2 Trace Interface The trace interface is parameterized, enabled, and disabled by means of a connected debugger (e.g. by Lauterbach) on the JTAG interface. A Trace port is provided in the ERTEC 400 for tracing internal processor states: PIPESTA [2:0] •...