24FC128-I/MNY Microchip Technology, 24FC128-I/MNY Datasheet - Page 8
![128K, 16K X 8, 2.5V HI-SPEED SER EE, IND 8 TDFN 2x3x0.8mm TUBE](/photos/7/21/72165/c04-129_mn_sml.jpg)
24FC128-I/MNY
Manufacturer Part Number
24FC128-I/MNY
Description
128K, 16K X 8, 2.5V HI-SPEED SER EE, IND 8 TDFN 2x3x0.8mm TUBE
Manufacturer
Microchip Technology
Datasheet
1.24LC128-ISN.pdf
(38 pages)
Specifications of 24FC128-I/MNY
Format - Memory
EEPROMs - Serial
Memory Type
EEPROM
Memory Size
128K (16K x 8)
Speed
400kHz, 1MHz
Interface
I²C, 2-Wire Serial
Voltage - Supply
1.7 V ~ 5.5 V
Operating Temperature
-40°C ~ 85°C
Package / Case
8-TDFN
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
24AA128/24LC128/24FC128
6.0
6.1
Following the Start condition from the master, the
control code (four bits), the Chip Select (three bits) and
the R/W bit (which is a logic low) are clocked onto the
bus by the master transmitter. This indicates to the
addressed slave receiver that the address high byte will
follow after it has generated an Acknowledge bit during
the ninth clock cycle. Therefore, the next byte
transmitted by the master is the high-order byte of the
word address and will be written into the Address
Pointer of the 24XX128. The next byte is the Least
Significant Address Byte. After receiving another
Acknowledge signal from the 24XX128, the master
device will transmit the data word to be written into the
addressed memory location. The 24XX128 acknowl-
edges again and the master generates a Stop
condition. This initiates the internal write cycle and
during this time, the 24XX128 will not generate
Acknowledge signals (Figure 6-1). If an attempt is
made to write to the array with the WP pin held high, the
device will acknowledge the command, but no write
cycle will occur, no data will be written, and the device
will immediately accept a new command. After a byte
Write command, the internal address counter will point
to the address location following the one that was just
written.
6.2
The write control byte, word address, and the first data
byte are transmitted to the 24XX128 in much the same
way as in a byte write. The exception is that instead of
generating a Stop condition, the master transmits up to
63 additional bytes, which are temporarily stored in the
on-chip page buffer, and will be written into memory
once the master has transmitted a Stop condition.
Upon receipt of each word, the six lower Address
Pointer bits are internally incremented by ‘
master should transmit more than 64 bytes prior to
generating the Stop condition, the address counter will
roll over and the previously received data will be over-
written. As with the byte write operation, once the Stop
condition is received, an internal write cycle will begin
(Figure 6-2). If an attempt is made to write to the array
with the WP pin held high, the device will acknowledge
the command, but no write cycle will occur, no data will
be written and the device will immediately accept a new
command.
DS21191S-page 8
Note:
WRITE OPERATIONS
Byte Write
Page Write
When doing a write of less than 64 bytes
the data in the rest of the page is refreshed
along with the data bytes being written.
This will force the entire page to endure a
write cycle, for this reason endurance is
specified per page.
1
’. If the
6.3
The WP pin allows the user to write-protect the entire
array (0000-3FFF) when the pin is tied to V
V
sampled at the Stop bit for every Write command
(Figure 1-1). Toggling the WP pin after the Stop bit will
have no effect on the execution of the write cycle.
SS
Note:
the write protection is disabled. The WP pin is
Write Protection
Page write operations are limited to
writing bytes within a single physical
page, regardless of the number of
bytes actually being written. Physical
page boundaries start at addresses
that are integer multiples of the page
buffer size (or ‘page size’) and end at
addresses that are integer multiples of
[page size – 1]. If a Page Write
command attempts to write across a
physical page boundary, the result is
that the data wraps around to the
beginning of the current page (over-
writing data previously stored there),
instead of being written to the next
page, as might be expected. It is,
therefore, necessary for the applica-
tion software to prevent page write
operations that would attempt to cross
a page boundary.
2010 Microchip Technology Inc.
CC
. If tied to