Designing an application board compatible with either
standard M24LRxx-R or energy-harvesting M24LRxxE-R devices
Introduction
The goal of this application note is to describe how to design application boards accepting
either standard M24LRxx-R or energy-harvesting M24LRxxE-R devices.
Figure 2.Typical schematic of an application powered from M24LRxxE-R. . . . . . . . . . . . . . . . . . . . . 6
4/11Doc ID 018544 Rev 2
AN3355M24LRxx-R and M24LRxxE-R pin-out comparison
%
!#
!#
6SS
6CC
%
3#,
3$!
6OUT
!#
!#
6SS
6CC
7)0"US Y
3#,
3$!
-36
-,2XX2
-,2XX%2
1 M24LRxx-R and M24LRxxE-R pin-out comparison
The standard dual-interface M24LRxx-R and the energy-harvesting M24LRxxE-R devices
have small differences in pin-out, which apply to only two pins:
●M24LRxx-R
–Pin1: E0 input (used to define the hardware address of the I²C-bus slave)
–Pin7: E1 input (used to define the hardware address of the I²C-bus slave)
●M24LRxxE-R
–Pin1: Vout (output used to deliver supply voltage to the application)
–Pin7: WIP/Busy output signal (during a Write cycle)
Figure 1.Two families, two pin-outs
When designing a new application, it can be useful to design an application board which can
embed either the standard M24LRxx-R or the energy-harvesting M24LRxxE-R devices.
Doc ID 018544 Rev 25/11
Designing a board compatible with both devicesAN3355
!PPLICATIONCONTROLLER
-#5!3)#x
6OUT
!#
!#
6SS
6CC
7)0"USY
3#,
3$!
2PULLUP
0OWERSUPPLY
MANAGEMENT
)NPU T(I:
)£#BUS
-36
-,2XX%2
2 Designing a board compatible with both devices
The purpose of this application note is to design an application board that accepts either the
standard M24LRxx-R (dual-interface) or the M24LRxxE-R (energy-harvesting) devices.
Let’s see how pin1 and pin7 are used in a typical application based on M24LRxxE-R.
●Pin1: M24LRxxE-R Vout pin, providing a power supply to the application.
This pin is actually connected to the input of the application power supply management
block.
●Pin7: M24LRxxE-R WIP/Busy output.
This pin is connected to one input of the application controller.
Figure 2.Typical schematic of an application powered from M24LRxxE-R
If we substitute the M24LRxxE-R (offering the Energy harvesting function) with an
M24LRxx-R (without energy-harvesting output), we have to check that the two pins 1 and 7
do not induce malfunction or stress in the application.
Conditions applying to pin1:
The M24LRxx-R pin1 is the E0 input. Its logical value is internally read as:
●either E0=1 when directly connected to V
●or E0=0 when directly connected to V
●or E0=0 when left unconnected (HiZ).
6/11Doc ID 018544 Rev 2
ss
cc
,
,
AN3355Designing a board compatible with both devices
Comparing this with the M24LRxxE-R requirements, we can see that:
●If pin1 is directly connected to V
cc
:
–OK for the M24LRxx-R,
–not compatible with the M24LRxxE-R: this would short-circuit Vout to V
●If pin1 is directly connected to V
ss
:
cc
.
–OK for the M24LRxx-R,
–not compatible with the M24LRxxE-R: this would short-circuit Vout to V
●If pin1 is left unconnected (HiZ):
ss
.
–OK for the M24LRxx-R.
–OK for the M24LRxxE-R.
Table 1.Compatibility overview (Pin1)
Pin1M24LRxxx-RM24LRxxE-RResult
Connected to V
Connected to V
Left unconnected
(or connected to a
high impedance)
cc
ss
E0=1Conflict on VoutNot possible
E0=0Conflict on VoutNot possible
E0=0OKOK
We can see that the correct way to design an application accepting either M24LRxx-R or
M24LRxxE-R is to define E0=0 for the M24LRxx-R.
Conditions applying to pin7:
The M24LRxx-R pin7 is the E1 input. Its logical value is internally read as:
●either E1=1 when directly connected to V
●or E1=0 when directly connected to V
●or E1=0 when left unconnected (HiZ).
Comparing this with the M24LRxxE-R requirements, we can see that, consequently:
●If pin7 is directly connected to V
cc
:
–OK for the M24LRxx-R,
–not compatible with the M24LRxxE-R: this would create a short-circuit when
WIP/Busy outputs a 0.
●If pin7 is directly connected to V
ss
:
–OK for the M24LRxx-R,
–not compatible with the M24LRxxE-R: this would force WIP/Busy signal to V
therefore inhibit the WIP/Busy information.
●If pin7 is left unconnected (HiZ):
–OK for the M24LRxx-R,
–OK for the M24LRxxE-R.
ss
,
CC
,
and
ss
Doc ID 018544 Rev 27/11
Designing a board compatible with both devicesAN3355
Table 2.Compatibility overview (Pin7)
Pin7M24LRxxx-RM24LRxxE-RResult
Connected to V
Connected to V
cc
ss
E1=1
E1=0
Conflict on
WIP/Busy
WIP/Busy = 0
(always)
Not possible
WIP/Busy info
inhibited
Left unconnected
(or connected to a
E1=0OKOK
high impedance)
One can see that the correct way to design an application accepting either M24LRxx-R or
M24xxxE-R is to define E1=0.
8/11Doc ID 018544 Rev 2
AN3355Summary
3 Summary
When designing an application board that will accept either M24LRxx-R or M24LRxxE-R,
the following rules should be kept in mind:
M24LRxx-R
The Device Select byte (first byte transmitted by the I²C-bus master selecting the device to
be accessed) is defined as shown in Tab le 3 .
Table 3.M24LRxx-R Device Select byte
Device type identifier
(1)
Chip Enable address
b7b6b5b4b3b2b1b0
Device select code1010E2
1. The most significant bit, b7, is sent first.
2. E0 and E1 are compared against the respective external pins on the memory device.
3. E2 selects either the memory of the system sector.
(3)
E1E0RW
(2)
RW
The inputs E0,E1 have to be defined as 0,0 (which is the case when the E0,E1 pins are left
unconnected). The Device Select byte is therefore:
●either 1.0.1.0. 0.0.0.RW (where RW is the Read/Write bit) when addressing data in the
memory array,
●or 1.0.1.0. 1.0.0.RW (where RW is the Read/Write bit) when addressing the system
parameter sector.
M24LRxxE-R
In this case of PCB implementation, the E0 and E1 inputs are connected to the power
supply management block and the WIP/Busy output is connected to a high impedance
input, as shown in Figure 2.
The Device Select byte (first byte transmitted by the I²C-bus master) defines the device to be
selected. The Device Select byte is defined as shown in the following table.
Table 4.M24LRxxE-R Device Select byte
Device type identifier
b7b6b5b4b3b2b1b0
Device select code1010E2
1. The most significant bit, b7, is sent first.
2. E2 selects either the memory of the system sector.
(1)
Chip Enable addressRW
(2)
11RW
The Device Select byte is therefore:
●either 1.0.1.0. 0.1.1.RW (where RW is the Read/Write bit) when addressing data in the
memory array,
●or 1.0.1.0. 1.1.1.RW (where RW is the Read/Write bit) when addressing the system
parameter sector.
Doc ID 018544 Rev 29/11
Revision historyAN3355
4 Revision history
Table 5.Document revision history
DateRevisionChanges
29-Mar-20111Initial release.
24-May-20112Updated Section 3: Summary.
10/11Doc ID 018544 Rev 2
AN3355
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries (“ST”) reserve the
right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any
time, without notice.
All ST products are sold pursuant to ST’s terms and conditions of sale.
Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no
liability whatsoever relating to the choice, selection or use of the ST products and services described herein.
No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this
document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products
or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such
third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST’S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS
OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS EXPRESSLY APPROVED IN WRITING BY AN AUTHORIZED ST REPRESENTATIVE, ST PRODUCTS ARE NOT
RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, AIR CRAFT, SPACE, LIFE SAVING, OR LIFE SUSTAINING
APPLICATIONS, NOR IN PRODUCTS OR SYSTEMS WHERE FAILURE OR MALFUNCTION MAY RESULT IN PERSONAL INJURY,
DEATH, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE. ST PRODUCTS WHICH ARE NOT SPECIFIED AS "AUTOMOTIVE
GRADE" MAY ONLY BE USED IN AUTOMOTIVE APPLICATIONS AT USER’S OWN RISK.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void
any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any
liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries.
Information in this document supersedes and replaces all information previously supplied.
The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.