EMAC Functional Architecture | www.ti.com |
2.1.3GMII Clocking
The GMII interface is available only on EMAC0 and requires two clock sources generated internally, the peripheral bus clock and the RFTCLK inputs to the EMAC module. SYSCLK14 is programmed to /4 for this interface to provide a
For timing purposes, data in
GMTCLK.
2.1.4RGMII Clocking
The RGMII interface is selected by programming MACSEL0 to 3 (011b) and MACSEL1 to 2 (10b). RGMII requires 4 internally generated clocks; peripheral bus clock and three reference clocks. The EMAC drives the transmit clock, while an external PHY generates the receive clock. The reference clock drives the device pin that gives the
The RGMII protocol takes a GMII data stream and turns it into an interface with half of the data bus width and sends the same amount of data with a reduced pinout. The RGMII protocol also allows for dynamic switching of the mode between
The RGMII interface has separate I/O pins from the other EMAC pins because the interface voltage is different from the other interfaces.
2.1.5S3MII Clocking
S3MII mode is selected by programming MACSEL0 to 5 (101b) and MACSEL1 to 1 (01b). The S3MII gasket needs a
2.2Memory Map
The EMAC includes an internal memory that holds information about the Ethernet packets that are received or transmitted. This internal RAM is 2K x 32 bits in size. The data can be written to and read from the EMAC internal memory via either the EMAC or the CPU. It stores buffer descriptors that are 4 words (16 bytes) deep. This 8K local memory holds enough information to transfer up to 512 Ethernet packets without CPU intervention.
The packet buffer descriptors can be put in internal processor memory (L2) on the TCI6486/C6472 device. There are some
16 | C6472/TCI6486 EMAC/MDIO | SPRUEF8F |
|
| Submit Documentation Feedback |
Copyright ©