IDT PCI Express 89HPES32NT24xG2, User Manual, Page: 277 / 744

IDT Non-Transparent Switch Operation
PES32NT24xG2 User Manual 14 - 29 January 30, 2013
Notes
Unexpected Completions
Table 14.6 lists the conditions for which the NT function handles completions as unexpected comple-
tions.
Conditions Handled as UR Description
PCI Express
Base Specifica-
tion Sect.
Effective BAR Aperture check Refer to section BAR Limit on page 14-2. n/a
Lookup Table Address Translation
error:
Table entry invalid, partition entry
invalid, or out-of-bounds lookup table
entry selected. Refer to section Lookup Table Address
Translation on page 14-5. n/a
Destination Partition errors:
Destination partition not active
Destination partition does not have an
NT endpoint
Destination partition is same as source
partition
BME bit cleared in NT function of desti-
nation partition when translating a
request TLP
Link is down in destination partition’s
upstream port and TLP is destined to
this link
1
.
1.
This excludes inter-function transfers (e.g., NT function to PCI-to-PCI bridge function) in the destination partition, as these
transfers are not destined to the upstream link. Refer to section Link States on page 7-9 for a list of link states in which the link
is considered down (e.g., L2/L3 Ready).
Refer to section Lookup Table Address
Translation on page 14-5, and section
Request ID Translation on page 14-11 n/a
Requester ID miss in NT Mapping Table Refer to section Request ID Translation on
page 14-11
n/a
NT function in D3Hot state Refer to section Overview on page 9-1. 5.3.1.4.1
NT function in destination partition in
D3Hot state Refer to section Overview on page 9-1. n/a
Type 1 Configuration Requests Reception of a Type 1 configuration request
at the NT function. 7.3.3
Vendor Defined Type 0 message recep-
tion
2
2.
NOTE: Vendor Defined Type 1 messages which target the NT function are silently discarded.
Vendor Defined Type 0 message which tar-
gets the NT function. 2.2.8.6
Messages with invalid message code Reception of a message TLP with invalid
message code that targets the NT function. 2.3.1
Poisoned configuration write request,
poisoned memory write request, or poi-
soned message with data targeting the
NT function Reception of a poisoned IO request, mem-
ory write request, or message with data
(except Vendor Defined messages) that tar-
gets a switch port’s NT function. 2.7.2.2
Reception of MRdLk Request Reception of an MRdLk request by the NT
function 6.5.7
Table 14.5 Conditions Handled as Unsupported Requests (UR) by the NT Function