Motor de Búsqueda de Datasheet de Componentes Electrónicos
  Mexican  ▼
ALLDATASHEET.COM.MX

X  

ST95HF Datasheet(PDF) 31 Page - STMicroelectronics

No. de pieza ST95HF
Descripción Electrónicos  Dedicated internal frame controller
PDF  93 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Fabricante Electrónico  STMICROELECTRONICS [STMicroelectronics]
Página de inicio  http://www.st.com
Logo STMICROELECTRONICS - STMicroelectronics

ST95HF Datasheet(HTML) 31 Page - STMicroelectronics

Back Button ST95HF Datasheet HTML 27Page - STMicroelectronics ST95HF Datasheet HTML 28Page - STMicroelectronics ST95HF Datasheet HTML 29Page - STMicroelectronics ST95HF Datasheet HTML 30Page - STMicroelectronics ST95HF Datasheet HTML 31Page - STMicroelectronics ST95HF Datasheet HTML 32Page - STMicroelectronics ST95HF Datasheet HTML 33Page - STMicroelectronics ST95HF Datasheet HTML 34Page - STMicroelectronics ST95HF Datasheet HTML 35Page - STMicroelectronics Next Button
Zoom Inzoom in Zoom Outzoom out
 31 / 93 page
background image
DocID025630 Rev 4
31/93
ST95HF
Commands
92
ISO/IEC
14443
Type A
NFC
Forum
Tag Type
4A
NFC
Forum
Tag Type
1
(Topaz)
NFC
Forum
Tag Type
2
Response
example
80
or
90
(1)
09
80B30B8DB500
00
00
00
ISO/IEC 14443-A is bit
oriented protocol, so we can
receive non-integer amount
of bytes. Number of
significant bits in the 1st byte
is the same as indicated in
the command sent.
To calculate a position of a
collision, application has to
take index of byte first. Index
of bit indicates a position
inside this byte. Note that
both indexes start from 0 and
bit index can be 8, meaning
that collision affected parity.
Note that collision
information is only valid when
bit ‘Collision is detected’ is
set. (2)
Result code
Length of entire data
field
Data received from TAG
7: Collision is detected
6: RFU
5: CRC error
4: Parity error
[3:0]: Shows how many significant bits are there
in the first byte
7:0: Index of the first byte where collision is detected
[7:4]: RFU
[3:0]: Index of the first bit where collision is detected
ISO/IEC
14443
Type B
NFC
Forum
Tag Type
4B
Response
example
80 0F
5092036A8D0
00000000071
71
3411
00
-
Result code
Length of entire data
field
Data received from tag
Original (received) value of CRC
[7:2]: RFU
1: CRC error if set
0: RFU
ISO/IEC
18092
NFC
Forum
Tag Type
3
Response
example
80 12
01010105017B0...93FF
00
<<<0x801201010105017B
06941004014B024F4993F
F00
Result code
Length of entire data
field
Data received from tag
[7:2]: RFU
1: CRC error if set
0: RFU
1. Result code 90: Response is decoded but number of byte is not an integer.
2. For more information on using split frames, refer to Appendix D on page 69.
Table 18. List of <Data> Response values for the SENDRECV command for different
protocols (continued)
Protocol Explanation
Response example
Comments



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93


Datasheet Descarga

Go To PDF Page


Enlace URL



¿ALLDATASHEET es útil para Ud.?  [ DONATE ] 

Todo acerca de Alldatasheet   |   Publicidad   |   Contáctenos   |   Política de Privacidad   |   Enlace a la hoja de datos    |   Intercambio de Enlaces   |   Lista de Fabricantes
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com