You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>NFC</strong>-A TechnologyRequirements 19: Format of SDD_REQ CommandPoll Mode4.7.1.1 The <strong>NFC</strong> Forum Device MUSTset SEL_CMD to a value that iscompliant with Table 10.4.7.1.3 If the <strong>NFC</strong> Forum Device doesnot support collision resolution,then the following applies:• The <strong>NFC</strong> Forum DeviceMUST set SEL_PAR to avalue that is compliant withthe length of the SDD_REQCommand. The SEL_PARvalue MUST be 20h.If the <strong>NFC</strong> Forum Devicesupports collision resolution, thenthe following applies:• The <strong>NFC</strong> Forum DeviceMUST set SEL_PAR to avalue that is compliant withthe length of the SDD_REQCommand. The minimumSEL_PAR value MUST be20h. The maximumSEL_PAR value MUST be67h.Listen Mode4.7.1.2 The <strong>NFC</strong> Forum Device MUST beready to receive a SEL_CMDvalue that is compliant withTable 10.The <strong>NFC</strong> Forum Device MUSTtreat a SEL_CMD value notcompliant with Table 10 as<strong>Protocol</strong> Error.4.7.1.4 The <strong>NFC</strong> Forum Device MUST beready to receive a SEL_PAR valuethat is compliant with the length ofthe SDD_REQ Command.The <strong>NFC</strong> Forum Device MUST beready to receive a minimumSEL_PAR value of 20h.For collision resolution, the <strong>NFC</strong>Forum Device MUST be ready toreceive a maximum SEL_PARvalue of 67h.The <strong>NFC</strong> Forum Device MUSTassign a <strong>Protocol</strong> Error to aSEL_PAR value that is notallowed.<strong>NFC</strong> <strong>Digital</strong> <strong>Protocol</strong> Page 30
Change language