
3-8
Signals
MTX_ACK
Transmit Data Acknowledge
Output
MTX_ACK, when asserted indicates that the MAC has
accepted the data present on the MTX_DATA[7:0] input
bus and that the host transmit data buffer should present
the next word of transmit frame data.
New transmit frame data is expected on every CLK125
cycle where MTX_ACK is asserted except when the
MTX_EOP input signal is asserted. The assertion of
MTX_ACK may also be interpreted as an
acknowledgment of the assertion of the MTX_DVALID
input signal. Note that MTX_ACK is not continuous when
in 10/100 mode due to the lower speeds of operation.
Similarly, data transfer in 10/100 mode is also not
continuous)
MTX_RETRY Transmit Frame Retry.Output
MTX_RETRY, when asserted, instructs the host to retry
the current frame. The MTX_RETRY output is asserted
as the result of a collision during transmission of the
current frame in half-duplex1 mode. Collisions can occur
during the transmission of preamble, frame data, or
carrier extension, and occur only in the half-duplex1
mode. MTX_RETRY is output only when the MAC is
congured in the E-110 mode.
In the Gigabit mode, MTX_RETRY is always LOW
(inactive).
MTX_ABORT Transmit Packet Abort
Output
MTX_ABORT, when asserted, indicates that the current
packet transmission was aborted. A transmit packet abort
is for any of the following conditions: a late collision,
excessive collisions, transmit underrun, long packet size
(unless specically enabled using the HUGE_PKT_EN
and MAX_PKT_LEN[15:0] conguration signals), or
excess deferrals. The MTX_ABORT output is asserted
anytime between MTX_SOP and MTX_EOP. Once
asserted, it stays asserted until the start of the next
packet or the next assertion of SOP.
In the Gigabit mode, MTX_ABORT is asserted only when
a transmit underrun occurs.
1. In the Gigabit mode, only full-duplex is supported, so MTX_RETRY is only active for 10 or
100 Mbits/s operation.