Am79C965A
109
controller
’
s BCR Data Port (BDP). In order to access a
particular BCR location, the Register Address Port
(RAP) should first be written with the appropriate BCR
address. The BDP now points to the selected BCR. A
read of the BDP will yield the selected BCR
’
s data. A
write to the BDP will write to the selected BCR.
When programmed for WIO mode, the BDP has a width
of 16 bits, hence, all BCR locations have 16 bits of
width in WIO mode. Note that when operating in WIO
mode, the upper two bytes of the data bus will be
undefined since the byte mask will not be active for
those bytes.
If DWIO mode has been invoked, then the BDP has a
width of 32 bits, hence, all BCR locations have 32 bits
of width and the upper two bytes of the data bus will be
active, as indicated by the byte mask. In this case, note
that the upper 16 bits of all BCR locations are reserved
and
written as zeros and read as undefined. Therefore,
during BDP write operations in DWIO mode, the upper
16 bits of all BCR locations should be written as zeros.
Reset Register (S_RESET)
A read of the reset register creates an internal
S_RESET pulse in the PCnet-32 controller. This read
access cycle must be 16 bits wide in WIO mode and 32
bits wide in DWIO mode. The internal S_RESET pulse
that is generated by this access is different from both
the assertion of the hardware RESET pin (H_RESET)
and from the assertion of the software STOP bit.
Specifically, the Reset register
’
s S_RESET will be the
equivalent of the assertion of the RESET pin
(H_RESET) assertion for all CSR locations, but
S_RESET will have no effect at all on the BCR
locations, and S_RESET will not cause a de-assertion
of the HOLD pin.
The NE2100 LANCE based family of Ethernet cards re-
quires that a write access to the reset register follows
each read access to the reset register. The PCnet-32
controller does not have a similar requirement. The
write access is not required but it does not have any
harmful effects.
Write accesses to the reset register will have no effect
on the PCnet-32 controller.
Note that a read of the Reset register will take longer
than the normal I/O access time of the PCnet-32
controller. This is because an internal S_RESET pulse
will be generated due to this access, and the access
will not be allowed to complete on the system bus until
the internal S_RESET operation has been completed.
This is to avoid the problem of allowing a new I/O
access to proceed while the S_RESET operation has
not yet completed, which would result in erroneous
data being returned by (or written into) the PCnet-32
controller. The length of a read of the Reset register
can be as long as 128 BCLK cycles when Am386 mode
has been selected and 64 BCLK cycles when Am486
mode or VESA VL-Bus mode has been selected.
Note that a read of the Reset register will
not
cause a
de-assertion of the HOLD signal, if it happens to be ac-
tive at the time of the read to the reset register. The
HOLD signal will remain active until the HLDA signal is
synchronously sampled as asserted. Following the
read of the RESET register, on the next clock cycle
after the HLDA signal is synchronously sampled as
asserted, the PCnet-32 controller will de-assert the
HOLD signal). No bus master accesses will have been
performed during this brief bus ownership period.
Note that this behavior differs from that which occurs
following the assertion of a minimum-width pulse on
the RESET pin (H_RESET). A RESET pin assertion
will cause the HOLD signal to de-assert within six clock
cycles following the assertion. In the RESET pin case,
the PCnet-32 controller will not wait for the assertion of
the HLDA signal before de-asserting the HOLD signal.
Vendor Specific Word
This I/O offset is reserved for use by the system de-
signer. The PCnet-32 controller will not respond to ac-
cesses directed toward this offset.
Reserved I/O Space
These locations are reserved for future use by AMD.
The PCnet-32 controller does not respond to accesses
directed toward these locations, but future AMD prod-
ucts that are intended to be upward compatible with the
PCnet-32 controller may decode accesses to these lo-
cations. Therefore, the system designer may not utilize
these I/O locations.