AM486DX5-133W16BHC AMD (ADVANCED MICRO DEVICES), AM486DX5-133W16BHC Datasheet - Page 31

• Manufacturer Part Number: AM486DX5-133W16BHC
• Manufacturer: AMD (ADVANCED MICRO DEVICES)

Specifications of AM486DX5-133W16BHC

• Family Name: Am486
• Device Core Size: 32b
• Frequency (max): 133MHz
• Instruction Set Architecture: RISC
• Supply Voltage 1 (typ): 3.45V
• Operating Supply Voltage (max): 3.6V
• Operating Supply Voltage (min): 3.3V
• Operating Temp Range: 0C to 85C
• Operating Temperature Classification: Commercial
• Mounting: Surface Mount
• Pin Count: 208
• Package Type: SQFP
• Lead Free Status / Rohs Status: Not Compliant

3.8.8.1
The microprocessor aborts a cache line fill during a burst
read if BOFF is asserted during the access. Upon re-
gaining the bus, the read access commences where it
left off when BOFF was recognized. External buffers
should take this cycle continuation into consideration if
BOFF is allowed to abort burst read cycles.
3.8.8.2
Similar to the burst read, the burst write also can be
aborted at any time with the BOFF signal. Upon regain-
ing access to the bus, the write continues from where it
was aborted. External buffers and control logic should
take into consideration the necessary control, if any, for
burst write continuations.
3.8.8.3
Locked bus cycles occur in various forms. Locked ac-
cesses occur during read-modify-write operations, in-
terrupt acknowledges, and page table updates.
Although asserting BOFF during a locked cycle is per-
mitted, extreme care should be taken to ensure data
coherency for semaphore updates and proper data or-
dering.
3.8.9 BOFF During Write-Back
If BOFF is asserted during a write-back, the processor
performing the write-back goes off the bus in the next
clock cycle. If BOFF is released, the processor restarts
that write-back access from the point at which it was
aborted. The behavior is identical to the normal BOFF
case that includes the abort and restart behavior.
3.8.10 Snooping Characteristics During a Cache
The microprocessor takes responsibility for responding
to snoop cycles for a cache line only during the time that
the line is actually in the cache or in a copy-back buffer.
There are times during the cache line fill cycle and during
the cache replacement cycle when the line is “in transit”
and snooping responsibility must be taken by other sys-
tem components.
The following cases apply if snooping is invoked via
AHOLD, and neither HOLD nor BOFF is asserted.
System designers should consider the possibility
that a snooping cycle may arrive at the same time
as a cache line fill or replacement for the same ad-
dress. If a snooping cycle arrives at the same time
as a cache line fill with the same address, the CPU
uses the cache line fill, but does not place it in the
cache.
If a snooping cycle occurs at the same time as a
cache line fill with a different address, the cache line
fill is placed into the cache unless EADS is recog-
nized before the first BRDY but after ADS is assert-
ed, or EADS is recognized on the last BRDY of the
Line Fill
Cache Line Fills
Cache Line Copy-Backs
Locked Accesses
Enhanced Am486DX Microprocessor Family
P R E L I M I N A R Y
3.8.11 Snooping Characteristics During a
If a copy-back is occurring because of a cache line re-
placement, the address being replaced can be matched
by a snoop until assertion of the last BRDY of the copy-
back. This is when the modified line resides in the copy-
back buffer. An EADS as late as two clocks before the
last BRDY can cause HITM to be asserted.
Figure 15 illustrates the microprocessor relinquishing
responsibility of recognizing snoops for a line that is
copied back. It shows the latest EADS assertion that
can cause HITM assertion. HITM remains active for only
one clock period in that example. HITM remains active
through the last BRDY of the corresponding write-back;
in that case, the write-back has already completed. This
is the latest point where snooping can start, because
two clock cycles later, the final BRDY of the write-back
is applied.
If a snoop cycle hits the copy-back address after the first
BRDY of the copy-back and ADS has been issued, the
microprocessor asserts HITM. Keep in mind that the
write-back was initiated due to a read miss and not due
to a snoop to a modified line. In the second case, no
snooping is recognized if a modified line is detected.
3.9
The Enhanced Am486DX microprocessors support
cache invalidation and flushing, much like the standard
486DX microprocessor Write-through mode. However,
the addition of the write-back cache adds some com-
plexity.
3.9.1 Cache Invalidation through Software
To invalidate the on-chip cache, the Enhanced
Am486DX microprocessors use the same instructions
as the Am486 microprocessors. The two invalidation in-
structions, INVD and WBINVD, while similar, are slightly
different for use in the write-back environment.
The WBINVD instruction first performs a write-back of
the modified data in the cache to external memory. Then
it invalidates the cache, followed by two special bus
cycles. The INVD instruction only invalidates the cache,
regardless of whether modified data exists, and follows
with a special bus cycle. The utmost care should be
taken when executing the INVD instruction to ensure
memory coherency. Otherwise, modified data may be
invalidated prior to writing back to main memory. In
Write-back mode, WBINVD requires a minimum of 4100
internal clocks to search the cache for modified data.
Writing back modified data adds to this minimum time.
WBINVD can only be stopped by a RESET.
cache line fill. In these cases, the line is not placed
into the cache.
Copy-Back
Cache Invalidation and Flushing in
Write-Back Mode
31