CS5535 datasheet(80/555 Pages) NSC

80 / 555 page

www.national.com

Revision 0.8

GLPCI_SB Functional Description (Continued)

4.2.15 Exception Handling

This section describes how various errors are handled by

the PCI Bus Interface block.

Since PERR# is not implemented on the CS5535 or the

GX2 processor, error reporting via this signal is not sup-

ported. In a GX2/CS5535 system, other PCI devices that

do have the PERR# pin must have a pull-up.

4.2.16 Out-Bound Write Exceptions

When performing an out-bound write on PCI, three errors

may occur: master abort, target abort, and parity error.

When a master or target abort occurs, the PCI Bus Inter-

face block will flush any stored write data. If enabled, an

ASMI is generated. ASMI generation is enabled and

reported in GLPCI_SB GLD_MSR_SMI (MSR 51000002h).

Parity errors are detected and handled by the processor.

The failed transaction will not be retried.

4.2.17 Out-Bound Read Exceptions

When performing an out-bound read on PCI, three errors

may occur: master abort, target abort, and detected parity

error. When a master or target abort occurs, the PCI Bus

Interface block will return the expected amount of data. If

enabled, an ASMI is generated. ASMI generation is

enabled and reported in GLPCI_SB GLD_MSR_SMI (MSR

51000002h). Parity errors are detected and handled by the

processor. The failed transaction will not be retried.

4.2.18 In-Bound Write Exceptions

When performing an in-bound write from PCI, 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, an ASMI is gener-

ated if it is enabled. ASMI generation is enabled and

reported in GLPCI_SB GLD_MSR_SMI (MSR 51000002h).

However, the corrupted write data will be passed along to

the GLIU.

4.2.19 In-Bound Read Exceptions

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 Bus Interface block along with the

associated exceptions. The PCI Bus Interface block should

simply pass the read response data along to the PCI bus.

CS5535 数据表(PDF) 80 Page - National Semiconductor (TI)

CS5535 数据表(HTML) 80 Page - National Semiconductor (TI)

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

数据表下载