PCI-MT32-XP-N2 Lattice, PCI-MT32-XP-N2 Datasheet - Page 39

• Manufacturer Part Number: PCI-MT32-XP-N2
• Description: FPGA - Field Programmable Gate Array PCI Master/Target 32B
• Manufacturer: Lattice

Specifications of PCI-MT32-XP-N2

• Factory Pack Quantity: 1

Lattice Semiconductor
IPUG18_09.2, November 2010
Table 2-14. 64-bit Master Single Write Transaction with a 64-bit Local Interface
CLK
10
11
1
2
3
4
5
6
7
8
9
Data 1 and 2
Turn around
Address
Phase
Wait
Wait
Idle
Idle
Idle
Idle
Idle
Idle
The local master asserts lm_req64n for the 64-bit data transaction request. It also issues the PCI
starting address, the bus command and the burst length on l_ad_in, lm_cben_in and
lm_burst_length respectively on the same clock cycle.
The Core's Local Master Interface detects the asserted lm_req64n and asserts reqn to request
the use of PCI bus.
gntn is asserted to grant the Core access to the PCI bus. Core is now the PCI master.
Since gntn is asserted and the current bus is idle, the Core is going to start the bus transactions.
The Core asserts lm_gntn to inform the local master that the bus request is granted.
If both lm_req64n and lm_gntn were asserted on the previous cycle, lm_status[3:0] is
changed to ‘Address Loading’ to indicate the starting address, the bus command and the burst
length are being latched.
The local master de-asserts lm_req64n when the previous lm_status[3:0] was ‘Address
Loading’ and if it doesn’t want to request another PCI bus transaction.
The Core asserts framen and req64n to initiate the 64-bit write transaction when gntn was
asserted and lm_status[3:0] was ‘Address Loading’ on the previous cycle. It also drives the
PCI starting address on ad[31:0] and the PCI command on cben[3:0]. On the same cycle, it
outputs lm_status[3:0] as ‘Bus Transaction’ to indicate the beginning of the address/data
phases.
lm_burst_cnt gets the value of the burst length.
Because lm_rdyn was asserted on the previous cycle and the next cycle is the first data phase,
the local master provides Data 1 and Data 2 on l_ad_in[63:0] and the byte enables on
lm_cben_in[7:0]. And the Core asserts lm_ldata_xfern and lm_hdata_xfern to the local
master to signify these data and byte enables are being read and will be transferred to the PCI
bus.
Asserting lm_rdyn means the local master is ready to write data. If it is not, it keeps lm_rdyn de-
asserted until it is ready.
The Core de-asserts reqn when framen was asserted and lm_req64n was de-asserted on the
previous cycle.
If the target completes the fast decode and is ready to receive 64-bit data, it asserts devseln,
ack64n and trdyn.
With lm_ldata_xfern and lm_hdata_xfern asserted on the previous cycle that was the
address phase, the local master increments the address counter while the Core transfers Data 1
and Data 2 and their byte enables to ad[63:0] and cben[7:0].
Because this is the first write data phase and devseln is just asserted, the master keeps framen
asserted and irdyn de-asserted to judge 64-bit or 32-bit transaction.
Since ack64n and trdyn are asserted on the previous cycle. The Core asserts
lm_64bit_transn to indicate the current data transaction is 64-bits wide. It de-asserts lm_gntn
to follow gntn.
With lm_rdyn asserted in the previous cycle, the Core asserts irdyn and deasserts framen for
a single cycle transaction. Since both irdyn and trdyn are asserted, the data phase is com-
pleted on the cycle.
The Core relinquishes control of framen, req64n, ad and cben. It de-asserts irdyn, decreases
‘lm_burst_cnt’ to zero and changes lm_status[3:0] into ‘Bus Termination’ with
lm_termination as ‘Normal Termination’ because both trdyn and irdyn were asserted last
cycle. The target de-asserts devseln, ack64n and trdyn.
The Core relinquishes control of irdyn, par and par64.
39
Description
Functional Description
PCI IP Core User’s Guide