View NT2H0301F0DTL_8313816.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1. general description nxp semiconductors has developed ntag203f - nfc forum type 2 tag compliant ic - to be used with nfc enabled devices accord ing to nfc forum tec hnical specifications (see ref. 8 and ref. 9 ), according to nfc forum recommendations or proximity coupling devices (pcd), according to iso/iec 14443a (see ref. 1 ). the communication layer (rf interface) complies to parts 2 and 3 of the iso/iec 14443a standard. the ntag203f is primarily designed for nfc forum type 2 tag a pplications in electronics (i.e. connection handover, bluetooth simple pairing, wi-fi prot ected set-up, device authentication, gaming and others). 1.1 contactless energy and data transfer communication to ntag can be established only when the ic is connected to an antenna. form and specification of the coil is out of scope of this document. for details on how to design antennas see ref. 6 . when the ntag is positioned in the rf fiel d, the high speed rf communication interface allows the transmission of the data with a baud rate of 106 kbit/s. ntag203f nfc forum type 2 tag complia nt ic with 144 bytes user memory and field detection rev. 3.4 ? 10 september 2013 220634 product data sheet company public fig 1. nfc tag interacting with nfc enabled device aaa-001749 energy e.g. c, power control unit data nfc enabled device nfc tag ntag ic
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 2 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 1.2 naming conventions 2. features and benefits 2.1 rf interface (iso/iec 14443a) ? contactless transmission of data and supply energy (no battery needed) ? operating distance: up to 100 mm (depending on various parameters as e.g. field strength and antenna geometry) ? operating frequency: 13.56 mhz ? fast data transfer: 106 kbit/s ? high data integrity: 16-bit crc, parity, bit coding, bit counting ? true anticollision ? 7 byte serial number (cascade le vel 2 according to iso/iec 14443-3) 2.2 eeprom ? 168 bytes of total memory, divided in 42 pages (4 bytes each) ? 144 bytes of user r/w memory area, divided in 36 pages (4 bytes each) ? field programmable read-only locking function per page 16 pages (64 bytes) of the memory ? field programmable read-only locking function per block (2 pages) ? 32-bit user definable one-time programmable (otp) area ? 16-bit counter ? data retention of 10 years ? write endurance 10000 cycles 2.3 nfc forum tag 2 type compliance ntag203f ic provides full compliance to the nfc forum tag 2 type technical specification (see ref. 8 ) and enables ndef data structure configurations (see ref. 9 ). 2.4 field detection ntag203f features an additional rf field det ection functionality. the corresponding output signal can be used as interrupt source to e.g. wake up an embedded microcontroller or trigger further actions. typical applications are bluetooth and wi-fi pairing. table 1. short naming convention (for easier product identification) family name description ntag nxp nfc tag product family name 2 platform indicator 0 generation number (starting from 0) 3 code number for size (0: < 64 bytes, 1: 64-96 bytes; 2: 96-128 bytes; 3: 128-256 bytes) f hwson8 and hxson4 package with field detection pin
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 3 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection for detailed information re fer to application note ref. 11 ? an11141 how to use the fd pin ? . 2.5 security ? anti-cloning support by unique 7-byte serial number for each device ? 32-bit one way counter ? field programmable read-only locking function per page for first 16 pages (64 bytes) of the memory ? read-only locking per block for rest of memory 2.6 cascaded uid the anticollision function is based on an ic individual serial number called unique identifier. the uid of the ntag203f is 7 bytes long and supports cascade level 2 according to iso/iec 14443-3. 2.7 anticollision an intelligent anticollision func tion according to iso/iec 1 4443 allows to operate more than one tag in the field simultaneously. the anticollision algorithm selects each tag individually and ensures that the execution of a transaction with a selected tag is performed correctly without data corruption resulting from other tags in the field. 3. ordering information table 2. ordering information type number package name description version nt2h0301f0dtp hwson8 plastic thermal enhanced extremely thin small outline package; no leads; 8 terminals; body 2.0 x 3,0 x 0,75 mm - NT2H0301F0DTL hxson4 plastic thermal enhanced extremely thin small outline package; no leads; 4 terminals; body 2.0 x 1,5 x 0,5 mm -
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 4 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 4. block diagram 5. pinning information fig 2. block diagram aaa-001748 antenna rf interface field detection digital control unit eeprom anticollision command interpreter eeprom interface fig 3. pin configuration for sot1069-2 (hwson8) table 3. pin description of the hwson8 package contactless interface module ntag203f antenna contacts symbol description pin 1 la antenna connection la pin 2 n.c. not connected pin 3 fd rf field detect connection pin 4 n.c. not connected pin 5 v ss gnd connection pin 6 n.c. not connected pin 7 lb antenna connection lb pin 8 n.c. not connected aaa-001766 terminal 1 index area 1 la ntag203f transparent top view 2n.c. 3 fd 4 8 7 6 5 n.c. n.c. lb n.c. v ss
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 5 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 6. marking 6.1 marking hwson8 6.2 marking hxson4 fig 4. pin configuration for sot1312ab2 (hxson4) table 4. pin description of the hxson4 package contactless interface module ntag203f antenna contacts symbol description pin 1 gnd ground pin 2 lb antenna connection lb pin 3 fd rf field detect connection pin 4 la antenna connection la aaa-002454 transparent top view terminal 1 index area fd la lb gnd 1 4 3 2 ntag203f table 5. marking hwson8 (ntag203f) type number description nt2h0301f0dtp marking line a n1f marking line b batch code marking line c ndy marking line c ww table 6. marking hxson4 (ntag203f) type number description NT2H0301F0DTL marking line a n1f marking line b yww
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 6 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7. functional description 7.1 block description the ntag203f chip consists of the 168 bytes of the total eeprom memory organized in 42 pages each 4 bytes. 144 bytes (36 pages ) are available for the user defined data. along with the memory, ntag203f contains th e rf-interface and the digital control unit. energy and data are transferred via an antenna, which consists of a coil with a few turns directly connected to the la and lb of the ntag203f (see section 5 for details). no further external components are necessary. (for details on antenna design please refer to the document ref. 6 ? an11276 ntag antenna design guide ? .)
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 7 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.2 state diagram and l ogical states description commands are initiated by the nfc device and controlled by the ntag203f command interpreter. this processes the internal st ates and generates the appropriate response. in all states, the command interpreter will return to the idle state on receipt of an unexpected command. if the ic was previously in the halt state, it will return to that state. fig 5. communication principle state diagram - 4-byte; 16-byte 001aak569 por idle state halt state s tat e diagram typical transaction time 5 ms without collision +1 ms for each collision read (16 bytes): 2.0 ms write (4 bytes): 4.6 ms c. write (4 bytes): 6.2 ms ready 1 state ready 2 state active state anticollision command anticollision command read of 16 byte write of 4 byte read command from address 0 read command from address 0 select command of cascade level 1 select command of cascade level 2 wupa command halt command reqa command wupa command memory operations identification and selection procedure
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 8 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.2.1 idle state after a power-on reset (por), the ntag203f s witches directly to t he idle state. it only exits this state when a reqa or a wupa command is received from the nfc device. any other data received while in the idle state is interpreted as an error and the ntag203f remains idle. after a correctly executed halt command, the halt state changes to the wait state which can be exited with a wupa command. 7.2.2 ready1 state in this state, the ntag203f supports the nfc device when resolving the first part of its uid (3 bytes) with the anticollision or se lect command from cascade level 1. this state is exited correctly after executio n of either of the following commands: ? select command from cascade level 1: t he nfc device switches ntag203f into ready2 state where the second part of the uid is resolved. ? read command (from address 0): all anticollision me chanisms are bypassed and ntag203f switches directly to the active state. remark: if more than one ntag203f is in the nfc device field, a read command from address 0 causes a collision due to the different serial numbers and all ntag203f devices are selected. any other data received in the ready1 state is interpreted as an error and depending on its previous state the ntag203f returns to the wait, idle or halt state. 7.2.3 ready2 state in this state, the ntag203f supports the nfc device when resolving the second part of its uid (4 bytes) with the cascade level 2 anticollision command. this state is usually exited using the cascade level 2 select command. alternatively, state ready2 may be skipped using a read command (from address 0) as described in state ready1. remark: if more than one ntag203f is in the nfc device field, a read command from address 0 causes a collision due to the different serial numbers and all ntag203f devices are selected. the response of the ntag203f to the cascade level 2 select command is the select ackn owledge (sak) byte. in acco rdance with iso/iec 14443 this byte indicates if the anticollision cascade procedure has finished. the ntag203f is now uniquely selected and only th is device will communicate wit h the nfc device even when other contactless devices are present in th e nfc device field. any other data received when the device is in this state is interpreted as an error and depending on its previous state the ntag203f returns to the wait, idle or halt state. 7.2.4 active state in the active state either a 16-byte read or 4-byte write command can be performed. the halt command exits either the read or write commands in their active state. any other data received when the device is in this state is interpreted as an error and depending on its previous state the ntag203f returns to the wait, idle or halt state.
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 9 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.2.5 halt state the halt and idle states constitute the sec ond wait state implemented in the ntag203f. an already processed ntag203f can be set into the halt state using the halt command. in the anticollision phase, this state helps the nfc devi ce to distinguish between processed tags and tags yet to be selected. the ntag203f can only exit this state on execution of the wupa command. any other data received when the device is in this state is interpreted as an error and the ntag203f state is unchanged. refer to the document mifare collection of currently available application notes for correct implementation of an anticollision procedure based on the idle and halt states and the reqa and wupa commands. 7.3 data integrity the following mechanisms are implemented in the contactless communication link between nfc device and ntag203f to ensure a reliable data transmission: ? 16 bits crc per block ? parity bit for each byte ? bit count checking ? bit coding to distinguish betw een "1", "0", and no information ? channel monitoring (protocol sequence and bit stream analysis) 7.4 rf interface the rf-interface is according to the standard for contactless smart cards iso/iec 14443a (see ref. 1 ). the rf-field from the nfc dev ice is always present (with short modulation pulses when transmitting data), because it is us ed for the power supply of the tag. for both directions of data communication there is one start bit at the beginning of each frame. each byte is tr ansmitted with a parity bit (odd parity) at the end. the ls bit of the byte with the lowest address of the selected block is transmitted first. the maximum frame length is 164 bits (16 data bytes + 2 crc bytes = 16 * 9 + 2 * 9 + 1 start bit + 1 end bit).
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 10 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.5 memory organization the 168 bytes of the total eepr om memory are organized in 42 pages each 4 bytes. 144 bytes (36 pages) are available for the user defined data. each page contains 4 bytes (32 bits). 7.5.1 uid/serial number the unique 7 byte serial number (uid) and its two block check character bytes (bcc) are programmed into the first 9 bytes of the memory. it therefore covers page 00h, page 01h and the first byte of page 02h. the second byte of page 02h is reserved for internal data. due to security and system requirements these bytes are write-protected after the programming during the ic production. according to iso/iec 14443-3 bcc0 is defined as ct ? sn0 ? sn1 ? sn2. abbreviations ct stays for cascade tag byte (88h) and bcc1 is defined as sn3 ? sn4 ? sn5 ? sn6. sn0 holds the manufacturer id for nxp (04h) according to iso/iec 14443-3 and iso/iec 7816-6 amd.1. table 7. memory organization page address byte number decimal hex 0 1 2 3 0 00h serial number 1 01h serial number 2 02h serial number internal lock byte 0 lock byte 1 3 03h capability container (cc) 4 to 39 04h to 27h user memory user memory user memory user memory 40 28h lock byte 2 lock byte 3 - - 41 29h 16-bit counter 16-bit counter - - fig 6. uid/serial number 001aai001 msb lsb page 0 byte check byte 0 serial number part 1 serial number part 2 manufacturer id for nxp semiconductors (04h) 00000100 0123 page 1 0123 page 2 0123 internal check byte 1 lock bytes
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 11 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.5.2 lock bytes lock bytes enable the user to lock parts of the complete memory area for writing. a read from user memory area cannot be restricted via lock bytes functionality. the lock bytes functionality is enabled with a write command (see section 7.9.7 ? write ? ) or compatibility write command (see section 7.9.8 ? compatibility write ? ), where 2 out of 4 bytes transmitted are used for setting the lock bytes. two corresponding bytes - either bytes 2 and 3 for page 02h or bytes 0 and 1 for page 28h - and the actual content of the lock bytes are bit-wise ?or-ed?. the re sult of or operation becomes the new content of the lock bytes. two unused bytes do not have to be considered. although included in the compatibility write or write command, they are ignored when programming the memory. due to the built-in bitwise or operation, this proc ess is irreversible. if a bit is set to ?1?, it cannot be changed back to ?0? again. therefor e, before locking the lock bytes, the user must ensure that the corresponding user memory area and/or configuration bytes are correctly written. the configuration written in the lock byte s is active upon the next reqa or wupa command. the single bits of the 4 bytes available fo r locking incorporate 3 different functions: ? the read-only locking of the single pages or blocks of the user memory area ? the read-only locking of the single by tes of the configuration memory area ? the locking of the lock bits themselves the mapping of single bits to memory area for the first 64 bytes (512 bits) is shown in figure 7 . the bits of byte 2 and 3 of page 02h represent the field-programmable read-only locking mechanism. each page from 03h (otp bits) to 0fh may be locked individually to prevent further write access by setting the corresponding locking bit lx to 1. after locking the page is read-only memory. the 3 least significant bits of lock byte 0 of page 2 are the block-locking bits. bit 2 handles pages 0fh to 0ah, bit 1 pages 09h to 04h and bit 0 page 03h (otp bits). once the block locking bits are set, the locking configuration for the corresponding memory area is frozen. table 8. lock bytes name page function number address lock byte 0 2 02h page and block locking lock byte 1 2 02h page locking lock byte 2 40 28h page and block locking lock byte 3 40 28h functionality and block locking
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 12 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection for locking of pages starting at page address 10h onwards, lock bytes located in page 28h are used. those two lock bytes cover the memory area of 96 data bytes together with configuration area from page address 28h onw ards. therefore, the granularity is larger then for the first 64 bytes as shown in figure 8 ? lock bytes 2 a nd 3 ? . the functionality beyond page address 28 h which can be locked read-only is: ? the counter ? the lock bytes themselves fig 7. lock bytes 0 and 1 001aai002 block locking lockbits 15 - 10 block locking lockbits 9 -4 block locking lockbit 3 (otp) lock page 3 otp bytes lock page 7 lock page 6 lock page 5 lock page 4 lock page 15 lock page 14 lock page 13 lock page 12 lock page 11 lock page 10 lock page 9 lock page 8 msb 654321 bit 7 65432 lsb msb lsb page 2 (02h) 1 023 lock byte 0 lock byte 1 0 1 0 bit 7 fig 8. lock bytes 2 and 3 aaa-001380 block locking bit 1 - 3 lock page 36 - 39 lock page 32 - 35 lock page 28 - 31 block locking bit 5 - 7 lock page 24 - 27 lock page 20 - 23 lock page 16 - 19 rfu rfu rfu block locking lockbit cnt rfu rfu lockbit cnt page 41 rfu msb 6 5 4 3 2 1 bit 7 65432 lsb msb lsb page 40 (28h) lock byte 2 1 023 0 1 0 bit 7 lock byte 3
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 13 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.5.3 capability container (cc) the capability container cc (pag e 3) is programmed during the ic production according to the nfc forum type 2 tag specification ref. 8 . these bytes may be bit-wise modified by a write command. the bytes of the write command and the current contents of the cc bytes are bit-wise ?or-ed? and the result becomes the new c ontent of the cc bytes. this process is irreversible. if a bit is set to ?1?, it cannot be changed back to ?0? again. 7.5.4 data pages ntag203f features 144 bytes of data memory. the address range from page 04h to 27h constitutes the read/write area. initial state of each byte in the user area is 00h. a write access to data memory is achieved with write (see section 7.9.7 ? write ? ) or compatibility write (see section 7.9.8 ? compatibility write ? ) command. in both cases, 4 bytes of memory (one page) will be overwritten. write access to data memory can be permanently restricted via lock bytes (see section 7.5.2 ? lock bytes ? ). nfc forum type 2 tag compliance ntag203f has been designed to be compliant wi th nfc forum type 2 tag specification (see also ref. 5 ? an1303 u ltralight as type 2 tag ? ). with its 144 bytes of data memory, it can easily support use cases like connection handover, bluetooth simple pairing, wi-fi protected set-up, device authent ication, gaming and others. (1) remark: this memory area may be used as a 32 ticks one-time counter. fig 9. cc bytes aaa-005802 page 3 default value example cc bytes byte cc bytes 0123 00000000 00000000 00000000 00000000 1st write command to page 3 11111111 11111100 00000101 00000111 result in page 3 11111111 11111100 00000101 00000111 2nd write command to page 3 11111111 00000000 00111001 10000000 result in page 3 11111111 11111100 00111101 10000111
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 14 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.5.5 initial memory configuration the memory configuration of ntag2 03f in delivery state is shown in table 9 ? initial memory organization ? : the memory configuration in pages 3 to 5 ensures that ntag203f is a nfc forum type 2 tag in initialized state according to the nfc forum techni cal specification, ref. 8 ? nfc forum t ag 2 type operation, technical specification ? . it is recommended that any further modification of the memory pages 2 to 40 should be according to the ref. 8 ? nfc forum t ag 2 type operation, technical specification ? . all lock bytes are set to zero me aning that no page or functionality is locked. counter is set to zero. table 9. initial memory organization page address byte number dec. hex. 0 1 2 3 0 00h uid0 uid1 uid2 bcc0 1 01h uid3 uid4 uid5 uid6 2 02h bcc1 internal 00h 00h 3 03h e1h 10h 12h 00h 4 04h 01h 03h a0h 10h 5 05h 44h 03h 00h feh 6 to 39 06h to 27h 00h 00h 00h 00h 40 28h 00h 00h rfu rfu 41 29h 00h 00h rfu rfu
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 15 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.6 counter ntag203f features 16-bit one-way counter, locate d at first two bytes of page 29h. in its delivery state, counter value is set to 0000h. the first 1 valid write or compatibility write to t he address 29h can be performed with any value in the range between 0001h and ffffh and corresponds to initial counter value. every consequent valid write command, whic h represents the increment, can contain values between 0001h and 000fh. upon such write command and following mandatory rf reset, the value written to the addre ss 29h is added to the counter content. if - after initial write - a value higher than 000fh is used as a parameter, ntag203f will answer with nak. once counter value reache s ffffh and an increment is performed via valid command, ntag203f will answer with na k. if the sum of counter value and increment is higher than fff fh, ntag203f will answer with na k and will not update the counter. increment by zero (00h) is always possible, but does not have any impact to counter value. 7.7 tag response to a command from nfc device nfc tag type 2 compliant ic uses, apart from the responses defined in the following sections, two half-byte answers to acknowle dge the command received in active state (see figure 5 ? communication principle state diagram - 4-byte; 16-byte ? ). nfc tag type 2 compliant ic distinguishes between positive (ack) and negative (nak) acknowledge. valid values for ack and nak are shown in table 10 ? ack and nak values ? . after every nak, ntag203f will perform an internal reset. 7.8 nfc forum device timings requirements for all read ( section 7.9.5 ) and write ( section 7.9.7 ) timings for the nfc device see section 9 of the nfc digital protocol, te chnical specification, version 1.0 (see ref. 12 ). 1. first valid write is defined as write to a counter value of zero with an argument different then zero table 10. ack and nak values answer value answer explanation ah positive acknowledge (ack) 1h parity or crc error (nak) 0h any other error (nak)
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 16 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.9 command set the atqa and sak are identical as for mifare ultralight (see ref. 7 ? mf0icu1 functional specification mifare ultralight ? ). for information on iso 14443 card activation, see ref. 3 ? an10834 mifare iso/iec 14443 picc selection ? . summary of data relevant for device id entification is given in section 7.10 ? summary of relevant data for device identification ? . the ntag203f comprises the command set as described in following chapters. 7.9.1 reqa description: the ntag203f accepts the reqa command in idle state only. the response is the 2-byte atqa (0044h). reqa and atqa are implemented fully according to iso/iec 14443-3. 7.9.2 wupa description: ntag203f accepts the wupa command in the idle and halt state only. the response is the 2-byte atqa (0044h). wupa is implemented fully according to iso/iec 14443-3. table 11. reqa code parameter data integrity mechanism response 26h (7-bit) - - parity 0044h remark: time units are not to scale and rounded off to 10 ? s fig 10. reqa aaa-001143 cmd (7 bit) atqa 80 s rwd command time ntag response 90 s 170 s 26 44 00 table 12. wupa code parameter data integrity mechanism response 52h (7-bit) - - parity 0044h remark: time units are not to scale and rounded off to 10 ? s fig 11. wupa aaa-001144 cmd (7 bit) atqa 70 s rwd command time ntag response 90 s 170 s 52 44 00
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 17 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.9.3 anticollision and select of cascade level 1 description: the anticollision and select commands are based on the same command code. they differ only in the paramete r byte. this byte is per definition 70h in case of select. ntag203f accepts these commands in the ready1 state only. the response is part 1 of the uid. even with incorrect crc value, the select command will be fully functional. table 13. anticollision and select of cascade level 1 code parameter data integrity mechanism response anticollision: 93h 20h - parity, bcc - anticollision: 93h 21h to 67h part of the uid parity, bcc parts of uid select: 93h 70h first 3 bytes of uid parity, bcc, crc sak (?04?) remark: time units are not to scale and rounded off to 10 ? s fig 12. anticollision of cascade level 1 aaa-001145 cmd ct uid of cascade level 1 180 s rwd command time ntag response 90 s 430 s 93 arg 20 88 sn0 sn1 sn2 bcc1 remark: time units are not to scale and rounded off to 10 ? s fig 13. select of cascade level 1 aaa-001146 cmd sak crc 780 s rwd command time ntag response 90 s 260 s 93 arg ct crc uid of cascade level 1 70 88 sn0 sn1 sn2 bcc1 c0 c1 04 c0 c1
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 18 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.9.4 anticollision and select of cascade level 2 description: the anticollision and select commands are based on the same command code. they differ only in the paramete r byte. this byte is per definition 70h in case of select. ntag203f accepts these commands in the ready2 state only. the response is part 2 of the uid. even with incorrect crc value, the select command will be fully functional. table 14. anticollision and select of cascade level 2 code parameter data integrity mechanism response anticollision: 95h 20h - parity, bcc - anticollision: 95h 21h to 67h part of the uid parity, bcc parts of uid select: 95h 70h second 4 bytes of uid parity, bcc, crc sak (?00?) remark: time units are not to scale and rounded off to 10 ? s fig 14. anticollision of cascade level 2 aaa-001147 cmd 180 s rwd command time ntag response 90 s 430 s 95 arg uid of cascade level 2 20 sn3 sn4 sn5 sn6 bcc2 remark: time units are not to scale and rounded off to 10 ? s fig 15. select of cascade level 2 aaa-001148 cmd 780 s rwd command time ntag response 90 s 260 s 95 arg crc sak crc uid of cascade level 1 70 sn3 sn4 sn5 sn6 bcc2 c0 c1 00 c0 c1
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 19 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.9.5 read description: the read command needs the page address as a parameter. only addresses 00h to 29h are decoded. for higher addresses, ntag203f returns a nak. the ntag203f responds to the read command by sending 16 bytes starting from the page address defined in the command (e.g. if adr is ?03h? pages 03h, 04h, 05h, 06h are returned. if adr is ?29h?, the contents of pages 29h, 00h, 01h and 02h is returned). 7.9.6 halt description: the halt command is used to set already processed ntag203f devices into a different waiting state (halt instead of idle), which allows a simple separation between devices whose uids are already known (as they have already passed the anticollision procedure) and devices that have not yet been identified by their uids. this mechanism is a very efficient way of finding all contactless devices in the field of a nfc device. even with incorrect parity value, the halt command will be fully functional. table 15. read code parameter/arg data integrity mechanism response 30h adr: ?00h? to ?29h? - parity, crc 16 byte date remark: time units are not to scale and rounded off to 10 ? s fig 16. read aaa-001149 cmd 350 s rwd command time ntag response 90 s 50 s 1540 s 30 arg crc 16 byte data crc adr nak c0 c1 d0 d1 d2 ... d13 d14 d15 c0 c1 table 16. halt code parameter data integrity mechanism response 50h 00h - parity, crc passive ack, nak remark: time units are not to scale and rounded off to 10 ? s fig 17. halt aaa-001150 cmd 350 s rwd command time ntag response 90 s 50 s 50 adr crc 00 nak c0 c1 - - -ack
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 20 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.9.7 write description: the write command is used to program the lock bytes in page 02h, the cc bytes in page 03h or the data bytes in pages 04h to 05h. a write command is performed page-wise, programming 4 bytes in a page. table 17. write code parameter/arg data integrity mechanism response a2h adr: ?02h? to ?29h? 4 byte parity, crc ack or nak remark: time units are not to scale and rounded off to 10 ? s fig 18. write aaa-001151 cmd 690 s rwd command time ntag response 90 s 50 s 50 s 4110 s a2 arg 4 byte data adr nak d0 d1 d2 crc d3 c0 c1 ak
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 21 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.9.8 compatibility write description: the compatibility write command was implemented to accommodate the established nfc device infrastructure. even though 16 bytes are transferred to the ntag203f, only the least significant 4 byte s (bytes d0 to d3) will be written to the specified address. it is recommended to set th e remaining bytes d4 to d15 to all ?0?. remark: the timings in fig.19 are typical timings. the nfc forum device must respect the following minimum timings and maximum timeouts. table 18. compatibility write code parameter/arg data integrity mechanism response a0h adr: ?02h? to ?29h? 16 byte parity, crc ack or nak remark: time units are not to scale and rounded off to 10 ? s fig 19. compatibility write aaa-001152 cmd 350 s rwd command time ntag response 90 s 1540 s 90 s 4110 s 50 s 50 s 50 s a0 arg crc adr c0 c1 16 byte data ... crc d15 d0 c0 c1 nak nak ack 50 s ack table 19. compatibility_write timing these times exclude the end of communication of the nfc forum device. t ack min t ack max t nak min t nak max t timeout compatibility_write 1st ack/nak 71 ?? st timeout 71?? st timeout 5 ms compatibility_write 2nd ack/nak 71 ?? st timeout 71?? st timeout 10 ms
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 22 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 7.10 summary of relevant da ta for device identification table 20. summary of relevant data for device identification code type value binary format remark atqa 2 byte 0044h 0000 0000 0100 0100 1 st ?1? indicates cascade level 2 2 nd ?1? indicates family ok ct 1 byte cascade tag 88h 1000 1000 ensures collision with cascade level 1 products hard coded sak (casc. level 1) 1 byte 04h 0000 0100 ?1? indicates additional cascade level ok sak (casc. level 2) 1 byte 00h 0000 0000 indicates complete uid and ntag203f functionality ok manufacturer byte 1 byte 04h 0000 0100 indicates manufacturer nxp acc. to iso/iec 14443-3 and iso/iec 7816-6 amd.1
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 23 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 8. limiting values [1] stresses above one or more of the limiting values may cause permanent damage to the device. [2] exposure to limiting values for ext ended periods may affect device reliability. [3] mil standard 883-c method 3015; human body model: c = 100 pf, r = 1.5 k ? . [4] for safe operation the suggested maximum static current from the vdd pin shall not be above the maximum load current (refer to application note ref. 11 ? an11141 how to use the fd pin ? ). 9. characteristics 9.1 electrical characteristics [1] stresses above one or more of the limiting va lues may cause permanent damage to the device. [2] these are stress ratings only. operation of the device at these or any other conditions above those given in the characteris tics section of the specification is not implied. [3] exposure to limiting values for extended periods may affect device reliability. [4] lcr meter hp 4285, t amb = 22 ? c, cp-d, f i = 13.56 mhz, 2veff. table 21. limiting values in accordance with the absolute maximum rating system (iec 60134). [1] [2] symbol parameter conditions min max unit i i input current - 30 ma i load load current fd-v ss [4] -10 ? a t stg storage temperature ? 55 +125 ?c t amb ambient temperature ? 25 +70 ?c v esd electrostatic discharge voltage measured on pin la-lb [3] 2-kv table 22. characteristics in accordance with the absolute ma ximum rating system (iec 60134). [1] [2] [3] symbol parameter conditions min typ max unit f i input frequency - 13.56 - mhz c i input capacitance 50 pf version [4] 44 50 56 pf v o output voltage fd pin 1.2 1.8 2.0 v eeprom characteristics t cy(w) write cycle time - 4.1 - ms t ret retention time t amb = 22 ?c 10--year n endu(w) write endurance t amb = 22 ?c 10000 - - cycle
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 24 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 10. package outline fig 20. package outline sot1069-2 references outline version european projection issue date iec jedec jeita sot1069-2 - - - mo-229 - - - sot1069-2_po 09-11-18 12-04-18 unit mm max nom min 0.80 0.75 0.70 0.05 0.02 0.00 2.1 2.0 1.9 1.6 1.5 1.4 3.1 3.0 2.9 0.5 1.5 0.45 0.40 0.35 0.05 a (1) dimensions note 1. plastic or metal protrusions of 0.075 mm maximum per side are not included. hwson8: plastic thermal enhanced very very thin small outline package; no leads; 8 terminals; body 2 x 3 x 0.75 mm sot1069-2 a 1 0.65 0.55 0.45 a 2 0.2 a 3 b 0.30 0.25 0.18 d (1) d 2 e (1) e 2 1.6 1.5 1.4 ee 1 k 0.40 0.35 0.30 lv 0.1 w 0.05 y 0.05 y 1 0 1 2 mm scale x c y c y 1 terminal 1 index area b a d e detail x a a 3 a 1 a 2 terminal 1 index area b e 1 e ac b v c w e 2 l k d 2 1 4 5 8
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 25 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection fig 21. package outline sot1312ab2 (hxson4) 2 references outline version european projection issue date iec jedec jeita sot1312-1 sot1312-1_po unit mm max nom min 0.50 0.05 0.30 1.60 1.05 2.10 0.5 0.1 a dimensions: (mm are the orginal dimensons) note 1. plastic or metal protrusions af 0.075 maximum per side are not included. sot1312-1 a 1 a 3 0.152 0.00 0.050 bdd h ee h 0.80 ekl 0.35 vw 0.05 0.05 0.05 0.25 1.001.50 2.00 0.20 0.75 0.30 0.20 0.951.40 1.90 y 0.85 y 1 0.40 0 2 mm scale x detail x e b ac b v c w c y c y 1 a 1 a a 3 terminal 1 index area terminal 1 index area b a d e d h 4 3 e h l k 1 hxson4: plastic thermal enhanced extremely thin small outline package; no leads; 4 terminals; body 2.0 x 1.5 x 0.5 mm 11-07-14 11-11-21
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 26 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 11. abbreviations table 23. abbreviations acronym description ack positive acknowledge atqa answer to request, type a bcc block check characters byte cbc cipher-block chaining cc capability container crc cyclic redundancy check ct cascade tag, type a eeprom electrically erasable programmable read-only memory iv initial value msb most significant bit nak negative acknowledge lsb least significant bit otp one time programmable passive ack implicit acknowledge without picc answer pcd proximity coupling device picc proximity integrated circuit card por power on reset reqa request answer, type a rf radio frequency sak select acknowledge, type a uid unique identifier wupa wake-up command, type a
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 27 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 12. references [1] iso/iec ? 14443-2 (2001) and iso/iec 14443-2 (2001) [2] an10833 mifare type identification procedure ? application note, bu-id doc. no.: 0184** 2 [3] an10834 mifare iso/iec 14443 picc selection ? application note, bu-id doc. no.: 1308** 2 [4] an ultralight features and hints ? application note, bu-id doc. no.: 0731** 2 [5] an1303 ultralight as type 2 tag ? application note, bu-i d doc. no.: 1303** 2 [6] an11276 ntag ante nna design guide ? application note, bu-id doc. no.: 2421** 2 [7] mf0icu1 functional specification mifare ultralight ? product data sheet, bu-id doc. no. 0286** 2 [8] nfc forum tag 2 type operation, technical specification ? nfc forum, 31.05.2011, version 1.1 [9] nfc data exchange format (ndef), technical specification ? nfc forum, 24.07.2006, version 1.0 [10] an10365 surface mount reflow soldering ? application note, nxp semiconductors [11] an11141 how to use the fd pin ? application note, bu-id doc. no.: 2214* 2 [12] nfc digital protocol, technical specification ? nfc forum, 17.11.2010, version 1.0 2. ** ... document version number
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 28 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 13. revision history table 24. revision history document id release date data sheet status change notice supersedes ntag203f v.3.4 20130910 product data sheet - ntag203f v.3.3 modifications: ? section 3 ? ordering information ? : package description updated ntag203f v.3.3 20130212 product data sheet - ntag203f v.3.2 modifications: ? drawings update ntag203f v.3.2 20130123 product data sheet - ntag203f v.3.1 modifications: ? correction of hxson4 marking ntag203f v.3.1 20121113 product data sheet - ntag203f v.3.0 modifications: ? editorial changings and corrections ? new package ?hxson4? added ? data retention updated to 10 years ? section 14.4 ? licenses ? : updated ? security status changed into ?company public? ntag203f v.3.0 20111215 product data sheet - -
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 29 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 14. legal information 14.1 data sheet status [1] please consult the most recently issued document before initiating or completing a design. [2] the term ?short data sheet? is explained in section ?definitions?. [3] the product status of device(s) described in this document may have changed since this document was published and may differ in case of multiple device s. the latest product status information is available on the internet at url http://www.nxp.com . 14.2 definitions draft ? the document is a draft versi on only. the content is still under internal review and subject to formal approval, which may result in modifications or additions. nxp semiconductors does not give any representations or warranties as to the accuracy or completeness of information included herein and shall hav e no liability for the consequences of use of such information. short data sheet ? a short data sheet is an extract from a full data sheet with the same product type number(s) and title. a short data sheet is intended for quick reference only and should not be relied upon to contain detailed and full information. for detailed and full information see the relevant full data sheet, which is available on request vi a the local nxp semiconductors sales office. in case of any inconsistency or conflict with the short data sheet, the full data sheet shall prevail. product specification ? the information and data provided in a product data sheet shall define the specification of the product as agreed between nxp semiconductors and its customer , unless nxp semiconductors and customer have explicitly agreed otherwis e in writing. in no event however, shall an agreement be valid in which the nxp semiconductors product is deemed to offer functions and qualities beyond those described in the product data sheet. 14.3 disclaimers limited warranty and liability ? information in this document is believed to be accurate and reliable. however, nxp semiconductors does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such info rmation. nxp semiconductors takes no responsibility for the content in this document if provided by an information source outside of nxp semiconductors. in no event shall nxp semiconductors be liable for any indirect, incidental, punitive, special or consequential damages (including - without limitation - lost profits, lost savings, business interruption, costs related to the removal or replacement of any products or rework charges) whether or not such damages are based on tort (including negligence), warranty, breach of contract or any other legal theory. notwithstanding any damages that customer might incur for any reason whatsoever, nxp semiconductors? aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the terms and conditions of commercial sale of nxp semiconductors. right to make changes ? nxp semiconductors reserves the right to make changes to information published in this document, including without limitation specifications and product descriptions, at any time and without notice. this document supersedes and replaces all information supplied prior to the publication hereof. suitability for use ? nxp semiconductors products are not designed, authorized or warranted to be suitable for use in life support, life-critical or safety-critical systems or equipment, nor in applications where failure or malfunction of an nxp semiconductors product can reasonably be expected to result in personal injury, death or severe property or environmental damage. nxp semiconductors and its suppliers accept no liability for inclusion and/or use of nxp semiconducto rs products in such equipment or applications and therefore such inclusion and/or use is at the customer?s own risk. applications ? applications that are described herein for any of these products are for illustrative purpos es only. nxp semiconductors makes no representation or warranty that such applications will be suitable for the specified use without further testing or modification. customers are responsible for the design and operation of their applications and products using nxp semiconductors products, and nxp semiconductors accepts no liability for any assistance with applications or customer product design. it is customer?s sole responsibility to determine whether the nxp semiconductors product is suitable and fit for the customer?s applications and products planned, as well as fo r the planned application and use of customer?s third party customer(s). customers should provide appropriate design and operating safeguards to minimize the risks associated with their applications and products. nxp semiconductors does not accept any liability related to any default, damage, costs or problem which is based on any weakness or default in the customer?s applications or products, or the application or use by customer?s third party customer(s). customer is responsible for doing all necessary testing for the customer?s applic ations and products using nxp semiconductors products in order to av oid a default of the applications and the products or of the application or use by customer?s third party customer(s). nxp does not accept any liability in this respect. limiting values ? stress above one or more limiting values (as defined in the absolute maximum ratings system of iec 60134) will cause permanent damage to the device. limiting values are stress ratings only and (proper) operation of the device at these or any other conditions above those given in the recommended operating conditions section (if present) or the characteristics sections of this document is not warranted. constant or repeated exposure to limiting values will permanently and irreversibly affect the quality and reliability of the device. terms and conditions of commercial sale ? nxp semiconductors products are sold subject to the gener al terms and conditions of commercial sale, as published at http://www.nxp.com/profile/terms , unless otherwise agreed in a valid written individual agreement. in case an individual agreement is concluded only the terms and conditions of the respective agreement shall apply. nxp semiconductors hereby expressly objects to applying the customer?s general terms and conditions with regard to the purchase of nxp semiconducto rs products by customer. no offer to sell or license ? nothing in this document may be interpreted or construed as an offer to sell products t hat is open for acceptance or the grant, conveyance or implication of any lic ense under any copyrights, patents or other industrial or intellectual property rights. document status [1] [2] product status [3] definition objective [short] data sheet development this document contains data from the objecti ve specification for product development. preliminary [short] data sheet qualification this document contains data from the preliminary specification. product [short] data sheet production this document contains the product specification.
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 30 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection export control ? this document as well as the item(s) described herein may be subject to export control regu lations. export might require a prior authorization from competent authorities. quick reference data ? the quick reference data is an extract of the product data given in the limiting values and characteristics sections of this document, and as such is not comple te, exhaustive or legally binding. non-automotive qualified products ? unless this data sheet expressly states that this specific nxp semicon ductors product is automotive qualified, the product is not suitable for automotive use. it is neither qualified nor tested in accordance with automotive testing or application requirements. nxp semiconductors accepts no liabili ty for inclusion and/or use of non-automotive qualified products in automotive equipment or applications. in the event that customer uses t he product for design-in and use in automotive applications to automotive specifications and standards, customer (a) shall use the product without nxp semiconductors? warranty of the product for such automotive applicat ions, use and specifications, and (b) whenever customer uses the product for automotive applications beyond nxp semiconductors? specifications such use shall be solely at customer?s own risk, and (c) customer fully in demnifies nxp semi conductors for any liability, damages or failed product claims resulting from customer design and use of the product for automotive app lications beyond nxp semiconductors? standard warranty and nxp semiconduct ors? product specifications. 14.4 licenses 14.5 trademarks notice: all referenced brands, produc t names, service names and trademarks are the property of their respective owners. mifare ? is a trademark of nxp b.v. mifare ultralight ? is a trademark of nxp b.v. 15. contact information for more information, please visit: http://www.nxp.com for sales office addresses, please send an email to: salesaddresses@nxp.com purchase of nxp ics with nfc technology purchase of an nxp semiconductors ic that complies with one of the near field communication (nfc) standards iso/iec 18092 and iso/iec 21481 does not convey an implied license unde r any patent right infringed by implementation of any of those standards.
ntag203f all information provided in this document is subject to legal disclaimers. ? nxp b.v. 2013. all rights reserved. product data sheet company public rev. 3.4 ? 10 september 2013 220634 31 of 32 nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection 16. tables table 1. short naming convention (for easier product identification) . . . . . . . . . . . . . . . . . . . . . . . . . . .2 table 2. ordering information . . . . . . . . . . . . . . . . . . . . . .3 table 3. pin description of the hwson8 package. . . . . .4 table 4. pin description of the hxson4 package . . . . . .5 table 5. marking hwson8 (ntag203f). . . . . . . . . . . . .5 table 6. marking hxson4 (ntag203f) . . . . . . . . . . . . .5 table 7. memory organization . . . . . . . . . . . . . . . . . . . .10 table 8. lock bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 table 9. initial memory organization . . . . . . . . . . . . . . .14 table 10. ack and nak values . . . . . . . . . . . . . . . . . . . .15 table 11. reqa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 table 12. wupa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 table 13. anticollision and select of cascade level 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 14. anticollision and select of cascade level 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 15. read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 16. halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 17. write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 18. compatibility write . . . . . . . . . . . . . . . . . 21 table 19. compatibility_write timing . . . . . . . . . . . 21 table 20. summary of relevant data for device identification . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 21. limiting values . . . . . . . . . . . . . . . . . . . . . . . . 23 table 22. characteristics . . . . . . . . . . . . . . . . . . . . . . . . 23 table 23. abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 24. revision history . . . . . . . . . . . . . . . . . . . . . . . . 28 17. figures fig 1. nfc tag interacting with nfc enabled device . . .1 fig 2. block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 fig 3. pin configuration for sot1069-2 (hwson8) . . . .4 fig 4. pin configuration for sot1312ab2 (hxson4) . . .5 fig 5. communication principle state diagram - 4-byte; 16-byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 fig 6. uid/serial number . . . . . . . . . . . . . . . . . . . . . . . .10 fig 7. lock bytes 0 and 1. . . . . . . . . . . . . . . . . . . . . . . .12 fig 8. lock bytes 2 and 3. . . . . . . . . . . . . . . . . . . . . . . .12 fig 9. cc bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 fig 10. reqa. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 fig 11. wupa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 fig 12. anticollision of cascade level 1 . . . . . . . . . .17 fig 13. select of cascade level 1 . . . . . . . . . . . . . . . . .17 fig 14. anticollision of cascade level 2 . . . . . . . . . .18 fig 15. select of cascade level 2 . . . . . . . . . . . . . . . . .18 fig 16. read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 fig 17. halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 fig 18. write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 fig 19. compatibility write . . . . . . . . . . . . . . . . . . .21 fig 20. package outline sot1069-2 . . . . . . . . . . . . . . . .24 fig 21. package outline sot1312ab2 (hxson4) . . . . .25
nxp semiconductors ntag203f nfc forum compliant ic with user memory and field detection ? nxp b.v. 2013. all rights reserved. for more information, please visit: http://www.nxp.com for sales office addresses, please se nd an email to: salesaddresses@nxp.com date of release: 10 september 2013 220634 please be aware that important notices concerning this document and the product(s) described herein, have been included in section ?legal information?. 18. contents 1 general description . . . . . . . . . . . . . . . . . . . . . . 1 1.1 contactless energy and data transfer. . . . . . . . 1 1.2 naming conventions . . . . . . . . . . . . . . . . . . . . . 2 2 features and benefits . . . . . . . . . . . . . . . . . . . . 2 2.1 rf interface (iso/iec 14443a) . . . . . . . . . . . . 2 2.2 eeprom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.3 nfc forum tag 2 type compliance . . . . . . . . . 2 2.4 field detection . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.5 security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.6 cascaded uid . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.7 anticollision. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3 ordering information . . . . . . . . . . . . . . . . . . . . . 3 4 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5 pinning information . . . . . . . . . . . . . . . . . . . . . . 4 6 marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1 marking hwson8 . . . . . . . . . . . . . . . . . . . . . . 5 6.2 marking hxson4 . . . . . . . . . . . . . . . . . . . . . . . 5 7 functional description . . . . . . . . . . . . . . . . . . . 6 7.1 block description . . . . . . . . . . . . . . . . . . . . . . . 6 7.2 state diagram and logical states description . . 7 7.2.1 idle state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2.2 ready1 state. . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2.3 ready2 state. . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2.4 active state . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2.5 halt state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.3 data integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.4 rf interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.5 memory organization . . . . . . . . . . . . . . . . . . . 10 7.5.1 uid/serial number. . . . . . . . . . . . . . . . . . . . . . 10 7.5.2 lock bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.5.3 capability container (cc). . . . . . . . . . . . . . . . 13 7.5.4 data pages . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.5.5 initial memory configuration . . . . . . . . . . . . . . 14 7.6 counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 7.7 tag response to a command from nfc device 15 7.8 nfc forum device timings requirements. . . . 15 7.9 command set . . . . . . . . . . . . . . . . . . . . . . . . . 16 7.9.1 reqa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 7.9.2 wupa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 7.9.3 anticollision and select of cascade level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 7.9.4 anticollision and select of cascade level 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 7.9.5 read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7.9.6 halt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7.9.7 write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.9.8 compatibility write . . . . . . . . . . . . . . . . 21 7.10 summary of relevant data for device identification . . . . . . . . . . . . . . . . . . . . . . . . . . 22 8 limiting values . . . . . . . . . . . . . . . . . . . . . . . . 23 9 characteristics . . . . . . . . . . . . . . . . . . . . . . . . 23 9.1 electrical characteristics . . . . . . . . . . . . . . . . 23 10 package outline. . . . . . . . . . . . . . . . . . . . . . . . 24 11 abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . 26 12 references. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 13 revision history . . . . . . . . . . . . . . . . . . . . . . . 28 14 legal information . . . . . . . . . . . . . . . . . . . . . . 29 14.1 data sheet status . . . . . . . . . . . . . . . . . . . . . . 29 14.2 definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 14.3 disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . 29 14.4 licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 14.5 trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 30 15 contact information . . . . . . . . . . . . . . . . . . . . 30 16 tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 17 figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 18 contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

▲Up To Search▲

Price & Availability of NT2H0301F0DTL

	To Download NT2H0301F0DTL Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .