SL3ICS1002 datasheet(31/56 Pages) NXP

31 / 56 page

139036

All information provided in this document is subject to legal disclaimers.

Product data sheet

COMPANY PUBLIC

Rev. 3.6 — 10 March 2011

139036

31 of 56

NXP Semiconductors

SL3ICS1002/1202

UCODE G2XM and G2XL

15.1.1.1 User memory (only G2XM)

The User Memory bank contains a sequential block of 512 bits (32 words of 16 bit)

ranging from address 00h to 1Fh. The user memory can be accessed via Select, Read or

Write command and it may be write locked, permanently write locked, unlocked or

permanently unlocked.

In addition reading of not only of the User Memory but of the whole memory including EPC

and TID can be protected by using the custom ReadProtect command.

15.1.1.2 Special behavior of user memory address 1Fh

WRITE or SELECT of user memory address 1Fh will falsely set an error flag. This will

affect the subsequent READ or SELECT.

The following commands will falsely set an internal error flag (without actually

causing an error):

1) WRITE to user memory with WordPtr=1Fh

2) SELECT to user memory with compare mask ending at bitaddress 1FFh

(e.g. Pointer=1FEh, length=1 or Pointer=1FDh, length=2 …)

Note: The error flag is set independent of the chip state (also chips in the e.g. Ready

state are affected).

The falsely set error flag will affect the following sub sequential commands:

A) READ command with WordCount=0

→ falsely responds with "memory overrun" error

B) SELECT command with Length<>0

→ falsely assumes non existing memory location

The behavior can be avoided with:

• Turning off the RF carrier to reset the chip (This is what readers typically do!).

• Using the READ command with WordCount<>0.

• Sending other command prior to READ or SELECT (e.g. WRITE to address<>1Fh,

ReqRN) or executing READ or SELECT two times.

Remark: The WRITE operation itself is not affected by this problem i.e. data is written

properly! With commercially available readers this behavior is typically not observed.

15.1.1.3 Supported EPC types

The EPC types are defined in the EPC Tag Standards document from EPCglobal.

These standards define completely that portion of EPC tag data that is standardized,

including how that data is encoded on the EPC tag itself (i.e. the EPC Tag Encodings), as

well as how it is encoded for use in the information systems layers of the EPC Systems

Network (i.e. the EPC URI or Uniform Resource Identifier Encodings).

The EPC Tag Encodings include a Header field followed by one or more Value Fields. The

Header field indicates the length of the Values Fields and contains a numbering system

identifier (NSI). The Value Fields contain a unique EPC Identifier and optional Filter Value

when the latter is judged to be important to encode on the tag itself.

SL3ICS1002 bảng dữ liệu(PDF) 31 Page - NXP Semiconductors

SL3ICS1002 bảng dữ liệu(HTML) 31 Page - NXP Semiconductors

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56

bảng dữ liệu tải về

Link URL