поискавой системы для электроныых деталей
  Russian  ▼
ALLDATASHEETRU.COM

X  

ORSPI4 датащи(PDF) 140 Page - Lattice Semiconductor

номер детали ORSPI4
подробное описание детали  Dual SPI4 Interface and High-Speed SERDES FPSC
PDF  263 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
производитель  LATTICE [Lattice Semiconductor]
домашняя страница  http://www.latticesemi.com
Logo LATTICE - Lattice Semiconductor

ORSPI4 датащи(HTML) 140 Page - Lattice Semiconductor

Back Button ORSPI4 Datasheet HTML 136Page - Lattice Semiconductor ORSPI4 Datasheet HTML 137Page - Lattice Semiconductor ORSPI4 Datasheet HTML 138Page - Lattice Semiconductor ORSPI4 Datasheet HTML 139Page - Lattice Semiconductor ORSPI4 Datasheet HTML 140Page - Lattice Semiconductor ORSPI4 Datasheet HTML 141Page - Lattice Semiconductor ORSPI4 Datasheet HTML 142Page - Lattice Semiconductor ORSPI4 Datasheet HTML 143Page - Lattice Semiconductor ORSPI4 Datasheet HTML 144Page - Lattice Semiconductor Next Button
Zoom Inzoom in Zoom Outzoom out
 140 / 263 page
background image
Lattice Semiconductor
ORCA ORSPI4 Data Sheet
140
Write Controller and Write Data DEMUX
The write timing shown in Figure 74 and Figure 75 is generated by the Memory Write Controller (MWC) logic based
on instruction and status signals from the write FIFOs and synchronization information from the Memory Read
Controller (MRC). The MWC has two functions. First it will read the instruction words from the instruction FIFO and
separate the bit fields into address, ID and Data length. Then it will generate write cycle timing based on the type of
memory configured (2 or 4 word burst).
The MWC will also do data/instruction data coherency (ID) checking and generate an error (output
MC_ID_STATUS) if the test fails. The write controllers run at 2x the clock rate (MCLCKx2) in order to generate the
QDRII SRAM data and address timing correctly in relation to the differential memory clock (K, K#). The MWC must
also arbitrate with the MRC to ensure that there is no contention between SRAM read and write cycles, as dis-
cussed in the previous section.
The MWC generates enables to initiate burst writes. Separate read and write address counters are required and
are loaded by the controllers with the content of the address field in the instruction word. In order to support 512k x
36 RAM in 2-word burst mode, 18 active address lines are required, whereas in 4-word burst mode, 17 are
required. Data to the QDRII SRAM must also be demultiplexed (DEMUX) by the Write Data DEMUX block in order
to convert from the MC internal format of 72 bit buses to the 36-bit DDR format for the QDR SRAM.
Read Data Capture, MUX and Read Controller
The read timing shown in Figure 74 and Figure 75 is generated by the Memory Read Controller (MRC) logic, based
on information from the read instruction FIFO. The MRC has two functions. First it will read the instruction words
from the instruction FIFO and separate the bit fields into address and data length information. Then it will generate
read cycle timing, based on the type of memory configured (2 or 4 word burst) and provide synchronization infor-
mation to the Memory Write Controller (MWC).
The read controller generates enables to initiate the read cycle. A separate read address counters is required and
is loaded by the controller with the content of the address field in the instruction word. As was true with the MWR,
to support 512k x 36 RAM in two word burst mode, 17 active address lines are required, whereas in 4-word burst
mode, 18 are required. Data from the QDR RAM must also be multiplexed (MUX) in order to convert to the MC
internal format of 72 bit buses from the 36-bit DDR format for the QDRII SRAM.
In order to capture the SRAM read data the echo clocks (CQ, CQ#) generated by the SRAM are used to latch the
data. This is the most robust and flexible of schemes available to capture the data, as with this source synchronous
technique, the impact of round trip delays from the data leaving the Memory Controller, to data being received back
can be minimized. The outputs of the capture latches are retimed back into the MCLK2x domain in order to be writ-
ten to the Read Data FIFO (RDFIFO) discussed in the next section.
Read Data and Instruction FIFOs
The Read Data FIFO (RDFIFO) is used to store the data that is returned from the QDRII SRAM. It is asynchro-
nously read by logic in the FPGA. The RDFIFO size is 64 X 72 bits.
The Read Instruction FIFO (RIFIFO) is similar to the WIFIFO and is configured 4 by 32 bits respectively in order to
store up to 4 instructions that are written to the MC by logic in the FPGA. The instruction fields are data length
(number of cache lines to read) and address (for QDR memory). The read instruction and data word formats are
shown in Figure 76 and Figure 77 respectively.



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


датащи скачать

Go To PDF Page


ссылки URL



Вашему бизинису помогли Аллдатащит?  [ DONATE ] 

Что такое Аллдатащит   |   реклама   |   контакт   |   Конфиденциальность   |   Ссылка на техническое описание    |   обмен ссыками   |   поиск по производителю
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com