Communication Processor Module
16-316
MPC823 USER’S MANUAL
MOTOROLA
SCC2
COMMUNICATION
16
PROCESSOR
MODULE
The EEST has similar names for its connection to the seven MPC823 pins mentioned above
and contains a loopback pin so the MPC823 can perform external loopback testing. This can
be controlled by any available parallel I/O pin on the MPC823. The passive components that
are needed to connect to AUI or twisted-pair media are external to the EEST. For more
information on the EEST connection circuits, refer to the MC68160 device description.
Using the SDMA channels, the MPC823 stores every byte that is received after the start
frame delimiter in system memory. When transmitting, you provide the destination address,
source address, type/length field, and the transmit data. The MPC823 automatically pads
frames with less than 46 bytes in the data field to meet the minimum frame requirements. In
addition, the MPC823 appends the FCS to the frame.
16.9.22.5 SCC2 ETHERNET CHANNEL FRAME TRANSMISSION PROCESS. The
Ethernet transmitter is designed to work with almost no intervention from the core. When the
core enables the transmitter, the SCC2 in Ethernet mode polls the first TX buffer descriptor
in the channel TX buffer descriptor table every 128 serial clocks. If you have a frame to
transmit, you can set the TOD bit in the TODR to avoid having to wait for the next poll to
To begin transmission, the SCC2 in Ethernet mode (also called the SCC2 Ethernet
controller) fetches the data from the data buffer, asserts TENA to the EEST, and starts
transmitting the preamble sequence, the start frame delimiter, and frame information.
However, the SCC2 Ethernet controller defers transmission if the line is busy. Before
transmitting, it waits for carrier sense to become inactive and stay that way for 6.0
s. If it
does, then the SCC2 Ethernet controller starts transmitting after waiting an additional 3.6
s
(9.6
s after carrier sense originally became inactive).
If a collision occurs during frame transmission, the SCC2 Ethernet controller follows the
specified backoff procedure and tries to retransmit the frame until the retry limit threshold is
reached. The SCC2 Ethernet controller stores the first 5 to 8 bytes of the transmit frame in
internal RAM, so that they do not have to be retrieved from system memory in case of a
collision. This improves bus utilization and latency when the backoff timer output requires
an immediate retransmission. If a collision occurs during frame transmission, the SCC2
Ethernet controller returns to the first buffer for a retransmission. The only restriction is that
the first buffer must contain at least 9 bytes.
Note: If an Ethernet frame is made up of multiple buffers, you should not reuse the first
buffer descriptor until the last buffer descriptor of the frame has had its R bit
cleared by the communication processor module.