AMX DESIGN XPRESS V 1.5 - PROGRAMMER GUIDE User's Guide download pdf (Page 72)

72 www.xilinx.com Virtex-5 FPGA Integrated Endpoint Block

UG197 (v1.5) July 22, 2009

Chapter 4: Integrated Endpoint Block Operation

That Memory Read Request-Locked (MRdLk) requests do not include a

payload. Any MRdLk requests with payload must be discarded by the

user and a malformed TLP must be signaled.

2.3 Required User

That a Completion with Data (CplD) has a 3DW header. Any CplD with

a 4 DW header must be discarded by the user and a malformed TLP must

be signaled.

2.3 Required User

That an I/O request has a 3DW header. Any I/O request with a 4DW

header must be discarded by the user and a malformed TLP must be

signaled.

2.2.7 Required User

That the byte enable rules for received memory reads are followed. If not,

TLP must be discarded by the user and a malformed TLP must be

signaled.

2.2.5 Required User

Checks Made Regarding Request Handling

Unsupported request types. Reported as an unsupported request. The

user must generate the appropriate completion TLP.

Note: While type 0 configuration requests are routed to the integrated

Endpoint block’s configuration completer, type 1 configuration requests

are routed to the receive Transaction Layer interface and should be

handled by the user as an unsupported request.

2.3.1 Required User

Requests that violate the programming model of the device. Reported as

a completer abort. The user must generate the appropriate completion

TLP.

2.3.1 Optional User

Requests that cannot be processed due to a device-specific error

condition. Reported as a completer abort. The user must generate the

appropriate completion TLP.

2.3.1 Required User

That completions do not include more data than permitted by the

MAX_PAYLOAD_SIZE. Any completion that violates this rule is treated

as a Malformed TLP.

2.3.1.1 Required Endpoint block

Violations of RCB. Any completion that violates the RCB rules is treated

as a Malformed TLP.

2.3.1.1 Optional User

Checks Made Regarding Completion Handling

Unexpected completions. 2.3.2 Required User

Completions with a status of request retry for requests other than

configuration requests. Treated as a malformed TLP.

2.3.2 Optional User

Completions with a completion status of unsupported request or

completer abort. Reported via conventional PCI reporting mechanisms.

2.3.2 Required User

Checks Made Regarding Virtual Channel Mechanism

That requesters that do not support the VC capability structure only

operate on TC0. Received requests on TC1-TC7 must be handled

normally (without error) and completions must be returned on the same

TC in which the request was received.

2.5 Optional User

Table 4-2: Error Checking Summary (Continued)

PCI Express

Specification

Section

Check is

Required

or Optional

Where Check is

Implemented

1 ... 71 72 73 ... 120

Comments to this Manuals

No comments

AMX DESIGN XPRESS V 1.5 - PROGRAMMER GUIDE User's Guide Page 72

Comments to this Manuals

Related products and manuals for TVs & monitors AMX DESIGN XPRESS V 1.5 - PROGRAMMER GUIDE