
Am79C965A
37
Table 14. CLL Value and Floating Address Pins
BCLK
Bus Clock
Clock input that provides timing edges for all interface
signals. This clock is used to drive the system bus inter-
face and the internal buffer management unit. This
clock is NOT used to drive the network functions.
Input
BE0
–
BE3
Byte Enable
These signals indicate which bytes on the data bus are
active during read and write cycles. When BE3 is
active, the byte on D31
–
D24 is valid. BE2
–
BE0 active
indicate valid data on pins D23
–
D16, D15
–
D8, D7
–
D0,
respectively. The byte enable signals are outputs for
bus master and inputs for bus slave operations.
Input/Output
BLAST
Burst Last Output
When the BLAST signal is asserted, then the next time
that BRDY or RDYRTN is asserted, the burst cycle is
complete.
BOFF
Backoff
BOFF is monitored as an input during Bus Master ac-
cesses. When PCnet-32 controller is current local bus
master, it will float all appropriate bus mastering signals
within 1 clock period of the assertion of BOFF. When
BOFF is de-asserted, PCnet-32 controller will restart
any accesses that were suspended due to the
assertion of BOFF and then will proceed with other
scheduled accesses, if any. Register access cannot be
performed to the PCnet-32 device while BOFF is
asserted.
Input
BRDY
Burst Ready
BRDY functions as an input to the PCnet-32 controller
during bus master cycles. When BRDY is asserted dur-
ing a master cycle, it indicates to the PCnet-32
controller that the target device is accepting burst
transfers. It also serves the same function as RDYRTN
does for non-burst accesses. That is, it indicates that
the target device has accepted the data on a master
write cycle, or that the target device has presented
valid data onto the bus during master read cycles.
Input/Output
If BRDY and RDYRTN are sampled active in the same
cycle, then RDYRTN takes precedence, causing the
next transfer cycle to begin with a T1 cycle.
BRDY functions as an output during PCnet-32
controller slave cycles and is always driven inactive
(HIGH).
BRDY is floated if the PCnet-32 controller is not being
accessed as the current slave device on the local bus.
D/C
Data/Control Select
During slave accesses to the PCnet-32 controller, the
D/C pin, along with M/IO and W/R, indicates the type of
cycle that is being performed. PCnet-32 controller will
only respond to local bus accesses in which D/C is
driven HIGH by the local bus master.
Input/Output
During PCnet-32 controller bus master accesses, the
D/C pin is an output and will always be driven HIGH.
D/C is floated if the PCnet-32 controller is not the
current master on the local bus.
D0
–
D31
Data Bus
Used to transfer data to and from the PCnet-32 control-
ler to system resources via the local bus. D31
–
D0 are
driven by the PCnet-32 controller when performing bus
master writes and slave read operations. Data on D31
–
D0 is latched by the PCnet-32 controller when
performing bus master reads and slave write
operations.
Input/Output
The PCnet-32 controller will always follow Am386DX
byte lane conventions. This means that for word and
byte accesses in which PCnet-32 controller drives the
data bus (i.e. master write operations and slave read
operations) the PCnet-32 controller will produce dupli-
cates of the active bytes on the unused half of the 32-
bit data bus. Table 15 illustrates the cases in which
duplicate bytes are created.
CLL Value
Floated Portion of Address
Bus During AHOLD
00000
None
00001
A31
–
A2
00010
A31
–
A3
00011
Reserved CLL Value
00100
A31
–
A4
00101
–
00111
Reserved CLL Values
01000
A31
–
A5
01001
–
01111
Reserved CLL Values
10000
A31
–
A6
10001
–
11111
Reserved CLL Values