<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>NFCのトピックPN7412 time optimization with CCID specification</title>
    <link>https://community.nxp.com/t5/NFC/PN7412-time-optimization-with-CCID-specification/m-p/1849345#M11581</link>
    <description>&lt;P&gt;Hello,&lt;BR /&gt;We've been using the PN7412 with the CCID program from the examples package. Everything works correctly but the times we get to access the SAM are slow.&lt;/P&gt;&lt;P&gt;We have connected an Imx8mn with the PN7412 via USB. In the Imx8mn we run a small program that uses the PCSClite library (version 1.9.1) to communicate with the PN7412 . In the PN7412 we run the example "phExCcid" and we can communicate with the SAM without any problem.&lt;/P&gt;&lt;P&gt;Measuring the time from when we send a certain APDU command from the library until we receive the response takes about 12 ms and we need to reduce this time.&amp;nbsp;We have tried to optimize to firmware in the PN7412 but we cannot reduce the time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have tested the same command using the NXP software called RFIDDiscover and the reader NXP Pegoda and the time for all the process is 7 ms approx. Although we have to take into account that we do not have access to the source code and we can only see the logs shown by the program.&lt;/P&gt;&lt;P&gt;We do not know where we can optimize the system to reduce the time, is the CCID specification the best way to communicate the Imx8mn and the PN7412?&lt;BR /&gt;Is there any configuration of the PN7412 that will help us to reduce the communication times?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any help or insights would be greatly appreciated.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Apr 2024 22:58:47 GMT</pubDate>
    <dc:creator>ggpr</dc:creator>
    <dc:date>2024-04-17T22:58:47Z</dc:date>
    <item>
      <title>PN7412 time optimization with CCID specification</title>
      <link>https://community.nxp.com/t5/NFC/PN7412-time-optimization-with-CCID-specification/m-p/1849345#M11581</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;We've been using the PN7412 with the CCID program from the examples package. Everything works correctly but the times we get to access the SAM are slow.&lt;/P&gt;&lt;P&gt;We have connected an Imx8mn with the PN7412 via USB. In the Imx8mn we run a small program that uses the PCSClite library (version 1.9.1) to communicate with the PN7412 . In the PN7412 we run the example "phExCcid" and we can communicate with the SAM without any problem.&lt;/P&gt;&lt;P&gt;Measuring the time from when we send a certain APDU command from the library until we receive the response takes about 12 ms and we need to reduce this time.&amp;nbsp;We have tried to optimize to firmware in the PN7412 but we cannot reduce the time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have tested the same command using the NXP software called RFIDDiscover and the reader NXP Pegoda and the time for all the process is 7 ms approx. Although we have to take into account that we do not have access to the source code and we can only see the logs shown by the program.&lt;/P&gt;&lt;P&gt;We do not know where we can optimize the system to reduce the time, is the CCID specification the best way to communicate the Imx8mn and the PN7412?&lt;BR /&gt;Is there any configuration of the PN7412 that will help us to reduce the communication times?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any help or insights would be greatly appreciated.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 22:58:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/PN7412-time-optimization-with-CCID-specification/m-p/1849345#M11581</guid>
      <dc:creator>ggpr</dc:creator>
      <dc:date>2024-04-17T22:58:47Z</dc:date>
    </item>
    <item>
      <title>Re: PN7412 time optimization with CCID specification</title>
      <link>https://community.nxp.com/t5/NFC/PN7412-time-optimization-with-CCID-specification/m-p/1880184#M11756</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;FONT&gt;------A&lt;STRONG&gt;bout CCID supported by embeded linux OS&lt;/STRONG&gt;-------&lt;BR clear="none" /&gt;&lt;BR clear="none" /&gt;&lt;FONT size="2"&gt;USB CCID is a standard protocol, but if there is no CCID in customer's embeded linux source code, she needs to download corresponding source code and compile them, below is for your reference:&lt;/FONT&gt;&lt;BR clear="none" /&gt;&lt;STRONG&gt;(1) downloading libusb:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT&gt;&lt;STRONG&gt;&lt;A href="http://www.libusb.org/" target="_blank" rel="noopener"&gt;http://www.libusb.org/&lt;/A&gt;, and cross compile it.&lt;/STRONG&gt;&lt;BR clear="none" /&gt;&lt;/FONT&gt;&lt;BR clear="none" /&gt;
