Signals Reference

For memory or I/O transactions, the byte-enable signals indicate that valid data is requested or being transferred on the corresponding byte on the 128-bit data bus. BE[0]# indicates that the least significant byte is valid, and BE[7]# indicates that the most significant byte is valid. Since BE[7:0]# specifies the validity of only 8 bytes on the 16 byte wide bus, A[3]# is used to determine which half of the data bus is validated by BE[7:0]#.

For special transactions ((REQa[5:0]# = 001000B) and (REQb[1:0]# = 01B)), the BE[7:0]# signals carry special cycle encodings as defined in Table A-3. All other encodings are reserved.

Table A-3. Special Transaction Encoding on Byte Enables

Special Transaction

Byte Enables[7:0]#

 

 

NOP

0000 0000

 

 

Shutdown

0000 0001

 

 

Flush (INVD)

0000 0010

 

 

Halt

0000 0011

 

 

Sync (WBINVD)

0000 0100

 

 

Reserved

0000 0101

 

 

StopGrant Acknowledge

0000 0110

 

 

Reserved

0000 0111

 

 

xTPR Update

0000 1000

 

 

For Deferred Reply transactions, BE[7:0]# signals are reserved. The Defer Phase transfer length is always the same length as that specified in the Request Phase except the Bus Invalidate Line (BIL) transaction.

A BIL transaction may return one cache line (128 bytes).

A.1.9 BERR# (I/O)

The Bus Error (BERR#) signal can be asserted to indicate a recoverable error with global MCA. BERR# assertion conditions are configurable at the system level. Configuration options enable BERR# to be driven as follows:

Asserted by the requesting agent of a bus transaction after it observes an internal error.

Asserted by any bus agent when it observes an error in a bus transaction.

When the bus agent samples an asserted BERR# signal and BERR# sampling is enabled, the processor enters a Machine Check Handler.

BERR# is a wired-OR signal to allow multiple bus agents to drive it at the same time.

Datasheet

93

Page 93
Image 93
Intel Itanium 2 Processor manual Berr# I/O, Table A-3. Special Transaction Encoding on Byte Enables