<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NFC type 4 and Linux (neard) interoperability</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/21182/nfc-type-4-and-linux-neard-interoperability</link><description>Hi,
I&amp;#39;m trying to use NFC type 4 tag on nRF52 side (PCA10040) and poll and read it on Embedded Linux using neard [1]. I&amp;#39;m not an expert in NFC area, so I could be wrong in some my assumptions, I beg a pardon in advance if something wrong with my setup</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 11 Apr 2017 12:26:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/21182/nfc-type-4-and-linux-neard-interoperability" /><item><title>RE: NFC type 4 and Linux (neard) interoperability</title><link>https://devzone.nordicsemi.com/thread/82893?ContentTypeID=1</link><pubDate>Tue, 11 Apr 2017 12:26:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:40136357-8698-4312-8435-1c6a07115023</guid><dc:creator>Alexey Roslyakov</dc:creator><description>&lt;p&gt;Hi Michał, it was clearly the problem in the code of neard (plugins/nfctype4.c). The ISO_Select function doesn&amp;#39;t work correctly for all cases. I&amp;#39;m preparing a patch for sending to upstream. Thank you very much, I really appreciate your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NFC type 4 and Linux (neard) interoperability</title><link>https://devzone.nordicsemi.com/thread/82892?ContentTypeID=1</link><pubDate>Tue, 11 Apr 2017 07:15:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:68979c2c-924f-4f2a-bf22-3d3d4d0813f7</guid><dc:creator>Michal</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;looking at your log, the adapter side sends a too short Command APDU: &lt;em&gt;02 00 a4 04 00 07 d2 76 00 00 85 01 01&lt;/em&gt; The first byte: 02 is an ISO-DEP I-block header, then &lt;em&gt;&amp;quot;Select NDEF Application&amp;quot;&lt;/em&gt; APDU is sent: &lt;em&gt;00 a4 04 00 07 d2 76 00 00 85 01 01 &lt;code&gt;00&lt;/code&gt;&lt;/em&gt;, but it is missing the highlighted &lt;em&gt;00&lt;/em&gt; byte at the end. This byte is called &lt;em&gt;Le&lt;/em&gt; and it tells how many data bytes shall be sent in a Response APDU, and in case of this command it should be 0 (see Table 10. in NFC Forum &lt;strong&gt;Type 4 Tag Operation Specification v2.0&lt;/strong&gt;).&lt;/p&gt;
&lt;p&gt;So please check with the adapter, why it sends a truncated first Command: &lt;em&gt;&amp;quot;Select NDEF Application&amp;quot;&lt;/em&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>