TRF7960EVM User's Guide Literature Number: SLOU192C November 2006 – Revised December 2008
SLOU192C – November 2006 – Revised December 2008 Submit Documentation Feedback
Contents Preface ............................................................................................................................... 7 1 1.1 1.2 ..................................................................................... 11 Description .................................................................................................................. 11 EVM Default Configuration ................................................................................................
www.ti.com 3.5.9 Reset to Ready .................................................................................................... 46 3.5.10 Write AFI (Application Family Identifier) ....................................................................... 47 3.5.11 Lock AFI (Application Family Identifier) ....................................................................... 49 3.5.12 Write DSFID (Data Storage Format ID) ....................................................................... 51 3.5.
www.ti.com List of Figures 2-1 2-2 2-3 2-4 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 TRF7960 EVM Rev - (top side) .......................................................................................... TRF7960EVM Rev A ...................................................................................................... TRF7960EVM Rev A Parallel and Serial Modes ....................................................................... TRF7960EVM Rev A Top and Bottom Views .................................
Tag-it is a trademark of Texas Instruments.
Preface SLOU192C – November 2006 – Revised December 2008 Read Me First This manual is written to provide information about the TRF7960 evaluation module. The user should keep in mind the following points. • It is recommended that the user initially review the data sheet of the device under test. • To better understand the TRF7960 EVM, it is recommended to review the schematic and layout files.
About This Manual www.ti.com Numerical Representations Extensive use is made in this user’s guide of the hexadecimal numbering system when describing bytes transmitted and received.
About This Manual www.ti.com Related Documentation • • • • • • • • • TRF7960/61 Multi-Standard Fully Integrated 13.
Read Me First SLOU192C – November 2006 – Revised December 2008 Submit Documentation Feedback
Chapter 1 SLOU192C – November 2006 – Revised December 2008 Introduction and Description The Texas Instruments TRF7960 evaluation module (EVM) helps designers evaluate the performance of the TRF7960 multiple-protocol RFID transceiver. This manual includes a list of EVM features, a brief description of the module, EVM specifications, details on connecting and using the EVM, and a discussion of the software interface for the EVM.
Introduction and Description SLOU192C – November 2006 – Revised December 2008 Submit Documentation Feedback
Chapter 2 SLOU192C – November 2006 – Revised December 2008 Using the EVM This section describes how to connect the EVM to the host computer. It is recommended that the user connect the EVM as described in this section to avoid damage to the EVM or the TRF7960 installed on the board. 2.1 Unpacking Carefully remove the EVM and accessories from the box. The box should contain: • EVM board (in ESD packaging): • This manual (check the Web for the latest downloadable version of this manual SLOU192).
Hardware Description 2.2 www.ti.com Hardware Description Shown in Figure 2-1 is a TRF7960 EVM Rev. -. An SMA connector can be installed to independently test either the reader or antenna while also configuring circuit components as needed. xxx xxx Figure 2-1.
Hardware Description www.ti.com Shown in Figure 2-2 is a TRF7960 EVM Rev A. The board allows for either a thru hole or edge mount SMA connector for reader or antenna testing. Figure 2-2 shows the board assembly configured for a parallel buss (HDR_4 connected HDR_5). Header 1 is used to inform the microprocessor what I/O buss is being implemented. Both reader and antenna circuits are 50-Ω interfaces. Resister R3 connects the reader output to the PCB antenna.
Hardware Description www.ti.com Shown in Figure 2-3 are examples of EVM configured for parallel and serial busses. xxx xxx TRF7960 Rev A EVM (Parallel Mode) TRF7960 Rev A EVM (Serial Mode) Figure 2-3. TRF7960EVM Rev A Parallel and Serial Modes For SPI or serial interface, jumpers are in place to connect header 5 to header 6. Header 1 is used to inform the microprocessor what I/O bus is being implemented. When using communications it is recommended to use SS (slave select).
Hardware Description www.ti.com Shown in Figure 2-4 are top and bottom views of the TRF7960 EVM Rev. A. In this application the headers are configured with 0-Ω resistors as a cost savings. If needed, 2-mm header pins can be installed. xxx xxx TRF7960 EVM Rev A (top) TRF7960 EVM Rev A (bottom) Figure 2-4.
Connection to a Host PC 2.3 www.ti.com Connection to a Host PC Connect the EVM to a host PC. A USB extension cable may be used, if desired. When using a graphical user interface, the ISO LEDs located on the EVM are inoperative. The ISO LEDs are only operative when the EVM is not being controlled by a host PC. Note: The TRF7960 EVM consumes (at 5-VDC operation) 120 mA of current from the USB port of the computer in full-power transmit mode.
Chapter 3 SLOU192C – November 2006 – Revised December 2008 EVM Software This chapter describes the installation and use of the USB drivers and EVM control program. 3.1 Software Installations Do not plug the EVM into the USB port until instructed to do so. If it is already connected to a USB port, disconnect it now. Download the USB driver and graphical user interface (GUI) software from the Web site http://focus.ti.com/docs/toolsw/folders/print/trf7960evm.html and save to a folder.
Software Installations www.ti.com 3.1.3 Software GUI Installation The software GUI is the file named TRF7960EVM_GUI_V1.1.zip. It can be unzipped using a standard unzip program and is a self-contained executable. Create a folder where desired on the host PC, and unzip the executable into that folder. The program can be run from the folder, or a shortcut can be created and placed on the desktop of the host computer. In most cases, the program automatically detects the COM port.
Software Installations www.ti.com Next, click on Device Manager, then click the + sign next to Ports to expand the ports: If the driver installation was successful and the EVM is plugged in, USB Serial Port should appear in the list of ports, followed by a port number (in this example, COM4). The actual port number may be different. Make note of the COM port number and enter it in the Select Port window of the GUI. Then select the Select Port on GUI (do not press the Enter key).
Software Installation for Rev. A EVM 3.2 www.ti.com Software Installation for Rev. A EVM Follow the steps in the following sections for the Rev. A version of the EVM. 3.2.1 USB Driver Installation Do not plug the EVM into the USB port until instructed to do so. If it is already connected to a USB port, disconnect it now. The USB software installation is a two-step process.
www.ti.com Software Installation for Rev. A EVM 3.2.3 Hardware Installation At this point, attach the EVM to an open USB port. The EVM can be plugged directly into the port or attached at the end of a USB extension cable (type A, not supplied). At this point, the power LED should be lit. Any RFID tag corresponding to a supported protocol can be detected and is indicated by the corresponding LED. 3.2.4 Software GUI Installation The software GUI is the file named TRF7960EVM_REVA_GUI_V1.1.zip.
Software Installation for Rev. A EVM www.ti.com If the driver installation was successful and the EVM is plugged in, CP210x USB to UART Bridge Controller should appear in the list of ports, followed by a port number (in this example, COM10). The actual port number may be different. If automatic detection does not take place, make note of the COM port number and enter it in the Select Port window of the GUI. Then select the Select Port on GUI (do not press the Enter key).
www.ti.com 3.3 Software Interface Software Interface The GUI window is shown following. Each section of the window has a different function. The figure shows the arrangement for the different protocols; Find Tags, Registers, and Test radically change the display. 3.3.1 Program Control Window (Lower Right-Hand Corner) The Select Port window allows the user to enter manually the USB serial port used by the host computer to communicate with the TRF7960 EVM board.
Software Interface www.ti.com 3.3.2 Protocol Tabs Window The protocol tabs window selects between tag protocols and program functions. Available options are: • (ISO/IEC) 15693 – vicinity cards • (ISO/IEC) 14443A – proximity cards • (ISO/IEC) 14443B – proximity cards • Tag-it™ – a proprietary TI protocol 3.3.3 Utility Tabs Window • • • Find Tags – a function that reads tags of all protocols Registers – allows the user to set TRF7960 register values manually Test 3.3.
www.ti.com Software Interface 3.3.9 RSSI Window The RSSI field displays the slot number, UID and the RSSI values of the corresponding tag. If there was a collision and the reader performed a second anticollision procedure, the slot numbers are indicated with an additional character: A = second procedure B = third procedure and so on The main channel, which is AM, is used as the primary one, and PM is the auxiliary channel. The RSSI maximum value is 7 and minimum value is 0.
Set Protocol www.ti.com 3.3.11 Other Functions Other functions on the main EVM control panel are: • Set protocol, which configures the program for the selected protocol once the protocol tab has been selected • Execute button, which processes the selected command • Power control (half or full), which can be used to simulate marginal reception conditions.
ISO/IEC 15693 Protocol www.ti.com 3.5 ISO/IEC 15693 Protocol This section describes commands for the 15693 protocol. After a command has been selected by clicking on the associated command button in the Commands window, the user should set any flags as needed (see Section A.1). If appropriate, enter data in the Tag Data window. An ISO15693 set protocol command sends three commands (register write, set AGC, and set receiver mode (AM/PM).
ISO/IEC 15693 Protocol www.ti.
ISO/IEC 15693 Protocol www.ti.com 3.5.1 Inventory The Inventory command is used to acquire the unique IDs (UID) of ISO15693 tags in the read zone. The two inventory methods supported are 16-slotted and single-slot. A single-slot request allows all transponders in the read zone to reply to the Inventory request. In cases where more than one tag is present, such a request would cause a data collision, which in turn causes a reader to send a collision error message to the GUI.
ISO/IEC 15693 Protocol www.ti.
www.ti.com ISO/IEC 15693 Protocol 3.5.2 Read Single Block The Read Single Block command gets the data from one memory block of the responding tag. In addition to this data, a Block Security Status byte can be requested. This byte shows the write-protection of the block specified [e.g., unlocked, (user/factory) locked, etc.]. To • • • • • read a single block, the user should: Click the button for Read Single Block in the Commands window. Click on any flags that must be set in the Tag Flags window.
ISO/IEC 15693 Protocol www.ti.com Request Packet: 01 0B 00 03 04 18 02 20 02 00 00 (all bytes are continuous; spaces are added for clarity) Note that Option flag is disabled.
www.ti.com ISO/IEC 15693 Protocol 3.5.3 Write Single Block The Write Single Block request writes data to one memory block of the addressed tag(s). In order to successfully write data, the host must know the size of the memory block of the tag. This information is available through the Get System Information request, if supported by the tag. A corrupted response or lack of response from TRF7960 does not necessarily indicate a failure to perform the write operation.
ISO/IEC 15693 Protocol www.ti.
www.ti.com ISO/IEC 15693 Protocol 3.5.4 Lock Block The Lock Block command write-protects one memory block of the addressed tag(s). A corrupted response or lack of response from the TRF7960 does not necessarily indicate a failure to perform the lock operation. Additionally, multiple transponders may process a non-addressed request. Used to permanently lock the requested block To • • • • • lock a block, the user should: Click the button for Lock Block in the Command window.
ISO/IEC 15693 Protocol www.ti.
www.ti.com ISO/IEC 15693 Protocol 3.5.5 Read Multiple Blocks The Read Multiple Blocks command gets the data from multiple memory blocks of the responding tag. In addition to this data, a Block Security Status byte can be requested for each block. This byte shows the write-protection of the block specified [e.g., unlocked, (user/factory) locked, etc.]. To • • • • • • read multiple a blocks, the user should: Click the button for Read Multiple Blocks in the Commands window.
ISO/IEC 15693 Protocol www.ti.
www.ti.com ISO/IEC 15693 Protocol 3.5.6 Write Multiple Blocks The Write Multiple Blocks command writes data to multiple memory blocks of the addressed tags. In order to successfully write data, the host must know the size of the memory block of the tag. Write Multiple Blocks is an optional command, and may not be supported by the tag (see the following screen capture). To • • • • • • write multiple blocks, the user should: Click the button for Write Multiple Blocks in the Commands window.
ISO/IEC 15693 Protocol www.ti.com Executes Write Single Block multiple times.
ISO/IEC 15693 Protocol www.ti.com 3.5.7 Stay Quiet The Stay Quiet command is used to silence a tag, preventing it from responding to any nonaddressed or inventory related commands. The tag does, however, respond to requests with matching UID. As there is no response to this request from the receiving tag, only request status and errors are reported. To • • • • command a tag to stay quiet, the user should: Click the button for Stay Quiet in the Commands window.
ISO/IEC 15693 Protocol www.ti.com 3.5.8 Select The Select command places the addressed tag in the Select state. In this state, it responds to requests with the ISO15693 Select Flag set. This flag is directly controlled by the field present in many ISO15693 library request messages. Any receiving tag currently in the Select state with UID not matching the value sent in the request command, exits that state and enters the Ready state but does not send a reply.
ISO/IEC 15693 Protocol www.ti.com Request Packet: 01 12 00 03 04 18 22 25 8C AC D6 06 00 00 07 E0 00 00 (all bytes are continuous; spaces are added for clarity) Field Contents Comments SOF 01 Start of frame Packet Length 12 Packet length = 18 bytes Constant 00 Begin Data Payload 03 04 Start of data payload Firmware Cmd 18 Request mode Flags 20 Addressed flag is set. Select Cmd 25 UID 8C AC D6 06 UID (reverse byte ordered).
ISO/IEC 15693 Protocol www.ti.com 3.5.9 Reset to Ready The Reset To Ready command places the addressed tag in the Ready state. In this state, it does not respond to requests with the ISO15693 Select Tag Flags set, but to any nonaddressed request or request matching its UID. This command is, in effect, the complement of the Select command, and undoes it. To • • • • reset a tag, the user should: Click the button for Reset to Ready in the Commands window.
www.ti.com ISO/IEC 15693 Protocol 3.5.10 Write AFI (Application Family Identifier) The Write AFI command records a new value to the AFI register (see Section A.6 for AFI codes) of the addressed tag(s). A corrupted response or lack of response from TRF7960 does not necessarily indicate a failure to perform the write operation. Additionally, multiple transponders may process a non-addressed request.
ISO/IEC 15693 Protocol www.ti.
ISO/IEC 15693 Protocol www.ti.com 3.5.11 Lock AFI (Application Family Identifier) The Lock AFI command write-protects the AFI register of the addressed tag(s). A corrupted response or lack of response does not necessarily indicate a failure to perform the lock operation. Additionally, multiple transponders may process a nonaddressed request. To • • • • a lock tag’s AFI, the user should: Click the button for Lock AFI in the Commands window. Click on any flags that must be set in the Tag Flags window.
ISO/IEC 15693 Protocol www.ti.
www.ti.com ISO/IEC 15693 Protocol 3.5.12 Write DSFID (Data Storage Format ID) The Write DSFID (data storage format ID) command writes a new value in the DSFID register of the addressed tag(s). A corrupted response or lack of response from the TRF7960 does not necessarily indicate a failure to perform the write operation. Additionally, multiple transponders may process a nonaddressed request. To • • • • • write a tag’s DSFID, the user should: Click the button for Write DSFID in the Commands Window.
ISO/IEC 15693 Protocol www.ti.
ISO/IEC 15693 Protocol www.ti.com 3.5.13 Lock DSFID (Data Storage Format ID) The Lock DSFID command write-protects the DSFID register of the addressed tag(s). A corrupted response or lack of response from TRF7960 does not necessarily indicate a failure to perform the lock operation. Additionally, multiple transponders may process a nonaddressed request. To • • • • a lock tag’s DSFID, the user should: Click the button for Lock DSFID in the Commands window.
ISO/IEC 15693 Protocol www.ti.
www.ti.com ISO/IEC 15693 Protocol 3.5.14 Get System Info The Get System Info command retrieves identification, application family, data formatting, and memory block sizes as specified in the ISO15693 standard (if tag supports this command). To • • • • get system information, the user should: Click the button for Get System Info in the Commands window. Click on any flags that must be set in the Tag Flags window.
ISO/IEC 15693 Protocol www.ti.
www.ti.com ISO/IEC 15693 Protocol 3.5.15 Get Multiple-Block Security Status (Get Mult_Blk Sel Status) The Get Multiple-Block Security Status (Get Mutt. Blk. Sel Status) command gets a block security status byte for each block requested. This byte encodes the write protection of the block specified (e.g., unlocked, (user/factory) locked, etc.). To • • • • • • get multiple block security status, the user should: Click the button for Get Mult.Blk.Sel Status in the Commands window.
ISO/IEC 15693 Protocol www.ti.
ISO/IEC 14443A Protocol www.ti.com 3.6 ISO/IEC 14443A Protocol This section describes the ISO/IEC 14443A protocol. Program operation is a little different in this protocol compared to ISO 15593. Some commands must be run in sequence: e.g., an Anticollision command, when executed, activates a radio button for the Select command, etc. An ISO14443A set protocol command sends three commands (register write, set AGC, and set receiver mode (AM / PM).
ISO/IEC 14443A Protocol www.ti.
www.ti.com ISO/IEC 14443A Protocol 3.6.1 Anticollision (Execute Button) The Anticollision command is linked with the Select command, in that it must be run first. The request packet specifies the cascade level of the UID, the number of bits send to the tag(s) using Anticollision/Select frame and the actual data bits/bytes. The Anticollision request is transmitted in a bit-oriented anticollision frame. The Select request is sent over the RF interface in a Standard frame.
ISO/IEC 14443A Protocol www.ti.com Request Packet: 01 09 00 03 04 A0 01 00 00 (all bytes are continuous; spaces are added for clarity) Field Contents Comment SOF 01 Start of frame Packet Length 09 Packet length = 9 bytes Constant 00 Begin Data Payload 03 04 Start of data payload Firmware Cmd A0 Tag type A, anticollision, REQA REQA 01 01 = REQA (REQuest type A) 00 = WUPA (Wake UP type A) EOF 00 00 End of frame Anticollision (Tag Response) 14443A REQA.
ISO/IEC 14443A Protocol www.ti.com 3.6.
ISO/IEC 14443B Protocol 3.7 www.ti.com ISO/IEC 14443B Protocol This section describes the ISO 14443B protocol. Similar to the ISO 14443A protocol, program operation is a little different compared to ISO 15693; some commands must be run in sequence. An ISO 14443B set protocol command sends three commands (register write, set AGC, and set receiver mode (AM / PM).
ISO/IEC 14443B Protocol www.ti.
ISO/IEC 14443B Protocol www.ti.com 3.7.1 Request Command (REQB Cmd Format) The Request command determines if a tag is present. To do a Request command, the user should: • Click the button for Request in the Commands window. • Execute the command.
ISO/IEC 14443B Protocol www.ti.
ISO/IEC 14443B Protocol www.ti.com 3.7.2 Wake Up B A Wake Up command is used to take a tag from the HALT state to its idle state.
ISO/IEC 14443B Protocol www.ti.com Wake Up (Tag Response) Response to Wake Up is as follows: 14443B REQB.
ISO/IEC 14443B Protocol www.ti.com 3.7.
ISO/IEC 14443B Protocol www.ti.com 3.7.4 HALTB Command The HALTB cmd is used to set a PICC in a HALT state, which in turn stops the PICC from responding to a REQB command. After entering this state, the PICC ignores all commands except the WUPB (wake up B) command. To do an HALTB command, the user should: • Click the button for HALTA in the Commands window. • Execute the command.
Tag-it Protocol 3.8 www.ti.com Tag-it Protocol A Tag-It set protocol command sends three commands (register write, set AGC, and set receiver mode (AM/PM).
Tag-it Protocol www.ti.
Tag-it Protocol www.ti.com 3.8.1 Simultaneous ID (SID) Poll The SID poll request is used to acquire the simultaneous IDs of Tag-it transponders. This request decreases the likelihood of a data collision by forcing transponders to respond in 1 of 16 slots based on a portion of their SIDs. To perform a slotted sequence, the Slot Marker/End-of-Frame Request is used in conjunction with this request.
Tag-it Protocol www.ti.
Tag-it Protocol www.ti.com 3.8.2 Get Version The Get VERSION request acquires information on the properties of a responding tag. These properties include IC version and manufacturer information as well as the number and size of memory blocks available. To • • • get the IC version, the user should: Click the button for Get Version in the Commands window. Click on the Address flag, if desired, in the Tag Flags window. Execute the command.
Tag-it Protocol www.ti.com Get Version Response Request mode 80T60F40E[C03400D2844102050307] Comment: 80T end of transmit, 60F receive data buffer 75% full, 40E end of receive, [C03400D2844102050307] tag response shown as follows: [C0 34 00D28441 02 05 03 07] Field Contents Comments Response Code C0 Response from tag to reader Command Code 34 Get version cmd = 3 Address flag set = 4, not set = 0 1100 00 0011 0100 C 0 3 4 SID 00D28441 4 bytes or 32 bits Chip Mfg.
Tag-it Protocol www.ti.com 3.8.3 Get Block The Get Block request gets the data from one memory block of the responding tag. In addition to this data, a block security status byte is returned. This byte indicates the write protection status of the block specified [e.g., unlocked, (user/factory) locked, etc.]. To • • • • • get blocks, the user should: Click the button for Get Block in the Commands window. Click on the Address flag, if desired, in the Tag Flags window.
Tag-it Protocol www.ti.com Get Block Response Request mode 80T40E[C010031DE2088440] Comment: 80T end of transmit, 40E end of receive, [C010031DE2088440] tag response shown as follows: Field Contents Comments Response Code C0 Response from tag to reader Figure 3-2 Command Code 10 Get block command Figure 3-2 Block number 03 No. + 1 = 4 Figure 3-2 Block data 1D E2 08 84 Note: Bits are shifted.
Tag-it Protocol www.ti.com 3.8.4 Put Block The Put Block request writes data to one memory block of the addressed tag(s). In order to successfully write data, the host must know the size of the memory block of the tag. This information is available through the Get IC Version Request or SID Poll sequence requesting version data. A corrupted response or lack of response from the TRF7960 does not necessarily indicate a failure to perform the write operation.
Tag-it Protocol www.ti.com GUI (Hexadecimal) 0 0 2 8 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 5 Tag-it protocol 0 0 Reader Request 0 3 < SID > < Block Number > < Data Blk > Cmd Code Added bits to complete byte Figure 3-4.
Tag-it Protocol www.ti.com 3.8.5 Put Block Lock The Put Block Lock request writes data to one memory block of the addressed tag(s) and locks that block from further write operations. In order to successfully write data, the host must know the size of the memory block of the tag. This information is available through the Get IC Version request or SID Poll sequence requesting version data. A corrupted response or lack of response does not necessarily indicate a failure to perform the write-lock operation.
Tag-it Protocol www.ti.com GUI (Hexadecimal) Tag-it protocol 0 3 0 0 3 8 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 7 0 0 Reader Request < SID > < Block Number > < Data Blk > Cmd Code Added bits to complete byte Figure 3-6.
Tag-it Protocol www.ti.com 3.8.6 Lock Block The Lock Block request write-protects one memory block of the addressed tag(s). A corrupted response or lack of response does not necessarily indicate a failure to perform the lock operation. Additionally, multiple tags may process a nonaddressed request. To • • • • lock a block (write protect a block), the user should: Click the button for Lock Block in the Commands window. Click on the Address flag, if desired, in the Tag Flags window.
Tag-it Protocol www.ti.com GUI (Hexadecimal) 0 3 0 0 4 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 8 Tag-it protocol 0 0 Reader Request < SID > < Block Number > < Data Blk > Cmd Code Added bits to complete byte Figure 3-8.
Tag-it Protocol www.ti.com 3.8.7 Quiet The Quiet request is used to silence a tag, preventing it from responding to any nonaddressed or SID Poll related requests. The tag does, however, respond to requests with matching SID. As there is no response to this request from the receiving tag, only request status and errors are reported. Information: The EVM transmitter remains ON in order to preserve the tag states changed by the request.
Tag-it Protocol www.ti.com Added bits to complete byte GUI (Hexadecimal) Tag-it protocol 0 0 5 8 0 0 0 0 0 0 0 0 0 1 0 1 1 0 0 0 0 0 0 Reader Request B Cmd Code Figure 3-10.
Find Tags 3.9 www.ti.com Find Tags The Find tags window enables the query of the RF field for all supported tags. It continuously switches from one standard to another and sends an Inventory request and displays all the tag labels found within the read range of the reader. The user can choose which protocols to be searched by selecting the appropriate buttons that correspond to the protocol field.
www.ti.com Registers 3.10 Registers The content of the registers can be read and written in the Registers window. Do not alter the register content unless you are familiar with the functions described in the TFR7960 specifications. If you change the content by mistake, press the Set Defaults button. The register values are updated automatically every time the user enters the Registers tab or when the special functions are changed.
Test www.ti.com 3.11 Test If desired, the user can send manual commands by using Test tab. Only the command + parameters field must be typed in. All other fields in the protocol can be left out: SOF (0x01) Number of bytes 0x00 0x0304 Command + parameters EOF (0x0000) The communication starts with SOF (0x01). The second byte defines the number of bytes in the frame including SOF. The third byte should be kept at 0x00, fourth byte at 0x03 and the fifth byte at 0x04.
Test www.ti.com 3.11.1 Expert Mode Selection There is an added feature that allows the user to keep the user adjusted register settings without having the individual set protocol do it for them. Currently, a user wanting to test to a particular standard would go to the desired tab and then do a set protocol, which configures all the registers to a default value.
EVM Software SLOU192C – November 2006 – Revised December 2008 Submit Documentation Feedback
Appendix A SLOU192C – November 2006 – Revised December 2008 ISO/IEC 15693 Reference Material A.1 UID Format The tags are uniquely identified by a 64-bit unique identifier (UID). This is used for addressing each tag uniquely and individually during the anticollision loop, and for one-to-one exchange between a reader and a tag. The format of the UID is shown below: Bits 64 to 57 Bits 56 to 49 Bits 48 to 1 E0 Manufacturer code IC serial number The UID is composed of: • The 8 MSBs, which are E0.
Flag Definitions A.3 www.ti.com Flag Definitions • • • High Data Rate: the default data rate is used for maximum detection range. If High Data Rate is selected in the Tag Flags window, communication with the tag is faster, but the range is reduced. AFI is present: The default setting for the AFI (Application Family Identifier – see Section A.6) is off. If AFI is present is selected in the Tag Flags window, AFI is enabled in commands and responses.
Error Codes www.ti.com (Ref.: ISO 15693-3:2000(E), Section 7.4.2 Table 7, Page 12) Response Flags (Ref.: ISO 15693-3:2000(E), Section 7.4.1 Table 6, Page 11) A.4 Bit Flag Name Value b1 Error flag 0 Description No error 1 Error detected. Error code is in the Error field of response. b2 RFU 0 Reserved for future use b3 RFU 0 Reserved for future use b4 Extension flag 0 No protocol format extension. 1 Protocol format is extended. Reserved for future use.
ISO15693 Commands That Must Be Supported by Third-Party Readers for Texas Instruments Endorsement A.5 www.ti.
Appendix B SLOU192C – November 2006 – Revised December 2008 Tag-it Reference Material B.1 Response Flags Bit Value Meaning 0 0 No error 1 Error 1 0 Reserved 2 0 Nonaddressed 1 Addressed 3 0 Format type 4 0 Unused 5 6 7 B.2 Status Flag (Response Frame) Bit Function 0 Exception 1 More 2 Emulation 3 Auto Repeat 4 BCC 5 Reserved 6 7 B.
Control Flags (Request Frame) 98 Tag-it Reference Material www.ti.
EVALUATION BOARD/KIT IMPORTANT NOTICE Texas Instruments (TI) provides the enclosed product(s) under the following conditions: This evaluation board/kit is intended for use for ENGINEERING DEVELOPMENT, DEMONSTRATION, OR EVALUATION PURPOSES ONLY and is not considered by TI to be a finished end-product fit for general consumer use. Persons handling the product(s) must have electronics training and observe good engineering practice standards.
EVALUATION BOARD/KIT/MODULE (EVM) ADDITIONAL TERMS Texas Instruments (TI) provides the enclosed Evaluation Board/Kit/Module (EVM) under the following conditions: The user assumes all responsibility and liability for proper and safe handling of the goods. Further, the user indemnifies TI from all claims arising from the handling or use of the goods.
For EVMs annotated as FCC – FEDERAL COMMUNICATIONS COMMISSION Part 15 Compliant Caution This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
For EVMs annotated as IC – INDUSTRY CANADA Compliant This Class A or B digital apparatus complies with Canadian ICES-003. Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. Concerning EVMs including radio transmitters This device complies with Industry Canada licence-exempt RSS standard(s).
【Important Notice for Users of this Product in Japan】 This development kit is NOT certified as Confirming to Technical Regulations of Radio Law of Japan! If you use this product in Japan, you are required by Radio Law of Japan to follow the instructions below with respect to this product: (1) Use this product in a shielded room or any other test facility as defined in the notification #173 issued by Ministry of Internal Affairs and Communications on March 28, 2006, based on Sub-section 1.
EVALUATION BOARD/KIT/MODULE (EVM) WARNINGS, RESTRICTIONS AND DISCLAIMERS For Feasibility Evaluation Only, in Laboratory/Development Environments. Unless otherwise indicated, this EVM is not a finished electrical equipment and not intended for consumer use.
IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete.
