TMS320C674x/OMAP-L1x Processor
Ethernet Media Access Controller (EMAC)/
Management Data Input/Output (MDIO) Module
User's Guide
Literature Number: SPRUFL5B
April 2011
2
SPRUFL5B–April 2011
Submit Documentation Feedback
© 2011, TexasInstruments Incorporated
Preface ...................................................................................................................................... 10
1 Introduction ...................................................................................................................... 12
1.1 Purpose of the Peripheral ............................................................................................. 12
1.2 Features ................................................................................................................. 12
1.3 Functional Block Diagram ............................................................................................. 13
1.4 Industry Standard(s) Compliance Statement ....................................................................... 14
2 Architecture ...................................................................................................................... 14
2.1 Clock Control ........................................................................................................... 14
2.2 Memory Map ............................................................................................................ 14
2.3 Signal Descriptions .................................................................................................... 14
2.4 Ethernet Protocol Overview .......................................................................................... 17
2.5 Programming Interface ................................................................................................ 18
2.6 EMAC Control Module ................................................................................................ 29
2.7 MDIO Module ........................................................................................................... 30
2.8 EMAC Module .......................................................................................................... 35
2.9 MAC Interface .......................................................................................................... 37
2.10 Packet Receive Operation ............................................................................................ 41
2.11 Packet Transmit Operation ........................................................................................... 46
2.12 Receive and Transmit Latency ....................................................................................... 47
2.13 Transfer Node Priority ................................................................................................. 47
2.14 Reset Considerations .................................................................................................. 48
2.15 Initialization ............................................................................................................. 49
2.16 Interrupt Support ....................................................................................................... 51
2.17 Power Management ................................................................................................... 55
2.18 Emulation Considerations ............................................................................................. 55
3 EMAC Control Module Registers ......................................................................................... 56
3.1 EMAC Control Module Revision ID Register (REVID) ............................................................ 57
3.2 EMAC Control Module Software Reset Register (SOFTRESET) ............................................... 58
3.3 EMAC Control Module Interrupt Control Register (INTCONTROL) ............................................. 59
3.4 EMAC Control Module Interrupt Core Receive Threshold Interrupt Enable Registers
(C0RXTHRESHEN-C2RXTHRESHEN) ............................................................................. 60
3.5 EMAC Control Module Interrupt Core Receive Interrupt Enable Registers (C0RXEN-C2RXEN) ........... 61
3.6 EMAC Control Module Interrupt Core Transmit Interrupt Enable Registers (C0TXEN-C2TXEN) ........... 62
3.7 EMAC Control Module Interrupt Core Miscellaneous Interrupt Enable Registers
(C0MISCEN-C2MISCEN) ............................................................................................. 63
3.8 EMAC Control Module Interrupt Core Receive Threshold Interrupt Status Registers
(C0RXTHRESHSTAT-C2RXTHRESHSTAT) ...................................................................... 64
3.9 EMAC Control Module Interrupt Core Receive Interrupt Status Registers (C0RXSTAT-C2RXSTAT)
............................................................................................................................ 65
3.10 EMAC Control Module Interrupt Core Transmit Interrupt Status Registers (C0TXSTAT-C2TXSTAT)
............................................................................................................................ 66
3.11 EMAC Control Module Interrupt Core Miscellaneous Interrupt Status Registers
(C0MISCSTAT-C2MISCSTAT) ...................................................................................... 67
3.12 EMAC Control Module Interrupt Core Receive Interrupts Per Millisecond Registers
SPRUFL5B–April 2011 Table of Contents
Submit Documentation Feedback
3
© 2011, TexasInstruments Incorporated
www.ti.com
(C0RXIMAX-C2RXIMAX) ............................................................................................. 68
3.13 EMAC Control Module Interrupt Core Transmit Interrupts Per Millisecond Registers
(C0TXIMAX-C2TXIMAX) .............................................................................................. 69
4 MDIO Registers ................................................................................................................. 70
4.1 MDIO Revision ID Register (REVID) ................................................................................ 70
4.2 MDIO Control Register (CONTROL) ................................................................................ 71
4.3 PHY Acknowledge Status Register (ALIVE) ....................................................................... 72
4.4 PHY Link Status Register (LINK) .................................................................................... 72
4.5 MDIO Link Status Change Interrupt (Unmasked) Register (LINKINTRAW) ................................... 73
4.6 MDIO Link Status Change Interrupt (Masked) Register (LINKINTMASKED) .................................. 74
4.7 MDIO User Command Complete Interrupt (Unmasked) Register (USERINTRAW) .......................... 75
4.8 MDIO User Command Complete Interrupt (Masked) Register (USERINTMASKED) ......................... 76
4.9 MDIO User Command Complete Interrupt Mask Set Register (USERINTMASKSET) ....................... 77
4.10 MDIO User Command Complete Interrupt Mask Clear Register (USERINTMASKCLEAR) ................. 78
4.11 MDIO User Access Register 0 (USERACCESS0) ................................................................ 79
4.12 MDIO User PHY Select Register 0 (USERPHYSEL0) ............................................................ 80
4.13 MDIO User Access Register 1 (USERACCESS1) ................................................................ 81
4.14 MDIO User PHY Select Register 1 (USERPHYSEL1) ............................................................ 82
5 EMAC Module Registers ..................................................................................................... 83
5.1 Transmit Revision ID Register (TXREVID) ......................................................................... 86
5.2 Transmit Control Register (TXCONTROL) ......................................................................... 86
5.3 Transmit Teardown Register (TXTEARDOWN) ................................................................... 87
5.4 Receive Revision ID Register (RXREVID) .......................................................................... 88
5.5 Receive Control Register (RXCONTROL) .......................................................................... 88
5.6 Receive Teardown Register (RXTEARDOWN) .................................................................... 89
5.7 Transmit Interrupt Status (Unmasked) Register (TXINTSTATRAW) ............................................ 90
5.8 Transmit Interrupt Status (Masked) Register (TXINTSTATMASKED) .......................................... 91
5.9 Transmit Interrupt Mask Set Register (TXINTMASKSET) ........................................................ 92
5.10 Transmit Interrupt Mask Clear Register (TXINTMASKCLEAR) .................................................. 93
5.11 MAC Input Vector Register (MACINVECTOR) ..................................................................... 94
5.12 MAC End Of Interrupt Vector Register (MACEOIVECTOR) ..................................................... 95
5.13 Receive Interrupt Status (Unmasked) Register (RXINTSTATRAW) ............................................ 96
5.14 Receive Interrupt Status (Masked) Register (RXINTSTATMASKED) .......................................... 97
5.15 Receive Interrupt Mask Set Register (RXINTMASKSET) ........................................................ 98
5.16 Receive Interrupt Mask Clear Register (RXINTMASKCLEAR) .................................................. 99
5.17 MAC Interrupt Status (Unmasked) Register (MACINTSTATRAW) ............................................ 100
5.18 MAC Interrupt Status (Masked) Register (MACINTSTATMASKED) .......................................... 100
5.19 MAC Interrupt Mask Set Register (MACINTMASKSET) ........................................................ 101
5.20 MAC Interrupt Mask Clear Register (MACINTMASKCLEAR) .................................................. 101
5.21 Receive Multicast/Broadcast/Promiscuous Channel Enable Register (RXMBPENABLE) .................. 102
5.22 Receive Unicast Enable Set Register (RXUNICASTSET) ...................................................... 105
5.23 Receive Unicast Clear Register (RXUNICASTCLEAR) ......................................................... 106
5.24 Receive Maximum Length Register (RXMAXLEN) .............................................................. 107
5.25 Receive Buffer Offset Register (RXBUFFEROFFSET) ......................................................... 107
5.26 Receive Filter Low Priority Frame Threshold Register (RXFILTERLOWTHRESH) ......................... 108
5.27 Receive Channel Flow Control Threshold Registers (RX0FLOWTHRESH-RX7FLOWTHRESH) ........ 108
5.28 Receive Channel Free Buffer Count Registers (RX0FREEBUFFER-RX7FREEBUFFER) ................. 109
5.29 MAC Control Register (MACCONTROL) .......................................................................... 110
5.30 MAC Status Register (MACSTATUS) ............................................................................. 112
4
Contents SPRUFL5B–April 2011
© 2011, TexasInstruments Incorporated
Submit Documentation Feedback
www.ti.com
5.31 Emulation Control Register (EMCONTROL) ...................................................................... 114
5.32 FIFO Control Register (FIFOCONTROL) ......................................................................... 114
5.33 MAC Configuration Register (MACCONFIG) ..................................................................... 115
5.34 Soft Reset Register (SOFTRESET) ................................................................................ 115
5.35 MAC Source Address Low Bytes Register (MACSRCADDRLO) .............................................. 116
5.36 MAC Source Address High Bytes Register (MACSRCADDRHI) .............................................. 116
5.37 MAC Hash Address Register 1 (MACHASH1) ................................................................... 117
5.38 MAC Hash Address Register 2 (MACHASH2) ................................................................... 117
5.39 Back Off Test Register (BOFFTEST) .............................................................................. 118
5.40 Transmit Pacing Algorithm Test Register (TPACETEST) ....................................................... 118
5.41 Receive Pause Timer Register (RXPAUSE) ...................................................................... 119
5.42 Transmit Pause Timer Register (TXPAUSE) ..................................................................... 119
5.43 MAC Address Low Bytes Register (MACADDRLO) ............................................................. 120
5.44 MAC Address High Bytes Register (MACADDRHI) ............................................................. 121
5.45 MAC Index Register (MACINDEX) ................................................................................. 121
5.46 Transmit Channel DMA Head Descriptor Pointer Registers (TX0HDP-TX7HDP) ........................... 122
5.47 Receive Channel DMA Head Descriptor Pointer Registers (RX0HDP-RX7HDP) ........................... 122
5.48 Transmit Channel Completion Pointer Registers (TX0CP-TX7CP) ............................................ 123
5.49 Receive Channel Completion Pointer Registers (RX0CP-RX7CP) ............................................ 123
5.50 Network Statistics Registers ........................................................................................ 124
Appendix A Glossary ............................................................................................................... 133
Appendix B Revision History ..................................................................................................... 135
SPRUFL5B–April 2011 Contents
Submit Documentation Feedback
5
© 2011, TexasInstruments Incorporated
www.ti.com
List of Figures
1 EMAC and MDIO Block Diagram........................................................................................ 13
2 Ethernet Configuration—MII Connections.............................................................................. 15
3 Ethernet Configuration—RMII Connections............................................................................ 16
4 Ethernet Frame Format................................................................................................... 17
5 Basic Descriptor Format.................................................................................................. 18
6 Typical Descriptor Linked List............................................................................................ 19
7 Transmit Buffer Descriptor Format...................................................................................... 22
8 Receive Buffer Descriptor Format....................................................................................... 25
9 EMAC Control Module Block Diagram.................................................................................. 29
10 MDIO Module Block Diagram............................................................................................ 31
11 EMAC Module Block Diagram........................................................................................... 35
12 EMAC Control Module Revision ID Register (REVID)................................................................ 57
13 EMAC Control Module Software Reset Register (SOFTRESET) ................................................... 58
14 EMAC Control Module Interrupt Control Register (INTCONTROL)................................................. 59
15 EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Enable Register
(CnRXTHRESHEN)....................................................................................................... 60
16 EMAC Control Module Interrupt Core 0-2 Receive Interrupt Enable Register (CnRXEN)....................... 61
17 EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Enable Register (CnTXEN) ...................... 62
18 EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Enable Register (CnMISCEN) ............ 63
19 EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Status Register
(CnRXTHRESHSTAT).................................................................................................... 64
20 EMAC Control Module Interrupt Core 0-2 Receive Interrupt Status Register (CnRXSTAT) .................... 65
21 EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Status Register (CnTXSTAT).................... 66
22 EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Status Register (CnMISCSTAT).......... 67
23 EMAC Control Module Interrupt Core 0-2 Receive Interrupts Per Millisecond Register (CnRXIMAX)......... 68
24 EMAC Control Module Interrupt Core 0-2 Transmit Interrupts Per Millisecond Register (CnTXIMAX) ........ 69
25 MDIO Revision ID Register (REVID).................................................................................... 70
26 MDIO Control Register (CONTROL).................................................................................... 71
27 PHY Acknowledge Status Register (ALIVE)........................................................................... 72
28 PHY Link Status Register (LINK)........................................................................................ 72
29 MDIO Link Status Change Interrupt (Unmasked) Register (LINKINTRAW)....................................... 73
30 MDIO Link Status Change Interrupt (Masked) Register (LINKINTMASKED) ..................................... 74
31 MDIO User Command Complete Interrupt (Unmasked) Register (USERINTRAW).............................. 75
32 MDIO User Command Complete Interrupt (Masked) Register (USERINTMASKED) ............................ 76
33 MDIO User Command Complete Interrupt Mask Set Register (USERINTMASKSET)........................... 77
34 MDIO User Command Complete Interrupt Mask Clear Register (USERINTMASKCLEAR) .................... 78
35 MDIO User Access Register 0 (USERACCESS0) .................................................................... 79
36 MDIO User PHY Select Register 0 (USERPHYSEL0) ............................................................... 80
37 MDIO User Access Register 1 (USERACCESS1) .................................................................... 81
38 MDIO User PHY Select Register 1 (USERPHYSEL1) ............................................................... 82
39 Transmit Revision ID Register (TXREVID)............................................................................. 86
40 Transmit Control Register (TXCONTROL)............................................................................. 86
41 Transmit Teardown Register (TXTEARDOWN)....................................................................... 87
42 Receive Revision ID Register (RXREVID) ............................................................................. 88
43 Receive Control Register (RXCONTROL) ............................................................................. 88
44 Receive Teardown Register (RXTEARDOWN) ....................................................................... 89
45 Transmit Interrupt Status (Unmasked) Register (TXINTSTATRAW) ............................................... 90
46 Transmit Interrupt Status (Masked) Register (TXINTSTATMASKED).............................................. 91
6
List of Figures SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
47 Transmit Interrupt Mask Set Register (TXINTMASKSET) ........................................................... 92
48 Transmit Interrupt Mask Clear Register (TXINTMASKCLEAR) ..................................................... 93
49 MAC Input Vector Register (MACINVECTOR) ........................................................................ 94
50 MAC End Of Interrupt Vector Register (MACEOIVECTOR)......................................................... 95
51 Receive Interrupt Status (Unmasked) Register (RXINTSTATRAW)................................................ 96
52 Receive Interrupt Status (Masked) Register (RXINTSTATMASKED) .............................................. 97
53 Receive Interrupt Mask Set Register (RXINTMASKSET)............................................................ 98
54 Receive Interrupt Mask Clear Register (RXINTMASKCLEAR)...................................................... 99
55 MAC Interrupt Status (Unmasked) Register (MACINTSTATRAW)................................................ 100
56 MAC Interrupt Status (Masked) Register (MACINTSTATMASKED) .............................................. 100
57 MAC Interrupt Mask Set Register (MACINTMASKSET)............................................................ 101
58 MAC Interrupt Mask Clear Register (MACINTMASKCLEAR)...................................................... 101
59 Receive Multicast/Broadcast/Promiscuous Channel Enable Register (RXMBPENABLE) ..................... 102
60 Receive Unicast Enable Set Register (RXUNICASTSET).......................................................... 105
61 Receive Unicast Clear Register (RXUNICASTCLEAR)............................................................. 106
62 Receive Maximum Length Register (RXMAXLEN).................................................................. 107
63 Receive Buffer Offset Register (RXBUFFEROFFSET)............................................................. 107
64 Receive Filter Low Priority Frame Threshold Register (RXFILTERLOWTHRESH)............................. 108
65 Receive Channel n Flow Control Threshold Register (RXnFLOWTHRESH).................................... 108
66 Receive Channel n Free Buffer Count Register (RXnFREEBUFFER) ........................................... 109
67 MAC Control Register (MACCONTROL) ............................................................................. 110
68 MAC Status Register (MACSTATUS)................................................................................. 112
69 Emulation Control Register (EMCONTROL) ......................................................................... 114
70 FIFO Control Register (FIFOCONTROL)............................................................................. 114
71 MAC Configuration Register (MACCONFIG)......................................................................... 115
72 Soft Reset Register (SOFTRESET)................................................................................... 115
73 MAC Source Address Low Bytes Register (MACSRCADDRLO).................................................. 116
74 MAC Source Address High Bytes Register (MACSRCADDRHI) .................................................. 116
75 MAC Hash Address Register 1 (MACHASH1)....................................................................... 117
76 MAC Hash Address Register 2 (MACHASH2)....................................................................... 117
77 Back Off Random Number Generator Test Register (BOFFTEST)............................................... 118
78 Transmit Pacing Algorithm Test Register (TPACETEST) .......................................................... 118
79 Receive Pause Timer Register (RXPAUSE) ......................................................................... 119
80 Transmit Pause Timer Register (TXPAUSE)......................................................................... 119
81 MAC Address Low Bytes Register (MACADDRLO)................................................................. 120
82 MAC Address High Bytes Register (MACADDRHI) ................................................................. 121
83 MAC Index Register (MACINDEX) .................................................................................... 121
84 Transmit Channel n DMA Head Descriptor Pointer Register (TXnHDP) ......................................... 122
85 Receive Channel n DMA Head Descriptor Pointer Register (RXnHDP).......................................... 122
86 Transmit Channel n Completion Pointer Register (TXnCP)........................................................ 123
87 Receive Channel n Completion Pointer Register (RXnCP) ........................................................ 123
88 Statistics Register........................................................................................................ 124
SPRUFL5B–April 2011 List of Figures
Submit Documentation Feedback
7
© 2011, Texas Instruments Incorporated
www.ti.com
List of Tables
1 EMAC and MDIO Signals for MII Interface............................................................................. 15
2 EMAC and MDIO Signals for RMII Interface........................................................................... 16
3 Ethernet Frame Description.............................................................................................. 17
4 Basic Descriptor Description............................................................................................. 19
5 Receive Frame Treatment Summary ................................................................................... 44
6 Middle of Frame Overrun Treatment.................................................................................... 45
7 Emulation Control ......................................................................................................... 55
8 EMAC Control Module Registers........................................................................................ 56
9 EMAC Control Module Revision ID Register (REVID) Field Descriptions ......................................... 57
10 EMAC Control Module Software Reset Register (SOFTRESET) ................................................... 58
11 EMAC Control Module Interrupt Control Register (INTCONTROL)................................................. 59
12 EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Enable Register
(CnRXTHRESHEN)....................................................................................................... 60
13 EMAC Control Module Interrupt Core 0-2 Receive Interrupt Enable Register (CnRXEN)....................... 61
14 EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Enable Register (CnTXEN) ...................... 62
15 EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Enable Register (CnMISCEN) ............ 63
16 EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Status Register
(CnRXTHRESHSTAT).................................................................................................... 64
17 EMAC Control Module Interrupt Core 0-2 Receive Interrupt Status Register (CnRXSTAT) .................... 65
18 EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Status Register (CnTXSTAT).................... 66
19 EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Status Register (CnMISCSTAT).......... 67
20 EMAC Control Module Interrupt Core 0-2 Receive Interrupts Per Millisecond Register (CnRXIMAX)......... 68
21 EMAC Control Module Interrupt Core 0-2 Transmit Interrupts Per Millisecond Register (CnTXIMAX) ........ 69
22 Management Data Input/Output (MDIO) Registers ................................................................... 70
23 MDIO Revision ID Register (REVID) Field Descriptions ............................................................. 70
24 MDIO Control Register (CONTROL) Field Descriptions ............................................................. 71
25 PHY Acknowledge Status Register (ALIVE) Field Descriptions..................................................... 72
26 PHY Link Status Register (LINK) Field Descriptions ................................................................. 72
27 MDIO Link Status Change Interrupt (Unmasked) Register (LINKINTRAW) Field Descriptions................. 73
28 MDIO Link Status Change Interrupt (Masked) Register (LINKINTMASKED) Field Descriptions ............... 74
29 MDIO User Command Complete Interrupt (Unmasked) Register (USERINTRAW) Field Descriptions........ 75
30 MDIO User Command Complete Interrupt (Masked) Register (USERINTMASKED) Field Descriptions...... 76
31 MDIO User Command Complete Interrupt Mask Set Register (USERINTMASKSET) Field Descriptions .... 77
32 MDIO User Command Complete Interrupt Mask Clear Register (USERINTMASKCLEAR) Field
Descriptions ................................................................................................................ 78
33 MDIO User Access Register 0 (USERACCESS0) Field Descriptions.............................................. 79
34 MDIO User PHY Select Register 0 (USERPHYSEL0) Field Descriptions......................................... 80
35 MDIO User Access Register 1 (USERACCESS1) Field Descriptions.............................................. 81
36 MDIO User PHY Select Register 1 (USERPHYSEL1) Field Descriptions......................................... 82
37 Ethernet Media Access Controller (EMAC) Registers ................................................................ 83
38 Transmit Revision ID Register (TXREVID) Field Descriptions ...................................................... 86
39 Transmit Control Register (TXCONTROL) Field Descriptions....................................................... 86
40 Transmit Teardown Register (TXTEARDOWN) Field Descriptions................................................. 87
41 Receive Revision ID Register (RXREVID) Field Descriptions....................................................... 88
42 Receive Control Register (RXCONTROL) Field Descriptions ....................................................... 88
43 Receive Teardown Register (RXTEARDOWN) Field Descriptions ................................................. 89
44 Transmit Interrupt Status (Unmasked) Register (TXINTSTATRAW) Field Descriptions......................... 90
45 Transmit Interrupt Status (Masked) Register (TXINTSTATMASKED) Field Descriptions ....................... 91
8
List of Tables SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
46 Transmit Interrupt Mask Set Register (TXINTMASKSET) Field Descriptions..................................... 92
47 Transmit Interrupt Mask Clear Register (TXINTMASKCLEAR) Field Descriptions............................... 93
48 MAC Input Vector Register (MACINVECTOR) Field Descriptions.................................................. 94
49 MAC End Of Interrupt Vector Register (MACEOIVECTOR) Field Descriptions................................... 95
50 Receive Interrupt Status (Unmasked) Register (RXINTSTATRAW) Field Descriptions ......................... 96
51 Receive Interrupt Status (Masked) Register (RXINTSTATMASKED) Field Descriptions........................ 97
52 Receive Interrupt Mask Set Register (RXINTMASKSET) Field Descriptions ..................................... 98
53 Receive Interrupt Mask Clear Register (RXINTMASKCLEAR) Field Descriptions ............................... 99
54 MAC Interrupt Status (Unmasked) Register (MACINTSTATRAW) Field Descriptions ......................... 100
55 MAC Interrupt Status (Masked) Register (MACINTSTATMASKED) Field Descriptions........................ 100
56 MAC Interrupt Mask Set Register (MACINTMASKSET) Field Descriptions ..................................... 101
57 MAC Interrupt Mask Clear Register (MACINTMASKCLEAR) Field Descriptions ............................... 101
58 Receive Multicast/Broadcast/Promiscuous Channel Enable Register (RXMBPENABLE) Field
59 Receive Unicast Enable Set Register (RXUNICASTSET) Field Descriptions ................................... 105
60 Receive Unicast Clear Register (RXUNICASTCLEAR) Field Descriptions ...................................... 106
61 Receive Maximum Length Register (RXMAXLEN) Field Descriptions............................................ 107
62 Receive Buffer Offset Register (RXBUFFEROFFSET) Field Descriptions....................................... 107
63 Receive Filter Low Priority Frame Threshold Register (RXFILTERLOWTHRESH) Field Descriptions ...... 108
64 Receive Channel n Flow Control Threshold Register (RXnFLOWTHRESH) Field Descriptions.............. 108
65 Receive Channel n Free Buffer Count Register (RXnFREEBUFFER) Field Descriptions ..................... 109
66 MAC Control Register (MACCONTROL) Field Descriptions ....................................................... 110
67 MAC Status Register (MACSTATUS) Field Descriptions........................................................... 112
68 Emulation Control Register (EMCONTROL) Field Descriptions................................................... 114
69 FIFO Control Register (FIFOCONTROL) Field Descriptions....................................................... 114
70 MAC Configuration Register (MACCONFIG) Field Descriptions .................................................. 115
71 Soft Reset Register (SOFTRESET) Field Descriptions............................................................. 115
72 MAC Source Address Low Bytes Register (MACSRCADDRLO) Field Descriptions ........................... 116
73 MAC Source Address High Bytes Register (MACSRCADDRHI) Field Descriptions............................ 116
74 MAC Hash Address Register 1 (MACHASH1) Field Descriptions................................................. 117
75 MAC Hash Address Register 2 (MACHASH2) Field Descriptions................................................. 117
76 Back Off Test Register (BOFFTEST) Field Descriptions ........................................................... 118
77 Transmit Pacing Algorithm Test Register (TPACETEST) Field Descriptions.................................... 118
78 Receive Pause Timer Register (RXPAUSE) Field Descriptions ................................................... 119
79 Transmit Pause Timer Register (TXPAUSE) Field Descriptions .................................................. 119
80 MAC Address Low Bytes Register (MACADDRLO) Field Descriptions .......................................... 120
81 MAC Address High Bytes Register (MACADDRHI) Field Descriptions........................................... 121
82 MAC Index Register (MACINDEX) Field Descriptions .............................................................. 121
83 Transmit Channel n DMA Head Descriptor Pointer Register (TXnHDP) Field Descriptions................... 122
84 Receive Channel n DMA Head Descriptor Pointer Register (RXnHDP) Field Descriptions ................... 122
85 Transmit Channel n Completion Pointer Register (TXnCP) Field Descriptions.................................. 123
86 Receive Channel n Completion Pointer Register (RXnCP) Field Descriptions.................................. 123
87 Physical Layer Definitions .............................................................................................. 134
88 Document Revision History............................................................................................. 135
Descriptions............................................................................................................... 102
SPRUFL5B–April 2011 List of Tables
Submit Documentation Feedback
9
© 2011, Texas Instruments Incorporated
About This Manual
This document provides a functional description of the Ethernet Media Access Controller (EMAC) and
physical layer (PHY) device Management Data Input/Output (MDIO) module integrated in the device.
Included are the features of the EMAC and MDIO modules, a discussion of their architecture and
operation, how these modules connect to the outside world, and the registers description for each module.
Notational Conventions
This document uses the following conventions.
• Hexadecimal numbers are shown with the suffix h. For example, the following number is 40
hexadecimal (decimal 64): 40h.
• Registers in this document are shown in figures and described in tables.
– Each register figure shows a rectangle divided into fields that represent the fields of the register.
Each field is labeled with its bit name, its beginning and ending bit numbers above, and its
read/write properties below. A legend explains the notation used for the properties.
– Reserved bits in a register figure designate a bit that is used for future device expansion.
Preface
SPRUFL5B–April 2011
Read This First
Related Documentation From Texas Instruments
The following documents describe the TMS320C674x Digital Signal Processors (DSPs) and OMAP-L1x
Applications Processors. Copies of these documents are available on the Internet at www.ti.com. Tip:
Enter the literature number in the search box provided at www.ti.com.
The current documentation that describes the DSP, related peripherals, and other technical collateral, is
available in the C6000 DSP product folder at: www.ti.com/c6000.
SPRUGM5 — TMS320C6742 DSP System Reference Guide. Describes the C6742 DSP subsystem,
system memory, device clocking, phase-locked loop controller (PLLC), power and sleep controller
(PSC), power management, and system configuration module.
SPRUGJ0 — TMS320C6743 DSP System Reference Guide. Describes the System-on-Chip (SoC)
including the C6743 DSP subsystem, system memory, device clocking, phase-locked loop
controller (PLLC), power and sleep controller (PSC), power management, and system configuration
module.
SPRUFK4 — TMS320C6745/C6747 DSP System Reference Guide. Describes the System-on-Chip
(SoC) including the C6745/C6747 DSP subsystem, system memory, device clocking, phase-locked
loop controller (PLLC), power and sleep controller (PSC), power management, and system
configuration module.
SPRUGM6 — TMS320C6746 DSP System Reference Guide. Describes the C6746 DSP subsystem,
system memory, device clocking, phase-locked loop controller (PLLC), power and sleep controller
(PSC), power management, and system configuration module.
SPRUGJ7 — TMS320C6748 DSP System Reference Guide. Describes the C6748 DSP subsystem,
system memory, device clocking, phase-locked loop controller (PLLC), power and sleep controller
(PSC), power management, and system configuration module.
SPRUG84 — OMAP-L137 Applications Processor System Reference Guide. Describes the
System-on-Chip (SoC) including the ARM subsystem, DSP subsystem, system memory, device
clocking, phase-locked loop controller (PLLC), power and sleep controller (PSC), power
management, ARM interrupt controller (AINTC), and system configuration module.
10
Preface SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
SPRUGM7 — OMAP-L138 Applications Processor System Reference Guide. Describes the
SPRUFK9 — TMS320C674x/OMAP-L1x Processor Peripherals Overview Reference Guide. Provides
SPRUFK5 — TMS320C674x DSP Megamodule Reference Guide. Describes the TMS320C674x digital
SPRUFE8 — TMS320C674x DSP CPU and Instruction Set Reference Guide. Describes the CPU
SPRUG82 — TMS320C674x DSP Cache User's Guide. Explains the fundamentals of memory caches
Related Documentation From Texas Instruments
System-on-Chip (SoC) including the ARM subsystem, DSP subsystem, system memory, device
clocking, phase-locked loop controller (PLLC), power and sleep controller (PSC), power
management, ARM interrupt controller (AINTC), and system configuration module.
an overview and briefly describes the peripherals available on the TMS320C674x Digital Signal
Processors (DSPs) and OMAP-L1x Applications Processors.
signal processor (DSP) megamodule. Included is a discussion on the internal direct memory access
(IDMA) controller, the interrupt controller, the power-down controller, memory protection, bandwidth
management, and the memory and cache.
architecture, pipeline, instruction set, and interrupts for the TMS320C674x digital signal processors
(DSPs). The C674x DSP is an enhancement of the C64x+ and C67x+ DSPs with added
functionality and an expanded instruction set.
and describes how the two-level cache-based internal memory architecture in the TMS320C674x
digital signal processor (DSP) can be efficiently used in DSP applications. Shows how to maintain
coherence with external memory, how to use DMA to reduce memory latencies, and how to
optimize your code to improve cache efficiency. The internal memory architecture in the C674x
DSP is organized in a two-level hierarchy consisting of a dedicated program cache (L1P) and a
dedicated data cache (L1D) on the first level. Accesses by the CPU to the these first level caches
can complete without CPU pipeline stalls. If the data requested by the CPU is not contained in
cache, it is fetched from the next lower memory level, L2 or external memory.
SPRUFL5B–April 2011 Read This First
Submit Documentation Feedback
11
© 2011, Texas Instruments Incorporated
1 Introduction
This document provides a functional description of the Ethernet Media Access Controller (EMAC) and
physical layer (PHY) device Management Data Input/Output (MDIO) module integrated in the device.
Included are the features of the EMAC and MDIO modules, a discussion of their architecture and
operation, how these modules connect to the outside world, and a description of the registers for each
module.
The EMAC controls the flow of packet data from the system to the PHY. The MDIO module controls PHY
configuration and status monitoring.
Both the EMAC and the MDIO modules interface to the system core through a custom interface that
allows efficient data transmission and reception. This custom interface is referred to as the EMAC control
module and is considered integral to the EMAC/MDIO peripheral.
1.1 Purpose of the Peripheral
The EMAC module is used to move data between the device and another host connected to the same
network, in compliance with the Ethernet protocol.
User's Guide
SPRUFL5B–April 2011
EMAC/MDIO Module
1.2 Features
The EMAC/MDIO has the following features:
• Synchronous 10/100 Mbps operation.
• Standard Media Independent Interface (MII) and/or Reduced Media Independent Interface (RMII) to
physical layer device (PHY).
• EMAC acts as DMA master to either internal or external device memory space.
• Eight receive channels with VLAN tag discrimination for receive quality-of-service (QOS) support.
• Eight transmit channels with round-robin or fixed priority for transmit quality-of-service (QOS) support.
• Ether-Stats and 802.3-Stats statistics gathering.
• Transmit CRC generation selectable on a per channel basis.
• Broadcast frames selection for reception on a single channel.
• Multicast frames selection for reception on a single channel.
• Promiscuous receive mode frames selection for reception on a single channel (all frames, all good
frames, short frames, error frames).
• Hardware flow control.
• 8k-byte local EMAC descriptor memory that allows the peripheral to operate on descriptors without
affecting the CPU. The descriptor memory holds enough information to transfer up to 512 Ethernet
packets without CPU intervention. (This memory is also known as CPPI RAM.)
• Programmable interrupt logic permits the software driver to restrict the generation of back-to-back
interrupts, which allows more work to be performed in a single call to the interrupt service routine.
12
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
DMA
Master
8KCPPI
RAM
Interrupt
Combiner
C0
C1
C2
ControlModule
EMAC
Module
MDIO
Module
EMAC
Interrupts
MDIO
Interrupts
Interrupts
EMACSubSystem
RegisterBus
DMA Bus
MII/RMIIBus
MDIOBus
www.ti.com
1.3 Functional Block Diagram
Figure 1 shows the three main functional modules of the EMAC/MDIO peripheral:
• EMAC control module
• EMAC module
• MDIO module
The EMAC control module is the main interface between the device core processor to the EMAC and
MDIO modules. The EMAC control module controls device interrupts and incorporates an 8k-byte internal
RAM to hold EMAC buffer descriptors (also known as CPPI RAM).
The MDIO module implements the 802.3 serial management interface to interrogate and control up to 32
Ethernet PHYs connected to the device by using a shared two-wire bus. Host software uses the MDIO
module to configure the autonegotiation parameters of each PHY attached to the EMAC, retrieve the
negotiation results, and configure required parameters in the EMAC module for correct operation. The
module is designed to allow almost transparent operation of the MDIO interface, with very little
maintenance from the core processor.
The EMAC module provides an efficient interface between the processor and the network. The EMAC on
this device supports 10Base-T (10 Mbits/sec) and 100BaseTX (100 Mbits/sec), half-duplex and full-duplex
mode, and hardware flow control and quality-of-service (QOS) support.
Figure 1 shows the main interface between the EMAC control module and the CPU. The following
connections are made to the device core:
• The DMA bus connection from the EMAC control module allows the EMAC module to read and write
both internal and external memory through the DMA memory transfer controller.
• The EMAC control, EMAC, and MDIO modules all have control registers. These registers are
memory-mapped into device memory space via the device configuration bus. Along with these
registers, the control module’s internal CPPI RAM is mapped into this same range.
• The EMAC and MDIO interrupts are combined into four interrupt signals within the control module.
Three configurable interrupt cores within the control module receive all four interrupt signals from the
combiner and submit interrupt requests to the CPU.
Introduction
Figure 1. EMAC and MDIO Block Diagram
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
13
© 2011, Texas Instruments Incorporated
Architecture
1.4 Industry Standard(s) Compliance Statement
The EMAC peripheral conforms to the IEEE 802.3 standard, describing the Carrier Sense Multiple Access
with Collision Detection (CSMA/CD) Access Method and Physical Layer specifications. The IEEE 802.3
standard has also been adopted by ISO/IEC and re-designated as ISO/IEC 8802-3:2000(E).
However, the EMAC deviates from the standard in the way it handles transmit underflow errors. The
EMAC MII interface does not use the Transmit Coding Error signal MTXER. Instead of driving the error pin
when an underflow condition occurs on a transmitted frame, the EMAC intentionally generates an incorrect
checksum by inverting the frame CRC, so that the transmitted frame is detected as an error by the
network.
2 Architecture
This section discusses the architecture and basic function of the EMAC peripheral.
2.1 Clock Control
All internal EMAC logic is clocked synchronously on one clock domain. See your device-specific data
manual for information.
The MDIO clock is based on a divide-down of the peripheral clock and is specified to run up to 2.5 MHz
(although typical operation would be 1.0 MHz). Because the peripheral clock frequency is variable, the
application software or driver must control the divide-down value.
The transmit and receive clock sources are provided by the external PHY to the MII_TXCLK and
MII_RXCLK pins or to the RMII reference clock pin. Data is transmitted and received with respect to the
reference clocks of the interface pins.
The MII interface frequencies for the transmit and receive clocks are fixed by the IEEE 802.3 specification
as:
• 2.5 MHz at 10 Mbps
• 25 MHz at 100 Mbps
The RMII interface frequency for the transmit and receive clocks are fixed at 50 MHz for both 10 Mbps
and 100 Mbps.
www.ti.com
2.2 Memory Map
The EMAC peripheral includes internal memory that is used to hold buffer descriptions of the Ethernet
packets to be received and transmitted. This internal RAM is 2K × 32 bits in size. Data can be written to
and read from the EMAC internal memory by either the EMAC or the CPU. It is used to store 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. This EMAC RAM is also referred to as the CPPI
buffer descriptor memory because it complies with the Communications Port Programming Interface
(CPPI) v3.0 standard.
The packet buffer descriptors can also be placed in other on- and off-chip memories such as L2 and
EMIF. There are some tradeoffs in terms of cache performance and throughput when descriptors are
placed in the system memory, versus when they are placed in the EMAC’s internal memory. In general,
the EMAC throughput is better when the descriptors are placed in the local EMAC CPPI RAM.
2.3 Signal Descriptions
Support of interfaces (MII and/or RMII) varies between devices. See your device-specific data manual for
information.
2.3.1 Media Independent Interface (MII) Connections
Figure 2 shows a device with integrated EMAC and MDIO interfaced via a MII connection in a typical
system. The EMAC module does not include a transmit error (MTXER) pin. In the case of transmit error,
CRC inversion is used to negate the validity of the transmitted frame.
14
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
MII_TXCLK
MII_TXD[3−0]
MII_TXEN
MII_COL
MII_CRS
MII_RXCLK
MII_RXD[3−0]
MII_RXDV
MII_RXER
MDIO_CLK
MDIO_D
Physical
layer
device
(PHY)
System
core
Transformer
2.5 MHz
or
25 MHz
RJ−45
EMACMDIO
www.ti.com
The individual EMAC and MDIO signals for the MII interface are summarized in Table 1. For more
information, refer to either the IEEE 802.3 standard or ISO/IEC 8802-3:2000(E).
Architecture
Figure 2. Ethernet Configuration—MII Connections
Table 1. EMAC and MDIO Signals for MII Interface
Signal Type Description
MII_TXCLK I Transmit clock (MII_TXCLK). The transmit clock is a continuous clock that provides the timing
MII_TXD[3-0] O Transmit data (MII_TXD). The transmit data pins are a collection of 4 data signals comprising 4 bits
MII_TXEN O Transmit enable (MII_TXEN). The transmit enable signal indicates that the MII_TXD pins are
MII_COL I Collision detected (MII_COL). In half-duplex operation, the MII_COL pin is asserted by the PHY
MII_CRS I Carrier sense (MII_CRS). In half-duplex operation, the MII_CRS pin is asserted by the PHY when
MII_RXCLK I Receive clock (MII_RXCLK). The receive clock is a continuous clock that provides the timing
MII_RXD[3-0] I Receive data (MII_RXD). The receive data pins are a collection of 4 data signals comprising 4 bits of
MII_RXDV I Receive data valid (MII_RXDV). The receive data valid signal indicates that the MII_RXD pins are
MII_RXER I Receive error (MII_RXER). The receive error signal is asserted for one or more MII_RXCLK periods
reference for transmit operations. The MII_TXD and MII_TXEN signals are tied to this clock. The
clock is generated by the PHY and is 2.5 MHz at 10 Mbps operation and 25 MHz at 100 Mbps
operation.
of data. MTDX0 is the least-significant bit (LSB). The signals are synchronized by MII_TXCLK and
valid only when MII_TXEN is asserted.
generating nibble data for use by the PHY. It is driven synchronously to MII_TXCLK.
when it detects a collision on the network. It remains asserted while the collision condition persists.
This signal is not necessarily synchronous to MII_TXCLK nor MII_RXCLK.
In full-duplex operation, the MII_COL pin is used for hardware transmit flow control. Asserting the
MII_COL pin will stop packet transmissions; packets in the process of being transmitted when
MII_COL is asserted will complete transmission. The MII_COL pin should be held low if hardware
transmit flow control is not used.
the network is not idle in either transmit or receive. The pin is deasserted when both transmit and
receive are idle. This signal is not necessarily synchronous to MII_TXCLK nor MII_RXCLK.
In full-duplex operation, the MII_CRS pin should be held low.
reference for receive operations. The MII_RXD, MII_RXDV, and MII_RXER signals are tied to this
clock. The clock is generated by the PHY and is 2.5 MHz at 10 Mbps operation and 25 MHz at
100 Mbps operation.
data. MRDX0 is the least-significant bit (LSB). The signals are synchronized by MII_RXCLK and
valid only when MII_RXDV is asserted.
generating nibble data for use by the EMAC. It is driven synchronously to MII_RXCLK.
to indicate that an error was detected in the received frame. This is meaningful only during data
reception when MII_RXDV is active.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
15
© 2011, Texas Instruments Incorporated
RMII_TXD[1-0]
RMII_TXEN
RMII_MHZ_50_CLK
RMII_RXD[1-0]
RMII_CRS_DV
RMII_RXER
MDIO_CLK
MDIO_D
MDIO
EMAC
Physical
Layer
Device
(PHY)
Transformer
50MHz
RJ-45
Architecture
Table 1. EMAC and MDIO Signals for MII Interface (continued)
Signal Type Description
MDIO_CLK O Management data clock (MDIO_CLK). The MDIO data clock is sourced by the MDIO module on the
system. It is used to synchronize MDIO data access operations done on the MDIO pin. The
frequency of this clock is controlled by the CLKDIV bits in the MDIO control register (CONTROL).
MDIO_D I/O Management data input output (MDIO_D). The MDIO data pin drives PHY management data into
and out of the PHY by way of an access frame consisting of start of frame, read/write indication,
PHY address, register address, and data bit cycles. The MDIO_D pin acts as an output for all but the
data bit cycles at which time it is an input for read operations.
2.3.2 Reduced Media Independent Interface (RMII) Connections
Figure 3 shows a device with integrated EMAC and MDIO interfaced via a RMII connection in a typical
system.
The individual EMAC and MDIO signals for the RMII interface are summarized in Table 2. For more
information, refer to either the IEEE 802.3 standard or ISO/IEC 8802-3:2000(E).
Figure 3. Ethernet Configuration—RMII Connections
www.ti.com
Table 2. EMAC and MDIO Signals for RMII Interface
Signal Type Description
RMII_TXD[1-0] O Transmit data (RMII_TXD). The transmit data pins are a collection of 2 bits of data. RMTDX0 is
RMII_TXEN O Transmit enable (RMII_TXEN). The transmit enable signal indicates that the RMII_TXD pins are
RMII_MHZ_50_CLK I RMII reference clock (RMII_MHZ_50_CLK). The reference clock is used to synchronize all RMII
RMII_RXD[1-0] I Receive data (RMII_RXD). The receive data pins are a collection of 2 bits of data. RMRDX0 is the
RMII_CRS_DV I Carrier sense/receive data valid (RMII_CRS_DV). Multiplexed signal between carrier sense and
RMII_RXER I Receive error (RMII_RXER). The receive error signal is asserted to indicate that an error was
MDIO_CLK O Management data clock (MDIO_CLK). The MDIO data clock is sourced by the MDIO module on
16
MDIO_D I/O Management data input output (MDIO_D). The MDIO data pin drives PHY management data into
EMAC/MDIO Module SPRUFL5B–April 2011
the least-significant bit (LSB). The signals are synchronized by RMII_MHZ_50_CLK and valid only
when RMII_TXEN is asserted.
generating data for use by the PHY. RMII_TXEN is synchronous to RMII_MHZ_50_CLK.
signals. RMII_MHZ_50_CLK must be continuous and fixed at 50 MHz.
least-significant bit (LSB). The signals are synchronized by RMII_MHZ_50_CLK and valid only
when RMII_CRS_DV is asserted and RMII_RXER is deasserted.
receive data valid.
detected in the received frame.
the system. It is used to synchronize MDIO data access operations done on the MDIO pin. The
frequency of this clock is controlled by the CLKDIV bits in the MDIO control register (CONTROL).
and out of the PHY by way of an access frame consisting of start of frame, read/write indication,
PHY address, register address, and data bit cycles. The MDIO_D pin acts as an output for all but
the data bit cycles at which time it is an input for read operations.
Submit Documentation Feedback
© 2011, Texas Instruments Incorporated
Preamble SFD Destination Source Len Data
7 1 6 6 2 46−1500 4
FCS
Number of bytes
Legend: SFD=Start Frame Delimeter; FCS=Frame Check Sequence (CRC)
www.ti.com
2.4 Ethernet Protocol Overview
A brief overview of the Ethernet protocol is given in the following subsections. See the IEEE 802.3
standard document for in-depth information on the Carrier Sense Multiple Access with Collision Detection
(CSMA/CD) Access Method.
2.4.1 Ethernet Frame Format
All the Ethernet technologies use the same frame structure. The format of an Ethernet frame is shown in
Figure 4 and described in Table 3. The Ethernet packet, which is the collection of bytes representing the
data portion of a single Ethernet frame on the wire, is shown outlined in bold. The Ethernet frames are of
variable lengths, with no frame smaller than 64 bytes or larger than RXMAXLEN bytes (header, data, and
CRC).
Architecture
Figure 4. Ethernet Frame Format
Table 3. Ethernet Frame Description
Field Bytes Description
Preamble 7 Preamble. These 7 bytes have a fixed value of 55h and serve to wake up the receiving
SFD 1 Start of Frame Delimiter. This field with a value of 5Dh immediately follows the preamble
Destination 6 Destination address. This field contains the Ethernet MAC address of the EMAC port for
Source 6 Source address. This field contains the MAC address of the Ethernet port that transmits the
Len 2 Length/Type field. The length field indicates the number of EMAC client data bytes
Data 46 to Data field. This field carries the datagram containing the upper layer protocol frame, that is,
(RXMAXLEN - 18) IP layer datagram. The maximum transfer unit (MTU) of Ethernet is (RXMAXLEN - 18)
FCS 4 Frame Check Sequence. A cyclic redundancy check (CRC) is used by the transmit and
EMAC ports and to synchronize their clocks to that of the sender’s clock.
pattern and indicates the start of important data.
which the frame is intended. It may be an individual or multicast (including broadcast)
address. When the destination EMAC port receives an Ethernet frame with a destination
address that does not match any of its MAC physical addresses, and no promiscuous,
multicast or broadcast channel is enabled, it discards the frame.
frame to the Local Area Network.
contained in the subsequent data field of the frame. This field can also be used to identify
the type of data the frame is carrying.
bytes. This means that if the upper layer protocol datagram exceeds (RXMAXLEN - 18)
bytes, then the host has to fragment the datagram and send it in multiple Ethernet packets.
The minimum size of the data field is 46 bytes. This means that if the upper layer datagram
is less then 46 bytes, the data field has to be extended to 46 bytes by appending extra bits
after the data field, but prior to calculating and appending the FCS.
receive algorithms to generate a CRC value for the FCS field. The frame check sequence
covers the 60 to 1514 bytes of the packet data. Note that this 4-byte field may or may not
be included as part of the packet data, depending on how the EMAC is configured.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
© 2011, Texas Instruments Incorporated
17
Architecture
2.4.2 Ethernet’s Multiple Access Protocol
Nodes in an Ethernet Local Area Network are interconnected by a broadcast channel -- when an EMAC
port transmits a frame, all the adapters on the local network receive the frame. Carrier Sense Multiple
Access with Collision Detection (CSMA/CD) algorithms are used when the EMAC operates in half-duplex
mode. When operating in full-duplex mode, there is no contention for use of a shared medium because
there are exactly two ports on the local network.
Each port runs the CSMA/CD protocol without explicit coordination with the other ports on the Ethernet
network. Within a specific port, the CSMA/CD protocol works as follows:
1. The port obtains data from upper layer protocols at its node, prepares an Ethernet frame, and puts the
frame in a buffer.
2. If the port senses that the medium is idle, it starts to transmit the frame. If the port senses that the
transmission medium is busy, it waits until it no longer senses energy (plus an Inter-Packet Gap time)
and then starts to transmit the frame.
3. While transmitting, the port monitors for the presence of signal energy coming from other ports. If the
port transmits the entire frame without detecting signal energy from other Ethernet devices, the port is
done with the frame.
4. If the port detects signal energy from other ports while transmitting, it stops transmitting its frame and
instead transmits a 48-bit jam signal.
5. After transmitting the jam signal, the port enters an exponential backoff phase. If a data frame
encounters back-to-back collisions, the port chooses a random value that is dependent on the number
of collisions. The port then waits an amount of time that is a multiple of this random value and returns
to step 2.
www.ti.com
2.5 Programming Interface
2.5.1 Packet Buffer Descriptors
The buffer descriptor is a central part of the EMAC module and is how the application software describes
Ethernet packets to be sent and empty buffers to be filled with incoming packet data. The basic descriptor
format is shown in Figure 5 and described in Table 4.
For example, consider three packets to be transmitted: Packet A is a single fragment (60 bytes), Packet B
is fragmented over three buffers (1514 bytes total), and Packet C is a single fragment (1514 bytes). The
linked list of descriptors to describe these three packets is shown in Figure 6.
Word
Offset 31 16 15 0
0 Next Descriptor Pointer
1 Buffer Pointer
2 Buffer Offset Buffer Length
3 Flags Packet Length
Figure 5. Basic Descriptor Format
Bit Fields
18
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
SOP | EOP 60
0 60
pBuffer
pNext
Packet A
60 bytes
0
SOP
Fragment 1
Packet B
512
1514
pBuffer
pNext
512 bytes
EOP
0
0
−−−
Packet B
Fragment 3
500 bytes
502
pBuffer
−−−
500
pNext
−−−
pBuffer
pNext
Packet B
Fragment 2
502 bytes
SOP | EOP
0
1514 bytes
Packet C
1514
pBuffer
pNext (NULL)
1514
www.ti.com
Architecture
Table 4. Basic Descriptor Description
Word Offset Field Field Description
0 Next Descriptor The next descriptor pointer is used to create a single linked list of descriptors. Each descriptor
Pointer describes a packet or a packet fragment. When a descriptor points to a single buffer packet
or the first fragment of a packet, the start of packet (SOP) flag is set in the flags field. When a
descriptor points to a single buffer packet or the last fragment of a packet, the end of packet
(EOP) flag is set. When a packet is fragmented, each fragment must have its own descriptor
and appear sequentially in the descriptor linked list.
1 Buffer Pointer The buffer pointer refers to the actual memory buffer that contains packet data during
transmit operations, or is an empty buffer ready to receive packet data during receive
operations.
2 Buffer Offset The buffer offset is the offset from the start of the packet buffer to the first byte of valid data.
This field only has meaning when the buffer descriptor points to a buffer that actually contains
data.
Buffer Length The buffer length is the actual number of valid packet data bytes stored in the buffer. If the
buffer is empty and waiting to receive data, this field represents the size of the empty buffer.
3 Flags The flags field contains more information about the buffer, such as, is it the first fragment in a
packet (SOP), the last fragment in a packet (EOP), or contains an entire contiguous Ethernet
packet (both SOP and EOP). The flags are described in Section 2.5.4 and Section 2.5.5.
Packet Length The packet length only has meaning for buffers that both contain data and are the start of a
new packet (SOP). In the case of SOP descriptors, the packet length field contains the length
of the entire Ethernet packet, regardless if it is contained in a single buffer or fragmented over
several buffers.
Figure 6. Typical Descriptor Linked List
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
19
© 2011, Texas Instruments Incorporated
Architecture
2.5.2 Transmit and Receive Descriptor Queues
The EMAC module processes descriptors in linked lists as discussed in Section 2.5.1. The lists used by
the EMAC are maintained by the application software through the use of the head descriptor pointer
registers (HDP). The EMAC supports eight channels for transmit and eight channels for receive. The
corresponding head descriptor pointers are:
• TXnHDP - Transmit Channel n DMA Head Descriptor Pointer Register
• RXnHDP - Receive Channel n DMA Head Descriptor Pointer Register
After an EMAC reset and before enabling the EMAC for send and receive, all 16 head descriptor pointer
registers must be initialized to 0.
The EMAC uses a simple system to determine if a descriptor is currently owned by the EMAC or by the
application software. There is a flag in the buffer descriptor flags called OWNER. When this flag is set, the
packet that is referenced by the descriptor is considered to be owned by the EMAC. Note that ownership
is done on a packet based granularity, not on descriptor granularity, so only SOP descriptors make use of
the OWNER flag. As packets are processed, the EMAC patches the SOP descriptor of the corresponding
packet and clears the OWNER flag. This is an indication that the EMAC has finished processing all
descriptors up to and including the first with the EOP flag set, indicating the end of the packet (note this
may only be one descriptor with both the SOP and EOP flags set).
To add a descriptor or a linked list of descriptors to an EMAC descriptor queue for the first time, the
software application simply writes the pointer to the descriptor or first descriptor of a list to the
corresponding HDP register. Note that the last descriptor in the list must have its “next” pointer cleared to
0. This is the only way the EMAC has of detecting the end of the list. Therefore, in the case where only a
single descriptor is added, its “next descriptor” pointer must be initialized to 0.
The HDP must never be written to while a list is active. To add additional descriptors to a descriptor list
already owned by the EMAC, the NULL “next” pointer of the last descriptor of the previous list is patched
with a pointer to the first descriptor of the new list. The list of new descriptors to be appended to the
existing list must itself be NULL terminated before the pointer patch is performed.
There is a potential race condition where the EMAC may read the “next” pointer of a descriptor as NULL in
the instant before an application appends additional descriptors to the list by patching the pointer. This
case is handled by the software application always examining the buffer descriptor flags of all EOP
packets, looking for a special flag called end of queue (EOQ). The EOQ flag is set by the EMAC on the
last descriptor of a packet when the descriptor’s “next” pointer is NULL. This is the way the EMAC
indicates to the software application that it believes it has reached the end of the list. When the software
application sees the EOQ flag set, the application may at that time submit the new list, or the portion of
the appended list that was missed by writing the new list pointer to the same HDP that started the
process.
This process applies when adding packets to a transmit list, and empty buffers to a receive list.
www.ti.com
20
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.5.3 Transmit and Receive EMAC Interrupts
The EMAC processes descriptors in linked list chains as discussed in Section 2.5.1, using the linked list
queue mechanism discussed in Section 2.5.2.
The EMAC synchronizes descriptor list processing through the use of interrupts to the software
application. The interrupts are controlled by the application using the interrupt masks, global interrupt
enable, and the completion pointer register (CP). The CP is also called the interrupt acknowledge register.
The EMAC supports eight channels for transmit and eight channels for receive. The corresponding
completion pointer registers are:
• TXnCP - Transmit Channel n Completion Pointer (Interrupt Acknowledge) Register
• RXnCP - Receive Channel n Completion Pointer (Interrupt Acknowledge) Register
These registers serve two purposes. When read, they return the pointer to the last descriptor that the
EMAC has processed. When written by the software application, the value represents the last descriptor
processed by the software application. When these two values do not match, the interrupt is active.
Interrupts in the EMAC control module are routed to three independent interrupt cores which are then
mapped to CPU interrupt controllers. The system configuration determines whether or not an active
interrupt actually interrupts the CPU. In general the following settings are required for basic EMAC
transmit and receive interrupts:
1. EMAC transmit and receive interrupts are enabled by setting the mask registers RXINTMASKSET and
TXINTMASKSET
2. Global interrupts for the appropriate interrupt core registers are set in the EMAC control module:
CnRXEN and CnTXEN on core n
3. The CPU interrupt controller is configured to accept Cn_RX_PULSE and Cn_TX_PULSE interrupts
from the EMAC control module
Whether or not the interrupt is enabled, the current state of the receive or transmit channel interrupt can
be examined directly by the software application reading the EMAC receive interrupt status (unmasked)
register (RXINTSTATRAW) and transmit interrupt status (unmasked) register (TXINTSTATRAW).
After servicing transmit or receive interrupts, the application software must acknowledge both the EMAC
and EMAC control module interrupts.
EMAC interrupts are acknowledged when the application software updates the value of TXnCP or RXnCP
with a value that matches the internal value kept by the EMAC. This mechanism ensures that the
application software never misses an EMAC interrupt because the interrupt acknowledgment is tied
directly to the buffer descriptor processing.
EMAC control module interrupts are acknowledged when the application software writes the appropriate
CnTX or CnRX key to the EMAC End-Of-Interrupt Vector register (MACEOIVECTOR). The
MACEOIVECTOR behaves as an interrupt pulse interlock -- once the EMAC control module has issued an
interrupt pulse to the CPU, it will not generate further pulses of the same type until the original pulse has
been acknowledged.
Architecture
2.5.4 Transmit Buffer Descriptor Format
A transmit (TX) buffer descriptor (Figure 7) is a contiguous block of four 32-bit data words aligned on a
32-bit boundary that describes a packet or a packet fragment. Example 1 shows the transmit buffer
descriptor described by a C structure.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
21
© 2011, Texas Instruments Incorporated
Architecture
www.ti.com
Figure 7. Transmit Buffer Descriptor Format
Word 0
31 0
Next Descriptor Pointer
Word 1
31 0
Buffer Pointer
Word 2
31 16 15 0
Buffer Offset Buffer Length
Word 3
31 30 29 28 27 26 25 16
SOP EOP OWNER EOQ TDOWNCMPLT PASSCRC Reserved
15 0
Packet Length
Example 1. Transmit Buffer Descriptor in C Structure Format
/*
// EMAC Descriptor
//
// The following is the format of a single buffer descriptor
// on the EMAC.
*/
typedef struct _EMAC_Desc {
struct _EMAC_Desc *pNext; /* Pointer to next descriptor in chain */
Uint8 *pBuffer; /* Pointer to data buffer */
Uint32 BufOffLen; /* Buffer Offset(MSW) and Length(LSW) */
Uint32 PktFlgLen; /* Packet Flags(MSW) and Length(LSW) */
} EMAC_Desc;
/* Packet Flags */
#define EMAC_DSC_FLAG_SOP 0x80000000u
#define EMAC_DSC_FLAG_EOP 0x40000000u
#define EMAC_DSC_FLAG_OWNER 0x20000000u
#define EMAC_DSC_FLAG_EOQ 0x10000000u
#define EMAC_DSC_FLAG_TDOWNCMPLT 0x08000000u
#define EMAC_DSC_FLAG_PASSCRC 0x04000000u
22
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.5.4.1 Next Descriptor Pointer
The next descriptor pointer points to the 32-bit word aligned memory address of the next buffer descriptor
in the transmit queue. This pointer is used to create a linked list of buffer descriptors. If the value of this
pointer is zero, then the current buffer is the last buffer in the queue. The software application must set
this value prior to adding the descriptor to the active transmit list. This pointer is not altered by the EMAC.
The value of pNext should never be altered once the descriptor is in an active transmit queue, unless its
current value is NULL. If the pNext pointer is initially NULL, and more packets need to be queued for
transmit, the software application may alter this pointer to point to a newly appended descriptor. The
EMAC will use the new pointer value and proceed to the next descriptor unless the pNext value has
already been read. In this latter case, the transmitter will halt on the transmit channel in question, and the
software application may restart it at that time. The software can detect this case by checking for an end
of queue (EOQ) condition flag on the updated packet descriptor when it is returned by the EMAC.
2.5.4.2 Buffer Pointer
The buffer pointer is the byte-aligned memory address of the memory buffer associated with the buffer
descriptor. The software application must set this value prior to adding the descriptor to the active transmit
list. This pointer is not altered by the EMAC.
2.5.4.3 Buffer Offset
This 16-bit field indicates how many unused bytes are at the start of the buffer. For example, a value of
0000h indicates that no unused bytes are at the start of the buffer and that valid data begins on the first
byte of the buffer, while a value of 000Fh indicates that the first 15 bytes of the buffer are to be ignored by
the EMAC and that valid buffer data starts on byte 16 of the buffer. The software application must set this
value prior to adding the descriptor to the active transmit list. This field is not altered by the EMAC.
Note that this value is only checked on the first descriptor of a given packet (where the start of packet
(SOP) flag is set). It can not be used to specify the offset of subsequent packet fragments. Also, since the
buffer pointer may point to any byte–aligned address, this field may be entirely superfluous, depending on
the device driver architecture.
The range of legal values for this field is 0 to (Buffer Length – 1).
Architecture
2.5.4.4 Buffer Length
This 16-bit field indicates how many valid data bytes are in the buffer. On single fragment packets, this
value is also the total length of the packet data to be transmitted. If the buffer offset field is used, the offset
bytes are not counted as part of this length. This length counts only valid data bytes. The software
application must set this value prior to adding the descriptor to the active transmit list. This field is not
altered by the EMAC.
2.5.4.5 Packet Length
This 16-bit field specifies the number of data bytes in the entire packet. Any leading buffer offset bytes are
not included. The sum of the buffer length fields of each of the packet’s fragments (if more than one) must
be equal to the packet length. The software application must set this value prior to adding the descriptor to
the active transmit list. This field is not altered by the EMAC. This value is only checked on the first
descriptor of a given packet (where the start of packet (SOP) flag is set).
2.5.4.6 Start of Packet (SOP) Flag
When set, this flag indicates that the descriptor points to a packet buffer that is the start of a new packet.
In the case of a single fragment packet, both the SOP and end of packet (EOP) flags are set. Otherwise,
the descriptor pointing to the last packet buffer for the packet sets the EOP flag. This bit is set by the
software application and is not altered by the EMAC.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
23
© 2011, Texas Instruments Incorporated
Architecture
2.5.4.7 End of Packet (EOP) Flag
When set, this flag indicates that the descriptor points to a packet buffer that is last for a given packet. In
the case of a single fragment packet, both the start of packet (SOP) and EOP flags are set. Otherwise, the
descriptor pointing to the last packet buffer for the packet sets the EOP flag. This bit is set by the software
application and is not altered by the EMAC.
2.5.4.8 Ownership (OWNER) Flag
When set, this flag indicates that all the descriptors for the given packet (from SOP to EOP) are currently
owned by the EMAC. This flag is set by the software application on the SOP packet descriptor before
adding the descriptor to the transmit descriptor queue. For a single fragment packet, the SOP, EOP, and
OWNER flags are all set. The OWNER flag is cleared by the EMAC once it is finished with all the
descriptors for the given packet. Note that this flag is valid on SOP descriptors only.
2.5.4.9 End of Queue (EOQ) Flag
When set, this flag indicates that the descriptor in question was the last descriptor in the transmit queue
for a given transmit channel, and that the transmitter has halted. This flag is initially cleared by the
software application prior to adding the descriptor to the transmit queue. This bit is set by the EMAC when
the EMAC identifies that a descriptor is the last for a given packet (the EOP flag is set), and there are no
more descriptors in the transmit list (next descriptor pointer is NULL).
The software application can use this bit to detect when the EMAC transmitter for the corresponding
channel has halted. This is useful when the application appends additional packet descriptors to a transmit
queue list that is already owned by the EMAC. Note that this flag is valid on EOP descriptors only.
www.ti.com
2.5.4.10 Teardown Complete (TDOWNCMPLT) Flag
This flag is used when a transmit queue is being torn down, or aborted, instead of allowing it to be
transmitted. This would happen under device driver reset or shutdown conditions. The EMAC sets this bit
in the SOP descriptor of each packet as it is aborted from transmission.
Note that this flag is valid on SOP descriptors only. Also note that only the first packet in an unsent list has
the TDOWNCMPLT flag set. Subsequent descriptors are not processed by the EMAC.
2.5.4.11 Pass CRC (PASSCRC) Flag
This flag is set by the software application in the SOP packet descriptor before it adds the descriptor to the
transmit queue. Setting this bit indicates to the EMAC that the 4 byte Ethernet CRC is already present in
the packet data, and that the EMAC should not generate its own version of the CRC.
When the CRC flag is cleared, the EMAC generates and appends the 4-byte CRC. The buffer length and
packet length fields do not include the CRC bytes. When the CRC flag is set, the 4-byte CRC is supplied
by the software application and is already appended to the end of the packet data. The buffer length and
packet length fields include the CRC bytes, as they are part of the valid packet data. Note that this flag is
valid on SOP descriptors only.
24
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.5.5 Receive Buffer Descriptor Format
A receive (RX) buffer descriptor (Figure 8) is a contiguous block of four 32-bit data words aligned on a
32-bit boundary that describes a packet or a packet fragment. Example 2 shows the receive buffer
descriptor described by a C structure.
2.5.5.1 Next Descriptor Pointer
This pointer points to the 32–bit word aligned memory address of the next buffer descriptor in the receive
queue. This pointer is used to create a linked list of buffer descriptors. If the value of this pointer is zero,
then the current buffer is the last buffer in the queue. The software application must set this value prior to
adding the descriptor to the active receive list. This pointer is not altered by the EMAC.
The value of pNext should never be altered once the descriptor is in an active receive queue, unless its
current value is NULL. If the pNext pointer is initially NULL, and more empty buffers can be added to the
pool, the software application may alter this pointer to point to a newly appended descriptor. The EMAC
will use the new pointer value and proceed to the next descriptor unless the pNext value has already been
read. In this latter case, the receiver will halt the receive channel in question, and the software application
may restart it at that time. The software can detect this case by checking for an end of queue (EOQ)
condition flag on the updated packet descriptor when it is returned by the EMAC.
2.5.5.2 Buffer Pointer
The buffer pointer is the byte-aligned memory address of the memory buffer associated with the buffer
descriptor. The software application must set this value prior to adding the descriptor to the active receive
list. This pointer is not altered by the EMAC.
Architecture
Figure 8. Receive Buffer Descriptor Format
Word 0
31 0
Next Descriptor Pointer
Word 1
31 0
Buffer Pointer
Word 2
31 16 15 0
Buffer Offset Buffer Length
Word 3
31 30 29 28 27 26 25 24
SOP EOP OWNER EOQ TDOWNCMPLT PASSCRC JABBER OVERSIZE
23 22 21 20 19 18 17 16
FRAGMENT UNDERSIZED CONTROL OVERRUN CODEERROR ALIGNERROR CRCERROR NOMATCH
15 0
Packet Length
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
25
© 2011, Texas Instruments Incorporated
Architecture
Example 2. Receive Buffer Descriptor in C Structure Format
/*
// EMAC Descriptor
//
// The following is the format of a single buffer descriptor
// on the EMAC.
*/
typedef struct _EMAC_Desc {
struct _EMAC_Desc *pNext; /* Pointer to next descriptor in chain */
Uint8 *pBuffer; /* Pointer to data buffer */
Uint32 BufOffLen; /* Buffer Offset(MSW) and Length(LSW) */
Uint32 PktFlgLen; /* Packet Flags(MSW) and Length(LSW) */
} EMAC_Desc;
/* Packet Flags */
#define EMAC_DSC_FLAG_SOP 0x80000000u
#define EMAC_DSC_FLAG_EOP 0x40000000u
#define EMAC_DSC_FLAG_OWNER 0x20000000u
#define EMAC_DSC_FLAG_EOQ 0x10000000u
#define EMAC_DSC_FLAG_TDOWNCMPLT 0x08000000u
#define EMAC_DSC_FLAG_PASSCRC 0x04000000u
#define EMAC_DSC_FLAG_JABBER 0x02000000u
#define EMAC_DSC_FLAG_OVERSIZE 0x01000000u
#define EMAC_DSC_FLAG_FRAGMENT 0x00800000u
#define EMAC_DSC_FLAG_UNDERSIZED 0x00400000u
#define EMAC_DSC_FLAG_CONTROL 0x00200000u
#define EMAC_DSC_FLAG_OVERRUN 0x00100000u
#define EMAC_DSC_FLAG_CODEERROR 0x00080000u
#define EMAC_DSC_FLAG_ALIGNERROR 0x00040000u
#define EMAC_DSC_FLAG_CRCERROR 0x00020000u
#define EMAC_DSC_FLAG_NOMATCH 0x00010000u
www.ti.com
2.5.5.3 Buffer Offset
This 16-bit field must be initialized to zero by the software application before adding the descriptor to a
receive queue.
Whether or not this field is updated depends on the setting of the RXBUFFEROFFSET register. When the
offset register is set to a non-zero value, the received packet is written to the packet buffer at an offset
given by the value of the register, and this value is also written to the buffer offset field of the descriptor.
When a packet is fragmented over multiple buffers because it does not fit in the first buffer supplied, the
buffer offset only applies to the first buffer in the list, which is where the start of packet (SOP) flag is set in
the corresponding buffer descriptor. In other words, the buffer offset field is only updated by the EMAC on
SOP descriptors.
The range of legal values for the BUFFEROFFSET register is 0 to (Buffer Length – 1) for the smallest
value of buffer length for all descriptors in the list.
26
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.5.5.4 Buffer Length
This 16-bit field is used for two purposes:
• Before the descriptor is first placed on the receive queue by the application software, the buffer length
field is first initialized by the software to have the physical size of the empty data buffer pointed to by
the buffer pointer field.
• After the empty buffer has been processed by the EMAC and filled with received data bytes, the buffer
length field is updated by the EMAC to reflect the actual number of valid data bytes written to the
buffer.
2.5.5.5 Packet Length
This 16-bit field specifies the number of data bytes in the entire packet. This value is initialized to zero by
the software application for empty packet buffers. The value is filled in by the EMAC on the first buffer
used for a given packet. This is signified by the EMAC setting a start of packet (SOP) flag. The packet
length is set by the EMAC on all SOP buffer descriptors.
2.5.5.6 Start of Packet (SOP) Flag
When set, this flag indicates that the descriptor points to a packet buffer that is the start of a new packet.
In the case of a single fragment packet, both the SOP and end of packet (EOP) flags are set. Otherwise,
the descriptor pointing to the last packet buffer for the packet has the EOP flag set. This flag is initially
cleared by the software application before adding the descriptor to the receive queue. This bit is set by the
EMAC on SOP descriptors.
Architecture
2.5.5.7 End of Packet (EOP) Flag
When set, this flag indicates that the descriptor points to a packet buffer that is last for a given packet. In
the case of a single fragment packet, both the start of packet (SOP) and EOP flags are set. Otherwise, the
descriptor pointing to the last packet buffer for the packet has the EOP flag set. This flag is initially cleared
by the software application before adding the descriptor to the receive queue. This bit is set by the EMAC
on EOP descriptors.
2.5.5.8 Ownership (OWNER) Flag
When set, this flag indicates that the descriptor is currently owned by the EMAC. This flag is set by the
software application before adding the descriptor to the receive descriptor queue. This flag is cleared by
the EMAC once it is finished with a given set of descriptors, associated with a received packet. The flag is
updated by the EMAC on SOP descriptor only. So when the application identifies that the OWNER flag is
cleared on an SOP descriptor, it may assume that all descriptors up to and including the first with the EOP
flag set have been released by the EMAC. (Note that in the case of single buffer packets, the same
descriptor will have both the SOP and EOP flags set.)
2.5.5.9 End of Queue (EOQ) Flag
When set, this flag indicates that the descriptor in question was the last descriptor in the receive queue for
a given receive channel, and that the corresponding receiver channel has halted. This flag is initially
cleared by the software application prior to adding the descriptor to the receive queue. This bit is set by
the EMAC when the EMAC identifies that a descriptor is the last for a given packet received (also sets the
EOP flag), and there are no more descriptors in the receive list (next descriptor pointer is NULL).
The software application can use this bit to detect when the EMAC receiver for the corresponding channel
has halted. This is useful when the application appends additional free buffer descriptors to an active
receive queue. Note that this flag is valid on EOP descriptors only.
2.5.5.10 Teardown Complete (TDOWNCMPLT) Flag
This flag is used when a receive queue is being torn down, or aborted, instead of being filled with received
data. This would happen under device driver reset or shutdown conditions. The EMAC sets this bit in the
descriptor of the first free buffer when the tear down occurs. No additional queue processing is performed.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
27
© 2011, Texas Instruments Incorporated
Architecture
2.5.5.11 Pass CRC (PASSCRC) Flag
This flag is set by the EMAC in the SOP buffer descriptor if the received packet includes the 4-byte CRC.
This flag should be cleared by the software application before submitting the descriptor to the receive
queue.
2.5.5.12 Jabber Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet is a jabber frame and was
not discarded because the RXCEFEN bit was set in the RXMBPENABLE. Jabber frames are frames that
exceed the RXMAXLEN in length, and have CRC, code, or alignment errors.
2.5.5.13 Oversize Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet is an oversized frame and
was not discarded because the RXCEFEN bit was set in the RXMBPENABLE.
2.5.5.14 Fragment Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet is only a packet fragment
and was not discarded because the RXCEFEN bit was set in the RXMBPENABLE.
2.5.5.15 Undersized Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet is undersized and was
not discarded because the RXCSFEN bit was set in the RXMBPENABLE.
www.ti.com
2.5.5.16 Control Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet is an EMAC control frame
and was not discarded because the RXCMFEN bit was set in the RXMBPENABLE.
2.5.5.17 Overrun Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet was aborted due to a
receive overrun.
2.5.5.18 Code Error (CODEERROR) Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet contained a code error
and was not discarded because the RXCEFEN bit was set in the RXMBPENABLE.
2.5.5.19 Alignment Error (ALIGNERROR) Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet contained an alignment
error and was not discarded because the RXCEFEN bit was set in the RXMBPENABLE.
2.5.5.20 CRC Error (CRCERROR) Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet contained a CRC error
and was not discarded because the RXCEFEN bit was set in the RXMBPENABLE.
2.5.5.21 No Match (NOMATCH) Flag
This flag is set by the EMAC in the SOP buffer descriptor, if the received packet did not pass any of the
EMAC’s address match criteria and was not discarded because the RXCAFEN bit was set in the
RXMBPENABLE. Although the packet is a valid Ethernet data packet, it was only received because the
EMAC is in promiscuous mode.
28
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
Arbiter and
bus switches
CPU
DMA Controllers
8K byte
descriptor
memory
Configuration
registers
Interrupt
logic
Interrupts
to CPU
EMAC interrupts
MDIO interrupts
Configuration bus
Transmit and Receive
www.ti.com
2.6 EMAC Control Module
The EMAC control module (Figure 9) interfaces the EMAC and MDIO modules to the rest of the system,
and also provides a local memory space to hold EMAC packet buffer descriptors. Local memory is used to
help avoid contention with device memory spaces. Other functions include the bus arbiter, and interrupt
logic control.
Architecture
Figure 9. EMAC Control Module Block Diagram
2.6.1 Internal Memory
2.6.2 Bus Arbiter
The EMAC control module includes 8K bytes of internal memory (CPPI buffer descriptor memory). The
internal memory block is essential for allowing the EMAC to operate more independently of the CPU. It
also prevents memory underflow conditions when the EMAC issues read or write requests to descriptor
memory. (Memory accesses to read or write the actual Ethernet packet data are protected by the EMAC's
internal FIFOs).
A descriptor is a 16-byte memory structure that holds information about a single Ethernet packet buffer,
which may contain a full or partial Ethernet packet. Thus with the 8K memory block provided for descriptor
storage, the EMAC module can send and received up to a combined 512 packets before it needs to be
serviced by application or driver software.
The EMAC control module bus arbiter operates transparently to the rest of the system. It is used:
• To arbitrate between the CPU and EMAC buses for access to internal descriptor memory.
• To arbitrate between internal EMAC buses for access to system memory.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
© 2011, Texas Instruments Incorporated
29
Architecture
2.6.3 Interrupt Control
Interrupt conditions generated by the EMAC and MDIO modules are combined into four interrupt signals
that are routed to three independent interrupt cores in the EMAC control module; the interrupt cores then
relay the interrupt signals to the CPU interrupt controller. The EMAC control module uses two sets of
registers to control the interrupt signals to the CPU:
• CnRXTHRESHEN, CnRXEN, CnTXEN, and CnMISCEN registers enable the interrupt core pulse
signals that are mapped to the CPU interrupt controller
• INTCONTROL, CnRXIMAX, and CnTXIMAX registers enable interrupt pacing to limit the number of
interrupt pulses generated per millisecond
Interrupts must be acknowledged by writing the appropriate value to the EMAC End-Of-Interrupt Vector
(MACEOIVECTOR). The MACEOIVECTOR behaves as an interrupt pulse interlock -- once the EMAC
control module has issued an interrupt pulse to the CPU, it will not generate further pulses of the same
type until the original pulse has been acknowledged.
2.7 MDIO Module
The MDIO module is used to manage up to 32 physical layer (PHY) devices connected to the Ethernet
Media Access Controller (EMAC). The device supports a single PHY being connected to the EMAC at any
given time. The MDIO module is designed to allow almost transparent operation of the MDIO interface
with little maintenance from the CPU.
The MDIO module continuously polls 32 MDIO addresses in order to enumerate all PHY devices in the
system. Once a PHY device has been detected, the MDIO module reads the MDIO PHY link status
register (LINK) to monitor the PHY link state. Link change events are stored in the MDIO module, which
can interrupt the CPU. This storing of the events allows the CPU to poll the link status of the PHY device
without continuously performing MDIO module accesses. However, when the CPU must access the MDIO
module for configuration and negotiation, the MDIO module performs the MDIO read or write operation
independent of the CPU. This independent operation allows the processor to poll for completion or
interrupt the CPU once the operation has completed.
The MDIO module does not support the "Clause 45" interface.
www.ti.com
2.7.1 MDIO Module Components
The MDIO module (Figure 10) interfaces to the PHY components through two MDIO pins (MDIO_CLK and
MDIO), and to the CPU through the EMAC control module and the configuration bus. The MDIO module
consists of the following logical components:
• MDIO clock generator
• Global PHY detection and link state monitoring
• Active PHY monitoring
• PHY register user access
30
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
EMAC
control
module
Control
registers
and logic
PHY
monitoring
Peripheral
clock
MDIO
clock
generator
USERINT
MDIO
interface
polling
PHY
MDCLK
MDIO
LINKINT
Configuration bus
www.ti.com
2.7.1.1 MDIO Clock Generator
The MDIO clock generator controls the MDIO clock based on a divide-down of the peripheral clock in the
EMAC control module. The MDIO clock is specified to run up to 2.5 MHz, although typical operation would
be 1.0 MHz. Since the peripheral clock frequency is variable, the application software or driver controls the
divide-down amount. See your device-specific data manual for peripheral clock speeds.
Architecture
Figure 10. MDIO Module Block Diagram
2.7.1.2 Global PHY Detection and Link State Monitoring
The MDIO module continuously polls all 32 MDIO addresses in order to enumerate the PHY devices in the
system. The module tracks whether or not a PHY on a particular address has responded, and whether or
not the PHY currently has a link. Using this information allows the software application to quickly
determine which MDIO address the PHY is using.
2.7.1.3 Active PHY Monitoring
Once a PHY candidate has been selected for use, the MDIO module transparently monitors its link state
by reading the MDIO PHY link status register (LINK). Link change events are stored on the MDIO device
and can optionally interrupt the CPU. This allows the system to poll the link status of the PHY device
without continuously performing costly MDIO accesses.
2.7.1.4 PHY Register User Access
When the CPU must access MDIO for configuration and negotiation, the PHY access module performs
the actual MDIO read or write operation independent of the CPU. This allows the CPU to poll for
completion or receive an interrupt when the read or write operation has been performed. The user access
registers USERACCESSn allows the software to submit the access requests for the PHY connected to the
device.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
31
© 2011, Texas Instruments Incorporated
Architecture
2.7.2 MDIO Module Operational Overview
The MDIO module implements the 802.3 serial management interface to interrogate and control an
Ethernet PHY, using a shared two-wired bus. It separately performs autodetection and records the current
link status of up to 32 PHYs, polling all 32 MDIO addresses.
Application software uses the MDIO module to configure the autonegotiation parameters of the PHY
attached to the EMAC, retrieve the negotiation results, and configure required parameters in the EMAC.
In this device, the Ethernet PHY attached to the system can be directly controlled and queried. The Media
Independent Interface (MII) address of this PHY device is specified in one of the PHYADRMON bits in the
MDIO user PHY select register (USERPHYSELn). The MDIO module can be programmed to trigger a
CPU interrupt on a PHY link change event, by setting the LINKINTENB bit in USERPHYSELn. Reads and
writes to registers in this PHY device are performed using the MDIO user access register
(USERACCESSn).
The MDIO module powers-up in an idle state until specifically enabled by setting the ENABLE bit in the
MDIO control register (CONTROL). At this time, the MDIO clock divider and preamble mode selection are
also configured. The MDIO preamble is enabled by default, but can be disabled when the connected PHY
does not require it. Once the MDIO module is enabled, the MDIO interface state machine continuously
polls the PHY link status (by reading the generic status register) of all possible 32 PHY addresses and
records the results in the MDIO PHY alive status register (ALIVE) and MDIO PHY link status register
(LINK). The corresponding bit for the connected PHY (0-31) is set in ALIVE, if the PHY responded to the
read request. The corresponding bit is set in LINK, if the PHY responded and also is currently linked. In
addition, any PHY register read transactions initiated by the application software using USERACCESSn
causes ALIVE to be updated.
The USERPHYSELn is used to track the link status of the connected PHY address. A change in the link
status of the PHY being monitored sets the appropriate bit in the MDIO link status change interrupt
registers (LINKINTRAW and LINKINTMASKED), if enabled by the LINKINTENB bit in USERPHYSELn.
While the MDIO module is enabled, the host issues a read or write transaction over the MII management
interface using the DATA, PHYADR, REGADR, and WRITE bits in USERACCESSn. When the application
sets the GO bit in USERACCESSn, the MDIO module begins the transaction without any further
intervention from the CPU. Upon completion, the MDIO module clears the GO bit and sets the
corresponding USERINTRAW bit (0 or 1) in the MDIO user command complete interrupt register
(USERINTRAW) corresponding to USERACCESSn used. The corresponding USERINTMASKED bit (0 or
1) in the MDIO user command complete interrupt register (USERINTMASKED) may also be set,
depending on the mask setting configured in the MDIO user command complete interrupt mask set
register (USERINTMASKSET) and the MDIO user interrupt mask clear register (USERINTMASKCLEAR).
A round-robin arbitration scheme is used to schedule transactions that may be queued using both
USERACCESS0 and USERACCESS1. The application software must check the status of the GO bit in
USERACCESSn before initiating a new transaction, to ensure that the previous transaction has
completed. The application software can use the ACK bit in USERACCESSn to determine the status of a
read transaction.
www.ti.com
32
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.7.2.1 Initializing the MDIO Module
The following steps are performed by the application software or device driver to initialize the MDIO
device:
1. Configure the PREAMBLE and CLKDIV bits in the MDIO control register (CONTROL).
2. Enable the MDIO module by setting the ENABLE bit in CONTROL.
3. The MDIO PHY alive status register (ALIVE) can be read in polling fashion until a PHY connected to
the system responded, and the MDIO PHY link status register (LINK) can determine whether this PHY
already has a link.
4. Setup the appropriate PHY addresses in the MDIO user PHY select register (USERPHYSELn), and set
the LINKINTENB bit to enable a link change event interrupt if desirable.
5. If an interrupt on general MDIO register access is desired, set the corresponding bit in the MDIO user
command complete interrupt mask set register (USERINTMASKSET) to use the MDIO user access
register (USERACCESSn). Since only one PHY is used in this device, the application software can use
one USERACCESSn to trigger a completion interrupt; the other USERACCESSn is not setup.
2.7.2.2 Writing Data To a PHY Register
The MDIO module includes a user access register (USERACCESSn) to directly access a specified PHY
device. To write a PHY register, perform the following:
1. Check to ensure that the GO bit in the MDIO user access register (USERACCESSn) is cleared.
2. Write to the GO, WRITE, REGADR, PHYADR, and DATA bits in USERACCESSn corresponding to the
PHY and PHY register you want to write.
3. The write operation to the PHY is scheduled and completed by the MDIO module. Completion of the
write operation can be determined by polling the GO bit in USERACCESSn for a 0.
4. Completion of the operation sets the corresponding USERINTRAW bit (0 or 1) in the MDIO user
command complete interrupt register (USERINTRAW) corresponding to USERACCESSn used. If
interrupts have been enabled on this bit using the MDIO user command complete interrupt mask set
register (USERINTMASKSET), then the bit is also set in the MDIO user command complete interrupt
register (USERINTMASKED) and an interrupt is triggered on the CPU.
Architecture
2.7.2.3 Reading Data From a PHY Register
The MDIO module includes a user access register (USERACCESSn) to directly access a specified PHY
device. To read a PHY register, perform the following:
1. Check to ensure that the GO bit in the MDIO user access register (USERACCESSn) is cleared.
2. Write to the GO, REGADR, and PHYADR bits in USERACCESSn corresponding to the PHY and PHY
register you want to read.
3. The read data value is available in the DATA bits in USERACCESSn after the module completes the
read operation on the serial bus. Completion of the read operation can be determined by polling the
GO and ACK bits in USERACCESSn. Once the GO bit has cleared, the ACK bit is set on a successful
read.
4. Completion of the operation sets the corresponding USERINTRAW bit (0 or 1) in the MDIO user
command complete interrupt register (USERINTRAW) corresponding to USERACCESSn used. If
interrupts have been enabled on this bit using the MDIO user command complete interrupt mask set
register (USERINTMASKSET), then the bit is also set in the MDIO user command complete interrupt
register (USERINTMASKED) and an interrupt is triggered on the CPU.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
33
© 2011, Texas Instruments Incorporated
Architecture
2.7.2.4 Example of MDIO Register Access Code
The MDIO module uses the MDIO user access register (USERACCESSn) to access the PHY control
registers. Software functions that implement the access process may simply be the following four macros:
• PHYREG_read( regadr, phyadr ) Start the process of reading a PHY register
• PHYREG_write( regadr, phyadr, data ) Start the process of writing a PHY register
• PHYREG_wait( ) Synchronize operation (make sure read/write is idle)
• PHYREG_waitResults( results ) Wait for read to complete and return data read
Note that it is not necessary to wait after a write operation, as long as the status is checked before every
operation to make sure the MDIO hardware is idle. An alternative approach is to call PHYREG_wait() after
every write, and PHYREG_waitResults( ) after every read, then the hardware can be assumed to be idle
when starting a new operation.
The implementation of these macros using the chip support library (CSL) is shown in Example 3
(USERACCESS0 is assumed).
Note that this implementation does not check the ACK bit in USERACCESSn on PHY register reads (does
not follow the procedure outlined in Section 2.7.2.3). Since the MDIO PHY alive status register (ALIVE) is
used to initially select a PHY, it is assumed that the PHY is acknowledging read operations. It is possible
that a PHY could become inactive at a future point in time. An example of this would be a PHY that can
have its MDIO addresses changed while the system is running. It is not very likely, but this condition can
be tested by periodically checking the PHY state in ALIVE.
www.ti.com
Example 3. MDIO Register Access Macros
#define PHYREG_read(regadr, phyadr)
MDIO_REGS->USERACCESS0 =
CSL_FMK(MDIO_USERACCESS0_GO,1u) | /
CSL_FMK(MDIO_USERACCESS0_REGADR,regadr) | /
#define PHYREG_write(regadr, phyadr, data)
#define PHYREG_wait()
#define PHYREG_waitResults( results ) {
results = CSL_FEXT(MDIO_REGS->USERACCESS0, MDIO_USERACCESS0_DATA); }
CSL_FMK(MDIO_USERACCESS0_PHYADR,phyadr)
MDIO_REGS->USERACCESS0 =
CSL_FMK(MDIO_USERACCESS0_GO,1u) | /
CSL_FMK(MDIO_USERACCESS0_WRITE,1) | /
CSL_FMK(MDIO_USERACCESS0_REGADR,regadr) | /
CSL_FMK(MDIO_USERACCESS0_PHYADR,phyadr) | /
CSL_FMK(MDIO_USERACCESS0_DATA, data)
while( CSL_FEXT(MDIO_REGS->USERACCESS0,MDIO_USERACCESS0_GO) )
while( CSL_FEXT(MDIO_REGS->USERACCESS0,MDIO_USERACCESS0_GO) );
34
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
Clock and
reset logic
Receive
DMA engine
Interrupt
controller
Transmit
DMA engine
Control
registers
Configuration bus
EMAC
control
module
Configuration bus
RAM
State
FIFO
Receive
FIFO
Transmit MAC
transmitter
Statistics
receiver
MAC
SYNC
MII
address
Receive
RMII
www.ti.com
2.8 EMAC Module
This section discusses the architecture and basic function of the EMAC module.
2.8.1 EMAC Module Components
The EMAC module (Figure 11) interfaces to the outside world through the Media Independent Interface
(MII) and/or Reduced Media Independent Interface (RMII). The interface between the EMAC module and
the system core is provided through the EMAC control module. The EMAC consists of the following logical
components:
• The receive path includes: receive DMA engine, receive FIFO, and MAC receiver
• The transmit path includes: transmit DMA engine, transmit FIFO, and MAC transmitter
• Statistics logic
• State RAM
• Interrupt controller
• Control registers and logic
• Clock and reset logic
Figure 11. EMAC Module Block Diagram
Architecture
2.8.1.1 Receive DMA Engine
The receive DMA engine is the interface between the receive FIFO and the system core. It interfaces to
the CPU through the bus arbiter in the EMAC control module. This DMA engine is totally independent of
the device DMA.
2.8.1.2 Receive FIFO
The receive FIFO consists of three cells of 64-bytes each and associated control logic. The FIFO buffers
receive data in preparation for writing into packet buffers in device memory.
2.8.1.3 MAC Receiver
The MAC receiver detects and processes incoming network frames, de-frames them, and puts them into
the receive FIFO. The MAC receiver also detects errors and passes statistics to the statistics RAM.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
© 2011, Texas Instruments Incorporated
35
Architecture
2.8.1.4 Transmit DMA Engine
The transmit DMA engine is the interface between the transmit FIFO and the CPU. It interfaces to the
CPU through the bus arbiter in the EMAC control module.
2.8.1.5 Transmit FIFO
The transmit FIFO consists of three cells of 64-bytes each and associated control logic. The FIFO buffers
data in preparation for transmission.
2.8.1.6 MAC Transmitter
The MAC transmitter formats frame data from the transmit FIFO and transmits the data using the
CSMA/CD access protocol. The frame CRC can be automatically appended, if required. The MAC
transmitter also detects transmission errors and passes statistics to the statistics registers.
2.8.1.7 Statistics Logic
The Ethernet statistics are counted and stored in the statistics logic RAM. This statistics RAM keeps track
of 36 different Ethernet packet statistics.
2.8.1.8 State RAM
State RAM contains the head descriptor pointers and completion pointers registers for both transmit and
receive channels.
www.ti.com
2.8.1.9 EMAC Interrupt Controller
The interrupt controller contains the interrupt related registers and logic. The 26 raw EMAC interrupts are
input to this submodule and masked module interrupts are output.
2.8.1.10 Control Registers and Logic
The EMAC is controlled by a set of memory-mapped registers. The control logic also signals transmit,
receive, and status related interrupts to the CPU through the EMAC control module.
2.8.1.11 Clock and Reset Logic
The clock and reset submodule generates all the EMAC clocks and resets. For more details on reset
capabilities, see Section 2.14.1.
2.8.2 EMAC Module Operational Overview
After reset, initialization, and configuration, the host may initiate transmit operations. Transmit operations
are initiated by host writes to the appropriate transmit channel head descriptor pointer contained in the
state RAM block. The transmit DMA controller then fetches the first packet in the packet chain from
memory. The DMA controller writes the packet into the transmit FIFO in bursts of 64-byte cells. When the
threshold number of cells, configurable using the TXCELLTHRESH bit in the FIFO control register
(FIFOCONTROL), have been written to the transmit FIFO, or a complete packet, whichever is smaller, the
MAC transmitter then initiates the packet transmission. The SYNC block transmits the packet over the MII
or RMII interfaces in accordance with the 802.3 protocol. Transmit statistics are counted by the statistics
block.
Receive operations are initiated by host writes to the appropriate receive channel head descriptor pointer
after host initialization and configuration. The SYNC submodule receives packets and strips off the
Ethernet related protocol. The packet data is input to the MAC receiver, which checks for address match
and processes errors. Accepted packets are then written to the receive FIFO in bursts of 64-byte cells.
The receive DMA controller then writes the packet data to memory. Receive statistics are counted by the
statistics block.
36
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
The EMAC module operates independently of the CPU. It is configured and controlled by its register set
mapped into device memory. Information about data packets is communicated by use of 16-byte
descriptors that are placed in an 8K-byte block of RAM in the EMAC control module (CPPI buffer
descriptor memory).
For transmit operations, each 16-byte descriptor describes a packet or packet fragment in the system's
internal or external memory. For receive operations, each 16-byte descriptor represents a free packet
buffer or buffer fragment. On both transmit and receive, an Ethernet packet is allowed to span one or
more memory fragments, represented by one 16-byte descriptor per fragment. In typical operation, there is
only one descriptor per receive buffer, but transmit packets may be fragmented, depending on the
software architecture.
An interrupt is issued to the CPU whenever a transmit or receive operation has completed. However, it is
not necessary for the CPU to service the interrupt while there are additional resources available. In other
words, the EMAC continues to receive Ethernet packets until its receive descriptor list has been
exhausted. On transmit operations, the transmit descriptors need only be serviced to recover their
associated memory buffer. Thus, it is possible to delay servicing of the EMAC interrupt if there are
real-time tasks to perform.
Eight channels are supplied for both transmit and receive operations. On transmit, the eight channels
represent eight independent transmit queues. The EMAC can be configured to treat these channels as an
equal priority "round-robin" queue or as a set of eight fixed-priority queues. On receive, the eight channels
represent eight independent receive queues with packet classification. Packets are classified based on the
destination MAC address. Each of the eight channels is assigned its own MAC address, enabling the
EMAC module to act like eight virtual MAC adapters. Also, specific types of frames can be sent to specific
channels. For example, multicast, broadcast, or other (promiscuous, error, etc.), can each be received on
a specific receive channel queue.
The EMAC keeps track of 36 different statistics, plus keeps the status of each individual packet in its
corresponding packet descriptor.
Architecture
2.9 MAC Interface
The following sections discuss the operation of the Media Independent Interface (MII) and Reduced Media
Independent Interface (RMII) in 10 Mbps and 100 Mbps mode. An IEEE 802.3 compliant Ethernet MAC
controls the interface.
2.9.1 Data Reception
2.9.1.1 Receive Control
Data received from the PHY is interpreted and output to the EMAC receive FIFO. Interpretation involves
detection and removal of the preamble and start-of-frame delimiter, extraction of the address and frame
length, data handling, error checking and reporting, cyclic redundancy checking (CRC), and statistics
control signal generation. Address detection and frame filtering is performed outside the MAC interface.
2.9.1.2 Receive Inter-Frame Interval
The 802.3 standard requires an interpacket gap (IPG), which is 96 bit times. However, the EMAC can
tolerate a reduced IPG of 8 bit times with a correct preamble and start frame delimiter. This interval
between frames must comprise (in the following order):
1. An Interpacket Gap (IPG).
2. A 7-byte preamble (all bytes 55h).
3. A 1-byte start of frame delimiter (5Dh).
2.9.1.3 Receive Flow Control
When enabled and triggered, receive flow control is initiated to limit the EMAC from further frame
reception. Two forms of receive buffer flow control are available:
• Collision-based flow control for half-duplex mode
• IEEE 802.3x pause frames flow control for full-duplex mode
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
37
© 2011, Texas Instruments Incorporated
Architecture
In either case, receive flow control prevents frame reception by issuing the flow control appropriate for the
current mode of operation. Receive flow control prevents reception of frames on the EMAC until all of the
triggering conditions clear, at which time frames may again be received by the EMAC.
Receive flow control is enabled by the RXBUFFERFLOWEN bit in the MAC control register
(MACCONTROL). The EMAC is configured for collision or IEEE 802.3X flow control using the
FULLDUPLEX bit in MACCONTROL. Receive flow control is triggered when the number of free buffers in
any enabled receive channel free buffer count register (RXnFREEBUFFER) is less than or equal to the
receive channel flow control threshold register (RXnFLOWTHRESH) value. Receive flow control is
independent of receive QOS, except that both use the free buffer values.
2.9.1.3.1 Collision-Based Receive Buffer Flow Control
Collision-based receive buffer flow control provides a means of preventing frame reception when the
EMAC is operating in half-duplex mode (the FULLDUPLEX bit is cleared in MACCONTROL). When
receive flow control is enabled and triggered, the EMAC generates collisions for received frames. The jam
sequence transmitted is the 12-byte sequence C3.C3.C3.C3.C3.C3.C3.C3.C3.C3.C3.C3h. The jam
sequence begins no later than approximately as the source address starts to be received. Note that these
forced collisions are not limited to a maximum of 16 consecutive collisions, and are independent of the
normal back-off algorithm.
Receive flow control does not depend on the value of the incoming frame destination address. A collision
is generated for any incoming packet, regardless of the destination address, if any EMAC enabled
channel’s free buffer register value is less than or equal to the channel’s flow threshold value.
2.9.1.3.2 IEEE 802.3x-Based Receive Buffer Flow Control
IEEE 802.3x-based receive buffer flow control provides a means of preventing frame reception when the
EMAC is operating in full-duplex mode (the FULLDUPLEX bit is set in MACCONTROL). When receive
flow control is enabled and triggered, the EMAC transmits a pause frame to request that the sending
station stop transmitting for the period indicated within the transmitted pause frame.
The EMAC transmits a pause frame to the reserved multicast address at the first available opportunity
(immediately if currently idle or following the completion of the frame currently being transmitted). The
pause frame contains the maximum possible value for the pause time (FFFFh). The EMAC counts the
receive pause frame time (decrements FF00h to 0) and retransmits an outgoing pause frame, if the count
reaches 0. When the flow control request is removed, the EMAC transmits a pause frame with a zero
pause time to cancel the pause request.
Note that transmitted pause frames are only a request to the other end station to stop transmitting.
Frames that are received during the pause interval are received normally (provided the receive FIFO is not
full).
Pause frames are transmitted if enabled and triggered, regardless of whether or not the EMAC is
observing the pause time period from an incoming pause frame.
The EMAC transmits pause frames as described below:
• The 48-bit reserved multicast destination address 01.80.C2.00.00.01h.
• The 48-bit source address (set using the MACSRCADDRLO and MACSRCADDRHI registers).
• The 16-bit length/type field containing the value 88.08h.
• The 16-bit pause opcode equal to 00.01h.
• The 16-bit pause time value of FF.FFh. A pause-quantum is 512 bit-times. Pause frames sent to
cancel a pause request have a pause time value of 00.00h.
• Zero padding to 64-byte data length (EMAC transmits only 64-byte pause frames).
• The 32-bit frame-check sequence (CRC word).
All quantities are hexadecimal and are transmitted most-significant byte first. The least-significant bit (LSB)
is transferred first in each byte.
If the RXBUFFERFLOWEN bit in MACCONTROL is cleared to 0 while the pause time is nonzero, then the
pause time is cleared to 0 and a zero count pause frame is sent.
www.ti.com
38
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.9.2 Data Transmission
The EMAC passes data to the PHY from the transmit FIFO (when enabled). Data is synchronized to the
transmit clock rate. Transmission begins when there are TXCELLTHRESH cells of 64 bytes each, or a
complete packet, in the FIFO.
2.9.2.1 Transmit Control
A jam sequence is output if a collision is detected on a transmit packet. If the collision was late (after the
first 64 bytes have been transmitted), the collision is ignored. If the collision is not late, the controller will
back off before retrying the frame transmission. When operating in full-duplex mode, the carrier sense
(MII_CRS) and collision-sensing (MII_COL) modes are disabled.
2.9.2.2 CRC Insertion
If the SOP buffer descriptor PASSCRC flag is cleared, the EMAC generates and appends a 32-bit
Ethernet CRC onto the transmitted data. For the EMAC-generated CRC case, a CRC (or placeholder) at
the end of the data is allowed but not required. The buffer byte count value should not include the CRC
bytes, if they are present.
If the SOP buffer descriptor PASSCRC flag is set, then the last four bytes of the transmit data are
transmitted as the frame CRC. The four CRC data bytes should be the last four bytes of the frame and
should be included in the buffer byte count value. The MAC performs no error checking on the outgoing
CRC.
2.9.2.3 Adaptive Performance Optimization (APO)
The EMAC incorporates adaptive performance optimization (APO) logic that may be enabled by setting
the TXPACE bit in the MAC control register (MACCONTROL). Transmission pacing to enhance
performance is enabled when the TXPACE bit is set. Adaptive performance pacing introduces delays into
the normal transmission of frames, delaying transmission attempts between stations, reducing the
probability of collisions occurring during heavy traffic (as indicated by frame deferrals and collisions),
thereby, increasing the chance of successful transmission.
When a frame is deferred, suffers a single collision, multiple collisions, or excessive collisions, the pacing
counter is loaded with an initial value of 31. When a frame is transmitted successfully (without
experiencing a deferral, single collision, multiple collision, or excessive collision), the pacing counter is
decremented by 1, down to 0.
With pacing enabled, a new frame is permitted to immediately (after one interpacket gap) attempt
transmission only if the pacing counter is 0. If the pacing counter is nonzero, the frame is delayed by the
pacing delay of approximately four interpacket gap (IPG)delays. APO only affects the IPG preceding the
first attempt at transmitting a frame; APO does not affect the back-off algorithm for retransmitted frames.
Architecture
2.9.2.4 Interpacket-Gap (IPG) Enforcement
The measurement reference for the IPG of 96 bit times is changed depending on frame traffic conditions.
If a frame is successfully transmitted without collision and MII_CRS is deasserted within approximately 48
bit times of MII_TXEN being deasserted, then 96 bit times is measured from MII_TXEN. If the frame
suffered a collision or MII_CRS is not deasserted until more than approximately 48 bit times after
MII_TXEN is deasserted, then 96 bit times (approximately, but not less) is measured from MII_CRS.
2.9.2.5 Back Off
The EMAC implements the 802.3 binary exponential back-off algorithm.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
39
© 2011, Texas Instruments Incorporated
Architecture
2.9.2.6 Transmit Flow Control
Incoming pause frames are acted upon, when enabled, to prevent the EMAC from transmitting any further
frames. Incoming pause frames are only acted upon when the FULLDUPLEX and TXFLOWEN bits in the
MAC control register (MACCONTROL) are set. Pause frames are not acted upon in half-duplex mode.
Pause frame action is taken if enabled, but normally the frame is filtered and not transferred to memory.
MAC control frames are transferred to memory, if the RXCMFEN bit in the receive
multicast/broadcast/promiscuous channel enable register (RXMBPENABLE) is set. The TXFLOWEN and
FULLDUPLEX bits affect whether or not MAC control frames are acted upon, but they have no affect upon
whether or not MAC control frames are transferred to memory or filtered.
Pause frames are a subset of MAC control frames with an opcode field of 0001h. Incoming pause frames
are only acted upon by the EMAC if:
• TXFLOWEN bit is set in MACCONTROL
• The frame’s length is 64 to RXMAXLEN bytes inclusive
• The frame contains no CRC error or align/code errors
The pause time value from valid frames is extracted from the two bytes following the opcode. The pause
time is loaded into the EMAC transmit pause timer and the transmit pause time period begins. If a valid
pause frame is received during the transmit pause time period of a previous transmit pause frame then:
• If the destination address is not equal to the reserved multicast address or any enabled or disabled
unicast address, then the transmit pause timer immediately expires, or
• If the new pause time value is 0, then the transmit pause timer immediately expires, else
• The EMAC transmit pause timer immediately is set to the new pause frame pause time value. (Any
remaining pause time from the previous pause frame is discarded).
If the TXFLOWEN bit in MACCONTROL is cleared, then the pause timer immediately expires.
The EMAC does not start the transmission of a new data frame any sooner than 512 bit-times after a
pause frame with a nonzero pause time has finished being received (MII_RXDV going inactive). No
transmission begins until the pause timer has expired (the EMAC may transmit pause frames in order to
initiate outgoing flow control). Any frame already in transmission when a pause frame is received is
completed and unaffected.
Incoming pause frames consist of:
• A 48-bit destination address equal to one of the following:
– The reserved multicast destination address 01.80.C2.00.00.01h
– Any EMAC 48-bit unicast address. Pause frames are accepted, regardless of whether the channel
is enabled or not.
• The 16-bit length/type field containing the value 88.08h.
• The 48-bit source address of the transmitting device.
• The 16-bit pause opcode equal to 00.01h.
• The 16-bit pause time. A pause-quantum is 512 bit-times.
• Padding to 64-byte data length.
• The 32-bit frame-check sequence (CRC word).
All quantities are hexadecimal and are transmitted most-significant byte first. The least-significant bit (LSB)
is transferred first in each byte.
The padding is required to make up the frame to a minimum of 64 bytes. The standard allows pause
frames longer than 64 bytes to be discarded or interpreted as valid pause frames. The EMAC recognizes
any pause frame between 64 bytes and RXMAXLEN bytes in length.
www.ti.com
2.9.2.7 Speed, Duplex, and Pause Frame Support
The MAC operates at 10 Mbps or 100 Mbps, in half-duplex or full-duplex mode, and with or without pause
frame support as configured by the host.
40
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.10 Packet Receive Operation
2.10.1 Receive DMA Host Configuration
To configure the receive DMA for operation the host must:
• Initialize the receive addresses.
• Initialize the receive channel n DMA head descriptor pointer registers (RXnHDP) to 0.
• Write the MAC address hash n registers (MACHASH1 and MACHASH2), if multicast addressing is
desired.
• If flow control is to be enabled, initialize:
– the receive channel n free buffer count registers (RXnFREEBUFFER)
– the receive channel n flow control threshold register (RXnFLOWTHRESH)
– the receive filter low priority frame threshold register (RXFILTERLOWTHRESH)
• Enable the desired receive interrupts using the receive interrupt mask set register (RXINTMASKSET)
and the receive interrupt mask clear register (RXINTMASKCLEAR).
• Set the appropriate configuration bits in the MAC control register (MACCONTROL).
• Write the receive buffer offset register (RXBUFFEROFFSET) value (typically zero).
• Setup the receive channel(s) buffer descriptors and initialize RXnHDP.
• Enable the receive DMA controller by setting the RXEN bit in the receive control register
(RXCONTROL).
• Configure and enable the receive operation, as desired, in the receive
multicast/broadcast/promiscuous channel enable register (RXMBPENABLE) and by using the receive
unicast set register (RXUNICASTSET) and the receive unicast clear register (RXUNICASTCLEAR).
Architecture
2.10.2 Receive Channel Enabling
Each of the eight receive channels has an enable bit (RXCHnEN) in the receive unicast set register
(RXUNICASTSET) that is controlled using RXUNICASTSET and the receive unicast clear register
(RXUNICASTCLEAR). The RXCHnEN bits determine whether the given channel is enabled (when set to
1) to receive frames with a matching unicast or multicast destination address.
The RXBROADEN bit in the receive multicast/broadcast/promiscuous channel enable register
(RXMBPENABLE) determines if broadcast frames are enabled or filtered. If broadcast frames are enabled
(when set to 1), then they are copied to only a single channel selected by the RXBROADCH bit in
RXMBPENABLE.
The RXMULTEN bit in RXMBPENABLE determines if hash matching multicast frames are enabled or
filtered. Incoming multicast addresses (group addresses) are hashed into an index in the hash table. If the
indexed bit is set then the frame hash matches and will be transferred to the channel selected by the
RXMULTCH bit in RXMBPENABLE when multicast frames are enabled. The multicast hash bits are set in
the MAC address hash n registers (MACHASH1 and MACHASH2).
The RXPROMCH bit in RXMBPENABLE selects the promiscuous channel to receive frames selected by
the RXCMFEN, RXCSFEN, RXCEFEN, and RXCAFEN bits. These four bits allow reception of MAC
control frames, short frames, error frames, and all frames (promiscuous), respectively.
2.10.3 Receive Address Matching
All eight MAC addresses corresponding to the eight receive channels share the upper 40 bits. Only the
lower byte is unique for each address. All eight receive addresses should be initialized, because pause
frames are acted upon regardless of whether a channel is enabled or not.
A MAC address is written by first writing the address number (channel) to be written into the MAC index
register (MACINDEX). The upper 32 bits of address are then written to the MAC address high bytes
register (MACADDRHI), which is followed by writing the lower 16 bits of address to the MAC address low
bytes register (MACADDRLO). Since all eight MAC addresses share the upper 40 bits of address,
MACADDRHI needs to be written only the first time (for the first channel configured).
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
41
© 2011, Texas Instruments Incorporated
Architecture
2.10.4 Hardware Receive QOS Support
Hardware receive quality of service (QOS) is supported, when enabled, by the Tag Protocol Identifier
format and the associated Tag Control Information (TCI) format priority field. When the incoming frame
length/type value is equal to 81.00h, the EMAC recognizes the frame as an Ethernet Encoded Tag
Protocol Type. The two octets immediately following the protocol type contain the 16-bit TCI field. Bits
15-13 of the TCI field contain the received frames priority (0 to 7). The received frame is a low-priority
frame, if the priority value is 0 to 3; the received frame is a high-priority frame, if the priority value is 4 to 7.
All frames that have a length/type field value not equal to 81.00h are low-priority frames. Received frames
that contain priority information are determined by the EMAC as:
• A 48-bit (6 bytes) destination address equal to:
– The destination station's individual unicast address.
– The destination station's multicast address (MACHASH1 and MACHASH2).
– The broadcast address of all ones.
• A 48-byte (6 bytes) source address.
• The 16-bit (2 bytes) length/type field containing the value 81.00h.
• The 16-bit (2 bytes) TCI field with the priority field in the upper 3 bits.
• Data bytes
• The 4 bytes CRC.
The receive filter low priority frame threshold register (RXFILTERLOWTHRESH) and the receive channel
n free buffer count registers (RXnFREEBUFFER) are used in conjunction with the priority information to
implement receive hardware QOS. Low-priority frames are filtered if the number of free buffers
(RXnFREEBUFFER) for the frame channel is less than or equal to the filter low threshold
(RXFILTERLOWTHRESH) value. Hardware QOS is enabled by the RXQOSEN bit in the receive
multicast/broadcast/promiscuous channel enable register (RXMBPENABLE).
www.ti.com
2.10.5 Host Free Buffer Tracking
The host must track free buffers for each enabled channel (including unicast, multicast, broadcast, and
promiscuous), if receive QOS or receive flow control is used. Disabled channel free buffer values are do
not cares. During initialization, the host should write the number of free buffers for each enabled channel
to the appropriate receive channel n free buffer count registers (RXnFREEBUFFER). The EMAC
decrements the appropriate channel’s free buffer value for each buffer used. When the host reclaims the
frame buffers, the host should write the channel free buffer register with the number of reclaimed buffers
(write to increment). There are a maximum of 65,535 free buffers available. RXnFREEBUFFER only
needs to be updated by the host if receive QOS or flow control is used.
2.10.6 Receive Channel Teardown
The host commands a receive channel teardown by writing the channel number to the receive teardown
register (RXTEARDOWN). When a teardown command is issued to an enabled receive channel, the
following occurs:
• Any current frame in reception completes normally.
• The TDOWNCMPLT flag is set in the next buffer descriptor in the chain, if there is one.
• The channel head descriptor pointer is cleared to 0.
• A receive interrupt for the channel is issued to the host.
• The corresponding receive channel n completion pointer register (RXnCP) contains the value FFFF
FFCh.
Channel teardown may be commanded on any channel at any time. The host is informed of the teardown
completion by the set teardown complete (TDOWNCMPLT) buffer descriptor bit. The EMAC does not
clear any channel enables due to a teardown command. A teardown command to an inactive channel
issues an interrupt that software should acknowledge with an FFFF FFFCh acknowledge value to RXnCP
(note that there is no buffer descriptor in this case). Software may read RXnCP to determine if the
interrupt was due to a commanded teardown. The read value is FFFF FFFCh, if the interrupt was due to a
teardown command.
42
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.10.7 Receive Frame Classification
Received frames are proper (good) frames, if they are between 64 bytes and the value in the receive
maximum length register (RXMAXLEN) bytes in length (inclusive) and contain no code, align, or CRC
errors.
Received frames are long frames, if their frame count exceeds the value in RXMAXLEN. The RXMAXLEN
reset (default) value is 5EEh (1518 in decimal). Long received frames are either oversized or jabber
frames. Long frames with no errors are oversized frames; long frames with CRC, code, or alignment
errors are jabber frames.
Received frames are short frames, if their frame count is less than 64 bytes. Short frames that address
match and contain no errors are undersized frames; short frames with CRC, code, or alignment errors are
fragment frames. If the frame length is less than or equal to 20, then the frame CRC is passed, regardless
of whether the RXPASSCRC bit is set or cleared in the receive multicast/broadcast/promiscuous channel
enable register (RXMBPENABLE).
A received long packet always contains RXMAXLEN number of bytes transferred to memory (if the
RXCEFEN bit is set in RXMBPENABLE), regardless of the value of the RXPASSCRC bit. Following is an
example with RXMAXLEN set to 1518:
• If the frame length is 1518, then the packet is not a long packet and there are 1514 or 1518 bytes
transferred to memory depending on the value of the RXPASSCRC bit.
• If the frame length is 1519, there are 1518 bytes transferred to memory regardless of the
RXPASSCRC bit value. The last three bytes are the first three CRC bytes.
• If the frame length is 1520, there are 1518 bytes transferred to memory regardless of the
RXPASSCRC bit value. The last two bytes are the first two CRC bytes.
• If the frame length is 1521, there are 1518 bytes transferred to memory regardless of the
RXPASSCRC bit value. The last byte is the first CRC byte.
• If the frame length is 1522, there are 1518 bytes transferred to memory. The last byte is the last data
byte.
Architecture
2.10.8 Promiscuous Receive Mode
When the promiscuous receive mode is enabled by setting the RXCAFEN bit in the receive
multicast/broadcast/promiscuous channel enable register (RXMBPENABLE), nonaddress matching frames
that would normally be filtered are transferred to the promiscuous channel. Address matching frames that
would normally be filtered due to errors are transferred to the address match channel when the RXCAFEN
and RXCEFEN bits in RXMBPENABLE are set. A frame is considered to be an address matching frame
only if it is enabled to be received on a unicast, multicast, or broadcast channel. Frames received to
disabled unicast, multicast, or broadcast channels are considered nonaddress matching.
MAC control frames address match only if the RXCMFEN bit in RXMBPENABLE is set. The RXCEFEN
and RXCSFEN bits in RXMBPENABLE determine whether error frames are transferred to memory or not,
but they do not determine whether error frames are address matching or not. Short frames are a special
type of error frames.
A single channel is selected as the promiscuous channel by the RXPROMCH bit in RXMBPENABLE. The
promiscuous receive mode is enabled by the RXCMFEN, RXCEFEN, RXCSFEN, and RXCAFEN bits in
RXMBPENABLE. Table 5 shows the effects of the promiscuous enable bits. Proper frames are frames
that are between 64 bytes and the value in the receive maximum length register (RXMAXLEN) bytes in
length inclusive and contain no code, align, or CRC errors.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
43
© 2011, Texas Instruments Incorporated
Architecture
Address Match RXCAFEN RXCEFEN RXCMFEN RXCSFEN Receive Frame Treatment
www.ti.com
Table 5. Receive Frame Treatment Summary
0 0 X X X No frames transferred.
0 1 0 0 0 Proper frames transferred to promiscuous channel.
0 1 0 0 1 Proper/undersized data frames transferred to
promiscuous channel.
0 1 0 1 0 Proper data and control frames transferred to
promiscuous channel.
0 1 0 1 1 Proper/undersized data and control frames
transferred to promiscuous channel.
0 1 1 0 0 Proper/oversize/jabber/code/align/CRC data frames
transferred to promiscuous channel. No control or
undersized/fragment frames are transferred.
0 1 1 0 1 Proper/undersized/fragment/oversize/jabber/code/
align/CRC data frames transferred to promiscuous
channel. No control frames are transferred.
0 1 1 1 0 Proper/oversize/jabber/code/align/CRC data and
control frames transferred to promiscuous channel.
No undersized frames are transferred.
0 1 1 1 1 All nonaddress matching frames with and without
errors transferred to promiscuous channel.
1 X 0 0 0 Proper data frames transferred to address match
channel.
1 X 0 0 1 Proper/undersized data frames transferred
to address match channel.
1 X 0 1 0 Proper data and control frames transferred to
address match channel.
1 X 0 1 1 Proper/undersized data and control frames
transferred to address match channel.
1 X 1 0 0 Proper/oversize/jabber/code/align/CRC data frames
transferred to address match channel. No control
or undersized frames are transferred.
1 X 1 0 1 Proper/oversize/jabber/fragment/undersized/code/
align/CRC data frames transferred to address
match channel. No control frames are transferred.
1 X 1 1 0 Proper/oversize/jabber/code/align/CRC data and
control frames transferred to address match
channel. No undersized/fragment frames are
transferred.
1 X 1 1 1 All address matching frames with and without
errors transferred to the address match channel
44
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.10.9 Receive Overrun
The types of receive overrun are:
• FIFO start of frame overrun (FIFO_SOF)
• FIFO middle of frame overrun (FIFO_MOF)
• DMA start of frame overrun (DMA_SOF)
• DMA middle of frame overrun (DMA_MOF)
The statistics counters used to track these types of receive overrun are:
• Receive start of frame overruns register (RXSOFOVERRUNS)
• Receive middle of frame overruns register (RXMOFOVERRUNS)
• Receive DMA overruns register (RXDMAOVERRUNS)
Start of frame overruns happen when there are no resources available when frame reception begins. Start
of frame overruns increment the appropriate overrun statistic(s) and the frame is filtered.
Middle of frame overruns happen when there are some resources to start the frame reception, but the
resources run out during frame reception. In normal operation, a frame that overruns after starting the
frame reception is filtered and the appropriate statistic(s) are incremented; however, the RXCEFEN bit in
the receive multicast/broadcast/promiscuous channel enable register (RXMBPENABLE) affects overrun
frame treatment. Table 6 shows how the overrun condition is handled for the middle of frame overrun.
Address Match RXCAFEN RXCEFEN Middle of Frame Overrun Treatment
0 0 X Overrun frame filtered.
0 1 0 Overrun frame filtered.
0 1 1 As much frame data as possible is transferred to the promiscuous channel
1 X 0 Overrun frame filtered with the appropriate overrun statistic(s) incremented.
1 X 1 As much frame data as possible is transferred to the address match
Architecture
Table 6. Middle of Frame Overrun Treatment
until overrun. The appropriate overrun statistic(s) is incremented and the
OVERRUN and NOMATCH flags are set in the SOP buffer descriptor. Note
that the RXMAXLEN number of bytes cannot be reached for an overrun to
occur (it would be truncated and be a jabber or oversize).
channel until overrun. The appropriate overrun statistic(s) is incremented
and the OVERRUN flag is set in the SOP buffer descriptor. Note that the
RXMAXLEN number of bytes cannot be reached for an overrun to occur (it
would be truncated).
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
45
© 2011, Texas Instruments Incorporated
Architecture
2.11 Packet Transmit Operation
The transmit DMA is an eight channel interface. Priority between the eight queues may be either fixed or
round-robin as selected by the TXPTYPE bit in the MAC control register (MACCONTROL). If the priority
type is fixed, then channel 7 has the highest priority and channel 0 has the lowest priority. Round-robin
priority proceeds from channel 0 to channel 7.
2.11.1 Transmit DMA Host Configuration
To configure the transmit DMA for operation the host must perform:
• Write the MAC source address low bytes register (MACSRCADDRLO) and the MAC source address
high bytes register (MACSRCADDRHI) (used for pause frames on transmit).
• Initialize the transmit channel n DMA head descriptor pointer registers (TXnHDP) to 0.
• Enable the desired transmit interrupts using the transmit interrupt mask set register (TXINTMASKSET)
and the transmit interrupt mask clear register (TXINTMASKCLEAR).
• Set the appropriate configuration bits in the MAC control register (MACCONTROL).
• Setup the transmit channel(s) buffer descriptors in host memory.
• Enable the transmit DMA controller by setting the TXEN bit in the transmit control register
(TXCONTROL).
• Write the appropriate TXnHDP with the pointer to the first descriptor to start transmit operations.
2.11.2 Transmit Channel Teardown
The host commands a transmit channel teardown by writing the channel number to the transmit teardown
register (TXTEARDOWN). When a teardown command is issued to an enabled transmit channel, the
following occurs:
• Any frame currently in transmission completes normally.
• The TDOWNCMPLT flag is set in the next SOP buffer descriptor in the chain, if there is one.
• The channel head descriptor pointer is cleared to 0.
• A transmit interrupt is issued to inform the host of the channel teardown.
• The corresponding transmit channel n completion pointer register (TXnCP) contains the value
FFFF FFFCh.
• The host should acknowledge a teardown interrupt with an FFFF FFFCh acknowledge value.
www.ti.com
Channel teardown may be commanded on any channel at any time. The host is informed of the teardown
completion by the set teardown complete (TDOWNCMPLT) buffer descriptor bit. The EMAC does not
clear any channel enables due to a teardown command. A teardown command to an inactive channel
issues an interrupt that software should acknowledge with an FFFF FFFCh acknowledge value to TXnCP
(note that there is no buffer descriptor in this case). Software may read the interrupt acknowledge location
(TXnCP) to determine if the interrupt was due to a commanded teardown. The read value is FFFF FFFCh,
if the interrupt was due to a teardown command.
46
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.12 Receive and Transmit Latency
The transmit and receive FIFOs each contain three 64-byte cells. The EMAC begins transmission of a
packet on the wire after TXCELLTHRESH (configurable through the FIFO control register) cells, or a
complete packet, are available in the FIFO.
Transmit underrun cannot occur for packet sizes of TXCELLTHRESH times 64 bytes (or less). For larger
packet sizes, transmit underrun occurs if the memory latency is greater than the time required to transmit
a 64-byte cell on the wire; this is 5.12 μs in 100 Mbps mode and 51.2 μs in 10 Mbps mode. The memory
latency time includes all buffer descriptor reads for the entire cell data.
Receive overrun is prevented if the receive memory cell latency is less than the time required to transmit a
64-byte cell on the wire: 5.12 μs in 100 Mbps mode, or 51.2 μs in 10 Mbps mode. The latency time
includes any required buffer descriptor reads for the cell data.
Latency to system’s internal and external RAM can be controlled through the use of the transfer node
priority allocation register available at the device level. Latency to descriptor RAM is low because RAM is
local to the EMAC, as it is part of the EMAC control module.
2.13 Transfer Node Priority
The device contains a chip-level master priority register that is used to set the priority of the transfer node
used in issuing memory transfer requests to system memory.
Although the EMAC has internal FIFOs to help alleviate memory transfer arbitration problems, the average
transfer rate of data read and written by the EMAC to internal or external processor memory must be at
least that of the Ethernet wire rate. In addition, the internal FIFO system can not withstand a single
memory latency event greater than the time it takes to fill or empty a TXCELLTHRESH number of internal
64 byte FIFO cells.
For 100 Mbps operation, these restrictions translate into the following rules:
• The short-term average, each 64-byte memory read/write request from the EMAC must be serviced in
no more than 5.12 μs.
• Any single latency event in request servicing can be no longer than (5.12 × TXCELLTHRESH) μs.
Architecture
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
47
© 2011, Texas Instruments Incorporated
Architecture
2.14 Reset Considerations
2.14.1 Software Reset Considerations
Peripheral clock and reset control is done through the Power and Sleep Controller (PSC) module included
with the device. For more on how the EMAC, MDIO, and EMAC control module are disabled or placed in
reset at runtime from the registers located in the PSC module, see Section 2.17.
With the EMAC still in reset (PSC in the default state):
1. Program the PINMUX register(s) as required for the desired interface (MII or RMII), see your
device-specific System Reference Guide and your device-specific data manual for details.
2. Program the PSC to enable the EMAC. For information on how to enable the EMAC peripheral from
the PSC, see your device-specific System Reference Guide.
Within the peripheral itself, the EMAC component of the Ethernet MAC peripheral can be placed in a reset
state by writing to the soft reset register (SOFTRESET). Writing a 1 to the SOFTRESET bit, causes the
EMAC logic to be reset and the register values to be set to their default values. Software reset occurs
when the receive and transmit DMA controllers are in an idle state to avoid locking up the configuration
bus; it is the responsibility of the software to verify that there are no pending frames to be transferred.
After writing a 1 to the SOFTRESET bit, it may be polled to determine if the reset has occurred. If a 1 is
read, the reset has not yet occurred; if a 0 is read, then a reset has occurred.
After a software reset operation, all the EMAC registers need to be reinitialized for proper data
transmission, including the FULLDUPLEX bit setting in the MAC control register (MACCONTROL).
Unlike the EMAC module, the MDIO and EMAC control modules cannot be placed in reset from a register
inside their memory map.
www.ti.com
2.14.2 Hardware Reset Considerations
When a hardware reset occurs, the EMAC peripheral has its register values reset and all the components
return to their default state. After the hardware reset, the EMAC needs to be initialized before being able
to resume its data transmission, as described in Section 2.15.
A hardware reset is the only means of recovering from the error interrupts (HOSTPEND), which are
triggered by errors in packet buffer descriptors. Before doing a hardware reset, you should inspect the
error codes in the MAC status register (MACSTATUS) that gives information about the type of software
error that needs to be corrected. For detailed information on error interrupts, see Section 2.16.1.4.
48
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.15 Initialization
2.15.1 Enabling the EMAC/MDIO Peripheral
When the device is powered on, the EMAC peripheral may be in a disabled state. Before any EMAC
specific initialization can take place, the EMAC needs to be enabled; otherwise, its registers cannot be
written and the reads will all return a value of zero.
The EMAC/MDIO is enabled through the Power and Sleep Controller (PSC) registers. For information on
how to enable the EMAC peripheral from the PSC, see your device-specific System Reference Guide.
When first enabled, the EMAC peripheral registers are set to their default values. After enabling the
peripheral, you may proceed with the module specific initialization.
2.15.2 EMAC Control Module Initialization
The EMAC control module is used for global interrupt enables and to pace interrupts using 1ms time
windows. There is also an 8K block of CPPI RAM local to the EMAC that is used to hold packet buffer
descriptors.
Note that although the EMAC control module and the EMAC module have slightly different functions, in
practice, the type of maintenance performed on the EMAC control module is more commonly conducted
from the EMAC module software (as opposed to the MDIO module).
The initialization of the EMAC control module consists of two parts:
1. Configuration of the interrupt to the CPU.
2. Initialization of the EMAC control module:
• Setting the interrupt pace counts using the EMAC control module registers INTCONTROL,
CnRXIMAX, and CnTXIMAX
• Initializing the EMAC and MDIO modules
• Enabling interrupts in the EMAC control module using the EMAC control module interrupt control
registers CnRXTHRESHEN, CnRXEN, CnTXEN, and CnMISCEN.
The process of mapping the EMAC interrupts to the CPU is done through the CPU interrupt controller.
Once the interrupt is mapped to a CPU interrupt, general masking and unmasking of interrupts (to control
reentrancy) should be done at the chip level by manipulating the interrupt core enable mask registers.
Architecture
2.15.3 MDIO Module Initialization
The MDIO module is used to initially configure and monitor one or more external PHY devices. Other than
initializing the software state machine (details on this state machine can be found in the IEEE 802.3
standard), all that needs to be done for the MDIO module is to enable the MDIO engine and to configure
the clock divider. To set the clock divider, supply an MDIO clock of 1 MHz. For example, if the peripheral
clock is 50 MHz, the divider can be set to 50.
Both the state machine enable and the MDIO clock divider are controlled through the MDIO control
register (CONTROL). If none of the potentially connected PHYs require the access preamble, the
PREAMBLE bit in CONTROL can also be set to speed up PHY register access.
If the MDIO module is to operate on an interrupt basis, the interrupts can be enabled at this time using the
MDIO user command complete interrupt mask set register (USERINTMASKSET) for register access and
the MDIO user PHY select register (USERPHYSELn) if a target PHY is already known.
Once the MDIO state machine has been initialized and enabled, it starts polling all 32 PHY addresses on
the MDIO bus, looking for an active PHY. Since it can take up to 50 μs to read one register, it can be
some time before the MDIO module provides an accurate representation of whether a PHY is available.
Also, a PHY can take up to 3 seconds to negotiate a link. Thus, it is advisable to run the MDIO software
off a time-based event rather than polling.
For more information on PHY control registers, see your PHY device documentation.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
49
© 2011, Texas Instruments Incorporated
Architecture
2.15.4 EMAC Module Initialization
The EMAC module is used to send and receive data packets over the network. This is done by
maintaining up to eight transmit and receive descriptor queues. The EMAC module configuration must
also be kept up-to-date based on PHY negotiation results returned from the MDIO module. Most of the
work in developing an application or device driver for Ethernet is programming this module.
The following is the initialization procedure a device driver would follow to get the EMAC to the state
where it is ready to receive and send Ethernet packets. Some of these steps are not necessary when
performed immediately after device reset.
1. If enabled, clear the device interrupt enable bits in the EMAC control module interrupt control registers
CnRXTHRESHEN, CnRXEN, CnTXEN, and CnMISCEN.
2. Clear the MAC control register (MACCONTROL), receive control register (RXCONTROL), and transmit
control register (TXCONTROL) (not necessary immediately after reset).
3. Initialize all 16 header descriptor pointer registers (RXnHDP and TXnHDP) to 0.
4. Clear all 36 statistics registers by writing 0 (not necessary immediately after reset).
5. Setup the local Ethernet MAC address by programming the MAC index register (MACINDEX), MAC
address high bytes register (MACADDRHI), and MAC address low bytes register (MACADDRLO). Be
sure to program all eight MAC address registers - whether the receive channel is to be enabled or not.
Duplicate the same MAC address across all unused channels. When using more than one receive
channel, start with channel 0 and progress upwards.
6. If buffer flow control is to be enabled, initialize the receive channel n free buffer count registers
(RXnFREEBUFFER), receive channel n flow control threshold register (RXnFLOWTHRESH), and
receive filter low priority frame threshold register (RXFILTERLOWTHRESH).
7. Most device drivers open with no multicast addresses, so clear the MAC address hash registers
(MACHASH1 and MACHASH2) to 0.
8. Write the receive buffer offset register (RXBUFFEROFFSET) value (typically zero).
9. Initially clear all unicast channels by writing FFh to the receive unicast clear register
(RXUNICASTCLEAR). If unicast is desired, it can be enabled now by writing the receive unicast set
register (RXUNICASTSET). Some drivers will default to unicast on device open while others will not.
10. Setup the receive multicast/broadcast/promiscuous channel enable register (RXMBPENABLE) with an
initial configuration. The configuration is based on the current receive filter settings of the device driver.
Some drivers may enable things like broadcast and multicast packets immediately, while others may
not.
11. Set the appropriate configuration bits in MACCONTROL (do not set the GMIIEN bit yet).
12. Clear all unused channel interrupt bits by writing the receive interrupt mask clear register
(RXINTMASKCLEAR) and the transmit interrupt mask clear register (TXINTMASKCLEAR).
13. Enable the receive and transmit channel interrupt bits in the receive interrupt mask set register
(RXINTMASKSET) and the transmit interrupt mask set register (TXINTMASKSET) for the channels to
be used, and enable the HOSTMASK and STATMASK bits using the MAC interrupt mask set register
(MACINTMASKSET).
14. Initialize the receive and transmit descriptor list queues.
15. Prepare receive by writing a pointer to the head of the receive buffer descriptor list to RXnHDP.
16. Enable the receive and transmit DMA controllers by setting the RXEN bit in RXCONTROL and the
TXEN bit in TXCONTROL. Then set the GMIIEN bit in MACCONTROL.
17. Enable the device interrupt in EMAC control module registers CnRXTHRESHEN, CnRXEN, CnTXEN,
and CnMISCEN.
www.ti.com
50
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.16 Interrupt Support
2.16.1 EMAC Module Interrupt Events and Requests
The EMAC module generates 26 interrupt events:
• TXPENDn: Transmit packet completion interrupt for transmit channels 0 through 7
• RXPENDn: Receive packet completion interrupt for receive channels 0 through 7
• RXTHRESHPENDn: Receive packet completion interrupt for receive channels 0 through 7 when flow
control is enabled and the number of free buffers is below the threshold
• STATPEND: Statistics interrupt
• HOSTPEND: Host error interrupt
2.16.1.1 Transmit Packet Completion Interrupts
The transmit DMA engine has eight channels, with each channel having a corresponding interrupt
(TXPENDn). The transmit interrupts are level interrupts that remain asserted until cleared by the CPU.
Each of the eight transmit channel interrupts may be individually enabled by setting the appropriate bit in
the transmit interrupt mask set register (TXINTMASKSET) to 1. Each of the eight transmit channel
interrupts may be individually disabled by clearing the appropriate bit by writing a 1 to the transmit
interrupt mask clear register (TXINTMASKCLEAR). The raw and masked transmit interrupt status may be
read by reading the transmit interrupt status (unmasked) register (TXINTSTATRAW) and the transmit
interrupt status (masked) register (TXINTSTATMASKED), respectively.
When the EMAC completes the transmission of a packet, the EMAC issues an interrupt to the CPU (via
the EMAC control module) when it writes the packet’s last buffer descriptor address to the appropriate
channel queue’s transmit completion pointer located in the state RAM block. The interrupt is generated by
the write when enabled by the interrupt mask, regardless of the value written.
Upon interrupt reception, the CPU processes one or more packets from the buffer chain and then
acknowledges an interrupt by writing the address of the last buffer descriptor processed to the queue’s
associated transmit completion pointer in the transmit DMA state RAM.
The data written by the host (buffer descriptor address of the last processed buffer) is compared to the
data in the register written by the EMAC port (address of last buffer descriptor used by the EMAC). If the
two values are not equal (which means that the EMAC has transmitted more packets than the CPU has
processed interrupts for), the transmit packet completion interrupt signal remains asserted. If the two
values are equal (which means that the host has processed all packets that the EMAC has transferred),
the pending interrupt is cleared. The value that the EMAC is expecting is found by reading the transmit
channel n completion pointer register (TXnCP).
The EMAC write to the completion pointer actually stores the value in the state RAM. The CPU written
value does not actually change the register value. The host written value is compared to the register
content (which was written by the EMAC) and if the two values are equal then the interrupt is removed;
otherwise, the interrupt remains asserted. The host may process multiple packets prior to acknowledging
an interrupt, or the host may acknowledge interrupts for every packet.
The application software must acknowledge the EMAC control module after processing packets by writing
the appropriate CnRX key to the EMAC End-Of-Interrupt Vector register (MACEOIVECTOR). See
Section 5.12 for the acknowledge key values.
Architecture
2.16.1.2 Receive Packet Completion Interrupts
The receive DMA engine has eight channels, which each channel having a corresponding interrupt
(RXPENDn). The receive interrupts are level interrupts that remain asserted until cleared by the CPU.
Each of the eight receive channel interrupts may be individually enabled by setting the appropriate bit in
the receive interrupt mask set register (RXINTMASKSET) to 1. Each of the eight receive channel
interrupts may be individually disabled by clearing the appropriate bit by writing a 1 in the receive interrupt
mask clear register (RXINTMASKCLEAR). The raw and masked receive interrupt status may be read by
reading the receive interrupt status (unmasked) register (RXINTSTATRAW) and the receive interrupt
status (masked) register (RXINTSTATMASKED), respectively.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
51
© 2011, Texas Instruments Incorporated
Architecture
When the EMAC completes a packet reception, the EMAC issues an interrupt to the CPU by writing the
packet's last buffer descriptor address to the appropriate channel queue's receive completion pointer
located in the state RAM block. The interrupt is generated by the write when enabled by the interrupt
mask, regardless of the value written.
Upon interrupt reception, the CPU processes one or more packets from the buffer chain and then
acknowledges one or more interrupt(s) by writing the address of the last buffer descriptor processed to the
queue's associated receive completion pointer in the receive DMA state RAM.
The data written by the host (buffer descriptor address of the last processed buffer) is compared to the
data in the register written by the EMAC (address of last buffer descriptor used by the EMAC). If the two
values are not equal (which means that the EMAC has received more packets than the CPU has
processed interrupts for), the receive packet completion interrupt signal remains asserted. If the two
values are equal (which means that the host has processed all packets that the EMAC has received), the
pending interrupt is de-asserted. The value that the EMAC is expecting is found by reading the receive
channel n completion pointer register (RXnCP).
The EMAC write to the completion pointer actually stores the value in the state RAM. The CPU written
value does not actually change the register value. The host written value is compared to the register
content (which was written by the EMAC) and if the two values are equal then the interrupt is removed;
otherwise, the interrupt remains asserted. The host may process multiple packets prior to acknowledging
an interrupt, or the host may acknowledge interrupts for every packet.
The application software must acknowledge the EMAC control module after processing packets by writing
the appropriate CnTX key to the EMAC End-Of-Interrupt Vector register (MACEOIVECTOR). See
Section 5.12 for the acknowledge key values.
www.ti.com
2.16.1.3 Statistics Interrupt
The statistics level interrupt (STATPEND) is issued when any statistics value is greater than or equal to
8000 0000h, if enabled by setting the STATMASK bit in the MAC interrupt mask set register
(MACINTMASKSET) to 1. The statistics interrupt is removed by writing to decrement any statistics value
greater than 8000 0000h. As long as the most-significant bit of any statistics value is set, the interrupt
remains asserted.
The application software must akcnowledge the EMAC control module after receiving statistics interrupts
by writing the appropriate CnMISC key to the EMAC End-Of-Interrupt Vector register (MACEOIVECTOR).
See Section 5.12 for the acknowledge key values.
2.16.1.4 Host Error Interrupt
The host error interrupt (HOSTPEND) is issued, if enabled, under error conditions dealing with the
handling of buffer descriptors, detected during transmit or receive DMA transactions. The failure of the
software application to supply properly formatted buffer descriptors results in this error. The error bit can
only be cleared by resetting the EMAC module in hardware.
The host error interrupt is enabled by setting the HOSTMASK bit in the MAC interrupt mask set register
(MACINTMASKSET) to 1. The host error interrupt is disabled by clearing the appropriate bit by writing a 1
in the MAC interrupt mask clear register (MACINTMASKCLEAR). The raw and masked host error interrupt
status may be read by reading the MAC interrupt status (unmasked) register (MACINTSTATRAW) and the
MAC interrupt status (masked) register (MACINTSTATMASKED), respectively.
The transmit host error conditions are:
• SOP error
• Ownership bit not set in SOP buffer
• Zero next buffer descriptor pointer with EOP
• Zero buffer pointer
• Zero buffer length
• Packet length error
52
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
The receive host error conditions are:
• Ownership bit not set in input buffer
• Zero buffer pointer
The application software must acknowledge the EMAC control module after receiving host error interrupts
by writing the appropriate CnMISC key to the EMAC End-Of-Interrupt Vector (MACEOIVECTOR). See
Section 5.12 for the acknowledge key values.
2.16.1.5 Receive Threshold Interrupts
Each of the eight receive channels have a corresponding receive threshold interrupt (RXnTHRESHPEND).
The receive threshold interrupts are level interrupts that remain asserted until the triggering condition is
cleared by the host. Each of the eight threshold interrupts may be individually enabled by setting to 1 the
appropriate bit in the RXINTMASKSET register. Each of the eight channel interrupts may be individually
disabled by clearing to zero the appropriate bit by writing a 1 in the receive interrupt mask clear register
(RXINTMASKCLEAR). The raw and masked interrupt receive interrupt status may be read by reading the
receive interrupt status (unmasked) register (RXINTSTATRAW) and the receive interrupt status (masked)
register (RXINTSTATMASKED),respectively.
An RXnTHRESHPEND interrupt bit is asserted when enabled and when the channel’s associated free
buffer count (RXnFREEBUFFER) is less than or equal to the channel’s associated flow control threshold
register (RXnFLOWTHRESH). The receive threshold interrupts use the same free buffer count and
threshold logic as does flow control, but the interrupts are independently enabled from flow control. The
threshold interrupts are intended to give the host an indication that resources are running low for a
particular channel(s).
The applications software must acknowledge the EMAC control module after receiving threshold interrupts
by writing the appropriate CnRXTHRESH key to the EMAC End-Of-Interrupt Vector (MACEOIVECTOR).
See Section 5.12 for the acknowledge key values.
Architecture
2.16.2 MDIO Module Interrupt Events and Requests
The MDIO module generates two interrupt events:
• LINKINT0: Serial interface link change interrupt. Indicates a change in the state of the PHY link
selected by the USERPHYSEL0 register
• USERINT0: Serial interface user command event complete interrupt selected by the USERACCESS0
register
2.16.2.1 Link Change Interrupt
The MDIO module asserts a link change interrupt (LINKINT0) if there is a change in the link state of the
PHY corresponding to the address in the PHYADRMON bit in the MDIO register USERPHYSEL0, and if
the LINKINTENB bit is also set in USERPHYSEL0. This interrupt event is also captured in the
LINKINTRAW bit in the MDIO link status change interrupt register (LINKINTRAW). LINKINTRAW bits 0
and 1 correspond to USERPHYSEL0 and USERPHYSEL1, respectively.
When the interrupt is enabled and generated, the corresponding LINKINTMASKED bit is also set in the
MDIO link status change interrupt register (LINKINTMASKED). The interrupt is cleared by writing back the
same bit to LINKINTMASKED (write to clear).
The application software must acknowledge the EMAC control module after receiving MDIO interrupts by
writing the appropriate CnMISC key to the EMAC End-Of-Interrupt Vector (MACEOIVECTOR). See
Section 5.12 for the acknowledge key values.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
53
© 2011, Texas Instruments Incorporated
Architecture
2.16.2.2 User Access Completion Interrupt
When the GO bit in one of the MDIO register USERACCESS0 transitions from 1 to 0 (indicating
completion of a user access) and the corresponding USERINTMASKSET bit in the MDIO user command
complete interrupt mask set register (USERINTMASKSET) corresponding to USERACCESS0 is set, a
user access completion interrupt (USERINT) is asserted. This interrupt event is also captured in the
USERINTRAW bit in the MDIO user command complete interrupt register (USERINTRAW).
USERINTRAW bits 0 and bit 1 correspond to USERACCESS0 and USERACCESS1, respectively.
When the interrupt is enabled and generated, the corresponding USERINTMASKED bit is also set in the
MDIO user command complete interrupt register (USERINTMASKED). The interrupt is cleared by writing
back the same bit to USERINTMASKED (write to clear).
The application software must acknowledge the EMAC control module after receiving MDIO interrupts by
writing the appropriate CnMISC key to the EMAC End-Of-Interrupt Vector (MACEOIVECTOR). See
Section 5.12 for the acknowledge key values.
2.16.3 Proper Interrupt Processing
All the interrupts signaled from the EMAC and MDIO modules are level driven, so if they remain active,
their level remains constant; the CPU core may require edge- or pulse-triggered interrupts. In order to
properly convert the level-driven interrupt signal to an edge- or pulse-triggered signal, the application
software must make use of the interrupt control logic contained in the EMAC control module.
Section 2.6.3 discusses the interrupt control contained in the EMAC control module. For safe interrupt
processing, upon entry to the ISR, the software application should disable interrupts using the EMAC
control module registers CnRXTHRESHEN, CnRXEN, CnTXEN, CnMISCEN, and then reenable them
upon leaving the ISR. If any interrupt signals are active at that time, this creates another rising edge on
the interrupt signal going to the CPU interrupt controller, thus triggering another interrupt. The EMAC
control module also uses the EMAC control module registers INTCONTROL, CnTXIMAX, and CnRXIMAX
to implement interrupt pacing. The application software must acknowledge the EMAC control module by
writing the appropriate key to the EMAC End-Of-Interrupt Vector (MACEOIVECTOR). See Section 5.12 for
the acknowledge key values.
www.ti.com
2.16.4 Interrupt Multiplexing
The EMAC control module combines different interrupt signals from both the EMAC and MDIO modules
into four interrupt signals (CnRXTHRESHPULSE, CnRXPULSE, CnTXPULSE, CnMISCPULSE) that are
routed to three independent interrupt cores in the control module. Each interrupt core is capable of
relaying all four interrupt signals out of the control module. Some devices may have an individual interrupt
core dedicated to a specific CPU or interrupt controller. This configuration gives users of devices greater
flexibility when allocating system resources for EMAC management.
When an interrupt is generated, the reason for the interrupt can be read from the MAC input vector
register (MACINVECTOR) located in the EMAC memory map. MACINVECTOR combines the status of the
following 28 interrupt signals: TXPENDn, RXPENDn, RXTHRESHPENDn, STATPEND, HOSTPEND,
LINKINT0, and USERINT0.
For more details on the interrupt mapping, see your device-specific System Reference Guide.
54
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
2.17 Power Management
Each of the three main components of the EMAC peripheral can independently be placed in
reduced-power modes to conserve power during periods of low activity. The power management of the
EMAC peripheral is controlled by the processor Power and Sleep Controller (PSC). The PSC acts as a
master controller for power management on behalf of all of the peripherals on the device.
The power conservation modes available for each of the three components of the EMAC/MDIO peripheral
are:
• Idle/Disabled state. This mode stops the clocks going to the peripheral, and prevents all the register
accesses. After reenabling the peripheral from this idle state, all the registers values prior to setting
into the disabled state are restored, and data transmission can proceed. No reinitialization is required.
• Synchronized reset. This state is similar to the Power-on Reset (POR) state, when the processor is
turned-on; reset to the peripheral is asserted, and clocks to the peripheral are gated after that. The
registers are reset to their default value. When powering-up after a synchronized reset, all the EMAC
submodules need to be reinitialized before any data transmission can happen.
For more information on the use of the PSC, see your device-specific System Reference Guide.
2.18 Emulation Considerations
EMAC emulation control is implemented for compatibility with other peripherals. The SOFT and FREE bits
in the emulation control register (EMCONTROL) allow EMAC operation to be suspended.
When the emulation suspend state is entered, the EMAC stops processing receive and transmit frames at
the next frame boundary. Any frame currently in reception or transmission is completed normally without
suspension. For transmission, any complete or partial frame in the transmit cell FIFO is transmitted. For
receive, frames that are detected by the EMAC after the suspend state is entered are ignored. No
statistics are kept for ignored frames.
Table 7 shows how the SOFT and FREE bits affect the operation of the emulation suspend.
Architecture
NOTE: Emulation suspend has not been tested.
Table 7. Emulation Control
SOFT FREE Description
0 0 Normal operation
1 0 Emulation suspend
X 1 Normal operation
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
55
© 2011, Texas Instruments Incorporated
EMAC Control Module Registers
3 EMAC Control Module Registers
Table 8 lists the memory-mapped registers for the EMAC control module. See your device-specific data
manual for the memory address of these registers.
Table 8. EMAC Control Module Registers
Offset Acronym Register Description Section
0h REVID EMAC Control Module Revision ID Register Section 3.1
4h SOFTRESET EMAC Control Module Software Reset Register Section 3.2
Ch INTCONTROL EMAC Control Module Interrupt Control Register Section 3.3
10h C0RXTHRESHEN EMAC Control Module Interrupt Core 0 Receive Threshold Interrupt Section 3.4
Enable Register
14h C0RXEN EMAC Control Module Interrupt Core 0 Receive Interrupt Section 3.5
Enable Register
18h C0TXEN EMAC Control Module Interrupt Core 0 Transmit Interrupt Section 3.6
Enable Register
1Ch C0MISCEN EMAC Control Module Interrupt Core 0 Miscellaneous Interrupt Section 3.7
Enable Register
20h C1RXTHRESHEN EMAC Control Module Interrupt Core 1 Receive Threshold Interrupt Section 3.4
Enable Register
24h C1RXEN EMAC Control Module Interrupt Core 1 Receive Interrupt Section 3.5
Enable Register
28h C1TXEN EMAC Control Module Interrupt Core 1 Transmit Interrupt Section 3.6
Enable Register
2Ch C1MISCEN EMAC Control Module Interrupt Core 1 Miscellaneous Interrupt Section 3.7
Enable Register
30h C2RXTHRESHEN EMAC Control Module Interrupt Core 2 Receive Threshold Interrupt Section 3.4
Enable Register
34h C2RXEN EMAC Control Module Interrupt Core 2 Receive Interrupt Section 3.5
Enable Register
38h C2TXEN EMAC Control Module Interrupt Core 2 Transmit Interrupt Section 3.6
Enable Register
3Ch C2MISCEN EMAC Control Module Interrupt Core 2 Miscellaneous Interrupt Section 3.7
Enable Register
40h C0RXTHRESHSTAT EMAC Control Module Interrupt Core 0 Receive Threshold Interrupt Section 3.8
Status Register
44h C0RXSTAT EMAC Control Module Interrupt Core 0 Receive Interrupt Section 3.9
Status Register
48h C0TXSTAT EMAC Control Module Interrupt Core 0 Transmit Interrupt Section 3.10
Status Register
4Ch C0MISCSTAT EMAC Control Module Interrupt Core 0 Miscellaneous Interrupt Section 3.11
Status Register
50h C1RXTHRESHSTAT EMAC Control Module Interrupt Core 1 Receive Threshold Interrupt Section 3.8
Status Register
54h C1RXSTAT EMAC Control Module Interrupt Core 1 Receive Interrupt Section 3.9
Status Register
58h C1TXSTAT EMAC Control Module Interrupt Core 1 Transmit Interrupt Section 3.10
Status Register
5Ch C1MISCSTAT EMAC Control Module Interrupt Core 1 Miscellaneous Interrupt Section 3.11
Status Register
60h C2RXTHRESHSTAT EMAC Control Module Interrupt Core 2 Receive Threshold Interrupt Section 3.8
Status Register
64h C2RXSTAT EMAC Control Module Interrupt Core 2 Receive Interrupt Section 3.9
Status Register
68h C2TXSTAT EMAC Control Module Interrupt Core 2 Transmit Interrupt Section 3.10
Status Register
6Ch C2MISCSTAT EMAC Control Module Interrupt Core 2 Miscellaneous Interrupt Section 3.11
Status Register
www.ti.com
56
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Control Module Registers
Table 8. EMAC Control Module Registers (continued)
Offset Acronym Register Description Section
70h C0RXIMAX EMAC Control Module Interrupt Core 0 Receive Interrupts Per Section 3.12
74h C0TXIMAX EMAC Control Module Interrupt Core 0 Transmit Interrupts Per Section 3.13
78h C1RXIMAX EMAC Control Module Interrupt Core 1 Receive Interrupts Per Section 3.12
7Ch C1TXIMAX EMAC Control Module Interrupt Core 1 Transmit Interrupts Per Section 3.13
80h C2RXIMAX EMAC Control Module Interrupt Core 2 Receive Interrupts Per Section 3.12
84h C2TXIMAX EMAC Control Module Interrupt Core 2 Transmit Interrupts Per Section 3.13
Millisecond Register
Millisecond Register
Millisecond Register
Millisecond Register
Millisecond Register
Millisecond Register
3.1 EMAC Control Module Revision ID Register (REVID)
The EMAC control module revision ID register (REVID) is shown in Figure 12 and described in Table 9.
Figure 12. EMAC Control Module Revision ID Register (REVID)
31 0
REV
R-4EC8 0100h
LEGEND: R = Read only; -n = value after reset
Table 9. EMAC Control Module Revision ID Register (REVID) Field Descriptions
Bit Field Value Description
31-0 REV Identifies the EMAC Control Module revision.
4EC8 0100h Current revision of the EMAC Control Module.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
57
© 2011, Texas Instruments Incorporated
EMAC Control Module Registers
www.ti.com
3.2 EMAC Control Module Software Reset Register (SOFTRESET)
The EMAC Control Module Software Reset Register (SOFTRESET) is shown in Figure 13 and described
in Table 10.
Figure 13. EMAC Control Module Software Reset Register (SOFTRESET)
31 16
Reserved
R-0
15 1 0
Reserved RESET
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 10. EMAC Control Module Software Reset Register (SOFTRESET)
Bit Field Value Description
31-1 Reserved 0 Reserved
0 RESET Software reset bit for the EMAC Control Module. Clears the interrupt status, control registers, and CPPI
Ram on the clock cycle following a write of 1.
0 No software reset.
1 Perform a software reset.
58
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Control Module Registers
3.3 EMAC Control Module Interrupt Control Register (INTCONTROL)
The EMAC control module interrupt control register (INTCONTROL) is shown in Figure 14 and described
in Table 11 . The settings in the INTCONTROL register are used in conjunction with the CnRXIMAX and
CnTXIMAX registers.
Figure 14. EMAC Control Module Interrupt Control Register (INTCONTROL)
31 24
Reserved
R-0
23 22 21 20 19 18 17 16
Reserved C2TXPACEEN C2RXPACEEN C1TXPACEEN C1RXPACEEN C0TXPACEEN C0RXPACEEN
R-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0
15 12 11 0
Reserved INTPRESCALE
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 11. EMAC Control Module Interrupt Control Register (INTCONTROL)
Bit Field Value Description
31-22 Reserved 0 Reserved
21 C2TXPACEEN Enable pacing for TX interrupt pulse generation on Interrupt Core 2
0 Pacing for TX interrupts on Core 2 disabled.
1 Pacing for TX interrupts on Core 2 enabled.
20 C2RXPACEEN Enable pacing for RX interrupt pulse generation on Interrupt Core 2
0 Pacing for RX interrupts on Core 2 disabled.
1 Pacing for RX interrupts on Core 2 enabled.
19 C1TXPACEEN Enable pacing for TX interrupt pulse generation on Interrupt Core 1
0 Pacing for TX interrupts on Core 1 disabled.
1 Pacing for TX interrupts on Core 1 enabled.
18 C1RXPACEEN Enable pacing for RX interrupt pulse generation on Interrupt Core 1
0 Pacing for RX interrupts on Core 1 disabled.
1 Pacing for RX interrupts on Core 1 enabled.
17 C0TXPACEEN Enable pacing for TX interrupt pulse generation on Interrupt Core 0
0 Pacing for TX interrupts on Core 0 disabled.
1 Pacing for TX interrupts on Core 0 enabled.
16 C0RXPACEEN Enable pacing for RX interrupt pulse generation on Interrupt Core 0
0 Pacing for RX interrupts on Core 0 disabled.
1 Pacing for RX interrupts on Core 0 enabled.
15-12 Reserved 0 Reserved
11-0 INTPRESCALE 0-7FFh Number of internal EMAC module reference clock periods within a 4 μs time window (see
your device-specific data manual for information).
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
59
© 2011, Texas Instruments Incorporated
EMAC Control Module Registers
www.ti.com
3.4 EMAC Control Module Interrupt Core Receive Threshold Interrupt Enable Registers
(C0RXTHRESHEN-C2RXTHRESHEN)
The EMAC control module interrupt core 0-2 receive threshold interrupt enable register
(CnRXTHRESHEN) is shown in Figure 15 and described in Table 12.
Figure 15. EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Enable Register
(CnRXTHRESHEN)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
RXCH7 RXCH6 RXCH5 RXCH4 RXCH3 RXCH2 RXCH1 RXCH0
THRESHEN THRESHEN THRESHEN THRESHEN THRESHEN THRESHEN THRESHEN THRESHEN
R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 12. EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Enable Register
(CnRXTHRESHEN)
Bit Field Value Description
31-8 Reserved 0 Reserved
7 RXCH7THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 7
0 CnRXTHRESHPULSE generation is disabled for RX Channel 7.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 7.
6 RXCH6THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 6
0 CnRXTHRESHPULSE generation is disabled for RX Channel 6.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 6.
5 RXCH5THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 5
0 CnRXTHRESHPULSE generation is disabled for RX Channel 5.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 5.
4 RXCH4THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 4
0 CnRXTHRESHPULSE generation is disabled for RX Channel 4.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 4.
3 RXCH3THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 3
0 CnRXTHRESHPULSE generation is disabled for RX Channel 3.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 3.
2 RXCH2THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 2
0 CnRXTHRESHPULSE generation is disabled for RX Channel 2.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 2.
1 RXCH1THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 1
0 CnRXTHRESHPULSE generation is disabled for RX Channel 1.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 1.
0 RXCH0THRESHEN Enable CnRXTHRESHPULSE interrupt generation for RX Channel 0
0 CnRXTHRESHPULSE generation is disabled for RX Channel 0.
1 CnRXTHRESHPULSE generation is enabled for RX Channel 0.
60
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Control Module Registers
3.5 EMAC Control Module Interrupt Core Receive Interrupt Enable Registers
(C0RXEN-C2RXEN)
The EMAC control module interrupt core 0-2 receive interrupt enable register (CnRXEN) is shown in
Figure 16 and described in Table 13
Figure 16. EMAC Control Module Interrupt Core 0-2 Receive Interrupt Enable Register (CnRXEN)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
RXCH7EN RXCH6EN RXCH5EN RXCH4EN RXCH3EN RXCH2EN RXCH1EN RXCH0EN
R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 13. EMAC Control Module Interrupt Core 0-2 Receive Interrupt Enable Register (CnRXEN)
Bit Field Value Description
31-8 Reserved 0 Reserved
7 RXCH7EN Enable CnRXPULSE interrupt generation for RX Channel 7
0 CnRXPULSE generation is disabled for RX Channel 7.
1 CnRXPULSE generation is enabled for RX Channel 7.
6 RXCH6EN Enable CnRXPULSE interrupt generation for RX Channel 6
0 CnRXPULSE generation is disabled for RX Channel 6.
1 CnRXPULSE generation is enabled for RX Channel 6.
5 RXCH5EN Enable CnRXPULSE interrupt generation for RX Channel 5
0 CnRXPULSE generation is disabled for RX Channel 5.
1 CnRXPULSE generation is enabled for RX Channel 5.
4 RXCH4EN Enable CnRXPULSE interrupt generation for RX Channel 4
0 CnRXPULSE generation is disabled for RX Channel 4.
1 CnRXPULSE generation is enabled for RX Channel 4.
3 RXCH3EN Enable CnRXPULSE interrupt generation for RX Channel 3
0 CnRXPULSE generation is disabled for RX Channel 3.
1 CnRXPULSE generation is enabled for RX Channel 3.
2 RXCH2EN Enable CnRXPULSE interrupt generation for RX Channel 2
0 CnRXPULSE generation is disabled for RX Channel 2.
1 CnRXPULSE generation is enabled for RX Channel 2.
1 RXCH1EN Enable CnRXPULSE interrupt generation for RX Channel 1
0 CnRXPULSE generation is disabled for RX Channel 1.
1 CnRXPULSE generation is enabled for RX Channel 1.
0 RXCH0EN Enable CnRXPULSE interrupt generation for RX Channel 0
0 CnRXPULSE generation is disabled for RX Channel 0.
1 CnRXPULSE generation is enabled for RX Channel 0.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
61
© 2011, Texas Instruments Incorporated
EMAC Control Module Registers
www.ti.com
3.6 EMAC Control Module Interrupt Core Transmit Interrupt Enable Registers
(C0TXEN-C2TXEN)
The EMAC control module interrupt core 0-2 transmit interrupt enable register (CnTXEN) is shown in
Figure 17 and described in Table 14
Figure 17. EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Enable Register (CnTXEN)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
TXCH7EN TXCH6EN TXCH5EN TXCH4EN TXCH3EN TXCH2EN TXCH1EN TXCH0EN
R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 14. EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Enable Register (CnTXEN)
Bit Field Value Description
31-8 Reserved 0 Reserved
7 TXCH7EN Enable CnTXPULSE interrupt generation for TX Channel 7
0 CnTXPULSE generation is disabled for TX Channel 7.
1 CnTXPULSE generation is enabled for TX Channel 7.
6 TXCH6EN Enable CnTXPULSE interrupt generation for TX Channel 6
0 CnTXPULSE generation is disabled for TX Channel 6.
1 CnTXPULSE generation is enabled for TX Channel 6.
5 TXCH5EN Enable CnTXPULSE interrupt generation for TX Channel 5
0 CnTXPULSE generation is disabled for TX Channel 5.
1 CnTXPULSE generation is enabled for TX Channel 5.
4 TXCH4EN Enable CnTXPULSE interrupt generation for TX Channel 4
0 CnTXPULSE generation is disabled for TX Channel 4.
1 CnTXPULSE generation is enabled for TX Channel 4.
3 TXCH3EN Enable CnTXPULSE interrupt generation for TX Channel 3
0 CnTXPULSE generation is disabled for TX Channel 3.
1 CnTXPULSE generation is enabled for TX Channel 3.
2 TXCH2EN Enable CnTXPULSE interrupt generation for TX Channel 2
0 CnTXPULSE generation is disabled for TX Channel 2.
1 CnTXPULSE generation is enabled for TX Channel 2.
1 TXCH1EN Enable CnTXPULSE interrupt generation for TX Channel 1
0 CnTXPULSE generation is disabled for TX Channel 1.
1 CnTXPULSE generation is enabled for TX Channel 1.
0 TXCH0EN Enable CnTXPULSE interrupt generation for TX Channel 0
0 CnTXPULSE generation is disabled for TX Channel 0.
1 CnTXPULSE generation is enabled for TX Channel 0.
62
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Control Module Registers
3.7 EMAC Control Module Interrupt Core Miscellaneous Interrupt Enable Registers
(C0MISCEN-C2MISCEN)
The EMAC control module interrupt core 0-2 miscellaneous interrupt enable register (CnMISCEN) is
shown in Figure 18 and described in Table 15
Figure 18. EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Enable Register
(CnMISCEN)
31 16
Reserved
R-0
15 4 3 2 1 0
Reserved STATPENDEN HOSTPENDEN LINKINT0EN USERINT0EN
R-0 R/W-0 R/W-0 R/W-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 15. EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Enable Register
(CnMISCEN)
Bit Field Value Description
31-4 Reserved 0 Reserved
3 STATPENDEN Enable CnMISCPULSE interrupt generation when EMAC statistics interrupts are generated
0 CnMISCPULSE generation is disabled for EMAC STATPEND interrupts.
1 CnMISCPULSE generation is enabled for EMAC STATPEND interrupts.
2 HOSTPENDEN Enable CnMISCPULSE interrupt generation when EMAC host interrupts are generated
0 CnMISCPULSE generation is disabled for EMAC HOSTPEND interrupts.
1 CnMISCPULSE generation is enabled for EMAC HOSTPEND interrupts.
1 LINKINT0EN Enable CnMISCPULSE interrupt generation when MDIO LINKINT0 interrupts (corresponding to
0 USERINT0EN Enable CnMISCPULSE interrupt generation when MDIO USERINT0 interrupts (corresponding
USERPHYSEL0) are generated
0 CnMISCPULSE generation is disabled for MDIO LINKINT0 interrupts.
1 CnMISCPULSE generation is enabled for MDIO LINKINT0 interrupts.
to USERACCESS0) are generated
0 CnMISCPULSE generation is disabled for MDIO USERINT0.
1 CnMISCPULSE generation is enabled for MDIO USERINT0.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
63
© 2011, Texas Instruments Incorporated
EMAC Control Module Registers
www.ti.com
3.8 EMAC Control Module Interrupt Core Receive Threshold Interrupt Status Registers
(C0RXTHRESHSTAT-C2RXTHRESHSTAT)
The EMAC control module interrupt core 0-2 receive threshold interrupt status register
(CnRXTHRESHSTAT) is shown in Figure 19 and described in Table 16
Figure 19. EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Status Register
(CnRXTHRESHSTAT)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
RXCH7THRESH RXCH6THRESH RXCH5THRESH RXCH4THRESH RXCH3THRESH RXCH2THRESH RXCH1THRESH RXCH0THRESH
STAT STAT STAT STAT STAT STAT STAT STAT
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 16. EMAC Control Module Interrupt Core 0-2 Receive Threshold Interrupt Status Register
(CnRXTHRESHSTAT)
Bit Field Value Description
31-8 Reserved 0 Reserved
7 RXCH7THRESHSTAT Interrupt status for RX Channel 7 masked by the CnRXTHRESHEN register
0 RX Channel 7 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 7 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
6 RXCH6THRESHSTAT Interrupt status for RX Channel 6 masked by the CnRXTHRESHEN register
0 RX Channel 6 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 6 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
5 RXCH5THRESHSTAT Interrupt status for RX Channel 5 masked by the CnRXTHRESHEN register
0 RX Channel 5 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 5 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
4 RXCH4THRESHSTAT Interrupt status for RX Channel 4 masked by the CnRXTHRESHEN register
0 RX Channel 4 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 4 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
3 RXCH3THRESHSTAT Interrupt status for RX Channel 3 masked by the CnRXTHRESHEN register
0 RX Channel 3 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 3 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
2 RXCH2THRESHSTAT Interrupt status for RX Channel 2 masked by the CnRXTHRESHEN register
0 RX Channel 2 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 2 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
1 RXCH1THRESHSTAT Interrupt status for RX Channel 1 masked by the CnRXTHRESHEN register
0 RX Channel 1 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 1 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
0 RXCH0THRESHSTAT Interrupt status for RX Channel 0 masked by the CnRXTHRESHEN register
0 RX Channel 0 does not satisfy conditions to generate a CnRXTHRESHPULSE interrupt.
1 RX Channel 0 satisfies conditions to generate a CnRXTHRESHPULSE interrupt.
64
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Control Module Registers
3.9 EMAC Control Module Interrupt Core Receive Interrupt Status Registers
(C0RXSTAT-C2RXSTAT)
The EMAC control module interrupt core 0-2 receive interrupt status register (CnRXSTAT) is shown in
Figure 20 and described in Table 17
Figure 20. EMAC Control Module Interrupt Core 0-2 Receive Interrupt Status Register (CnRXSTAT)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
RXCH7STAT RXCH6STAT RXCH5STAT RXCH4STAT RXCH3STAT RXCH2STAT RXCH1STAT RXCH0STAT
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 17. EMAC Control Module Interrupt Core 0-2 Receive Interrupt Status Register (CnRXSTAT)
Bit Field Value Description
31-8 Reserved 0 Reserved
7 RXCH7STAT Interrupt status for RX Channel 7 masked by the CnRXEN register
0 RX Channel 7 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 7 satisfies conditions to generate a CnRXPULSE interrupt.
6 RXCH6STAT Interrupt status for RX Channel 6 masked by the CnRXEN register
0 RX Channel 6 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 6 satisfies conditions to generate a CnRXPULSE interrupt.
5 RXCH5STAT Interrupt status for RX Channel 5 masked by the CnRXEN register
0 RX Channel 5 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 5 satisfies conditions to generate a CnRXPULSE interrupt.
4 RXCH4STAT Interrupt status for RX Channel 4 masked by the CnRXEN register
0 RX Channel 4 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 4 satisfies conditions to generate a CnRXPULSE interrupt.
3 RXCH3STAT Interrupt status for RX Channel 3 masked by the CnRXEN register
0 RX Channel 3 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 3 satisfies conditions to generate a CnRXPULSE interrupt.
2 RXCH2STAT Interrupt status for RX Channel 2 masked by the CnRXEN register
0 RX Channel 2 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 2 satisfies conditions to generate a CnRXPULSE interrupt.
1 RXCH1STAT Interrupt status for RX Channel 1 masked by the CnRXEN register
0 RX Channel 1 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 1 satisfies conditions to generate a CnRXPULSE interrupt.
0 RXCH0STAT Interrupt status for RX Channel 0 masked by the CnRXEN register
0 RX Channel 0 does not satisfy conditions to generate a CnRXPULSE interrupt.
1 RX Channel 0 satisfies conditions to generate a CnRXPULSE interrupt.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
65
© 2011, Texas Instruments Incorporated
EMAC Control Module Registers
www.ti.com
3.10 EMAC Control Module Interrupt Core Transmit Interrupt Status Registers
(C0TXSTAT-C2TXSTAT)
The EMAC control module interrupt core 0-2 transmit interrupt status register (CnTXSTAT) is shown in
Figure 21 and described in Table 18
Figure 21. EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Status Register (CnTXSTAT)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
TXCH7STAT TXCH6STAT TXCH5STAT TXCH4STAT TXCH3STAT TXCH2STAT TXCH1STAT TXCH0STAT
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 18. EMAC Control Module Interrupt Core 0-2 Transmit Interrupt Status Register (CnTXSTAT)
Bit Field Value Description
31-8 Reserved 0 Reserved
7 TXCH7STAT Interrupt status for TX Channel 7 masked by the CnTXEN register
0 TX Channel 7 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 7 satisfies conditions to generate a CnTXPULSE interrupt.
6 TXCH6STAT Interrupt status for TX Channel 6 masked by the CnTXEN register
0 TX Channel 6 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 6 satisfies conditions to generate a CnTXPULSE interrupt.
5 TXCH5STAT Interrupt status for TX Channel 5 masked by the CnTXEN register
0 TX Channel 5 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 5 satisfies conditions to generate a CnTXPULSE interrupt.
4 TXCH4STAT Interrupt status for TX Channel 4 masked by the CnTXEN register
0 TX Channel 4 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 4 satisfies conditions to generate a CnTXPULSE interrupt.
3 TXCH3STAT Interrupt status for TX Channel 3 masked by the CnTXEN register
0 TX Channel 3 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 3 satisfies conditions to generate a CnTXPULSE interrupt.
2 TXCH2STAT Interrupt status for TX Channel 2 masked by the CnTXEN register
0 TX Channel 2 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 2 satisfies conditions to generate a CnTXPULSE interrupt.
1 TXCH1STAT Interrupt status for TX Channel 1 masked by the CnTXEN register
0 TX Channel 1 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 1 satisfies conditions to generate a CnTXPULSE interrupt.
0 TXCH0STAT Interrupt status for TX Channel 0 masked by the CnTXEN register
0 TX Channel 0 does not satisfy conditions to generate a CnTXPULSE interrupt.
1 TX Channel 0 satisfies conditions to generate a CnTXPULSE interrupt.
66
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Control Module Registers
3.11 EMAC Control Module Interrupt Core Miscellaneous Interrupt Status Registers
(C0MISCSTAT-C2MISCSTAT)
The EMAC control module interrupt core 0-2 miscellaneous interrupt status register (CnMISCSTAT) is
shown in Figure 22 and described in Table 19
Figure 22. EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Status Register
(CnMISCSTAT)
31 16
Reserved
R-0
15 4 3 2 1 0
Reserved STATPENDSTAT HOSTPENDSTAT LINKINT0STAT USERINT0STAT
R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 19. EMAC Control Module Interrupt Core 0-2 Miscellaneous Interrupt Status Register
(CnMISCSTAT)
Bit Field Value Description
31-4 Reserved 0 Reserved
3 STATPENDSTAT Interrupt status for EMAC STATPEND masked by the CnMISCEN register
0 EMAC STATPEND does not satisfy conditions to generate a CnMISCPULSE interrupt.
1 EMAC STATPEND satisfies conditions to generate a CnMISCPULSE interrupt.
2 HOSTPENDSTAT Interrupt status for EMAC HOSTPEND masked by the CnMISCEN register
0 EMAC HOSTPEND does not satisfy conditions to generate a CnMISCPULSE interrupt.
1 EMAC HOSTPEND satisfies conditions to generate a CnMISCPULSE interrupt.
1 LINKINT0STAT Interrupt status for MDIO LINKINT0 masked by the CnMISCEN register
0 MDIO LINKINT0 does not satisfy conditions to generate a CnMISCPULSE interrupt.
1 MDIO LINKINT0 satisfies conditions to generate a CnMISCPULSE interrupt.
0 USERINT0STAT Interrupt status for MDIO USERINT0 masked by the CnMISCEN register
0 MDIO USERINT0 does not satisfy conditions to generate a CnMISCPULSE interrupt.
1 MDIO USERINT0 satisfies conditions to generate a CnMISCPULSE interrupt.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
67
© 2011, Texas Instruments Incorporated
EMAC Control Module Registers
www.ti.com
3.12 EMAC Control Module Interrupt Core Receive Interrupts Per Millisecond Registers
(C0RXIMAX-C2RXIMAX)
The EMAC control module interrupt core 0-2 receive interrupts per millisecond register (CnRXIMAX) is
shown in Figure 23 and described in Table 20
Figure 23. EMAC Control Module Interrupt Core 0-2 Receive Interrupts Per Millisecond Register
(CnRXIMAX)
31 16
Reserved
R-0
15 6 5 0
Reserved RXIMAX
R-0 R/W-0
LEGEND: R = Read only; R/W = Read/Write; -n = value after reset
Table 20. EMAC Control Module Interrupt Core 0-2 Receive Interrupts Per Millisecond Register
(CnRXIMAX)
Bit Field Value Description
31-6 Reserved 0 Reserved
5-0 RXIMAX 2-3Fh RXIMAX is the desired number of CnRXPULSE interrupts generated per millisecond when
CnRXPACEEN is enabled in INTCONTROL.
The pacing mechanism can be described by the following pseudo-code:
while(1) {
interrupt_count = 0;
/* Count interrupts over a 1ms window */
for(i = 0; i < INTCONTROL[INTPRESCALE]*250; i++) {
interrupt_count += NEW_INTERRUPT_EVENTS();
if(i < INTCONTROL[INTPRESCALE]*pace_counter)
BLOCK_EMAC_INTERRUPTS();
else
ALLOW_EMAC_INTERRUPTS();
}
ALLOW_EMAC_INTERRUPTS();
if(interrupt_count > 2*RXIMAX)
pace_counter = 255;
else if(interrupt_count > 1.5*RXIMAX)
pace_counter = previous_pace_counter*2 + 1;
else if(interrupt_count > 1.0*RXIMAX)
pace_counter = previous_pace_counter + 1;
else if(interrupt_count > 0.5*RXIMAX)
pace_counter = previous_pace_counter - 1;
else if(interrupt_count != 0)
pace_counter = previous_pace_counter/2;
else
pace_counter = 0;
previous_pace_counter = pace_counter;
}
68
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Control Module Registers
3.13 EMAC Control Module Interrupt Core Transmit Interrupts Per Millisecond Registers
(C0TXIMAX-C2TXIMAX)
The EMAC control module interrupt core 0-2 transmit interrupts per millisecond register (CnTXIMAX) is
shown in Figure 24 and described in Table 21
Figure 24. EMAC Control Module Interrupt Core 0-2 Transmit Interrupts Per Millisecond Register
(CnTXIMAX)
31 16
Reserved
R-0
15 6 5 0
Reserved TXIMAX
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 21. EMAC Control Module Interrupt Core 0-2 Transmit Interrupts Per Millisecond Register
(CnTXIMAX)
Bit Field Value Description
31-6 Reserved 0 Reserved
5-0 TXIMAX 2-3Fh TXIMAX is the desired number of CnTXPULSE interrupts generated per millisecond when
CnTXPACEEN is enabled in INTCONTROL.
The pacing mechanism can be described by the following pseudo-code:
while(1) {
interrupt_count = 0;
/* Count interrupts over a 1ms window */
for(i = 0; i < INTCONTROL[INTPRESCALE]*250; i++) {
interrupt_count += NEW_INTERRUPT_EVENTS();
if(i < INTCONTROL[INTPRESCALE]*pace_counter)
BLOCK_EMAC_INTERRUPTS();
else
ALLOW_EMAC_INTERRUPTS();
}
ALLOW_EMAC_INTERRUPTS();
if(interrupt_count > 2*TXIMAX)
pace_counter = 255;
else if(interrupt_count > 1.5*TXIMAX)
pace_counter = previous_pace_counter*2 + 1;
else if(interrupt_count > 1.0*TXIMAX)
pace_counter = previous_pace_counter + 1;
else if(interrupt_count > 0.5*TXIMAX)
pace_counter = previous_pace_counter - 1;
else if(interrupt_count != 0)
pace_counter = previous_pace_counter/2;
else
pace_counter = 0;
previous_pace_counter = pace_counter;
}
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
69
© 2011, Texas Instruments Incorporated
MDIO Registers
4 MDIO Registers
Table 22 lists the memory-mapped registers for the MDIO module. See your device-specific data manual
for the memory address of these registers.
Offset Acronym Register Description Section
0h REVID MDIO Revision ID Register Section 4.1
4h CONTROL MDIO Control Register Section 4.2
8h ALIVE PHY Alive Status register Section 4.3
Ch LINK PHY Link Status Register Section 4.4
10h LINKINTRAW MDIO Link Status Change Interrupt (Unmasked) Register Section 4.5
14h LINKINTMASKED MDIO Link Status Change Interrupt (Masked) Register Section 4.6
20h USERINTRAW MDIO User Command Complete Interrupt (Unmasked) Register Section 4.7
24h USERINTMASKED MDIO User Command Complete Interrupt (Masked) Register Section 4.8
28h USERINTMASKSET MDIO User Command Complete Interrupt Mask Set Register Section 4.9
2Ch USERINTMASKCLEAR MDIO User Command Complete Interrupt Mask Clear Register Section 4.10
80h USERACCESS0 MDIO User Access Register 0 Section 4.11
84h USERPHYSEL0 MDIO User PHY Select Register 0 Section 4.12
88h USERACCESS1 MDIO User Access Register 1 Section 4.13
8Ch USERPHYSEL1 MDIO User PHY Select Register 1 Section 4.14
www.ti.com
Table 22. Management Data Input/Output (MDIO) Registers
4.1 MDIO Revision ID Register (REVID)
The MDIO revision ID register (REVID) is shown in Figure 25 and described in Table 23.
Figure 25. MDIO Revision ID Register (REVID)
31 0
REV
R-0007 0104h
LEGEND: R = Read only; -n = value after reset
Table 23. MDIO Revision ID Register (REVID) Field Descriptions
Bit Field Value Description
31-0 REV Identifies the MDIO Module revision.
0007 0104h Current revision of the MDIO Module.
70
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
MDIO Registers
4.2 MDIO Control Register (CONTROL)
The MDIO control register (CONTROL) is shown in Figure 26 and described in Table 24.
Figure 26. MDIO Control Register (CONTROL)
31 30 29 28 24 23 21 20 19 18 17 16
IDLE ENABLE Rsvd HIGHEST_USER_CHANNEL Reserved PREAMBLE FAULT FAULTENB Reserved
R-1 R/W-0 R-0 R-1 R-0 R/W-0 R/W1C-0 R/W-0 R-0
15 0
CLKDIV
R/W-FFh
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 24. MDIO Control Register (CONTROL) Field Descriptions
Bit Field Value Description
31 IDLE State machine IDLE status bit.
0 State machine is not in idle state.
1 State machine is in idle state.
30 ENABLE State machine enable control bit. If the MDIO state machine is active at the time it is
29 Reserved 0 Reserved
28-24 HIGHEST_USER_CHANNEL 0-1Fh Highest user channel that is available in the module. It is currently set to 1. This
23-21 Reserved 0 Reserved
20 PREAMBLE Preamble disable
19 FAULT Fault indicator. This bit is set to 1 if the MDIO pins fail to read back what the device
18 FAULTENB Fault detect enable. This bit has to be set to 1 to enable the physical layer fault
17-16 Reserved 0 Reserved
15-0 CLKDIV 0-FFFFh Clock Divider bits. This field specifies the division ratio between the peripheral clock
disabled, it will complete the current operation before halting and setting the idle bit.
0 Disables the MDIO state machine.
1 Enable the MDIO state machine.
implies that MDIOUserAccess1 is the highest available user access channel.
0 Standard MDIO preamble is used.
1 Disables this device from sending MDIO frame preambles.
is driving onto them. This indicates a physical layer fault and the module state
machine is reset. Writing a 1 to this bit clears this bit, writing a 0 has no effect.
0 No failure
1 Physical layer fault; the MDIO state machine is reset.
detection.
0 Disables the physical layer fault detection.
1 Enables the physical layer fault detection.
and the frequency of MDIO_CLK. MDIO_CLK is disabled when CLKDIV is cleared to
0. MDIO_CLK frequency = peripheral clock frequency/(CLKDIV + 1).
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
71
© 2011, Texas Instruments Incorporated
MDIO Registers
www.ti.com
4.3 PHY Acknowledge Status Register (ALIVE)
The PHY acknowledge status register (ALIVE) is shown in Figure 27 and described in Table 25.
Figure 27. PHY Acknowledge Status Register (ALIVE)
31 0
ALIVE
R/W1C-0
LEGEND: R/W = Read/Write; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 25. PHY Acknowledge Status Register (ALIVE) Field Descriptions
Bit Field Value Description
31-0 ALIVE MDIO Alive bits. Each of the 32 bits of this register is set if the most recent access to the PHY with
address corresponding to the register bit number was acknowledged by the PHY; the bit is reset if the
PHY fails to acknowledge the access. Both the user and polling accesses to a PHY will cause the
corresponding alive bit to be updated. The alive bits are only meant to be used to give an indication of the
presence or not of a PHY with the corresponding address. Writing a 1 to any bit will clear it, writing a 0
has no effect.
0 The PHY fails to acknowledge the access.
1 The most recent access to the PHY with an address corresponding to the register bit number was
acknowledged by the PHY.
4.4 PHY Link Status Register (LINK)
The PHY link status register (LINK) is shown in Figure 28 and described in Table 26.
Figure 28. PHY Link Status Register (LINK)
31 0
LINK
R-0
LEGEND: R = Read only; -n = value after reset
Table 26. PHY Link Status Register (LINK) Field Descriptions
Bit Field Value Description
31-0 LINK MDIO Link state bits. This register is updated after a read of the generic status register of a PHY. The bit
is set if the PHY with the corresponding address has link and the PHY acknowledges the read
transaction. The bit is reset if the PHY indicates it does not have link or fails to acknowledge the read
transaction. Writes to the register have no effect.
0 The PHY indicates it does not have a link or fails to acknowledge the read transaction
1 The PHY with the corresponding address has a link and the PHY acknowledges the read transaction.
72
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
MDIO Registers
4.5 MDIO Link Status Change Interrupt (Unmasked) Register (LINKINTRAW)
The MDIO link status change interrupt (unmasked) register (LINKINTRAW) is shown in Figure 29 and
described in Table 27.
Figure 29. MDIO Link Status Change Interrupt (Unmasked) Register (LINKINTRAW)
31 16
Reserved
R-0
15 2 1 0
Reserved USERPHY1 USERPHY0
R-0 R/W1C-0 R/W1C-0
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 27. MDIO Link Status Change Interrupt (Unmasked) Register (LINKINTRAW)
Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 USERPHY1 MDIO Link change event, raw value. When asserted, the bit indicates that there was an MDIO link
0 USERPHY0 MDIO Link change event, raw value. When asserted, the bit indicates that there was an MDIO link
change event (that is, change in the LINK register) corresponding to the PHY address in
USERPHYSEL1. Writing a 1 will clear the event, writing a 0 has no effect.
0 No MDIO link change event.
1 An MDIO link change event (change in the LINK register) corresponding to the PHY address in
MDIO user PHY select register USERPHYSEL1
change event (that is, change in the LINK register) corresponding to the PHY address in
USERPHYSEL0. Writing a 1 will clear the event, writing a 0 has no effect.
0 No MDIO link change event.
1 An MDIO link change event (change in the LINK register) corresponding to the PHY address in
MDIO user PHY select register USERPHYSEL0
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
73
© 2011, Texas Instruments Incorporated
MDIO Registers
www.ti.com
4.6 MDIO Link Status Change Interrupt (Masked) Register (LINKINTMASKED)
The MDIO link status change interrupt (masked) register (LINKINTMASKED) is shown in Figure 30 and
described in Table 28.
Figure 30. MDIO Link Status Change Interrupt (Masked) Register (LINKINTMASKED)
31 16
Reserved
R-0
15 2 1 0
Reserved USERPHY1 USERPHY0
R-0 R/W1C-0 R/W1C-0
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 28. MDIO Link Status Change Interrupt (Masked) Register (LINKINTMASKED)
Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 USERPHY1 MDIO Link change interrupt, masked value. When asserted, the bit indicates that there was an
0 USERPHY0 MDIO Link change interrupt, masked value. When asserted, the bit indicates that there was an
MDIO link change event (that is, change in the LINK register) corresponding to the PHY address in
USERPHYSEL1 and the corresponding LINKINTENB bit was set. Writing a 1 will clear the event,
writing a 0 has no effect.
0 No MDIO link change event.
1 An MDIO link change event (change in the LINK register) corresponding to the PHY address in
MDIO user PHY select register USERPHYSEL1 and the LINKINTENB bit in USERPHYSEL1 is set
to 1.
MDIO link change event (that is, change in the LINK register) corresponding to the PHY address in
USERPHYSEL0 and the corresponding LINKINTENB bit was set. Writing a 1 will clear the event,
writing a 0 has no effect.
0 No MDIO link change event.
1 An MDIO link change event (change in the LINK register) corresponding to the PHY address in
MDIO user PHY select register USERPHYSEL0 and the LINKINTENB bit in USERPHYSEL0 is set
to 1.
74
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
MDIO Registers
4.7 MDIO User Command Complete Interrupt (Unmasked) Register (USERINTRAW)
The MDIO user command complete interrupt (unmasked) register (USERINTRAW) is shown in Figure 31
and described in Table 29.
Figure 31. MDIO User Command Complete Interrupt (Unmasked) Register (USERINTRAW)
31 16
Reserved
R-0
15 2 1 0
Reserved USERACCESS1 USERACCESS0
R-0 R/W1C-0 R/W1C-0
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 29. MDIO User Command Complete Interrupt (Unmasked) Register (USERINTRAW)
Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 USERACCESS1 MDIO User command complete event bit. When asserted, the bit indicates that the previously
0 USERACCESS0 MDIO User command complete event bit. When asserted, the bit indicates that the previously
scheduled PHY read or write command using the USERACCESS1 register has completed.
Writing a 1 will clear the event, writing a 0 has no effect.
0 No MDIO user command complete event.
1 The previously scheduled PHY read or write command using MDIO user access register
USERACCESS1 has completed.
scheduled PHY read or write command using the USERACCESS0 register has completed.
Writing a 1 will clear the event, writing a 0 has no effect.
0 No MDIO user command complete event.
1 The previously scheduled PHY read or write command using MDIO user access register
USERACCESS0 has completed.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
75
© 2011, Texas Instruments Incorporated
MDIO Registers
www.ti.com
4.8 MDIO User Command Complete Interrupt (Masked) Register (USERINTMASKED)
The MDIO user command complete interrupt (masked) register (USERINTMASKED) is shown in
Figure 32 and described in Table 30.
Figure 32. MDIO User Command Complete Interrupt (Masked) Register (USERINTMASKED)
31 16
Reserved
R-0
15 2 1 0
Reserved USERACCESS1 USERACCESS0
R-0 R/W1C-0 R/W1C-0
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 30. MDIO User Command Complete Interrupt (Masked) Register (USERINTMASKED)
Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 USERACCESS1 Masked value of MDIO User command complete interrupt. When asserted, The bit indicates
0 USERACCESS0 Masked value of MDIO User command complete interrupt. When asserted, The bit indicates
that the previously scheduled PHY read or write command using that particular
USERACCESS1 register has completed. Writing a 1 will clear the interrupt, writing a 0 has no
effect.
0 No MDIO user command complete event.
1 The previously scheduled PHY read or write command using MDIO user access register
USERACCESS1 has completed and the corresponding bit in USERINTMASKSET is set to 1.
that the previously scheduled PHY read or write command using that particular
USERACCESS0 register has completed. Writing a 1 will clear the interrupt, writing a 0 has no
effect.
0 No MDIO user command complete event.
1 The previously scheduled PHY read or write command using MDIO user access register
USERACCESS0 has completed and the corresponding bit in USERINTMASKSET is set to 1.
76
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
MDIO Registers
4.9 MDIO User Command Complete Interrupt Mask Set Register (USERINTMASKSET)
The MDIO user command complete interrupt mask set register (USERINTMASKSET) is shown in
Figure 33 and described in Table 31.
Figure 33. MDIO User Command Complete Interrupt Mask Set Register (USERINTMASKSET)
31 16
Reserved
R-0
15 2 1 0
Reserved USERACCESS1 USERACCESS0
R-0 R/W1S-0 R/W1S-0
LEGEND: R/W = Read/Write; R = Read only; W1S = Write 1 to set (writing a 0 has no effect); -n = value after reset
Table 31. MDIO User Command Complete Interrupt Mask Set Register (USERINTMASKSET)
Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 USERACCESS1 MDIO user interrupt mask set for USERINTMASKED[1]. Setting a bit to 1 will enable MDIO user
0 USERACCESS0 MDIO user interrupt mask set for USERINTMASKED[0]. Setting a bit to 1 will enable MDIO user
command complete interrupts for the USERACCESS1 register. MDIO user interrupt for
USERACCESS1 is disabled if the corresponding bit is 0. Writing a 0 to this bit has no effect.
0 MDIO user command complete interrupts for the MDIO user access register USERACCESS0 is
disabled.
1 MDIO user command complete interrupts for the MDIO user access register USERACCESS0 is
enabled.
command complete interrupts for the USERACCESS0 register. MDIO user interrupt for
USERACCESS0 is disabled if the corresponding bit is 0. Writing a 0 to this bit has no effect.
0 MDIO user command complete interrupts for the MDIO user access register USERACCESS0 is
disabled.
1 MDIO user command complete interrupts for the MDIO user access register USERACCESS0 is
enabled.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
77
© 2011, Texas Instruments Incorporated
MDIO Registers
www.ti.com
4.10 MDIO User Command Complete Interrupt Mask Clear Register
(USERINTMASKCLEAR)
The MDIO user command complete interrupt mask clear register (USERINTMASKCLEAR) is shown in
Figure 34 and described in Table 32.
Figure 34. MDIO User Command Complete Interrupt Mask Clear Register (USERINTMASKCLEAR)
31 16
Reserved
R-0
15 2 1 0
Reserved USERACCESS1 USERACCESS0
R-0 R/W1C-0 R/W1C-0
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 32. MDIO User Command Complete Interrupt Mask Clear Register (USERINTMASKCLEAR)
Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 USERACCESS1 MDIO user command complete interrupt mask clear for USERINTMASKED[1]. Setting the bit to
0 USERACCESS0 MDIO user command complete interrupt mask clear for USERINTMASKED[0]. Setting the bit to
1 will disable further user command complete interrupts for USERACCESS1. Writing a 0 to this
bit has no effect.
0 MDIO user command complete interrupts for the MDIO user access register USERACCESS1 is
enabled.
1 MDIO user command complete interrupts for the MDIO user access register USERACCESS1 is
disabled.
1 will disable further user command complete interrupts for USERACCESS0. Writing a 0 to this
bit has no effect.
0 MDIO user command complete interrupts for the MDIO user access register USERACCESS0 is
enabled.
1 MDIO user command complete interrupts for the MDIO user access register USERACCESS0 is
disabled.
78
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
MDIO Registers
4.11 MDIO User Access Register 0 (USERACCESS0)
The MDIO user access register 0 (USERACCESS0) is shown in Figure 35 and described in Table 33.
Figure 35. MDIO User Access Register 0 (USERACCESS0)
31 30 29 28 26 25 21 20 16
GO WRITE ACK Reserved REGADR PHYADR
R/W1S-0 R/W-0 R/W-0 R-0 R/W-0 R/W-0
15 0
DATA
R/W-0
LEGEND: R/W = Read/Write; R = Read only; W1S = Write 1 to set (writing a 0 has no effect); -n = value after reset
Table 33. MDIO User Access Register 0 (USERACCESS0) Field Descriptions
Bit Field Value Description
31 GO 0-1 Go bit. Writing a 1 to this bit causes the MDIO state machine to perform an MDIO access when it
30 WRITE Write enable bit. Setting this bit to 1 causes the MDIO transaction to be a register write; otherwise,
0 The user command is a read operation.
1 The user command is a write operation.
29 ACK 0-1 Acknowledge bit. This bit is set if the PHY acknowledged the read transaction.
28-26 Reserved 0 Reserved
25-21 REGADR 0-1Fh Register address bits. This field specifies the PHY register to be accessed for this transaction
20-16 PHYADR 0-1Fh PHY address bits. This field specifies the PHY to be accessed for this transaction.
15-0 DATA 0-FFFFh User data bits. These bits specify the data value read from or to be written to the specified PHY
is convenient for it to do so; this is not an instantaneous process. Writing a 0 to this bit has no
effect. This bit is writeable only if the MDIO state machine is enabled. This bit will self clear when
the requested access has been completed. Any writes to USERACCESS0 are blocked when the
GO bit is 1.
it is a register read.
register.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
79
© 2011, Texas Instruments Incorporated
MDIO Registers
www.ti.com
4.12 MDIO User PHY Select Register 0 (USERPHYSEL0)
The MDIO user PHY select register 0 (USERPHYSEL0) is shown in Figure 36 and described in Table 34.
Figure 36. MDIO User PHY Select Register 0 (USERPHYSEL0)
31 16
Reserved
R-0
15 8 7 6 5 4 0
Reserved LINKSEL LINKINTENB Rsvd PHYADRMON
R-0 R/W-0 R/W-0 R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 34. MDIO User PHY Select Register 0 (USERPHYSEL0) Field Descriptions
Bit Field Value Description
31-8 Reserved 0 Reserved
7 LINKSEL Link status determination select bit. Default value is 0, which implies that the link status is
6 LINKINTENB Link change interrupt enable. Set to 1 to enable link change status interrupts for PHY address
5 Reserved 0 Reserved
4-0 PHYADRMON 0-1Fh PHY address whose link status is to be monitored.
determined by the MDIO state machine. This is the only option supported on this device.
0 The link status is determined by the MDIO state machine.
1 Not supported.
specified in PHYADRMON. Link change interrupts are disabled if this bit is cleared to 0.
0 Link change interrupts are disabled.
1 Link change status interrupts for PHY address specified in PHYADDRMON bits are enabled.
80
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
MDIO Registers
4.13 MDIO User Access Register 1 (USERACCESS1)
The MDIO user access register 1 (USERACCESS1) is shown in Figure 37 and described in Table 35.
Figure 37. MDIO User Access Register 1 (USERACCESS1)
31 30 29 28 26 25 21 20 16
GO WRITE ACK Reserved REGADR PHYADR
R/W1S-0 R/W-0 R/W-0 R-0 R/W-0 R/W-0
15 0
DATA
R/W-0
LEGEND: R/W = Read/Write; R = Read only; W1S = Write 1 to set (writing a 0 has no effect); -n = value after reset
Table 35. MDIO User Access Register 1 (USERACCESS1) Field Descriptions
Bit Field Value Description
31 GO 0-1 Go bit. Writing 1 to this bit causes the MDIO state machine to perform an MDIO access when it is
30 WRITE Write enable bit. Setting this bit to 1 causes the MDIO transaction to be a register write; otherwise,
0 The user command is a read operation.
1 The user command is a write operation.
29 ACK 0-1 Acknowledge bit. This bit is set if the PHY acknowledged the read transaction.
28-26 Reserved 0 Reserved
25-21 REGADR 0-1Fh Register address bits. This field specifies the PHY register to be accessed for this transaction
20-16 PHYADR 0-1Fh PHY address bits. This field specifies the PHY to be accessed for this transaction.
15-0 DATA 0-FFFFh User data bits. These bits specify the data value read from or to be written to the specified PHY
convenient for it to do so; this is not an instantaneous process. Writing 0 to this bit has no effect.
This bit is writeable only if the MDIO state machine is enabled. This bit will self clear when the
requested access has been completed. Any writes to USERACCESS0 are blocked when the GO
bit is 1.
it is a register read.
register.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
81
© 2011, Texas Instruments Incorporated
MDIO Registers
www.ti.com
4.14 MDIO User PHY Select Register 1 (USERPHYSEL1)
The MDIO user PHY select register 1 (USERPHYSEL1) is shown in Figure 38 and described in Table 36.
Figure 38. MDIO User PHY Select Register 1 (USERPHYSEL1)
31 16
Reserved
R-0
15 8 7 6 5 4 0
Reserved LINKSEL LINKINTENB Rsvd PHYADRMON
R-0 R/W-0 R/W-0 R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 36. MDIO User PHY Select Register 1 (USERPHYSEL1) Field Descriptions
Bit Field Value Description
31-8 Reserved 0 Reserved
7 LINKSEL Link status determination select bit. Default value is 0, which implies that the link status is
6 LINKINTENB Link change interrupt enable. Set to 1 to enable link change status interrupts for the PHY address
5 Reserved 0 PHY address whose link status is to be monitored.
4-0 PHYADRMON 0-1Fh PHY address whose link status is to be monitored.
determined by the MDIO state machine. This is the only option supported on this device.
0 The link status is determined by the MDIO state machine.
1 Not supported.
specified in PHYADRMON. Link change interrupts are disabled if this bit is cleared to 0.
0 Link change interrupts are disabled.
1 Link change status interrupts for PHY address specified in PHYADDRMON bits are enabled.
82
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
5 EMAC Module Registers
Table 37 lists the memory-mapped registers for the EMAC. See your device-specific data manual for the
memory address of these registers.
Table 37. Ethernet Media Access Controller (EMAC) Registers
Offset Acronym Register Description Section
0h TXREVID Transmit Revision ID Register Section 5.1
4h TXCONTROL Transmit Control Register Section 5.2
8h TXTEARDOWN Transmit Teardown Register Section 5.3
10h RXREVID Receive Revision ID Register Section 5.4
14h RXCONTROL Receive Control Register Section 5.5
18h RXTEARDOWN Receive Teardown Register Section 5.6
80h TXINTSTATRAW Transmit Interrupt Status (Unmasked) Register Section 5.7
84h TXINTSTATMASKED Transmit Interrupt Status (Masked) Register Section 5.8
88h TXINTMASKSET Transmit Interrupt Mask Set Register Section 5.9
8Ch TXINTMASKCLEAR Transmit Interrupt Clear Register Section 5.10
90h MACINVECTOR MAC Input Vector Register Section 5.11
94h MACEOIVECTOR MAC End Of Interrupt Vector Register Section 5.12
A0h RXINTSTATRAW Receive Interrupt Status (Unmasked) Register Section 5.13
A4h RXINTSTATMASKED Receive Interrupt Status (Masked) Register Section 5.14
A8h RXINTMASKSET Receive Interrupt Mask Set Register Section 5.15
ACh RXINTMASKCLEAR Receive Interrupt Mask Clear Register Section 5.16
B0h MACINTSTATRAW MAC Interrupt Status (Unmasked) Register Section 5.17
B4h MACINTSTATMASKED MAC Interrupt Status (Masked) Register Section 5.18
B8h MACINTMASKSET MAC Interrupt Mask Set Register Section 5.19
BCh MACINTMASKCLEAR MAC Interrupt Mask Clear Register Section 5.20
100h RXMBPENABLE Receive Multicast/Broadcast/Promiscuous Channel Enable Register Section 5.21
104h RXUNICASTSET Receive Unicast Enable Set Register Section 5.22
108h RXUNICASTCLEAR Receive Unicast Clear Register Section 5.23
10Ch RXMAXLEN Receive Maximum Length Register Section 5.24
110h RXBUFFEROFFSET Receive Buffer Offset Register Section 5.25
114h RXFILTERLOWTHRESH Receive Filter Low Priority Frame Threshold Register Section 5.26
120h RX0FLOWTHRESH Receive Channel 0 Flow Control Threshold Register Section 5.27
124h RX1FLOWTHRESH Receive Channel 1 Flow Control Threshold Register Section 5.27
128h RX2FLOWTHRESH Receive Channel 2 Flow Control Threshold Register Section 5.27
12Ch RX3FLOWTHRESH Receive Channel 3 Flow Control Threshold Register Section 5.27
130h RX4FLOWTHRESH Receive Channel 4 Flow Control Threshold Register Section 5.27
134h RX5FLOWTHRESH Receive Channel 5 Flow Control Threshold Register Section 5.27
138h RX6FLOWTHRESH Receive Channel 6 Flow Control Threshold Register Section 5.27
13Ch RX7FLOWTHRESH Receive Channel 7 Flow Control Threshold Register Section 5.27
140h RX0FREEBUFFER Receive Channel 0 Free Buffer Count Register Section 5.28
144h RX1FREEBUFFER Receive Channel 1 Free Buffer Count Register Section 5.28
148h RX2FREEBUFFER Receive Channel 2 Free Buffer Count Register Section 5.28
14Ch RX3FREEBUFFER Receive Channel 3 Free Buffer Count Register Section 5.28
150h RX4FREEBUFFER Receive Channel 4 Free Buffer Count Register Section 5.28
154h RX5FREEBUFFER Receive Channel 5 Free Buffer Count Register Section 5.28
158h RX6FREEBUFFER Receive Channel 6 Free Buffer Count Register Section 5.28
15Ch RX7FREEBUFFER Receive Channel 7 Free Buffer Count Register Section 5.28
160h MACCONTROL MAC Control Register Section 5.29
EMAC Module Registers
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
83
© 2011, Texas Instruments Incorporated
EMAC Module Registers
Table 37. Ethernet Media Access Controller (EMAC) Registers (continued)
Offset Acronym Register Description Section
164h MACSTATUS MAC Status Register Section 5.30
168h EMCONTROL Emulation Control Register Section 5.31
16Ch FIFOCONTROL FIFO Control Register Section 5.32
170h MACCONFIG MAC Configuration Register Section 5.33
174h SOFTRESET Soft Reset Register Section 5.34
1D0h MACSRCADDRLO MAC Source Address Low Bytes Register Section 5.35
1D4h MACSRCADDRHI MAC Source Address High Bytes Register Section 5.36
1D8h MACHASH1 MAC Hash Address Register 1 Section 5.37
1DCh MACHASH2 MAC Hash Address Register 2 Section 5.38
1E0h BOFFTEST Back Off Test Register Section 5.39
1E4h TPACETEST Transmit Pacing Algorithm Test Register Section 5.40
1E8h RXPAUSE Receive Pause Timer Register Section 5.41
1ECh TXPAUSE Transmit Pause Timer Register Section 5.42
500h MACADDRLO MAC Address Low Bytes Register, Used in Receive Address Matching Section 5.43
504h MACADDRHI MAC Address High Bytes Register, Used in Receive Address Matching Section 5.44
508h MACINDEX MAC Index Register Section 5.45
600h TX0HDP Transmit Channel 0 DMA Head Descriptor Pointer Register Section 5.46
604h TX1HDP Transmit Channel 1 DMA Head Descriptor Pointer Register Section 5.46
608h TX2HDP Transmit Channel 2 DMA Head Descriptor Pointer Register Section 5.46
60Ch TX3HDP Transmit Channel 3 DMA Head Descriptor Pointer Register Section 5.46
610h TX4HDP Transmit Channel 4 DMA Head Descriptor Pointer Register Section 5.46
614h TX5HDP Transmit Channel 5 DMA Head Descriptor Pointer Register Section 5.46
618h TX6HDP Transmit Channel 6 DMA Head Descriptor Pointer Register Section 5.46
61Ch TX7HDP Transmit Channel 7 DMA Head Descriptor Pointer Register Section 5.46
620h RX0HDP Receive Channel 0 DMA Head Descriptor Pointer Register Section 5.47
624h RX1HDP Receive Channel 1 DMA Head Descriptor Pointer Register Section 5.47
628h RX2HDP Receive Channel 2 DMA Head Descriptor Pointer Register Section 5.47
62Ch RX3HDP Receive Channel 3 DMA Head Descriptor Pointer Register Section 5.47
630h RX4HDP Receive Channel 4 DMA Head Descriptor Pointer Register Section 5.47
634h RX5HDP Receive Channel 5 DMA Head Descriptor Pointer Register Section 5.47
638h RX6HDP Receive Channel 6 DMA Head Descriptor Pointer Register Section 5.47
63Ch RX7HDP Receive Channel 7 DMA Head Descriptor Pointer Register Section 5.47
640h TX0CP Transmit Channel 0 Completion Pointer Register Section 5.48
644h TX1CP Transmit Channel 1 Completion Pointer Register Section 5.48
648h TX2CP Transmit Channel 2 Completion Pointer Register Section 5.48
64Ch TX3CP Transmit Channel 3 Completion Pointer Register Section 5.48
650h TX4CP Transmit Channel 4 Completion Pointer Register Section 5.48
654h TX5CP Transmit Channel 5 Completion Pointer Register Section 5.48
658h TX6CP Transmit Channel 6 Completion Pointer Register Section 5.48
65Ch TX7CP Transmit Channel 7 Completion Pointer Register Section 5.48
660h RX0CP Receive Channel 0 Completion Pointer Register Section 5.49
664h RX1CP Receive Channel 1 Completion Pointer Register Section 5.49
668h RX2CP Receive Channel 2 Completion Pointer Register Section 5.49
66Ch RX3CP Receive Channel 3 Completion Pointer Register Section 5.49
670h RX4CP Receive Channel 4 Completion Pointer Register Section 5.49
674h RX5CP Receive Channel 5 Completion Pointer Register Section 5.49
678h RX6CP Receive Channel 6 Completion Pointer Register Section 5.49
www.ti.com
84
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
Table 37. Ethernet Media Access Controller (EMAC) Registers (continued)
Offset Acronym Register Description Section
67Ch RX7CP Receive Channel 7 Completion Pointer Register Section 5.49
Network Statistics Registers
200h RXGOODFRAMES Good Receive Frames Register Section 5.50.1
204h RXBCASTFRAMES Broadcast Receive Frames Register Section 5.50.2
208h RXMCASTFRAMES Multicast Receive Frames Register Section 5.50.3
20Ch RXPAUSEFRAMES Pause Receive Frames Register Section 5.50.4
210h RXCRCERRORS Receive CRC Errors Register Section 5.50.5
214h RXALIGNCODEERRORS Receive Alignment/Code Errors Register Section 5.50.6
218h RXOVERSIZED Receive Oversized Frames Register Section 5.50.7
21Ch RXJABBER Receive Jabber Frames Register Section 5.50.8
220h RXUNDERSIZED Receive Undersized Frames Register Section 5.50.9
224h RXFRAGMENTS Receive Frame Fragments Register Section 5.50.10
228h RXFILTERED Filtered Receive Frames Register Section 5.50.11
22Ch RXQOSFILTERED Receive QOS Filtered Frames Register Section 5.50.12
230h RXOCTETS Receive Octet Frames Register Section 5.50.13
234h TXGOODFRAMES Good Transmit Frames Register Section 5.50.14
238h TXBCASTFRAMES Broadcast Transmit Frames Register Section 5.50.15
23Ch TXMCASTFRAMES Multicast Transmit Frames Register Section 5.50.16
240h TXPAUSEFRAMES Pause Transmit Frames Register Section 5.50.17
244h TXDEFERRED Deferred Transmit Frames Register Section 5.50.18
248h TXCOLLISION Transmit Collision Frames Register Section 5.50.19
24Ch TXSINGLECOLL Transmit Single Collision Frames Register Section 5.50.20
250h TXMULTICOLL Transmit Multiple Collision Frames Register Section 5.50.21
254h TXEXCESSIVECOLL Transmit Excessive Collision Frames Register Section 5.50.22
258h TXLATECOLL Transmit Late Collision Frames Register Section 5.50.23
25Ch TXUNDERRUN Transmit Underrun Error Register Section 5.50.24
260h TXCARRIERSENSE Transmit Carrier Sense Errors Register Section 5.50.25
264h TXOCTETS Transmit Octet Frames Register Section 5.50.26
268h FRAME64 Transmit and Receive 64 Octet Frames Register Section 5.50.27
26Ch FRAME65T127 Transmit and Receive 65 to 127 Octet Frames Register Section 5.50.28
270h FRAME128T255 Transmit and Receive 128 to 255 Octet Frames Register Section 5.50.29
274h FRAME256T511 Transmit and Receive 256 to 511 Octet Frames Register Section 5.50.30
278h FRAME512T1023 Transmit and Receive 512 to 1023 Octet Frames Register Section 5.50.31
27Ch FRAME1024TUP Transmit and Receive 1024 to RXMAXLEN Octet Frames Register Section 5.50.32
280h NETOCTETS Network Octet Frames Register Section 5.50.33
284h RXSOFOVERRUNS Receive FIFO or DMA Start of Frame Overruns Register Section 5.50.34
288h RXMOFOVERRUNS Receive FIFO or DMA Middle of Frame Overruns Register Section 5.50.35
28Ch RXDMAOVERRUNS Receive DMA Overruns Register Section 5.50.36
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
85
© 2011, Texas Instruments Incorporated
EMAC Module Registers
www.ti.com
5.1 Transmit Revision ID Register (TXREVID)
The transmit revision ID register (TXREVID) is shown in Figure 39 and described in Table 38.
Figure 39. Transmit Revision ID Register (TXREVID)
31 0
TXREV
R-4EC0 020Dh
LEGEND: R = Read only; -n = value after reset
Table 38. Transmit Revision ID Register (TXREVID) Field Descriptions
Bit Field Value Description
31-0 TXREV Transmit module revision
4EC0 020Dh Current transmit revision value
5.2 Transmit Control Register (TXCONTROL)
The transmit control register (TXCONTROL) is shown in Figure 40 and described in Table 39.
Figure 40. Transmit Control Register (TXCONTROL)
31 16
Reserved
R-0
15 1 0
Reserved TXEN
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 39. Transmit Control Register (TXCONTROL) Field Descriptions
Bit Field Value Description
31-1 Reserved 0 Reserved
0 TXEN Transmit enable
0 Transmit is disabled.
1 Transmit is enabled.
86
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
5.3 Transmit Teardown Register (TXTEARDOWN)
The transmit teardown register (TXTEARDOWN) is shown in Figure 41 and described in Table 40.
Figure 41. Transmit Teardown Register (TXTEARDOWN)
31 16
Reserved
R-0
15 3 2 0
Reserved TXTDNCH
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 40. Transmit Teardown Register (TXTEARDOWN) Field Descriptions
Bit Field Value Description
31-3 Reserved 0 Reserved
2-0 TXTDNCH 0-7h Transmit teardown channel. The transmit channel teardown is commanded by writing the encoded
value of the transmit channel to be torn down. The teardown register is read as 0.
0 Teardown transmit channel 0
1h Teardown transmit channel 1
2h Teardown transmit channel 2
3h Teardown transmit channel 3
4h Teardown transmit channel 4
5h Teardown transmit channel 5
6h Teardown transmit channel 6
7h Teardown transmit channel 7
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
87
© 2011, Texas Instruments Incorporated
EMAC Module Registers
www.ti.com
5.4 Receive Revision ID Register (RXREVID)
The receive revision ID register (RXREVID) is shown in Figure 42 and described in Table 41.
Figure 42. Receive Revision ID Register (RXREVID)
31 0
RXREV
R-4EC0 020Dh
LEGEND: R = Read only; -n = value after reset
Table 41. Receive Revision ID Register (RXREVID) Field Descriptions
Bit Field Value Description
31-0 RXREV Receive module revision
4EC0 020Dh Current receive revision value
5.5 Receive Control Register (RXCONTROL)
The receive control register (RXCONTROL) is shown in Figure 43 and described in Table 42.
Figure 43. Receive Control Register (RXCONTROL)
31 16
Reserved
R-0
15 1 0
Reserved RXEN
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 42. Receive Control Register (RXCONTROL) Field Descriptions
Bit Field Value Description
31-1 Reserved 0 Reserved
0 RXEN Receive enable
0 Receive is disabled.
1 Receive is enabled.
88
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
5.6 Receive Teardown Register (RXTEARDOWN)
The receive teardown register (RXTEARDOWN) is shown in Figure 44 and described in Table 43.
Figure 44. Receive Teardown Register (RXTEARDOWN)
31 16
Reserved
R-0
15 3 2 0
Reserved RXTDNCH
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 43. Receive Teardown Register (RXTEARDOWN) Field Descriptions
Bit Field Value Description
31-3 Reserved 0 Reserved
2-0 RXTDNCH 0-7h Receive teardown channel. The receive channel teardown is commanded by writing the encoded value
of the receive channel to be torn down. The teardown register is read as 0.
0 Teardown receive channel 0
1h Teardown receive channel 1
2h Teardown receive channel 2
3h Teardown receive channel 3
4h Teardown receive channel 4
5h Teardown receive channel 5
6h Teardown receive channel 6
7h Teardown receive channel 7
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
89
© 2011, Texas Instruments Incorporated
EMAC Module Registers
www.ti.com
5.7 Transmit Interrupt Status (Unmasked) Register (TXINTSTATRAW)
The transmit interrupt status (unmasked) register (TXINTSTATRAW) is shown in Figure 45 and described
in Table 44.
Figure 45. Transmit Interrupt Status (Unmasked) Register (TXINTSTATRAW)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
TX7PEND TX6PEND TX5PEND TX4PEND TX3PEND TX2PEND TX1PEND TX0PEND
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 44. Transmit Interrupt Status (Unmasked) Register (TXINTSTATRAW) Field Descriptions
Bit Field Value Description
31-8 Reserved 0 Reserved
7 TX7PEND 0-1 TX7PEND raw interrupt read (before mask)
6 TX6PEND 0-1 TX6PEND raw interrupt read (before mask)
5 TX5PEND 0-1 TX5PEND raw interrupt read (before mask)
4 TX4PEND 0-1 TX4PEND raw interrupt read (before mask)
3 TX3PEND 0-1 TX3PEND raw interrupt read (before mask)
2 TX2PEND 0-1 TX2PEND raw interrupt read (before mask)
1 TX1PEND 0-1 TX1PEND raw interrupt read (before mask)
0 TX0PEND 0-1 TX0PEND raw interrupt read (before mask)
90
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
5.8 Transmit Interrupt Status (Masked) Register (TXINTSTATMASKED)
The transmit interrupt status (masked) register (TXINTSTATMASKED) is shown in Figure 46 and
described in Table 45.
Figure 46. Transmit Interrupt Status (Masked) Register (TXINTSTATMASKED)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
TX7PEND TX6PEND TX5PEND TX4PEND TX3PEND TX2PEND TX1PEND TX0PEND
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 45. Transmit Interrupt Status (Masked) Register (TXINTSTATMASKED) Field Descriptions
Bit Field Value Description
31-8 Reserved 0 Reserved
7 TX7PEND 0-1 TX7PEND masked interrupt read
6 TX6PEND 0-1 TX6PEND masked interrupt read
5 TX5PEND 0-1 TX5PEND masked interrupt read
4 TX4PEND 0-1 TX4PEND masked interrupt read
3 TX3PEND 0-1 TX3PEND masked interrupt read
2 TX2PEND 0-1 TX2PEND masked interrupt read
1 TX1PEND 0-1 TX1PEND masked interrupt read
0 TX0PEND 0-1 TX0PEND masked interrupt read
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
91
© 2011, Texas Instruments Incorporated
EMAC Module Registers
www.ti.com
5.9 Transmit Interrupt Mask Set Register (TXINTMASKSET)
The transmit interrupt mask set register (TXINTMASKSET) is shown in Figure 47 and described in
Table 46.
Figure 47. Transmit Interrupt Mask Set Register (TXINTMASKSET)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
TX7MASK TX6MASK TX5MASK TX4MASK TX3MASK TX2MASK TX1MASK TX0MASK
R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0
LEGEND: R/W = Read/Write; R = Read only; W1S = Write 1 to set (writing a 0 has no effect); -n = value after reset
Table 46. Transmit Interrupt Mask Set Register (TXINTMASKSET) Field Descriptions
Bit Field Value Description
31-8 Reserved 0 Reserved
7 TX7MASK 0-1 Transmit channel 7 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
6 TX6MASK 0-1 Transmit channel 6 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
5 TX5MASK 0-1 Transmit channel 5 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
4 TX4MASK 0-1 Transmit channel 4 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
3 TX3MASK 0-1 Transmit channel 3 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
2 TX2MASK 0-1 Transmit channel 2 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
1 TX1MASK 0-1 Transmit channel 1 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
0 TX0MASK 0-1 Transmit channel 0 interrupt mask set bit. Write 1 to enable interrupt, a write of 0 has no effect.
92
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
5.10 Transmit Interrupt Mask Clear Register (TXINTMASKCLEAR)
The transmit interrupt mask clear register (TXINTMASKCLEAR) is shown in Figure 48 and described in
Table 47.
Figure 48. Transmit Interrupt Mask Clear Register (TXINTMASKCLEAR)
31 16
Reserved
R-0
15 8
Reserved
R-0
7 6 5 4 3 2 1 0
TX7MASK TX6MASK TX5MASK TX4MASK TX3MASK TX2MASK TX1MASK TX0MASK
R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 47. Transmit Interrupt Mask Clear Register (TXINTMASKCLEAR) Field Descriptions
Bit Field Value Description
31-8 Reserved 0 Reserved
7 TX7MASK 0-1 Transmit channel 7 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
6 TX6MASK 0-1 Transmit channel 6 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
5 TX5MASK 0-1 Transmit channel 5 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
4 TX4MASK 0-1 Transmit channel 4 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
3 TX3MASK 0-1 Transmit channel 3 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
2 TX2MASK 0-1 Transmit channel 2 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
1 TX1MASK 0-1 Transmit channel 1 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
0 TX0MASK 0-1 Transmit channel 0 interrupt mask clear bit. Write 1 to disable interrupt, a write of 0 has no effect.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
93
© 2011, Texas Instruments Incorporated
EMAC Module Registers
5.11 MAC Input Vector Register (MACINVECTOR)
The MAC input vector register (MACINVECTOR) is shown in Figure 49 and described in Table 48.
Figure 49. MAC Input Vector Register (MACINVECTOR)
31 28 27 26 25 24 23 16
Reserved STATPEND HOSTPEND LINKINT0 USERINT0 TXPEND
R-0 R-0 R-0 R-0 R-0 R-0
15 8 7 0
RXTHRESHPEND RXPEND
R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 48. MAC Input Vector Register (MACINVECTOR) Field Descriptions
Bit Field Value Description
31-28 Reserved 0 Reserved
27 STATPEND 0-1 EMAC module statistics interrupt (STATPEND) pending status bit
26 HOSTPEND 0-1 EMAC module host error interrupt (HOSTPEND) pending status bit
25 LINKINT0 0-1 MDIO module USERPHYSEL0 (LINKINT0) status bit
24 USERINT0 0-1 MDIO module USERACCESS0 (USERINT0) status bit
23-16 TXPEND 0-FFh Transmit channels 0-7 interrupt (TXnPEND) pending status. Bit 16 is TX0PEND.
15-8 RXTHRESHPEND 0-FFh Receive channels 0-7 interrupt (RXnTHRESHPEND) pending status. Bit 8 is
RX0THRESHPEND.
7-0 RXPEND 0-FFh Receive channels 0-7 interrupt (RXnPEND) pending status bit. Bit 0 is RX0PEND.
www.ti.com
94
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
5.12 MAC End Of Interrupt Vector Register (MACEOIVECTOR)
The MAC end of interrupt vector register (MACEOIVECTOR) is shown in Figure 50 and described in
Table 49.
Figure 50. MAC End Of Interrupt Vector Register (MACEOIVECTOR)
31 16
Reserved
R-0
15 5 4 0
Reserved INTVECT
R-0 R/W-0
LEGEND: R/W = Read/Write; R = Read only; -n = value after reset
Table 49. MAC End Of Interrupt Vector Register (MACEOIVECTOR) Field Descriptions
Bit Field Value Description
31-5 Reserved 0 Reserved
4-0 INTVECT 0-1Fh Acknowledge EMAC Control Module Interrupts
0h Acknowledge C0RXTHRESH Interrupt
1h Acknowledge C0RX Interrupt
2h Acknowledge C0TX Interrupt
3h Acknowledge C0MISC Interrupt (STATPEND, HOSTPEND, MDIO LINKINT0, MDIO USERINT0)
4h Acknowledge C1RXTHRESH Interrupt
5h Acknowledge C1RX Interrupt
6h Acknowledge C1TX Interrupt
7h Acknowledge C1MISC Interrupt (STATPEND, HOSTPEND, MDIO LINKINT0, MDIO USERINT0)
8h Acknowledge C2RXTHRESH Interrupt
9h Acknowledge C2RX Interrupt
Ah Acknowledge C2TX Interrupt
Bh Acknowledge C2MISC Interrupt (STATPEND, HOSTPEND, MDIO LINKINT0, MDIO USERINT0)
Ch-1Fh Reserved
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
95
© 2011, Texas Instruments Incorporated
EMAC Module Registers
www.ti.com
5.13 Receive Interrupt Status (Unmasked) Register (RXINTSTATRAW)
The receive interrupt status (unmasked) register (RXINTSTATRAW) is shown in Figure 51 and described
in Table 50.
Figure 51. Receive Interrupt Status (Unmasked) Register (RXINTSTATRAW)
31 16
Reserved
R-0
15 14 13 12 11 10 9 8
RX7THRESHPEND RX6THRESHPEND RX5THRESHPEND RX4THRESHPEND RX3THRESHPEND RX2THRESHPEND RX1THRESHPEND RX0THRESHPEND
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
7 6 5 4 3 2 1 0
RX7PEND RX6PEND RX5PEND RX4PEND RX3PEND RX2PEND RX1PEND RX0PEND
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 50. Receive Interrupt Status (Unmasked) Register (RXINTSTATRAW) Field Descriptions
Bit Field Value Description
31-16 Reserved 0 Reserved
15 RX7THRESHPEND 0-1 RX7THRESHPEND raw interrupt read (before mask)
14 RX6THRESHPEND 0-1 RX6THRESHPEND raw interrupt read (before mask)
13 RX5THRESHPEND 0-1 RX5THRESHPEND raw interrupt read (before mask)
12 RX4THRESHPEND 0-1 RX4THRESHPEND raw interrupt read (before mask)
11 RX3THRESHPEND 0-1 RX3THRESHPEND raw interrupt read (before mask)
10 RX2THRESHPEND 0-1 RX2THRESHPEND raw interrupt read (before mask)
9 RX1THRESHPEND 0-1 RX1THRESHPEND raw interrupt read (before mask)
8 RX0THRESHPEND 0-1 RX0THRESHPEND raw interrupt read (before mask)
7 RX7PEND 0-1 RX7PEND raw interrupt read (before mask)
6 RX6PEND 0-1 RX6PEND raw interrupt read (before mask)
5 RX5PEND 0-1 RX5PEND raw interrupt read (before mask)
4 RX4PEND 0-1 RX4PEND raw interrupt read (before mask)
3 RX3PEND 0-1 RX3PEND raw interrupt read (before mask)
2 RX2PEND 0-1 RX2PEND raw interrupt read (before mask)
1 RX1PEND 0-1 RX1PEND raw interrupt read (before mask)
0 RX0PEND 0-1 RX0PEND raw interrupt read (before mask)
96
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
5.14 Receive Interrupt Status (Masked) Register (RXINTSTATMASKED)
The receive interrupt status (masked) register (RXINTSTATMASKED) is shown in Figure 52 and
described in Table 51.
Figure 52. Receive Interrupt Status (Masked) Register (RXINTSTATMASKED)
31 16
Reserved
R-0
15 14 13 12 11 10 9 8
RX7THRESHPEND RX6THRESHPEND RX5THRESHPEND RX4THRESHPEND RX3THRESHPEND RX2THRESHPEND RX1THRESHPEND RX0THRESHPEND
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
7 6 5 4 3 2 1 0
RX7PEND RX6PEND RX5PEND RX4PEND RX3PEND RX2PEND RX1PEND RX0PEND
R-0 R-0 R-0 R-0 R-0 R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 51. Receive Interrupt Status (Masked) Register (RXINTSTATMASKED) Field Descriptions
Bit Field Value Description
31-16 Reserved 0 Reserved
15 RX7THRESHPEND 0-1 RX7THRESHPEND masked interrupt read
14 RX6THRESHPEND 0-1 RX6THRESHPEND masked interrupt read
13 RX5THRESHPEND 0-1 RX5THRESHPEND masked interrupt read
12 RX4THRESHPEND 0-1 RX4THRESHPEND masked interrupt read
11 RX3THRESHPEND 0-1 RX3THRESHPEND masked interrupt read
10 RX2THRESHPEND 0-1 RX2THRESHPEND masked interrupt read
9 RX1THRESHPEND 0-1 RX1THRESHPEND masked interrupt read
8 RX0THRESHPEND 0-1 RX0THRESHPEND masked interrupt read
7 RX7PEND 0-1 RX7PEND masked interrupt read
6 RX6PEND 0-1 RX6PEND masked interrupt read
5 RX5PEND 0-1 RX5PEND masked interrupt read
4 RX4PEND 0-1 RX4PEND masked interrupt read
3 RX3PEND 0-1 RX3PEND masked interrupt read
2 RX2PEND 0-1 RX2PEND masked interrupt read
1 RX1PEND 0-1 RX1PEND masked interrupt read
0 RX0PEND 0-1 RX0PEND masked interrupt read
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
97
© 2011, Texas Instruments Incorporated
EMAC Module Registers
www.ti.com
5.15 Receive Interrupt Mask Set Register (RXINTMASKSET)
The receive interrupt mask set register (RXINTMASKSET) is shown in Figure 53 and described in
Table 52.
Figure 53. Receive Interrupt Mask Set Register (RXINTMASKSET)
31 16
Reserved
R-0
15 14 13 12 11 10 9 8
RX7THRESHMASK RX6THRESHMASK RX5THRESHMASK RX4THRESHMASK RX3THRESHMASK RX2THRESHMASK RX1THRESHMASK RX0THRESHMASK
R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0
7 6 5 4 3 2 1 0
RX7MASK RX6MASK RX5MASK RX4MASK RX3MASK RX2MASK RX1MASK RX0MASK
R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0 R/W1S-0
LEGEND: R/W = Read/Write; R = Read only; W1S = Write 1 to set (writing a 0 has no effect); -n = value after reset
Table 52. Receive Interrupt Mask Set Register (RXINTMASKSET) Field Descriptions
Bit Field Value Description
31-16 Reserved 0 Reserved
15 RX7THRESHMASK 0-1 Receive channel 7 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
14 RX6THRESHMASK 0-1 Receive channel 6 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
13 RX5THRESHMASK 0-1 Receive channel 5 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
12 RX4THRESHMASK 0-1 Receive channel 4 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
11 RX3THRESHMASK 0-1 Receive channel 3 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
10 RX2THRESHMASK 0-1 Receive channel 2 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
9 RX1THRESHMASK 0-1 Receive channel 1 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
8 RX0THRESHMASK 0-1 Receive channel 0 threshold mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
7 RX7MASK 0-1 Receive channel 7 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
6 RX6MASK 0-1 Receive channel 6 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
5 RX5MASK 0-1 Receive channel 5 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
4 RX4MASK 0-1 Receive channel 4 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
3 RX3MASK 0-1 Receive channel 3 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
2 RX2MASK 0-1 Receive channel 2 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
1 RX1MASK 0-1 Receive channel 1 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
0 RX0MASK 0-1 Receive channel 0 mask set bit. Write 1 to enable interrupt; a write of 0 has no effect.
98
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
www.ti.com
EMAC Module Registers
5.16 Receive Interrupt Mask Clear Register (RXINTMASKCLEAR)
The receive interrupt mask clear register (RXINTMASKCLEAR) is shown in Figure 54 and described in
Table 53.
Figure 54. Receive Interrupt Mask Clear Register (RXINTMASKCLEAR)
31 16
Reserved
R-0
15 14 13 12 11 10 9 8
RX7THRESHMASK RX6THRESHMASK RX5THRESHMASK RX4THRESHMASK RX3THRESHMASK RX2THRESHMASK RX1THRESHMASK RX0THRESHMASK
R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0
7 6 5 4 3 2 1 0
RX7MASK RX6MASK RX5MASK RX4MASK RX3MASK RX2MASK RX1MASK RX0MASK
R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0 R/W1C-0
LEGEND: R/W = Read/Write; R = Read only; W1C = Write 1 to clear (writing a 0 has no effect); -n = value after reset
Table 53. Receive Interrupt Mask Clear Register (RXINTMASKCLEAR) Field Descriptions
Bit Field Value Description
31-16 Reserved 0 Reserved
15 RX7THRESHMASK 0-1 Receive channel 7 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
14 RX6THRESHMASK 0-1 Receive channel 6 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
13 RX5THRESHMASK 0-1 Receive channel 5 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
12 RX4THRESHMASK 0-1 Receive channel 4 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
11 RX3THRESHMASK 0-1 Receive channel 3 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
10 RX2THRESHMASK 0-1 Receive channel 2 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
9 RX1THRESHMASK 0-1 Receive channel 1 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
8 RX0THRESHMASK 0-1 Receive channel 0 threshold mask clear bit. Write 1 to disable interrupt; a write of 0 has no
7 RX7MASK 0-1 Receive channel 7 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
6 RX6MASK 0-1 Receive channel 6 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
5 RX5MASK 0-1 Receive channel 5 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
4 RX4MASK 0-1 Receive channel 4 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
3 RX3MASK 0-1 Receive channel 3 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
2 RX2MASK 0-1 Receive channel 2 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
1 RX1MASK 0-1 Receive channel 1 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
0 RX0MASK 0-1 Receive channel 0 mask clear bit. Write 1 to disable interrupt; a write of 0 has no effect.
effect.
effect.
effect.
effect.
effect.
effect.
effect.
effect.
SPRUFL5B–April 2011 EMAC/MDIO Module
Submit Documentation Feedback
99
© 2011, Texas Instruments Incorporated
EMAC Module Registers
5.17 MAC Interrupt Status (Unmasked) Register (MACINTSTATRAW)
The MAC interrupt status (unmasked) register (MACINTSTATRAW) is shown in Figure 55 and described
in Table 54.
Figure 55. MAC Interrupt Status (Unmasked) Register (MACINTSTATRAW)
31 16
Reserved
R-0
15 2 1 0
Reserved HOSTPEND STATPEND
R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 54. MAC Interrupt Status (Unmasked) Register (MACINTSTATRAW) Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 HOSTPEND 0-1 Host pending interrupt (HOSTPEND); raw interrupt read (before mask).
0 STATPEND 0-1 Statistics pending interrupt (STATPEND); raw interrupt read (before mask).
www.ti.com
5.18 MAC Interrupt Status (Masked) Register (MACINTSTATMASKED)
The MAC interrupt status (masked) register (MACINTSTATMASKED) is shown in Figure 56 and described
in Table 55.
Figure 56. MAC Interrupt Status (Masked) Register (MACINTSTATMASKED)
31 16
Reserved
R-0
15 2 1 0
Reserved HOSTPEND STATPEND
R-0 R-0 R-0
LEGEND: R = Read only; -n = value after reset
Table 55. MAC Interrupt Status (Masked) Register (MACINTSTATMASKED) Field Descriptions
Bit Field Value Description
31-2 Reserved 0 Reserved
1 HOSTPEND 0-1 Host pending interrupt (HOSTPEND); masked interrupt read.
0 STATPEND 0-1 Statistics pending interrupt (STATPEND); masked interrupt read.
100
EMAC/MDIO Module SPRUFL5B–April 2011
© 2011, Texas Instruments Incorporated
Submit Documentation Feedback
Loading...