QG80331M500SL9BE Datasheet, PDF (51/67 Pages) Intel Corporation – Intel 80331 I/O Processor Specification Update

Intel^® 80331 I/O Processor
Specification Clarifications
Specification Clarifications
1.
Issue:
Status:
2.
Issue:
Status:
3.
Issue:
Status:
4.
Issue:
Status:
5.
Issue:
Status:
64 MB and 2 GB DDR333 capacities not to be tested in post-silicon
validation
Intel is not able to test 64 MB and 2 GB DDR333 DIMMs due to availability. Intel cannot
guarantee proper functionality since validation cannot be completed.
No Fix. See the Table , “Summary Table of Changes” on page 9.
DDR-II 400 Unbuffered DIMMs are not supported
The Intel^® 80331 I/O processor (80331) supports DDR333 buffered (registered) and unbuffered
DIMMs, but only supports DDR-II 400 buffered (registered) DIMMs. DDR-II 400 unbuffered
DIMMs are not supported.
No Fix. See the Table , “Summary Table of Changes” on page 9.
Interrupt behavior in the 80331 no bridge mode
When in the 80331 No Bridge Mode (BRG_EN = 0), the external interrupts behave just like when
the bridge is enabled in the 80331 (BRG_EN = 1), in that the S_INT[D:A]# interrupt inputs can be
forwarded to the P_INT[D:A]# interrupt outputs. The only difference between the two modes is
how the internal Messaging Unit interrupt is forwarded. In the 80331 Mode, it is forwarded to
P_INTC#, and in the 80331 No Bridge Mode it is forwarded on P_INTA#.
No Fix. See the Table , “Summary Table of Changes” on page 9.
Memory map for 2 GByte of DDR memory
The 80331 can support up to 2Gbytes of DDR SDRAM, but it cannot cross a 2GB boundary,
therefore it must be mapped to either 0x00000000 - 0x7fffffff or 0x80000000 - 0xffffffff. Either
range conflicts with one or more of the statically assigned regions. The recommendation is to
disable the direct outbound ATU window, in order to use the larger 2GB memory, by clearing
ATUCR.8 (default setting is ‘0’ - disabled).
No Fix. See the Table , “Summary Table of Changes” on page 9.
Back to back MCU MMR reads
The memory controller unit (MCU) returns the wrong memory mapped register (MMR) read data,
when two MMR read transactions are enqueued into the transaction queues at the same time. This
cannot happen from the BIU port as mapping the MMRs to this space is illegal. The only way this
can occur is for two internal bus devices to request info from the MCU MMRs at the same time
(with different addresses). For example, the BIU (via the Intel XScale^® core) and the ATU (via the
host), which is a very unlikely usage model.
No Fix. See the Table , “Summary Table of Changes” on page 9.
Specification Update
51