<?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>Kinetis MicrocontrollersのトピックRe: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936962#M54243</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Estephania,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have attached the airtrace of the issue, where for every disconnection,&amp;nbsp;&lt;STRONG&gt;gHciRemoteUserTerminatedConnection_c&amp;nbsp;&lt;/STRONG&gt;reason is received.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prakash V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Jul 2019 16:52:01 GMT</pubDate>
    <dc:creator>pvelayu1</dc:creator>
    <dc:date>2019-07-26T16:52:01Z</dc:date>
    <item>
      <title>FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936958#M54239</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whenever&amp;nbsp;KW36&amp;nbsp;(BLE module) disconnects from the connected phone, the reason for disconnection in "&lt;STRONG&gt;gConnEvtDisconnected_c&lt;/STRONG&gt;"is always&amp;nbsp;&lt;STRONG&gt;gHciRemoteUserTerminatedConnection_c,&amp;nbsp;&lt;/STRONG&gt;But what I would like to know why NXP LE stack is not sending the reason "&lt;STRONG&gt;gHciPinOrKeyMissing_c"&amp;nbsp;&lt;/STRONG&gt;or any other disconnect reasons appropriately.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prakash V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jul 2019 06:24:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936958#M54239</guid>
      <dc:creator>pvelayu1</dc:creator>
      <dc:date>2019-07-18T06:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936959#M54240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have a sniffer log with the information you are mentioning ? How are you seeing this ? Also, which example are you using ? How are you configuring ? Are you using some mobile application ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Estephania&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jul 2019 17:46:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936959#M54240</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2019-07-18T17:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936960#M54241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/estephania_martinez"&gt;estephania_martinez&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am keeping breakpoint in the application event ""&lt;STRONG&gt;gConnEvtDisconnected_c&lt;/STRONG&gt;"&amp;nbsp; during various disconnection scenarios but even at different disconnect scenarios, i could see always the reason as&amp;nbsp;&lt;STRONG style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: bold;"&gt;gHciRemoteUserTerminatedConnection_c.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I am using hid_device project, i am not configuring anything related to disconnect reason.&lt;/P&gt;&lt;P&gt;No i am not using any mobile application.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jul 2019 11:11:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936960#M54241</guid>
      <dc:creator>pvelayu1</dc:creator>
      <dc:date>2019-07-22T11:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936961#M54242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please share with me the sniffer log of the communication ? Also, have you tried using the temperature collector example ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Estephania&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jul 2019 16:57:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936961#M54242</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2019-07-22T16:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936962#M54243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Estephania,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have attached the airtrace of the issue, where for every disconnection,&amp;nbsp;&lt;STRONG&gt;gHciRemoteUserTerminatedConnection_c&amp;nbsp;&lt;/STRONG&gt;reason is received.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prakash V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jul 2019 16:52:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936962#M54243</guid>
      <dc:creator>pvelayu1</dc:creator>
      <dc:date>2019-07-26T16:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936963#M54244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you pull the device away, you will get the reason ‘gHciConnectionTimeout_c’ after disconnecting.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Aug 2019 07:30:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936963#M54244</guid>
      <dc:creator>xing_chang</dc:creator>
      <dc:date>2019-08-01T07:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936964#M54245</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Xing Chang,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any disconnect reason for link key miss?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Prakash V&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Aug 2019 16:54:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936964#M54245</guid>
      <dc:creator>pvelayu1</dc:creator>
      <dc:date>2019-08-02T16:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM KW36(BLE): Getting gHciRemoteUserTerminatedConnection_c as disconnection reason for every disconnection</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936965#M54246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/pvelayu1@visteon.com"&gt;pvelayu1@visteon.com&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;When the KW36 loses the link key, the encryption will fail when reconnecting, but the kw36 will not be disconnected. The disconnection is initiated by the mobile phone.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/85758iBEC09F24D526B3FC/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Aug 2019 08:45:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KW36-BLE-Getting-gHciRemoteUserTerminatedConnection-c-as/m-p/936965#M54246</guid>
      <dc:creator>xing_chang</dc:creator>
      <dc:date>2019-08-07T08:45:48Z</dc:date>
    </item>
  </channel>
</rss>

