Datenblatt-Suchmaschine für elektronische Bauteile
  German  ▼
ALLDATASHEETDE.COM

X  

S80KS2563 Datenblatt(PDF) 5 Page - Infineon Technologies AG

Teilenummer S80KS2563
Bauteilbeschribung  256 Mb: HYPERRAM??self-refresh dynamic RAM (DRAM) with Octal xSPI interface 1.8 V
PDF  53 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Hersteller  INFINEON [Infineon Technologies AG]
Direct Link  http://www.infineon.com
Logo INFINEON - Infineon Technologies AG

S80KS2563 Datenblatt(HTML) 5 Page - Infineon Technologies AG

  S80KS2563 Datasheet HTML 1Page - Infineon Technologies AG S80KS2563 Datasheet HTML 2Page - Infineon Technologies AG S80KS2563 Datasheet HTML 3Page - Infineon Technologies AG S80KS2563 Datasheet HTML 4Page - Infineon Technologies AG S80KS2563 Datasheet HTML 5Page - Infineon Technologies AG S80KS2563 Datasheet HTML 6Page - Infineon Technologies AG S80KS2563 Datasheet HTML 7Page - Infineon Technologies AG S80KS2563 Datasheet HTML 8Page - Infineon Technologies AG S80KS2563 Datasheet HTML 9Page - Infineon Technologies AG Next Button
Zoom Inzoom in Zoom Outzoom out
 5 / 53 page
background image
Datasheet
5 of 53
002-31339 Rev. *C
2021-09-27
256 Mb: HYPERRAM™ self-refresh dynamic RAM (DRAM) with Octal xSPI interface
1.8 V
General description
1
General description
The 256 Mb HYPERRAM™ device is a high-speed CMOS, self-refresh DRAM, with xSPI (Octal) interface. The DRAM
array uses dynamic cells that require periodic refresh. Refresh control logic within the device manages the refresh
operations on the DRAM array when the memory is not being actively read or written by the xSPI interface master
(host). Since the host is not required to manage any refresh operations, the DRAM array appears to the host as
though the memory uses static cells that retain data without refresh. Hence, the memory is more accurately
described as pseudo static RAM (PSRAM).
Since the DRAM cells cannot be refreshed during a read or write transaction, there is a requirement that the host
limit read or write burst transfers lengths to allow internal logic refresh operations when they are needed. The
host must confine the duration of transactions and allow additional initial access latency, at the beginning of a
new transaction, if the memory indicates a refresh operation is needed.
1.1
xSPI (Octal) interface
xSPI (Octal) is a SPI-compatible low signal count, DDR interface supporting eight I/Os. The DDR protocol in xSPI
(Octal) transfers two data bytes per clock cycle on the DQ input/output signals. A read or write transaction on
xSPI (Octal) consists of a series of 16-bit wide, one clock cycle data transfers at the internal RAM array with two
corresponding 8-bit wide, one-half-clock-cycle data transfers on the DQ signals. All inputs and outputs are
LV-CMOS compatible. Device are available as 1.8 V VCC/VCCQ (nominal) for array (VCC) and I/O buffer (VCCQ)
supplies, through different ordering part number (OPN).
Each transaction on xSPI (Octal) must include a command whereas address and data are optional. The transac-
tions are structures as follows:
• Each transaction begins with CS# going LOW and ends with CS# returning HIGH.
• The serial clock (CK) marks the transfer of each bit or group of bits between the host and memory. All transfers
occur on every CK edge (DDR mode).
• Each transaction has a 16-bit command which selects the type of device operation to perform. The 16-bit
command is based on two 8-bit opcodes. The same 8-bit opcode is sent on both edges of the clock.
• A command may be stand-alone or may be followed by address bits to select a memory location in the device
to access data.
• Read transactions require a latency period after the address bits and can be zero to several CK cycles. CK must
continue to toggle during any read transaction latency period. During the command and address parts of a
transaction, the memory can indicate whether an additional latency period is needed for a required refresh time
(tRFH) which is added to the initial latency period; by driving the RWDS signal to the HIGH state.
• Write transactions to registers do not require a latency period.
• Write transactions to the memory array require a latency period after the address bits and can be zero to several
CK cycles. CK must continue to toggle during any write transaction latency period. During the command and
address parts of a transaction, the memory can indicate whether an additional latency period is needed for a
required refresh time (tRFH) which is added to the initial latency period by driving the RWDS signal to the HIGH
state.
• In all transactions, command and address bits are shifted in the device with the most significant bits (MSb) first.
The individual data bits within a data byte are shifted in and out of the device MSb first as well. All data bytes
are transferred with the lowest address byte sent out first.



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


Datenblatt Download

Go To PDF Page


Link URL



War ALLDATASHEET hilfreich?  [ DONATE ] 

Über Alldatasheet   |   Werbung   |   Kontakt   |   Privatsphäre und Datenschutz   |   Link zum Datenblatt    |   Linktausch   |   Hersteller
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