SL3S1003_1013 All information provided in this document is subject to legal disclaimers. © NXP Semiconductors N.V. 2015. All rights reserved.
Product data sheet
COMPANY PUBLIC
Rev. 3.7 — 21 May 2015
201237 20 of 43
NXP Semiconductors
SL3S1003_1013
UCODE G2iM and G2iM+
The features can only be activated/deactivated using standard EPC WRITE if the EPC
bank is unlocked. The permanent and temporary bits of the Configuration Word can be
toggled without the need for an Access Password in case the Access Password is set to
zero. In case the EPC bank is locked the lock needs to be removed before applying
changes or the ChangeConfig command has to be used.
10.7.2 UCODE G2iM and UCODE G2iM+ special features control mechanism
Special features of the UCODE G2iM are managed using a configuration word
(Config-Word) located at address 200h in the EPC memory bank.
The entire Config-Word is selectable (using the standard EPC SELECT command), as
well as single bits, and can be read using standard EPC READ command and modified
using the standard EPC WRITE or ChangeConfig custom command in case the EPC
memory is locked for writing.
ChangeConfig can be executed from the OPEN and SECURED state.
The chip will take all “Toggle Bits” for ’0’ if the chip is in the OPEN state or the ACCESS
password is zero; therefore it will not alter any status bits, but report the current status
only. The command will be ignored with an invalid CRC-16 or an invalid handle. The chip
will then remain in the current state. The CRC-16 is calculated from the first
command-code bit to the last handle bit.
A ChangeConfig command without frame-sync and proceeding Req_RN will be ignored.
The command will also be ignored if any of the RFU bits are toggled.
In order to change the configuration, to activate/deactivate a feature a ’1’ has to be written
to the corresponding register flag to toggle the status. E.g. sending 0x0002 to the register
will activate the read protection of the TID. Sending the same command a second time will
again clear the read protection of the TID. Invalid toggling on indicator or RFU bits are
ignored.
Executing the command with zero as payload or in the OPEN state will return the current
register settings. The chip will reply to a successful ChangeStatus with an extended
preamble regardless of the TRext value of the Query command.
After sending a ChangeConfig an interrogator shall transmit CW for less than TReply or
20ms, where TReply is the time between the interrogator's ChangeConfig command and
the chip’s backscattered reply. An interrogator may observe three possible responses
after sending a ChangeConfig, depending on the success or failure of the operation
• ChangeConfig succeeded: The chip will backscatter the reply shown above
comprising a header (a 0-bit), the current Config-Word setting, the handle, and a
CRC-16 calculated over the 0-bit, the Config-Word and the handle. If the interrogator
observes this reply within 20 ms then the ChangeConfig completed successfully.
• The chip encounters an error: The chip will backscatter an error code during the CW
period rather than the reply shown below (see EPCglobal Spec for error-code
definitions and for the reply format).
• ChangeConfig does not succeed: If the interrogator does not observe a reply within
20 ms then the ChangeConfig did not complete successfully. The interrogator may
issue a Req_RN command (containing the handle) to verify that the chip is still in the
interrogator's field, and may reissue the ChangeConfig command.
