<?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: How to get disconnection event with reason 278 immediately</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-get-disconnection-event-with-reason-278-immediately/m-p/1233120#M59675</link>
    <description>&lt;P&gt;Hi Federico, I hope you're doing well!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These functions are implemented in the pre-compiled section of the NXP BLE Stack. Error and status codes are implemented following the BLE Specification established by the Bluetooth SIG.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Still, could you please provide some more information about the intention with the modification you're planning? And also some more details about the disconnection reason you want to implement?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Sebastian&lt;/P&gt;</description>
    <pubDate>Thu, 18 Feb 2021 20:37:16 GMT</pubDate>
    <dc:creator>Sebastian_Del_Rio</dc:creator>
    <dc:date>2021-02-18T20:37:16Z</dc:date>
    <item>
      <title>How to get disconnection event with reason 278 immediately</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-get-disconnection-event-with-reason-278-immediately/m-p/1229440#M59593</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;I am using NXP KW38 with SDK 2.6.9. In my application there is a central and a peripheral BLE devices.&lt;/P&gt;&lt;P&gt;When central forces disconnection, I would like to get the disconnection event (with reason 278) as soon as possible, not after supervision timeout, on both central and peripheral.&lt;/P&gt;&lt;P&gt;How can I achieve this?&lt;/P&gt;</description>
      <pubDate>Wed, 10 Feb 2021 16:58:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-get-disconnection-event-with-reason-278-immediately/m-p/1229440#M59593</guid>
      <dc:creator>FedericoWegher</dc:creator>
      <dc:date>2021-02-10T16:58:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to get disconnection event with reason 278 immediately</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-get-disconnection-event-with-reason-278-immediately/m-p/1233120#M59675</link>
      <description>&lt;P&gt;Hi Federico, I hope you're doing well!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These functions are implemented in the pre-compiled section of the NXP BLE Stack. Error and status codes are implemented following the BLE Specification established by the Bluetooth SIG.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Still, could you please provide some more information about the intention with the modification you're planning? And also some more details about the disconnection reason you want to implement?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Sebastian&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2021 20:37:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-get-disconnection-event-with-reason-278-immediately/m-p/1233120#M59675</guid>
      <dc:creator>Sebastian_Del_Rio</dc:creator>
      <dc:date>2021-02-18T20:37:16Z</dc:date>
    </item>
  </channel>
</rss>

