STMicroelectronics AN3057 How to manage simultaneous Datasheet

AN3057
Application note
How to manage simultaneous I²C and RF data transfers with
the M24LRxx-R and M24LRxxE-R devices
1
Introduction
The M24LRxx-R or M24LRxxE-R is an EEPROM device designed to be accessed via two
different interfaces: a wired I²C interface and a standard contactless ISO 15693 RFID
interface.
Figure 1.
Typical application of an M24LRxx-R or M24LRxxE-R dual interface EEPROM
Application master
SDA
I²C bus
M24LRxx
SCL
ISO 15693
15693 RF
RF
ISO
Application board
ai17547v2
ST has published various supporting application notes explaining how the RF interface
works and the basic principles of passive RFID technology. These documents are available
from: www.st.com/dualeeprom.
The possibility of using two different interfaces to control the dual-interface EEPROM implies
two host controllers: a microcontroller with an I²C bus and an ISO 15693 RFID reader. Due
to their nature, these two host controllers are not synchronized, which means that both
controllers might try to access the M24LRxx-R or M24LRxxE-R concurrently.
To manage this kind of situation, the M24LRxx-R or M24LRxxE-R has a built-in circuitry able
to handle possible concurrent communications and powering activities from the RF and I²C
sides.
This application note describes how the M24LRxx-R or M24LRxxE-R arbitration circuitry
operates.
Table 1 lists the products concerned by this application note.
Table 1.
Applicable products
Type
Dual interface EEPROMs
Note:
October 2012
Applicable products
M24LRxx-R, M24LRxxE-R
The standard M24LRxx-R and energy-harvesting M24LRxxE-R devices will be referred to
as M24LRxx devices throughout the document.
Doc ID 16239 Rev 4
1/15
www.st.com
Contents
AN3057
Contents
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2
RF - I²C arbitration mechanism description . . . . . . . . . . . . . . . . . . . . . . 5
3
2.1
Communications and power supply conditions . . . . . . . . . . . . . . . . . . . . . 5
2.2
Communication arbitration when the RF and I²C channels are
both active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2
2/15
I²C busy states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.2
RF busy states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.3
Arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Recommendations when developing the M24LRxx
application software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1
4
2.2.1
Issuing a command through the I²C channel . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1
I²C request while the RF channel is busy . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.2
I²C requests and RF time slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.3
An I²C request was interrupted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Issuing a command through the RF channel . . . . . . . . . . . . . . . . . . . . . . 13
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Doc ID 16239 Rev 4
AN3057
List of tables
List of tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Applicable products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Four possible combinations of power supply sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Possible cases of communication arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
M24LRxx status according to command and VCC supply. . . . . . . . . . . . . . . . . . . . . . . . . . 13
Document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Doc ID 16239 Rev 4
3/15
List of figures
AN3057
List of figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
4/15
Typical application of an M24LRxx-R or M24LRxxE-R dual interface EEPROM . . . . . . . . . 1
I²C read command busy state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
I²C write command busy state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
RF read command busy state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
RF write command busy state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
RF Stay Quiet command busy state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Example of an Inventory command where the M24LRxx is decoded in
Slot 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
I²C polling when the RF channel is processing a command . . . . . . . . . . . . . . . . . . . . . . . . . 9
M24LRxx state transition diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Optimal hardware schematic of an M24LRxx application . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Doc ID 16239 Rev 4
AN3057
2
RF - I²C arbitration mechanism description
RF - I²C arbitration mechanism description
The M24LRxx arbitration circuitry is twofold. It contains:
2.1
●
a power management unit that handles the power coming potentially from the RF or the
I²C side
●
a communication arbitration unit that tackles potential concurrent communications from
the RF and the I²C sides
Communications and power supply conditions
The power supply management unit has been designed to allow for flexibility, especially
when both the RF power and the wired power line are active at the same time.
The basic principle is:
●
When supplied only from the RF side:
–
●
the M24LRxx can be accessed only by the RF reader
When supplied from both the VCC pin and the RF field:
–
the M24LRxx will serve the first decoded command (either RF or I²C) and will not
decode any command from the other interface (either I²C or RF) until the first
decoded command is complete.
Table 2.
Possible
cases
Four possible combinations of power supply sources
VCC
RF field
Actions
Case 1
0 V or not
connected
Off
The M24LRxx is reset.
Case 2
0 V or not
connected
On
RF data transfers: yes
I²C data transfers: no
Case 3
On(1)
On
RF data transfers: yes
I²C data transfers: yes
(see Section 2.2: Communication
arbitration when the RF and I²C channels
are both active for details).
Case 4
On(1)
Off
RF data transfers: no
I²C data transfers: yes
1.
VCC is “On” when the value is between VCCmin and VCCmax. Please refer to the M24LRxx datasheet for
full details.
Doc ID 16239 Rev 4
5/15
RF - I²C arbitration mechanism description
2.2
AN3057
Communication arbitration when the RF and I²C channels are
both active
Arbitration depends on whether the I²C and RF channels are in the busy state. Section 2.2.1
and Section 2.2.2 give the definitions of the I²C and RF busy states, respectively.
2.2.1
I²C busy states
When decoding an I²C read command, the M24LRxx is in the I²C busy state from the Start
condition until the Stop condition.
Figure 2.
I²C read command busy state
Start
Read command
Stop
I²C busy
ai17339
When decoding an I²C write command, the M24LRxx is in the I²C busy state from the Start
condition until the completion of the write cycle (triggered by the Stop condition).
Figure 3.
I²C write command busy state
Start
Write command
Stop
Write cycle
I²C busy
ai17340
2.2.2
RF busy states
In most cases, an RF command is defined as a received request initiated by the SOF (start
of frame) and terminated by the decoding of the EOF (end of frame) of the response frame.
RF commands can be gathered into several groups:
Read command group
When decoding an RF read command, the M24LRxx is in the RF busy state from the SOF
(start of frame) of the request frame until the EOF (end of frame) of the response frame. The
figure below shows the RF busy state of commands in the read group.
Figure 4.
RF read command busy state
SOF
Request
EOF
SOF
Response
EOF
RF busy
ai17341
6/15
Doc ID 16239 Rev 4
AN3057
RF - I²C arbitration mechanism description
Commands in the RF read command group are:
●
Read Block, Fast Read Single Block, Read Multiple Blocks, Fast Read Multiple Blocks
●
Get System Info
●
Select
●
Reset to Ready
●
Get Multiple Block Security Status
●
Initiate, Fast Initiate
●
Inventory Initiated
Write command group
When decoding an RF write command, the M24LRxx is in the RF busy state from the SOF
(start of frame) of the request frame until the EOF (end of frame) of the response frame.
Write commands include a write cycle tW. The figure below shows the RF busy state of
commands in the write group.
Figure 5.
RF write command busy state
SOF
Request
EOF
Write cycle tW
SOF
Response
EOF
RF busy
ai17503
Commands in the RF write command group are:
●
Write Block
●
Write AFI, Lock AFI
●
Write DSFID, Lock DSFID
●
Write-sector Password, Lock-sector Password, Present-sector Password
Stay Quiet command
The Stay Quiet command is the only command defined as a single request frame (not
followed by a response frame). The M24LRxx is in the RF busy state during the whole [SOF
…. EOF] sequence as shown in the figure below.
Figure 6.
RF Stay Quiet command busy state
SOF
Request
EOF
RF busy
ai17504
Inventory command
An Inventory command is used when several M24LRxx devices are inside the range of the
same RF electromagnetic field.
When the Inventory command scans 16 slots, the M24LRxx is in the RF busy state from the
SOF (start of frame) of the request frame until the EOF (end of frame) of the response
frame.
Note:
The addressed M24LRxx device might stay a long time in the RF busy state if it is decoded
during the last (16th) time slot.
Doc ID 16239 Rev 4
7/15
RF - I²C arbitration mechanism description
Figure 7.
AN3057
Example of an Inventory command where the M24LRxx is decoded in
Slot 13
Slot 1
SOF
Request
EOF
Slots 2 to 12
EOF
Slot 13
EOF
Response
EOF
RF busy
ai17505
2.2.3
Arbitration
When both interfaces are active (as defined in Case 3 in Table 2: Four possible
combinations of power supply sources), the M24LRxx decodes and executes the first
received command, as detailed in Table 3: Possible cases of communication arbitration.
Table 3.
Possible cases of communication arbitration
Initial state
Event
M24LRxx action
RF command transmitted during an
I²C command
RF command is not
decoded
M24LRxx is in the RF busy state: an RF
VCC active and I²C command
command is being decoded or
transmitted during an RF command
executed
I²C command is not
decoded
M24LRxx is in the I²C busy state: VCC
active and an I²C command is being
decoded or executed
8/15
Doc ID 16239 Rev 4
AN3057
3
Recommendations when developing the M24LRxx application software
Recommendations when developing the M24LRxx
application software
The application software has to take into account that a command might not be executed if
the other channel (I²C or RF) is already processing a command. The application software
should therefore check the M24LRxx busy status before sending a command.
3.1
Issuing a command through the I²C channel
3.1.1
I²C request while the RF channel is busy
If the M24LRxx is processing a command from the RF channel, no command issued on the
I²C bus will be executed, therefore none of the bytes transmitted on the I²C bus will be
acknowledged (NoAck). This information can be considered as the RF busy state(a) and the
application’s I²C software should include a polling loop on the RF busy state (with a timeout
limit) when issuing a command on the I²C bus. In this way, the I²C command can be
completed once the RF command under process has completed.
Figure 8.
I²C polling when the RF channel is processing a command
RF command
in progress
Start condition
Device select
with RW = 0
NO
First byte of the
I²C command
(with RW bit= 0) is
now decoded by the
M24LR64-R
ACK
returned
YES
Send address
and receive ACK
NO
Start
condition
YES
Data for the
Write operation
Device select
with RW = 1
Continue the
Write operation
Continue the
Random Read operation
ai17342
a. In the same way as during an internal write cycle, the M24LRxx is “busy” during tW (please refer to the
M24LRxx datasheet for more details about the polling loop during tW).
Doc ID 16239 Rev 4
9/15
Recommendations when developing the M24LRxx application software
AN3057
Important
It is paramount to exactly carry out the I²C polling sequence described in Figure 8 in order to
keep the M24LRxx in a constant I²C busy state.
●
Right method: once the device select is acknowledged, the I²C command starts
executing until full completion, that is, until the transmission of the Stop condition which
ends the command (or at the end of the write cycle tW, for a write command).
●
Wrong method: looping on the device select until it is acknowledged, sending a Stop
condition and then initiating a new I²C command: this is inadequate as an RF request
might have been served between [Ack] and the new I²C command (time slot during
which the M24LRxx is not in the I²C busy state.
Note:
If the application is disturbed by too great a number of decoded RF commands, it might be
convenient that the I²C bus master prompts the application to stop RF requests so that the
I²C bus can access the M24LRxx.
3.1.2
I²C requests and RF time slots
Application software management
In most cases, the application fully controls the I²C bus. On the other hand, it cannot always
predict RF commands. To have a robust application, the M24LRxx should be fully controlled
through the I²C bus, that is, the application master has to:
1.
determine when the I²C commands have to be transmitted
2.
determine the time slots during which RF transfers may be processed
The reason for this is that RF commands might not be properly transmitted (for example, if
the M24LRxx leaves the RF field). The I²C bus Master has to prevent this from happening by
applying the following rules:
●
The Master determines when the I²C commands have to be transmitted
The Master delivers the supply voltage (through one of its I/Os) to the M24LRxx’s VCC
pin only when an I²C data transfer is under way
●
The Master determines the RF time slots
The Master stops supplying (I/O in Hi-Z) the M24LRxx through its VCC pin upon
completion of the I²C data transfer. RF transfers are processed more safely when the
VCC pin is not supplied, because:
10/15
–
If the decoded RF command is correct, it is executed (no need to supply power
through the VCC pin)
–
If the RF command is truncated (M24LRxx is outside the RF field), the M24LRxx is
reset (Power-off state, see Figure 9).
Doc ID 16239 Rev 4
AN3057
Recommendations when developing the M24LRxx application software
Figure 9.
M24LRxx state transition diagram
Power Off
In field
Out of field
Any other Command
where Select_Flag
is not set
Ready
qu
iet
ay
St
dy
re
a
o
tt
se
Re
Out of RF field
and(1) no DC
power supply
e
er r
)
ID
wh o
y et D)
(U
ad s UI
ct
le
re is t
o ag en
Se
t t Fl er
se ct_ diff
Re ele ect(
S el
S
(U
I
D)
Out of RF field
and(1) no DC
power supply
Select (UID)
Quiet
Stay quiet(UID)
Any other command where the
Address_Flag is set AND
where Inventory_Flag is not set
Selected
Any other command
AI06681b
1. The M24LRxx returns to the “Power-off” state only when both conditions are met: the VCC pin is not
supplied (0 V or Hi-Z) and the tag is outside the RF field.
The M24LRxx reverts to the Power-off state only when the two following conditions are met:
●
the M24LRxx is outside the RF field
●
its VCC pin is not supplied (VCC = 0 V or Hi-Z)
If the M24LRxx is outside the RF field with its VCC pin powered, it retains its internal state
(either “Quiet” or “Selected”, as shown in Figure 9). This means that when the M24LRxx reenters the RF field, it might not answer further RF requests properly.
Doc ID 16239 Rev 4
11/15
Recommendations when developing the M24LRxx application software
AN3057
Application hardware architecture
The application Master should control the I²C bus lines and the power supply line so as to
keep full control of the M24LRxx. Figure 10 shows a typical hardware schematic.
Figure 10. Optimal hardware schematic of an M24LRxx application
VCC
VCC
R=10 Ω
I/O
Application master
VCC
Rpull-up
Battery
C = 10 nF
I²C bus SDA
Master SCL
M24LRxx
V SS
ai17545v2
This type of hardware architecture is optimal in applications where power saving is a key
feature (like portable applications supplied from a battery). The supply voltage can be
directly delivered to an ultralow power microcontroller (for instance the STM8L, information
available from http://www.st.com/mcu/). This implementation makes it possible to keep the
application supply current in the 1 µA range (value of the STM8L supply current when in the
Active-Alt mode) and:
3.1.3
●
the application saves power when in the Standby mode, as the battery does not supply
the standby current to the M24LRxx (40 µA) nor the current through the SDA pull-up
resistor
●
the application controls the M24LRxx in a safe mode (the VCC pin is supplied by the
Master only when an I²C request is being processed)
An I²C request was interrupted
A Start condition defines the I²C channel as busy until the completion of the I²C command
(Stop condition). Therefore, if, for some uncontrolled reasons, the I²C bus master sends a
single Start condition (due to a glitch on the bus or some other unpredictable conditions),
the I²C bus might possibly remain busy indefinitely. The resulting I²C busy state inhibits the
decoding of any subsequent I²C and/or RF requests.
The I²C busy state is reset either by:
●
decoding a device select byte different from 1010 XXXXb
●
decoding a Stop condition
●
the completion of the internal write cycle (tW, triggered by a decoded write instruction)
The best way for the I²C bus Master to clear a spurious busy state is to periodically issue a
[Start+Stop] sequence.
Note:
12/15
In noisy applications, ST recommends to implement the “9 Start + 1 Stop” sequence
described in AN1471 (available from the ST website: www.st.com).
Doc ID 16239 Rev 4
AN3057
3.2
Recommendations when developing the M24LRxx application software
Issuing a command through the RF channel
Case 1: the M24LRxx is processing an I²C command
If the M24LRxx is processing a command from the I²C channel, no command issued on the
RF channel will be executed (the RF command will not provide any response) when the
M24LRxx is I²C busy.
The application’s RF software should include an “I²C busy polling loop” (including a timeout
as there might not be a response) when issuing an RF command. In this way, the RF
command is always correctly executed once the I²C commands under execution are
completed.
Case 2: the M24LRxx application is powered on
The first condition for a safe design of an M24LRxx application is that all the sensitive data
stored in the M24LRxx memory is protected with RF passwords, so that a spurious RF
command could not modify this data.
The second condition for a safe application design is that the application Master fully
controls the M24LRxx. We know that, as explained in Section 3.1.2, if the VCC pin is not
supplied, and the RF field drops to zero while the M24LRxx is decoding an RF command,
then the M24LRxx is reset. This means that the Master has to supply the M24LRxx’s VCC
pin only during an I²C transfer, and leave the VCC pin floating the rest of the time (see
Figure 10).
Depending on the application’s RF data transfer flow, it might also be wise to add a third
level of safety:
●
blindly send a Reset to Ready command before sending any new RF command
sequence: this will reset the M24LRxx logic
●
once an RF session (several commands) is completed, blindly send a Write-sector
Password command with a wrong password value: this will set the internal flag defining
the status of the presented password (flag set as “wrong password presented”).
Case 3: the M24LRxx application is not powered
This is the typical case where the application is packed in a box (at the end of the production
line) and the data update is performed through RF.
The only condition for a safe application design is that the sensitive data stored in the
M24LRxx memory is protected with RF passwords, so that a spurious RF command could
not modify this data.
Table 4.
M24LRxx status according to command and VCC supply
Command processed
by the M24LRxx
I²C command
RF command
VCC pin status
Device status
VCC supplied
I²C busy state
VCC supplied
To be avoided in cases where the RF field might
drop to 0 (RF=0 does not reset the RF logic of the
M24LRxx when VCC is supplied)
VCC = high impedance The M24LRxx is fully dedicated to RF commands
Doc ID 16239 Rev 4
13/15
Revision history
4
AN3057
Revision history
Table 5.
Document revision history
Date
Revision
17-Sep-2009
1
Initial release.
2
Table 2: Four possible combinations of power supply sources
modified.
Section 2.2: Communication arbitration when the RF and I²C
channels are both active, Section 3.1: Issuing a command through
the I²C channel and Section 3.2: Issuing a command through the RF
channel revised.
Small text changes.
19-Nov-2009
3
Figure 1: Typical application of an M24LR64-R dual interface
EEPROM modified.
Section 2.1: Communications and power supply conditions modified.
Table 3: Possible cases of communication arbitration clarified.
Section 3.1: Issuing a command through the I²C channel and
Section 3.2: Issuing a command through the RF channel modified.
Figure 9: M24LRxx state transition diagram added.
24-Oct-2012
4
M24LR64-R replaced by M24LRxx-R and M24LRxxE-R on the cover
page, then by M24LRxx (see Note:).
Added Table 1: Applicable products.
19-Oct-2009
14/15
Changes
Doc ID 16239 Rev 4
AN3057
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 TWO AUTHORIZED ST REPRESENTATIVES, 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.
© 2012 STMicroelectronics - All rights reserved
STMicroelectronics group of companies
Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan Malaysia - Malta - Morocco - Philippines - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America
www.st.com
Doc ID 16239 Rev 4
15/15