- 您現(xiàn)在的位置：買(mǎi)賣(mài)IC網(wǎng) > PDF目錄366550 > AM79C940VCW (ADVANCED MICRO DEVICES INC) Media Access Controller for Ethernet (MACE) PDF資料下載
參數(shù)資料
| 型號(hào)： | AM79C940VCW |
| 廠商： | ADVANCED MICRO DEVICES INC |
| 元件分類(lèi)： | 微控制器/微處理器 |
| 英文描述： | Media Access Controller for Ethernet (MACE) |
| 中文描述： | 4 CHANNEL(S), 10M bps, LOCAL AREA NETWORK CONTROLLER, PQFP80 |
| 封裝： | TQFP-80 |
| 文件頁(yè)數(shù)： | 32/122頁(yè) |
| 文件大小： | 914K |
| 代理商： | AM79C940VCW |
第1頁(yè)第2頁(yè)第3頁(yè)第4頁(yè)第5頁(yè)第6頁(yè)第7頁(yè)第8頁(yè)第9頁(yè)第10頁(yè)第11頁(yè)第12頁(yè)第13頁(yè)第14頁(yè)第15頁(yè)第16頁(yè)第17頁(yè)第18頁(yè)第19頁(yè)第20頁(yè)第21頁(yè)第22頁(yè)第23頁(yè)第24頁(yè)第25頁(yè)第26頁(yè)第27頁(yè)第28頁(yè)第29頁(yè)第30頁(yè)第31頁(yè)當(dāng)前第32頁(yè)第33頁(yè)第34頁(yè)第35頁(yè)第36頁(yè)第37頁(yè)第38頁(yè)第39頁(yè)第40頁(yè)第41頁(yè)第42頁(yè)第43頁(yè)第44頁(yè)第45頁(yè)第46頁(yè)第47頁(yè)第48頁(yè)第49頁(yè)第50頁(yè)第51頁(yè)第52頁(yè)第53頁(yè)第54頁(yè)第55頁(yè)第56頁(yè)第57頁(yè)第58頁(yè)第59頁(yè)第60頁(yè)第61頁(yè)第62頁(yè)第63頁(yè)第64頁(yè)第65頁(yè)第66頁(yè)第67頁(yè)第68頁(yè)第69頁(yè)第70頁(yè)第71頁(yè)第72頁(yè)第73頁(yè)第74頁(yè)第75頁(yè)第76頁(yè)第77頁(yè)第78頁(yè)第79頁(yè)第80頁(yè)第81頁(yè)第82頁(yè)第83頁(yè)第84頁(yè)第85頁(yè)第86頁(yè)第87頁(yè)第88頁(yè)第89頁(yè)第90頁(yè)第91頁(yè)第92頁(yè)第93頁(yè)第94頁(yè)第95頁(yè)第96頁(yè)第97頁(yè)第98頁(yè)第99頁(yè)第100頁(yè)第101頁(yè)第102頁(yè)第103頁(yè)第104頁(yè)第105頁(yè)第106頁(yè)第107頁(yè)第108頁(yè)第109頁(yè)第110頁(yè)第111頁(yè)第112頁(yè)第113頁(yè)第114頁(yè)第115頁(yè)第116頁(yè)第117頁(yè)第118頁(yè)第119頁(yè)第120頁(yè)第121頁(yè)第122頁(yè)
AMD
32
Am79C940
ensure the XMTFIFO does not underflow during the
transmit process, versus using the default XMTSP
value. Note that if 64 single byte writes are executed on
the XMTFIFO, and the XMTSP is set to 64-bytes, the
transmission will commence, and all 64-bytes of infor-
mation will be accepted by the XMTFIFO.
The number of write cycles that the host uses to write the
packet into the Transmit FIFO will also directly influence
the amount of space utilized by the transmit message. If
the number of write cycles (n) required to transfer a
packet to the Transmit FIFO is even, the number of
bytes used in the Transmit FIFO will be 2*n. If the num-
ber of write cycles required to transfer a packet to the
Transmit FIFO is odd, the number of bytes used in the
Transmit FIFO will be 2*n + 2 because the End Of Frame
indication in the XMTFIFO is always placed at the end of
a 4-byte boundary. For example, a 32-byte message
written as bytes (n = 32 cycles) will use 64-bytes of
space in the Transmit FIFO (2*n = 64), whereas a
65-byte message written as 32 words and 1 byte (n = 33
cycles) would use 68-bytes (2*n + 2 = 68) .
The Transmit FIFO has been sized appropriately to
minimize the system interface overhead. However, con-
sideration must be given to overall system design if byte
writes are supported. In order to guarantee that suffi-
cient space is present in the XMTFIFO to accept the
number of write cycles programmed by the XMTFW (in-
cluding an End Of Framedelimiter),
TDTREQ
may go
inactive before the XMTSP threshold is reached when
using the non burst mode (XMTBRST = 0). For instance,
assume that the XMTFW is programmed to allow 32
write cycles (default), and XMTSP is programmed to re-
quire 64 bytes (default) before starting transmission. As-
suming that the host bursts the transmit data in a 32
cycle block, writing a single byte anywhere within this
block will mean that XMTSP will not have been reached.
This would be a typical scenario if the transmit data
buffer was not aligned to a word boundary. The MACE
device will continue to assert
TDTREQ
since an addi-
tional 36 write cycles can still be executed. If the host
starts a second burst, the XMTSP will be reached, and
TDTREQ
will deassert when less that 32 write cycle can
be performed although the data written by the host will
continue to be accepted.
The host must be aware that additional space exists in
the XMTFIFO although
TDTREQ
becomes inactive, and
must continue to write data to ensure the XMTSP
threshold is achieved. No transmit activity will com-
mence until the XMTSP threshold is reached. Once 36
write cycles have been executed.
Note that write cycles can be performed to the XMTFIFO
even if the
TDTREQ
is inactive. When
TDTREQ
is as-
serted, it guarantees that a minimum amount of space
exists, when
TDTREQ
is deasserted, it does not neces-
sarily indicate that there is no space in the XMTFIFO.
The
DTV
pin will indicate the successful acceptance of
data by the Transmit FIFO.
As another example, assume again that the XMTFW is
programmed for 32 write cycles. If the host writes word
wide data continuously to the XMTFIFO, the
TDTREQ
will deassert when 36 writes have executed on the
XMTFIFO, at which point 72-bytes will have been writ-
ten to the XMTFIFO, the 64-byte XMTSP will have been
exceeded and the transmission of preamble will have
commenced.
TDTREQ
will not re-assert until the trans-
mission of the packet data has commenced and the pos-
sibility of losing data due to a collision within the slot time
is removed (512 bits have been transmitted without a
collision indication). Assuming that the host actually
stopped writing data after the initial 72-bytes, there will
be only 16-bytes of data remaining in the XMTFIFO
(8-bytes of preamble/SFD plus 56-bytes of data have
been transmitted), corresponding to 12.8
μ
s of latency
before an XMTFIFO underrun occurs. This latency is
considerably less than the maximum possible 57.6
μ
s
the system may have assumed. If the host had contin-
ued with the block transfer until 64 write cycles had been
performed, 128-bytes would have been written to the
XMTFIFO, and 72-bytes of latency would remain
(57.6
μ
s) when
TDTREQ
was re-asserted.
Transmit FIFO—Burst Operation:
The XMTFIFO burst mode, programmed by the
XMTBRST bit in the FIFO Configuration Control regis-
ter, modifies
TDTREQ
behavior. The assertion of
TDTREQ
is controlled by the programming of the
XMTFW bits, such that when the specified number of
write cycles can be guaranteed (8, 16 or 32),
TDTREQ
will be asserted.
TDTREQ
will be de-asserted when the
XMTFIFO can only accept a single write cycle (one word
write including an End Of Framedelimiter) allowing the
external device to burst data into the XMTFIFO when
TDTREQ
is asserted, and stop when
TDTREQ
is
deasserted.
Receive FIFO—General Operation:
The Receive FIFO contains additional logic to ensure
that sufficient data is present in the RCVFIFO to allow
the specified number of bytes to be read, regardless of
the ordering of byte/word read accesses. This has an
impact on the perceived latency that the Receive FIFO
provides to the host system. The description and table
below outline the point at which
RDTREQ
will be as-
serted when the first duration of the packet has been re-
ceived and when any subsequent transfer of the packet
to the host system is required.
No preamble/SFD bytes are loaded into the Receive
FIFO. All references to bytes pass through the receive
FIFO. These references are received after the pream-
ble/SFD sequence.
相關(guān)PDF資料 |
PDF描述 |
|---|---|
| AM79C940 | Media Access Controller for Ethernet (MACE) |
| AM79C940JCW | Media Access Controller for Ethernet (MACE) |
| AM79C940KCW | Media Access Controller for Ethernet (MACE) |
| AM79C960 | PCnetTM-ISA Single-Chip Ethernet Controller |
| AM79C960KC | PCnetTM-ISA Single-Chip Ethernet Controller |
相關(guān)代理商/技術(shù)參數(shù) |
參數(shù)描述 |
|---|---|
| AM79C940VI | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述:LAN Node Controller |
| AM79C940VI/W | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述:LAN Node Controller |
| AM79C945 | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述: |
| AM79C945-16 | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述: |
| AM79C945-16JC | 制造商:未知廠家 制造商全稱(chēng):未知廠家 功能描述:LAN Node Controller |
發(fā)布緊急采購(gòu)，3分鐘左右您將得到回復(fù)。