&lt;DIV&gt;./configure --host=mipsel-linux --prefix=/tango/ccid/ CC="/root/mips-4.3/bin/mips-linux-gnu-gcc -EL" CXX="/root/mips-4.3/bin/mips-linux-gnu-g++ -EL"&lt;/DIV&gt;
&lt;DIV&gt;make&lt;/DIV&gt;
&lt;DIV&gt;make install&lt;/DIV&gt;
&lt;FONT&gt;&lt;BR clear="none" /&gt;&lt;STRONG&gt;(2) downloading ccid and pcsclite :&lt;/STRONG&gt;&lt;/FONT&gt;&lt;STRONG&gt;&lt;A href="http://alioth.debian.org/projects/pcsclite/" target="_blank" rel="noopener"&gt;http://alioth.debian.org/projects/pcsclite/&lt;/A&gt;, and cross compile them.&lt;/STRONG&gt;&lt;BR clear="none" /&gt;--&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#3333FF"&gt;&lt;STRONG&gt;Cross compile pcsclite:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR clear="none" /&gt;
&lt;DIV&gt;./configure --host=mipsel-linux --prefix=/tango/ccid/ CC="/root/mips-4.3/bin/mips-linux-gnu-gcc -EL" CXX="/root/mips-4.3/bin/mips-linux-gnu-g++ -EL" --enable-libusb LIBUSB_LIBS="-L/tango/ccid/lib/ -lusb-1.0" LIBUSB_CFLAGS="-I/tango/ccid/include/libusb-1.0/" --disable-static --disable-libudev&lt;/DIV&gt;
&lt;DIV&gt;make&lt;/DIV&gt;
&lt;DIV&gt;make install&lt;/DIV&gt;
--&lt;FONT color="#3333FF"&gt;&lt;STRONG&gt;Cross compile CCID&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR clear="none" /&gt;
&lt;DIV&gt;./configure --host=mipsel-linux --prefix=/tango/ccid/ CC="/root/mips-4.3/bin/mips-linux-gnu-gcc -EL" CXX="/root/mips-4.3/bin/mips-linux-gnu-g++ -EL" --enable-libusb LIBUSB_LIBS="-L/tango/ccid/lib/ -lusb-1.0" LIBUSB_CFLAGS="-I/tango/ccid/include/libusb-1.0/" PCSC_CFLAGS="-I/tango/ccid/include/PCSC/" PCSC_LIBS="-L/tango/ccid/lib/ -lpcsclite" --enable-usbdropdir="/tango/ccid/pcsc/drivers"&lt;/DIV&gt;
&lt;DIV&gt;make&lt;/DIV&gt;
&lt;DIV&gt;make install&lt;/DIV&gt;
&lt;STRONG&gt;(3) Running them&lt;/STRONG&gt;&lt;BR clear="none" /&gt;
&lt;DIV&gt;mount -t usbfs none /proc/bus/usb&lt;/DIV&gt;
&lt;DIV&gt;LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/xxx/ccid/lib&lt;/DIV&gt;
&lt;DIV&gt;export LD_LIBRARY_PATH&lt;/DIV&gt;
&lt;DIV&gt;./pcscd &amp;amp;&lt;/DIV&gt;
&lt;BR clear="none" /&gt;&lt;STRONG&gt;Note:&lt;/STRONG&gt;&lt;BR clear="none" /&gt;&lt;FONT size="2"&gt;(1)pcsc is the server of CCID, so we must start pcsc service.&lt;BR clear="none" /&gt;(2)pcsc service needs&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://libccid.so/" target="_blank" rel="noopener"&gt;libccid.so&lt;/A&gt;, we should re-configure corresponding path, generally, path is in config.h.&lt;BR clear="none" /&gt;(3)ccid driver needs libusb &amp;amp; libpcsclite, so before running it, we should cross compile libusb and libpcsclite.&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="Arial, sans-serif" size="2"&gt;&lt;BR clear="none" /&gt;&lt;BR clear="none" /&gt;&lt;FONT color="#3333FF"&gt;&lt;STRONG&gt;Above steps are common method that add CCID driver to embeded linux OS.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR clear="none" /&gt;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="Arial, sans-serif" size="2"&gt;Since ExCcid demo application from NFC Reader Library is a demonstration on how to implement CCID functionality, this software maybe not fully optimized.&amp;nbsp;&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="Arial, sans-serif" size="2"&gt;Regards&lt;/FONT&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;FONT face="Arial, sans-serif" size="2"&gt;Daniel&lt;/FONT&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 04 Jun 2024 02:06:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/PN7412-time-optimization-with-CCID-specification/m-p/1880184#M11756</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2024-06-04T02:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: PN7412 time optimization with CCID specification</title>
      <link>https://community.nxp.com/t5/NFC/PN7412-time-optimization-with-CCID-specification/m-p/1939541#M12053</link>
      <description>&lt;P&gt;For the PN7412 CCID example I do not have particular recommendations of optimization. The obvious things are compiling for speed instead of balance/size.&lt;/P&gt;
&lt;P&gt;For RFIDDiscover reader CLRD 730,&amp;nbsp; there is PN7642 chip inside.&amp;nbsp; The PN7642 is more powerful as&amp;nbsp; the PN74xx.&amp;nbsp; The PN74xx is based on a Cortex-M0 with 20Mhz while the PN76xx is a cortex-m33 with 90MHZ.&amp;nbsp; So you can re-use the Pegoda 3 or order a PNEV7642 board.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Sat, 24 Aug 2024 09:23:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/PN7412-time-optimization-with-CCID-specification/m-p/1939541#M12053</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2024-08-24T09:23:25Z</dc:date>
    </item>
  </channel>
</rss>

