<?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のトピックRe: clrc663 phalI15693_WriteMultipleBlocks function</title>
    <link>https://community.nxp.com/t5/NFC/clrc663-phalI15693-WriteMultipleBlocks-function/m-p/1957368#M12170</link>
    <description>&lt;P&gt;Hi Vick:&lt;/P&gt;
&lt;P&gt;Please kindly note that ISO/IEC 15693 defines the WRITE MULTIPLE BLOCKS command as optional command. In reader library, we only implemented ReadMultipleBlock,&amp;nbsp; &amp;nbsp;but no WriteMultipleBlocks.&amp;nbsp;&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>Thu, 19 Sep 2024 07:42:48 GMT</pubDate>
    <dc:creator>danielchen</dc:creator>
    <dc:date>2024-09-19T07:42:48Z</dc:date>
    <item>
      <title>clrc663 phalI15693_WriteMultipleBlocks function</title>
      <link>https://community.nxp.com/t5/NFC/clrc663-phalI15693-WriteMultipleBlocks-function/m-p/1956122#M12169</link>
      <description>&lt;P&gt;Hi there!&lt;/P&gt;&lt;P&gt;My team has achived read/write signle block with clrc663 chip using STM32. But when I use the&amp;nbsp;phalI15693_WriteMultipleBlocks function.The return status is 2688 which is a wrong status. My code shows below:&lt;/P&gt;&lt;P&gt;bOption = PHAL_I15693_OPTION_DEFAULT;&lt;BR /&gt;bFlags = 0x32;&lt;BR /&gt;bAfi = 0x00;&lt;BR /&gt;bBlockNo = 0x00;&lt;/P&gt;&lt;P&gt;wDataLength = 16;&lt;BR /&gt;uint8_t NumBlocks = 4;&lt;BR /&gt;uint8_t Wr_t[16] = {1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16};&lt;/P&gt;&lt;P&gt;phalI15693_Sw_DataParams_t al15693;&lt;/P&gt;&lt;P&gt;// 写多个blocks的数据&lt;BR /&gt;status = phalI15693_WriteMultipleBlocks(&amp;amp;al15693,bOption, bBlockNo, NumBlocks, Wr_t, wDataLength);&lt;BR /&gt;printf("status = %d\r\n", status);&lt;/P&gt;&lt;P&gt;Can u tell me why this situation happen? Otherwise, when I read multiple blocks, the chip works fine.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 02:41:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/clrc663-phalI15693-WriteMultipleBlocks-function/m-p/1956122#M12169</guid>
      <dc:creator>VicKyyyyy</dc:creator>
      <dc:date>2024-09-18T02:41:05Z</dc:date>
    </item>
    <item>
      <title>Re: clrc663 phalI15693_WriteMultipleBlocks function</title>
      <link>https://community.nxp.com/t5/NFC/clrc663-phalI15693-WriteMultipleBlocks-function/m-p/1957368#M12170</link>
      <description>&lt;P&gt;Hi Vick:&lt;/P&gt;
&lt;P&gt;Please kindly note that ISO/IEC 15693 defines the WRITE MULTIPLE BLOCKS command as optional command. In reader library, we only implemented ReadMultipleBlock,&amp;nbsp; &amp;nbsp;but no WriteMultipleBlocks.&amp;nbsp;&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>Thu, 19 Sep 2024 07:42:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/clrc663-phalI15693-WriteMultipleBlocks-function/m-p/1957368#M12170</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2024-09-19T07:42:48Z</dc:date>
    </item>
  </channel>
</rss>

