AT25DF161-SSH-T Atmel, AT25DF161-SSH-T Datasheet - Page 40

• Manufacturer Part Number: AT25DF161-SSH-T
• Description: IC FLASH 16MBIT 100MHZ 8SOIC
• Manufacturer: Atmel

Specifications of AT25DF161-SSH-T

• Format - Memory: FLASH
• Memory Type: DataFLASH
• Memory Size: 16M (2M x 8)
• Speed: 100MHz
• Interface: SPI, RapidS
• Voltage - Supply: 2.7 V ~ 3.6 V
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 8-SOIC (3.9mm Width)
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

Figure 12-5. Hold Mode
CS
SCK
HOLD
13.
Atmel RapidS Implementation
®
™
To implement Atmel
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 Atmel AT25DF161
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 AT25DF161 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 AT25DF161 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. For example, 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.
Atmel AT25DF161
40
3687E–DFLASH–11/10