ALXD800EEXJ2VD AMD (ADVANCED MICRO DEVICES), ALXD800EEXJ2VD Datasheet - Page 568

no-image

ALXD800EEXJ2VD

Manufacturer Part Number
ALXD800EEXJ2VD
Description
Manufacturer
AMD (ADVANCED MICRO DEVICES)
Datasheet

Specifications of ALXD800EEXJ2VD

Operating Temperature (min)
0C
Operating Temperature (max)
85C
Operating Temperature Classification
Commercial
Mounting
Surface Mount
Lead Free Status / RoHS Status
Compliant

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
ALXD800EEXJ2VD
Manufacturer:
AMD
Quantity:
453
Part Number:
ALXD800EEXJ2VD
Manufacturer:
AMD
Quantity:
784
Part Number:
ALXD800EEXJ2VD
Manufacturer:
AMD
Quantity:
20 000
Company:
Part Number:
ALXD800EEXJ2VD C3
Quantity:
91
Part Number:
ALXD800EEXJ2VD-C3
Manufacturer:
INTEL
Quantity:
472
Part Number:
ALXD800EEXJ2VD-C3
Manufacturer:
AMD
Quantity:
20 000
6.15.6
6.15.6.1
When performing an out-bound write on the PCI bus, two
errors may occur: target abort and PERR# assertion.
When a target abort occurs, the PCI Bus Interface block
must flush any stored write data. It must then report the
error. The assertion of PERR# is handled generically. The
failed transaction will not be retried.
6.15.6.2
When performing an out-bound read on the PCI bus, two
errors may occur: target abort and parity error. When a tar-
get abort occurs, the PCI Bus Interface block must return
the expected amount of data with sufficient error signals.
568
Exception Handling
Out-Bound Write Exceptions
Out-Bound Read Exceptions
33234C
6.15.6.3
When performing an in-bound write from the PCI bus, two
errors may occur: a detected parity error and a GLIU
exception. A GLIU exception cannot be relayed back to the
originating PCI bus master because in-bound PCI writes
are always posted. When a parity error is detected, the
PERR# signal must be asserted by the PCI Bus Interface
block. However, the corrupted write data will be passed
along to the GLIU.
6.15.6.4
When performing an in-bound read from the GLIU, the
EXCEP flag may be set on any received bus-WORD of
data. This may be due to an address configuration error
caused by software or by an error reported by the source of
data. The asynchronous ERR and/or SMI bit will be set by
the PCI Bus Interface block and the read data, valid or not,
will be passed to the PCI Interface block along with the
associated exceptions. The PCI Bus Interface block should
simply pass the read response data along to the PCI bus.
In-Bound Write Exceptions
In-Bound Read Exceptions
AMD Geode™ LX Processors Data Book
GeodeLink™ PCI Bridge

Related parts for ALXD800EEXJ2VD