www.quicklogic.com
© 2003 QuickLogic Corporation
•
•
•
•
•
•
QL5732 Enhanced QuickPCI Device Data Sheet Rev C
8
PCI Target Interface
Table 2: PCI Target Interface
Signal I/O Description
Usr_Addr_WrData[31:0] O Target address, and target Write data
During all target accesses, the address is presented
on Usr_Addr_WrData[31:0]; at the same time, Usr_Adr_Valid is active. During target Write
transactions, this port also presents valid Write data to the PCI configuration space or user
logic when Usr_Adr_Inc is active.
Usr_CBE[3:0] O PCI command and byte enables During target accesses, the PCI command is presented on
Usr_CBE[3:0]; at the same time, Usr_Adr_Valid is active. This port also presents active-low
byte enables to the PCI configuration space or user logic.
Usr_Adr_Valid O Indicates the beginning of a PCI transaction, and that a target address is valid on
Usr_Addr_WrData[31:0] and the PCI command is valid on Usr_CBE[3:0]. When this signal is
active, the target address must be latched and decoded to determine if this address belongs to
the device's memory or I/O space. Also, the PCI command must be decoded to determine the
type of PCI transaction. On subsequent clocks of a target access, this signal is low, indicating
that address is NOT present on Usr_Addr_WrData[31:0].
Usr_Adr_Inc O Indicates that the target address should be incremented, because the pr evious data transfer has
completed. During burst target accesses, the target address is only presented to the back-end
logic at the beginning of the transaction (when Usr_Adr_V alid is active), and must therefore be
latched and incremented by four for subsequent data transfers. Note that during target Write
transactions, Usr_Adr_Inc indicates valid data on Usr_Addr_WrData[31:0] that must be
accepted by the backend logic (regardless of the state of Usr_Rdy). During Read transactions,
Usr_Adr_Inc signals to the backend that the PCI core has presented the read data on the PCI
bus (TRDYN asserted).
Usr_RdDecode I This signal should be the combinatorial decode of the "user read" command from
Usr_CBE[3:0]. This command may be mapped from any of the PCI Read commands, such as
Memory Read, Memory Read Line, Memory Read Multiple, I/O Read, etc. It is internally
gated with Usr_Adr_Valid.
Usr_WrDecode I This signal should be the combinatorial decode of the "user write" command from
Usr_CBE[3:0]. This command may be mapped from any of the PCI Write comma nds, such as
Memory Write or I/O Write. It is internally gated with Usr_Adr_Valid.
Usr_Select I This signal should be driven active when the address on Usr_Addr_WrData[31:0] has been
decoded and determined to be within the address space of the device. Usr_Addr_WrData[31:0]
must be compared to each of the valid Base Address Registers in the PCI configuration space.
Also, this signal must be gated by the Memory Access Enable or I/O Access Enable registers in
the PCI configuration space (Command Register bits 1 or 0 at offset 04h). Internally gated
with Usr_Adr_Valid.
Usr_Write O This signal is active throughout a "user write" transaction, which has been decoded by
Usr_WrDecode at the beginning of the transaction. The Write strobe for individual DWORDs
of data (on Usr_Addr_WrData[31:0]) during a user Write transaction should be generated by
logically ANDing this signal with Usr_Adr_Inc.
Cfg_Write O This signal is active throughout a "configuration write" transaction. The Write strobe for
individual DWORDs of data (on Usr_Addr_WrData[31:0]) during a configuration Write
transaction should be generated by logically ANDing this signal with Usr_Adr_Inc.
Usr_Read O This signal is active throughout a "user read" transaction, which has been decoded by
Usr_RdDecode at the beginning of the transaction.
Cfg_Read O This signal is active throughout a "configuration read" transaction.