欢迎访问ic37.com |
会员登录 免费注册
发布采购

FM24V01-G 参数 Datasheet PDF下载

FM24V01-G图片预览
型号: FM24V01-G
PDF下载: 下载PDF文件 查看货源
内容描述: [Memory Circuit, 16KX8, CMOS, PDSO8, GREEN, MS-012AA, SOIC-8]
分类和应用: PC静态存储器光电二极管内存集成电路
文件页数/大小: 14 页 / 372 K
品牌: RAMTRON [ RAMTRON INTERNATIONAL CORPORATION ]
 浏览型号FM24V01-G的Datasheet PDF文件第1页浏览型号FM24V01-G的Datasheet PDF文件第2页浏览型号FM24V01-G的Datasheet PDF文件第3页浏览型号FM24V01-G的Datasheet PDF文件第5页浏览型号FM24V01-G的Datasheet PDF文件第6页浏览型号FM24V01-G的Datasheet PDF文件第7页浏览型号FM24V01-G的Datasheet PDF文件第8页浏览型号FM24V01-G的Datasheet PDF文件第9页  
FM24V01 - 128Kb I2C FRAM  
SCL  
SDA  
7
6
0
Stop  
(Master) (Master)  
Start  
Data bits  
(Transmitter)  
Data bit Acknowledge  
(Transmitter) (Receiver)  
Figure 3. Data Transfer Protocol  
Stop Condition  
Second and most common, the receiver does not  
acknowledge to deliberately end an operation. For  
example, during a read operation, the FM24V01 will  
continue to place data onto the bus as long as the  
receiver sends acknowledges (and clocks). When a  
read operation is complete and no more data is  
needed, the receiver must not acknowledge the last  
byte. If the receiver acknowledges the last byte, this  
will cause the FM24V01 to attempt to drive the bus  
on the next clock while the master is sending a new  
command such as stop.  
A stop condition is indicated when the bus master  
drives SDA from low to high while the SCL signal is  
high. All operations using the FM24V01 should end  
with a stop condition. If an operation is in progress  
when a stop is asserted, the operation will be aborted.  
The master must have control of SDA (not a memory  
read) in order to assert a stop condition.  
Start Condition  
A start condition is indicated when the bus master  
drives SDA from high to low while the SCL signal is  
high. All commands should be preceded by a start  
condition. An operation in progress can be aborted by  
asserting a start condition at any time. Aborting an  
operation using the start condition will ready the  
FM24V01 for a new operation.  
Slave Address  
The first byte that the FM24V01 expects after a start  
condition is the slave address. As shown in Figure 4,  
the slave address contains the device type or slave  
ID, the device select address bits, a page address bit,  
and a bit that specifies if the transaction is a read or a  
write.  
If during operation the power supply drops below the  
specified VDD minimum, the system should issue a  
start condition prior to performing another operation.  
Bits 7-4 are the device type (slave ID) and should be  
set to 1010b for the FM24V01. These bits allow other  
function types to reside on the 2-wire bus within an  
identical address range. Bits 3-1 are the device select  
address bits. They must match the corresponding  
value on the external address pins to select the  
device. Up to eight FM24V01 devices can reside on  
the same two-wire bus by assigning a different  
address to each. Bit 0 is the read/write bit. R/W=1  
indicates a read operation and R/W=0 indicates a  
write operation.  
Data/Address Transfer  
All data transfers (including addresses) take place  
while the SCL signal is high. Except under the two  
conditions described above, the SDA signal should  
not change while SCL is high.  
Acknowledge  
The acknowledge takes place after the 8th data bit has  
been transferred in any transaction. During this state  
the transmitter should release the SDA bus to allow  
the receiver to drive it. The receiver drives the SDA  
signal low to acknowledge receipt of the byte. If the  
receiver does not drive SDA low, the condition is a  
no-acknowledge and the operation is aborted.  
High Speed Mode (HS-mode)  
The FM24V01 supports a 3.4MHz high speed mode.  
A master code (0000 1XXXb) must be issued to place  
the device into high speed mode. Communication  
between master and slave will then be enabled for  
speeds up to 3.4MHz. A stop condition will exit HS-  
mode. Single- and multiple-byte reads and writes are  
supported. See Figures 10 and 11 for HS-mode  
timings.  
The receiver would fail to acknowledge for two  
distinct reasons. First is that a byte transfer fails. In  
this case, the no-acknowledge ceases the current  
operation so that the part can be addressed again.  
This allows the last byte to be recovered in the event  
of a communication error.  
Rev. 3.0  
Jan. 2012  
Page 4 of 14