<?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>Wireless MCUのトピックChanging Opcode  command for write req</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/Changing-Opcode-command-for-write-req/m-p/528611#M1236</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;When I am tring to transfer data from Client (data write request) , Data transfering with write attribute as &lt;STRONG&gt;gAttOpcodeWriteCommand_c(0x52) &lt;/STRONG&gt;but Data transfer need to configure as&lt;STRONG&gt; gAttOpcodeWriteRequest_c(0x12)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer attached snapshot and suggest us, any seperate API call for gAttOpcodeWriteRequest_c(0x12) or &lt;/P&gt;&lt;P&gt;How to change the Opcode command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Jul 2016 16:03:51 GMT</pubDate>
    <dc:creator>rajarathinamlaw</dc:creator>
    <dc:date>2016-07-21T16:03:51Z</dc:date>
    <item>
      <title>Changing Opcode  command for write req</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Changing-Opcode-command-for-write-req/m-p/528611#M1236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;When I am tring to transfer data from Client (data write request) , Data transfering with write attribute as &lt;STRONG&gt;gAttOpcodeWriteCommand_c(0x52) &lt;/STRONG&gt;but Data transfer need to configure as&lt;STRONG&gt; gAttOpcodeWriteRequest_c(0x12)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer attached snapshot and suggest us, any seperate API call for gAttOpcodeWriteRequest_c(0x12) or &lt;/P&gt;&lt;P&gt;How to change the Opcode command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jul 2016 16:03:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Changing-Opcode-command-for-write-req/m-p/528611#M1236</guid>
      <dc:creator>rajarathinamlaw</dc:creator>
      <dc:date>2016-07-21T16:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: Changing Opcode  command for write req</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Changing-Opcode-command-for-write-req/m-p/528612#M1237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi Rajarathinam,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Be sure the initialization characteristics write procedure, the param bool_t withoutResponse is selected by 0. &lt;/P&gt;&lt;P&gt;The &lt;STRONG&gt;gAttOpcodeWriteRequest_c&lt;/STRONG&gt; will enable, and if you check with the sniffer the opcode will change and wait for an answer request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if the problem continues&lt;/P&gt;&lt;P&gt;Hope It helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Aug 2016 21:31:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Changing-Opcode-command-for-write-req/m-p/528612#M1237</guid>
      <dc:creator>mario_castaneda</dc:creator>
      <dc:date>2016-08-05T21:31:19Z</dc:date>
    </item>
  </channel>
</rss>

