<?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>topic MKW24D512  RF issue in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/MKW24D512-RF-issue/m-p/787218#M4894</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;We have two setups (Coordinator + 16 routers and coordinator + 12 routers). All of the devices are using &lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;MKW24D512 processors. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;We observed that ZigBee modules on coordinators stopped RF transmission on both networks after continuous operation of 40+ (43 and 44) days. In order to debug the issue, we used UART and we were able to communicate with the processor through ZTC command and read MAC address etc. This indicates that core of &lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;MKW24D512 &lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;processor was up and running and only RF part was having issues.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;The solution we found to resolve the issue is to reset the ZigBee processor on coordinator, which is not desirable.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Sep 2018 12:28:29 GMT</pubDate>
    <dc:creator>haimliberman</dc:creator>
    <dc:date>2018-09-21T12:28:29Z</dc:date>
    <item>
      <title>MKW24D512  RF issue</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/MKW24D512-RF-issue/m-p/787218#M4894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;We have two setups (Coordinator + 16 routers and coordinator + 12 routers). All of the devices are using &lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;MKW24D512 processors. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;We observed that ZigBee modules on coordinators stopped RF transmission on both networks after continuous operation of 40+ (43 and 44) days. In order to debug the issue, we used UART and we were able to communicate with the processor through ZTC command and read MAC address etc. This indicates that core of &lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;MKW24D512 &lt;/SPAN&gt;&lt;SPAN style="color: #1f497d;"&gt;processor was up and running and only RF part was having issues.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #1f497d;"&gt;The solution we found to resolve the issue is to reset the ZigBee processor on coordinator, which is not desirable.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2018 12:28:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/MKW24D512-RF-issue/m-p/787218#M4894</guid>
      <dc:creator>haimliberman</dc:creator>
      <dc:date>2018-09-21T12:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: MKW24D512  RF issue</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/MKW24D512-RF-issue/m-p/787219#M4895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We no longer support/recommend BeeKit, but it is available for KW24D.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently, the available devices with ZigBee support are the &lt;A href="http://www.nxp.com/products/wireless-connectivity/2.4-ghz-wireless-solutions/support-resources-for-jn516x-mcus:SUPPORT-RESOURCES-JN516X-MCUS"&gt;JN516x family&lt;/A&gt;&amp;nbsp;and the &lt;A class="link-titled" href="https://www.nxp.com/products/wireless-connectivity/zigbee/kinetis-kw41z-2.4-ghz-dual-mode-ble-and-802.15.4-wireless-radio-microcontroller-mcu-based-on-arm-cortex-m0-plus-core:KW41Z" title="https://www.nxp.com/products/wireless-connectivity/zigbee/kinetis-kw41z-2.4-ghz-dual-mode-ble-and-802.15.4-wireless-radio-microcontroller-mcu-based-on-arm-cortex-m0-plus-core:KW41Z"&gt;KW41Z&lt;/A&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The currently supported stacks by KW24D are: &lt;A href="http://www.nxp.com/products/wireless-connectivity/2.4-ghz-wireless-solutions/thread-networking-protocol:THREAD-NETWORKING-PROTOCOL-NXP"&gt;Thread&lt;/A&gt;, 802.15.4 MAC and SMAC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Estephania&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Sep 2018 17:57:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/MKW24D512-RF-issue/m-p/787219#M4895</guid>
      <dc:creator>stephanie_m</dc:creator>
      <dc:date>2018-09-24T17:57:54Z</dc:date>
    </item>
  </channel>
</rss>

