AT25DL081-MHN-Y Adesto Technologies, AT25DL081-MHN-Y Datasheet - Page 47
![no-image](/images/no-image-200.jpg)
AT25DL081-MHN-Y
Manufacturer Part Number
AT25DL081-MHN-Y
Description
Flash 8M 1.65-1.95V 100Mhz Serial Flash
Manufacturer
Adesto Technologies
Datasheet
1.AT25DL081-MHN-T.pdf
(59 pages)
Specifications of AT25DL081-MHN-Y
Rohs
yes
Data Bus Width
8 bit
Memory Type
Flash
Memory Size
8 Mbit
Architecture
Flexible, Uniform Erase
Timing Type
Synchronous
Interface Type
SPI
Supply Voltage - Max
1.95 V
Supply Voltage - Min
1.65 V
Maximum Operating Current
20 mA
Operating Temperature
- 40 C to + 85 C
Mounting Style
SMD/SMT
Package / Case
UDFN-8
13.
RapidS Implementation
To implement RapidS and operate at clock frequencies higher than what can be achieved in a viable SPI implementation,
a full clock cycle can be used to transmit data back and forth across the serial bus. The AT25DL081 is designed to
always clock its data out on the falling edge of the SCK signal and clock data in on the rising edge of SCK.
For full clock cycle operation to be achieved, when the AT25DL081 is clocking data out on the falling edge of SCK, the
host controller should wait until the next falling edge of SCK to latch the data in. Similarly, the host controller should clock
its data out on the rising edge of SCK in order to give the AT25DL081 a full clock cycle to latch the incoming data in on
the next rising edge of SCK.
Implementing RapidS allows a system to run at higher clock frequencies since a full clock cycle is used to accommodate
a device’s clock-to-output time, input setup time, and associated rise/fall times.
Example:
Figure 13-1. RapidS Operation
Slave
MOSI = Master Out, Slave In
The Master is the ASIC/MCU and the Slave is the memory device.
The Master always clocks data out on the rising edge of SCK and always clocks data in on the falling edge of SCK.
The Slave always clocks data out on the falling edge of SCK and always clocks data in on the rising edge of SCK.
A. Master clocks out first bit of BYTE A on the rising edge of SCK.
B. Slave clocks in first bit of BYTE A on the next rising edge of SCK.
C. Master clocks out second bit of BYTE A on the same rising edge of SCK.
D. Last bit of BYTE A is clocked out from the Master.
E.
F.
G. Master clocks in first bit of BYTE B.
H. Slave clocks out second bit of BYTE B.
I.
MOSI
MISO
SCK
Last bit of BYTE A is clocked into the slave.
Slave clocks out first bit of BYTE B.
Master clocks in last bit of BYTE B.
CS
If the system clock frequency is 100MHz (10ns cycle time) with a 50% duty cycle, and the host controller
has an input setup time of 2ns, then a standard SPI implementation would require that the slave device be
capable of outputting its data in less than 3ns to meet the 2ns host controller setup time
[(10ns x 50%) – 2ns] not accounting for rise/fall times. In an SPI Mode 0 or 3 implementation, the SPI
Master is designed to clock in data on the next immediate rising edge of SCK after the SPI slave has
clocked its data out on the preceding falling edge. This essentially makes SPI a half-clock cycle protocol and
requires extremely fast clock-to-output times and input setup times in order to run at high clock frequencies.
With a RapidS implementation of this example, however, the full 10ns cycle time is available which gives the
slave device up to 8ns, not accounting for rise/fall times, to clock its data out. Likewise, with RapidS, the
host controller has more time available to output its data to the slave since the slave device would be
clocking that data in a full clock cycle later.
A
1
B
MSB
MISO = Master In, Slave Out
2
C
3
4
BYTE A
t
V
5
6
7
D
8
E
LSB
F
1
G
MSB
2
H
3
AT25DL081 [DATASHEET]
4
BYTE B
5
6
8732E–DFLASH–1/2013
7
8
I
LSB
1
47