User's Manual
Table Of Contents
- Table of Contents
- Preface
- 1 Introduction and Description
- 2 Using the EVM
- 3 EVM Software
- 3.1 Software Installations
- 3.2 Software Installation for Rev. A EVM
- 3.3 Software Interface
- 3.4 Set Protocol
- 3.5 ISO/IEC 15693 Protocol
- 3.5.1 Inventory
- 3.5.2 Read Single Block
- 3.5.3 Write Single Block
- 3.5.4 Lock Block
- 3.5.5 Read Multiple Blocks
- 3.5.6 Write Multiple Blocks
- 3.5.7 Stay Quiet
- 3.5.8 Select
- 3.5.9 Reset to Ready
- 3.5.10 Write AFI (Application Family Identifier)
- 3.5.11 Lock AFI (Application Family Identifier)
- 3.5.12 Write DSFID (Data Storage Format ID)
- 3.5.13 Lock DSFID (Data Storage Format ID)
- 3.5.14 Get System Info
- 3.5.15 Get Multiple-Block Security Status (Get Mult_Blk Sel Status)
- 3.6 ISO/IEC 14443A Protocol
- 3.7 ISO/IEC 14443B Protocol
- 3.8 Tag-it Protocol
- 3.9 Find Tags
- 3.10 Registers
- 3.11 Test
- A ISO/IEC 15693 Reference Material
- B Tag-it Reference Material
- Important Notices
3.5.4LockBlock
www.ti.com
ISO/IEC15693Protocol
TheLockBlockcommandwrite-protectsonememoryblockoftheaddressedtag(s).Acorruptedresponse
orlackofresponsefromtheTRF7960doesnotnecessarilyindicateafailuretoperformthelock
operation.Additionally,multipletranspondersmayprocessanon-addressedrequest.
Usedtopermanentlylocktherequestedblock
Tolockablock,theusershould:
•ClickthebuttonforLockBlockintheCommandwindow.
•ClickonanyflagsthatmustbesetintheTagFlagswindow.
•OptionallyselectatagfromtheUIDpulldownlistintheTagDatawindowandsettheAddressedflag
(ifonlyonetagispresent,onlyonechoiceisavailable).
•Entertwohexdigitscorrespondingtotheblocknumberinthe(First)BlockNumberfieldintheTag
Datawindow.
•Executethecommand.
Note:TheOptionflag(bit7)oftheISO15693definedRequestflagsmustbesetto1forallWriteand
Lockcommandstorespondproperly.
SLOU192C–November2006–RevisedDecember2008EVMSoftware37
SubmitDocumentationFeedback