AN3408 Datasheet, PDF (18/38 Pages) STMicroelectronics – The NFC technology allows accessing standard

Example of NDEF record
AN3408
4.1.1
Memory mapping for text record type on LRI2K
Each message character is written in hexadecimal.
Table 24. LRI2K memory mapping for “ISO15693 as NFC tag” NDEF message
RF block Byte number
0
1
2
3
0
CC field
0xE1
0x10
0x20
0x00
1
User data field 0x03
0x1A
0xD1
0x01
2
0x16
0x54
0x02
0x65[e]
3
0x6E[n]
0x49[I]
0x53[S]
0x4F[O]
4
0x31|1]
0x35[5]
0x36[6]
0x39[9]
5
0x33[3]
0x20[ ]
0x61[a]
0x73[s]
6
0x20[ ]
0x4E[N]
0x46[F]
0x43[C]
7
0x20[ ]
0x74[t]
0x61[a]
0x67[g]
8
0xFE
4.2
18/38
URI record
Example 2: This example defines an NDEF message which is made of one single record.
The message is the URL “http://www.st.com”.
The record header is 0xD1.
In this case, the payload is 0x01 and “st.com”.
Table 25. URI record message structure
NDEF data
T
L
V as defined into URI Record Definition document⁽¹⁾
Terminator
0x03
0x0B
0xD1
0x01
0x07
0x55
0x01 “st.com” 0xFE
Type
NDEF
message
TLV
Length (11 bytes)
Record head
Type length
Payload length (07 bytes)⁽²⁾
Type (U value) for URI record type
URI header identifier (http://www.)
URI body Identifier in UTF-8 string
Terminator TLV
1. Refer to [URI] document – on page 1.
2. Payload length = URI identifier + UTF-8 string length = 1 + 6 = 7d.
DocID018867 Rev 4