![]() |
|
If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
Datasheet File OCR Text: |
this is information on a product in full production. november 2014 docid023348 rev 7 1/32 m34e04 4-kbit serial presence dete ct (spd) eeprom compatible with jedec ee1004 datasheet - production data features ? 512-byte serial presence detect eeprom compatible with jedec ee1004 specification ? compatible with smbu s serial interface: ? up to 1 mhz transfer rate ? eeprom memory array: ? 4 kbits organized as two pages of 256 bytes each ? each page is composed of two 128-byte blocks ? software data protection for each 128-byte block ? write: ? byte write within 5 ms ? 16 bytes page write within 5 ms ? noise filtering: ? schmitt trigger on bus inputs ? noise filter on bus inputs ? single supply voltage: ? 1.7 v to 3.6 v ? operating temperature range: ? from 0 c up to +95 c ? enhanced esd/latch-up protection ? more than 4million write cycles ? more than 200-year data retention ? rohs-compliant and halogen-free 8-lead ultra thin fine pitch dual flat no lead package (ecopack2 ? ) ufdfpn8 (mc) 2 x 3 mm www.st.com
contents m34e04 2/32 docid023348 rev 7 contents 1 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2 signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.1 serial clock (scl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2 serial data (sda) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.3 slave address (sa2, sa1, sa0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.4 write control (wc ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.5 supply voltage (v cc ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.5.1 operating supply voltage v cc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.5.2 power-up conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.5.3 device reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.5.4 power-down conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1 start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3.2 stop condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3.3 acknowledge bit (ack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3.4 data input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3.5 memory addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3.6 write operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.6.1 byte write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.6.2 page write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.6.3 minimizing system delays by polling on ack . . . . . . . . . . . . . . . . . . . . 14 3.7 read operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.7.1 random address read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.7.2 current address read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.7.3 sequential read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.7.4 acknowledge in read mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.8 setting the write protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.8.1 set and clear the write protection (swpn and cwp) . . . . . . . . . . . . . . 17 3.8.2 read the protection status (rpsn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.8.3 set the page address (span) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.8.4 read the page address (rpa) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 docid023348 rev 7 3/32 m34e04 contents 3 4 initial delivery state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5 use within a ddr4 dram module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1 programming the m34e04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1.1 isolated dram module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1.2 dram module inserted in the applicat ion motherboard . . . . . . . . . . . . 20 6 maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7 dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 8 package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 9 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 10 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 list of tables m34e04 4/32 docid023348 rev 7 list of tables table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 table 2. device type identifier code (dti c) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 table 3. dram dimm connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 4. acknowledge when writing data or defining the write-protection status (instructions with r/w bit = 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 5. acknowledge when reading the pr otection status (instructions with r/w bit = 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 6. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 7. operating conditions (for temperature range 8 device s) . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 8. ac measurement conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 9. input parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 10. cycling performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 11. memory cell data retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 12. dc characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 13. ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 14. ufdfpn8 (mlp8) 8-lead ultra thin fine pitch dual flat package no lead 2 x 3 mm, data29 table 15. ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 16. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 docid023348 rev 7 5/32 m34e04 list of figures 5 list of figures figure 1. logic diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 2. 8-pin package connections (top view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 3. device select code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 4. bus protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 5. write mode sequences in a non write-protected area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 6. write cycle polling flowchart using ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 4 figure 7. read mode sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 8. setting the write protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 figure 9. serial presence detect block diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 figure 10. ac measurement i/o wa veform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 figure 11. ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 figure 12. maximum r bus value versus bus parasitic capacitance (c bus ) for an i 2 c bus at maximum frequency f c = 1 mhz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 13. maximum r bus value versus bus parasitic capacitance (c bus ) for an i 2 c bus at maximum frequency f c = 400 khz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 14. ufdfpn8 (mlp8) 8-lead ultra thin fine pitch dual flat no lead, package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 description m34e04 6/32 docid023348 rev 7 1 description the m34e04 is a 512-b yte eeprom device designed to operate the smbus bus in the 1.7 v - 3.6 v voltage range, with a maximum of 1 mhz transfer rate in the 2.2 v - 3.6 v voltage range, over the jedec defined ambient temperature of 0c / 95c. the m34e04 includes a 4-kbit serial eeprom organized as two pages of 256 bytes each, or 512 bytes of total memory. each page is composed of two 128-byte blocks. the device is able to selectively lock the data in any or all of the four 128-byte blocks. designed specifically for use in dram dimms (dual inline memory modules) with serial presence detect, all the information concerning the dram module configuration (such as its access speed, its size, its organization) can be kept write-protected in one or more memory blocks. the m34e04 device is protocol-compatible with the previous generation of 2-kbit devices, m34e02. the page selection method allows co mmands used with lega cy devices such as m34e02 to be applied to the lower or upper pages of the eeprom. individually locking a 128-byte block may be accomplished using a software write protection mechanism in conjunction with a high input voltage v hv on input sa0. by sending the device a specific smbus sequence, each block may be protected from writes until the write protection is electrically reversed using a separate smbus sequence which also requires v hv on input sa0. the write protection for all four blocks is cleared simultaneously. figure 1. logic diagram figure 2. 8-pin package connections (top view) 1. see the package mechanical data section for package dimensions, and how to identify pin 1. ! ) c 3 ! 3 ! 3 ! 3 $ ! 6 # # - % 7 # 3 # , 6 3 3 3 $ ! 6 3 3 3 # , 7 # 3 ! 3 ! 6 # # 3 ! ! ) c - % docid023348 rev 7 7/32 m34e04 description 31 table 1. signal names signal names description sa2, sa1, sa0 slave address sda serial data scl serial clock wc write control v cc supply voltage v ss ground signal description m34e04 8/32 docid023348 rev 7 2 signal description 2.1 serial clock (scl) the signal applied on this input is used to stro be the data available on sda(in) and to output the data on sda(out). if scl is driven low for ttimeout (see table 13 ) or longer, the m34e04 is set back in standby mode, ready to receive a new start condition. 2.2 serial data (sda) sda is an input/output used to transfer data in or out of the device. sda(out) is an open drain output that may be wire-or?ed with other open drain or open collector signals on the bus. a pull-up resistor must be connected from serial data (sda) to v cc . ( figure 12 indicates how the value of the pull-up resistor can be calculated). 2.3 slave address (sa2, sa1, sa0) (sa2,sa1,sa0) input signals are used to set the value that is to be looked for on the three least significant bits (b3, b2, b1) of the 7- bit device type identifier code (dtic, see table 2 ). these inputs must be tied to v cc or v ss , as shown in figure 3 . when not connected (left floating), these inputs are read as low (0). the sa0 input is used to detect the v hv voltage, when decoding an swp or cwp instruction. figure 3. device select code 2.4 write control (wc ) this input signal is provided for protecti ng the contents of the whole memory from inadvertent write operat ions. write control ( wc ) is used to enable (when driven low) or disable (when driven high) write instructions to the entire memory area. when write control ( wc ) is tied low or left unconnected, the write protection of the memory is determined by the status def ined by the execution of the previous swpi instructions. ! i c 6 # # 6 3 3 3 ! i 6 # # - % 6 3 3 3 ! - % i docid023348 rev 7 9/32 m34e04 signal description 31 2.5 supply voltage (v cc ) 2.5.1 operating supply voltage v cc prior to selecting the memory and issuing instructions to it, a valid and stable v cc voltage within the specified [v cc (min), v cc (max)] range must be applied (see table 8 ). in order to secure a stable dc supply voltage, it is recommended to decouple the v cc line with a suitable capacitor (usually of the order of 10 nf to 100 nf) close to the v cc /v ss package pins. this voltage must remain stable and valid unt il the end of the transmission of the instruction and, for a write instructio n, until the completion of the internal write cycle (t w ). 2.5.2 power-up conditions the v cc voltage has to rise continuously from 0 v up to the minimum v cc operating voltage defined in table 8 and the rise time must not vary faster than 1 v/s. 2.5.3 device reset in order to prevent inadvertent write operations during power-up, a power-on reset (por) circuit is included. at power- up, the device does not respon d to any instruction until v cc reaches the internal reset threshold voltage (this threshold is lower than the minimum v cc operating voltage defined in table 8 ). when v cc passes over the por threshold, the de vice is reset and enters the standby power mode. however, the device must not be accessed until v cc reaches a valid and stable v cc voltage within the specified [v cc (min), v cc (max)] range. in a similar way, during power-down (continuous decrease in v cc ), as soon as v cc drops below the power-on reset threshold voltage, t he device stops responding to any instruction sent to it. 2.5.4 power-down conditions during power-down (continuous decrease in v cc ), the device must be in standby power mode (mode reached after decoding a stop condition, assuming that there is no internal write cycle in progress). signal description m34e04 10/32 docid023348 rev 7 figure 4. bus protocol 3 # , 3 $ ! 3 # , 3 $ ! 3 $ ! 3 t a r t c o n d i t i o n 3 $ ! ) n p u t 3 $ ! # h a n g e ! ) c 3 t o p c o n d i t i o n - 3 " ! # + 3 t a r t c o n d i t i o n 3 # , - 3 " ! # + 3 t o p c o n d i t i o n docid023348 rev 7 11/32 m34e04 device operation 31 3 device operation the device supports the i 2 c protocol. this is summarized in figure 4 . any device that sends data onto the bus is defined to be a transm itter, and any device t hat reads the data is defined to be a receiver. the device that cont rols the data transfer is known as the bus master, and the other device is known as the slave device. a data transfer can only be initiated by the bu s master, which will also provide the se rial clock for synchronization. the memory device is always a slave in all communication. 3.1 start condition start is identified by a falling edge of serial da ta (sda) while serial clock (scl) is stable in the high state. a start condition must precede any data transfer command. the device continuously monitors (except during a writ e cycle) serial data (sda) and serial clock (scl) for a start condition. 3.2 stop condition stop is identified by a rising edge of serial da ta (sda) while serial clock (scl) is stable and driven high. a stop condition terminates communication between the device and the bus master. a read command that is followed by noack can be followed by a stop condition to force the device into the standby mode. a stop condition at the end of a write command triggers the internal eeprom write cycle. 3.3 acknowledge bit (ack) the acknowledge bit is used to indicate a succ essful byte transfer. the bus transmitter, whether a bus master or a slave device, releases serial data (sda) after sending eight bits of data. during the 9 th clock pulse period, the receiver pulls serial data (sda) low to acknowledge the receipt of the eight data bits. 3.4 data input during data input, the device samples serial da ta (sda) on the rising edge of serial clock (scl). for correct device operation, serial data (sda) must be stable during the rising edge of serial clock (scl), and the serial data (sda) signal must change only when serial clock (scl) is driven low. 3.5 memory addressing to start a communication between the bus ma ster and the slave device, the bus master must initiate a start condition. following this, the bus master sends the device select code, shown in table 2 (on serial data (sda), most significant bit first). the device type identifier code (dtic) consists of a 4-bit device type identifier, and a 3-bit slave address (sa2, sa1, sa0). to address the memory array, the 4-bit device type identifier is 1010b; to access the writ e-protection settings, it is 0110b. device operation m34e04 12/32 docid023348 rev 7 up to eight memory devices can be connected on a single serial bus. each one is given a unique 3-bit code on the slave address (sa2, sa1, sa0) inputs. when the device select code is received, the device onl y responds if the slave address is the same as the value on the slave address (sa2, sa1, sa0) inputs. the 8 th bit is the read/ write bit (r w ). this bit is set to 1 for read and 0 for write operations. if a match occurs on the device select code, the corresponding device gives an acknowledgment on serial data (sda) during the 9 th bit time. if the de vice does not match the device select code, it de selects itself from the bus, and goes into standby mode. table 2. device type identifier code (dtic) abbr device type identifier (1) select address (2) (3) r_w_n sa0 pin (4) b7 b6 b5 b4 b3 b2 b1 b0 read rspd 1 0 1 0 lsa2 lsa1 lsa0 1 0 or 1 write wspd 0 set write protection, block 0 swp0 0110 001 0 v hv set write protection, block 1 swp1 1 0 0 0 v hv set write protection, block 2 swp2 1 0 1 0 v hv set write protection, block 3 swp3 0 0 0 0 v hv clear all write protection cwp 0 1 1 0 v hv read protection status, block 0 (5) rps0 0 0 1 1 0, 1 or v hv read protection status, block 1 (5) rps1 1 0 0 1 0, 1 or v hv read protection status, block 2 (5) rps2 1 0 1 1 0, 1 or v hv read protection status, block 3 (5) rps3 0 0 0 1 0, 1 or v hv set page address to 0 (6) spa0 1 1 0 0 0, 1 or v hv set page address to 1 (6) spa1 1 1 1 0 0, 1 or v hv read page address (7) rpa 110 10, 1 or v hv reserved - all other encodings 1. the most significant bit, b7, is sent first. 2. logical serial addresses (lsa) are generated by the combination of inputs on the sa pins. 3. for backward compatibility with m34e02 devices, the order of block select bits (b3 and b1) is not a simple binary encoding of the block number. 4. sa0 pin is driven to vss, vcc or vhv. 5. reading the block protection status results in ack when the block is not write-protected, and results in noack when the block is write-protected. 6. setting the ee page address to 0 selects the lower 256 bytes of eeprom; setting it to 1 selects the upper 256 bytes of eeprom. subsequent read ee or write ee commands operate on the selected ee page. 7. reading the ee page address results in ack when the current page is 0, and noack when the current page is 1. docid023348 rev 7 13/32 m34e04 device operation 31 3.6 write operations following a start condition, the bus master sends a device select code with the r w bit reset to 0. the device acknowledges this, as shown in figure 5 , and waits for an address byte. the device responds to the address byte with an acknowledge bit, and then waits for the data byte. when the bus master generates a stop condit ion immediately after a data byte ack bit (in the ?10 th bit? time slot), either at the end of a by te write or a page write, the internal memory write cycle is triggered. a stop condition at any other time slot does not trigger the internal write cycle. during the internal write cycle, serial data (sda) and serial clock (scl) are ignored, and the device does not respond to any requests. 3.6.1 byte write after the device select code and the address by te, the bus master sends one data byte. if the addressed location is hardware write-protec ted, the device replies to the data byte with noack, and the location is not modified. if, instead, the addressed location is not write- protected, the device replies with ack. the bus master terminates the transfer by generating a stop condition, as shown in figure 5 . figure 5. write mode sequences in a non write-protected area 3.6.2 page write the page write mode allows up to 16 bytes to be written in a single write cycle, provided that they are all located in the same page in the memory: that is, the most significant memory address bits are the same . if more bytes are sent than will fit up to the end of the page, a condition known as ?roll-over? occurs. this should be avoided, as data starts to become overwritten in an implementation dependent way. the bus master sends from 1 to 16 bytes of data, each of which is acknowledged by the device if write control ( wc ) is low. if the addressed location is hardware write-protected, the device replies to the data byte with noac k, and the locations are not modified. after each byte is transferred, the internal byte address counter (the 4 least significant address 3 t o p 3 t a r t " y t e 7 r i t e $ e v i c e s e l e c t " y t e a d d r e s s $ a t a i n 3 t a r t 0 a g e 7 r i t e $ e v i c e s e l e c t " y t e a d d r e s s $ a t a i n $ a t a i n ! ) b 3 t o p $ a t a i n . ! # + ! # + ! # + 2 7 ! # + ! # + ! # + 2 7 ! # + ! # + device operation m34e04 14/32 docid023348 rev 7 bits only) is incremented. the transfer is terminated by the bus master generating a stop condition. 3.6.3 minimizing system delays by polling on ack the sequence, as shown in figure 6 , is: ? initial condition: a write cycle is in progress. ? step 1: the bus master issues a start condi tion followed by a device select code (the first byte of the new instruction). ? step 2: if the device is bu sy with the internal write cycl e, no ack will be returned and the bus master goes back to step 1. if t he device has terminated the internal write cycle, it responds with an ack, indicating th at the device is ready to receive the second part of the instruction (the first byte of this instruction having been sent during step 1). figure 6. write cycle polling flowchart using ack $ , g : u l w h f \ f o h l q s u r j u h v v 1 h [ w 2 s h u d w l r q l v d g g u h v v l q j w k h p h p r u \ 6 w d u w f r q g l w l r q ' h y l f h v h o h f w z l w k 5 : $ & |