<?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 Re: Error about zigbee-jip-daemon: free() in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927634#M7056</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did not make changes to the official protocol stack, but instead used the routine JN-AN-1216 (Zigbee-3-0-IoT-ControlBridge).&lt;/P&gt;&lt;P&gt;The difference is that the gateway application i use is located in JN-AN-1194 (ZigbeeNodeControlBridge), and JN-AN-1216 does not provide such a program.&lt;BR /&gt;So I am still not sure if it is because the gateway application in JN-AN-1194 does not support the Zigbee-3-0-IoT-ControlBridge in JN-AN-1216.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/RHinnen"&gt;RHinnen&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Jul 2019 05:18:43 GMT</pubDate>
    <dc:creator>jshpy</dc:creator>
    <dc:date>2019-07-17T05:18:43Z</dc:date>
    <item>
      <title>Error about zigbee-jip-daemon: free()</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927633#M7055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have some troubles and would like to ask everyone for help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I try to deploy the application on my development board according to the steps described in &lt;STRONG&gt;JN-AN-1194-ZigBee-IoT-Gateway-Host.pdf&lt;/STRONG&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; * The &lt;STRONG&gt;ZigBee Control Bridge&lt;/STRONG&gt; used by the development board is based on the &lt;STRONG&gt;JN5169&lt;/STRONG&gt; reference &lt;STRONG&gt;JN-AN-1216-Zigbee-3-0-IoT-ControlBridge&lt;/STRONG&gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; * The operating system of the development board is &lt;STRONG&gt;Ubuntu 17.04&lt;/STRONG&gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; * The architecture of the CPU is &lt;STRONG&gt;ARMv7 Processor rev 10 (v7l)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Things seem to be going very well. I&amp;nbsp;successfully deployed and ran &lt;STRONG&gt;JIP Web Interfaces&lt;/STRONG&gt; and were able to exchange information with the Control Bridge.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But when&amp;nbsp;i try to add a ZigBee node to the coordinator network where the Control Bridge is located, &lt;STRONG&gt;zigbee-jip-daemon&lt;/STRONG&gt; unexpectedly crashes and exits:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN style="color: red;"&gt;*** Error in `zigbee-jip-daemon': free(): invalid next size (fast): 0xb22005b8 ***&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I&amp;nbsp;located the location of the error, located at&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #215868;"&gt;JN-AN-1194.zip\ZigbeeNodeControlBridge\Source\Host\zigbee-jip-daemon-1v4.tar.gz\zigbee-jip-daemon.tar\zigbee-jip-daemon\ZCB\Source\ZigbeeControlBridge.c &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;line 792&lt;/STRONG&gt;, the log collected is attached to &lt;STRONG&gt;error_log.txt&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you give some advice?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Related documents and source code can be found in below:&lt;/P&gt;&lt;P&gt;&lt;A href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nxp.com%2Fdocs%2Fen%2Fapplication-note%2FJN-AN-1194.zip%3Ffromsite%3Dzh&amp;amp;data=02%7C01%7Cneo.tsai%40arrowasia.com%7Ceb218980752d4436e6ef08d709ce54a0%7C0beb0c359cbb4feb99e5589e415c7944%7C1%7C0%7C636988654674390538&amp;amp;sdata=NAeGeYlyLM7XQV4W0TOLIjl%2B297YaSS7HJF3U%2F4mIuk%3D&amp;amp;reserved=0"&gt;JN-AN-1194.zip&lt;/A&gt;(ZigbeeNodeControlBridge)&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nxp.com%2Fdocs%2Fen%2Fapplication-note%2FJN-AN-1216.zip&amp;amp;data=02%7C01%7Cneo.tsai%40arrowasia.com%7Ceb218980752d4436e6ef08d709ce54a0%7C0beb0c359cbb4feb99e5589e415c7944%7C1%7C0%7C636988654674390538&amp;amp;sdata=Zxf1IfXb3IMQIN78LvKYmq5aJGWY6TVAuOhS7v49PdY%3D&amp;amp;reserved=0"&gt;JN-AN-1216.zip&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN style="color: windowtext; text-decoration: none; "&gt;(Zigbee-3-0-IoT-ControlBridge)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;【error_log】&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;---------------------------------------------------------&lt;BR /&gt;zigbee-jip-daemon -s /dev/ttyS3 -m coordinator -f&lt;BR /&gt;---------------------------------------------------------&lt;BR /&gt;root@rd:~# zigbee-jip-daemon -s /dev/ttyS3 -m coordinator -f&lt;BR /&gt;Opening serial device '/dev/ttyS3' at baud rate 1000000bps&lt;BR /&gt;Opened tun device: zb0&lt;BR /&gt;eBR_Init: Starting JIP&lt;BR /&gt;eBR_Init: Loading JIP Definitions&lt;BR /&gt;eBR_Init: Adding IPv6 address fd04:bd3:80e8:10::1 to interface&lt;BR /&gt;eBR_Init: Empty network table initialised&lt;BR /&gt;Starting avahi client.&lt;BR /&gt;Message 0x8010 was not handled&lt;BR /&gt;Adding hostname 'BR_zb0.local'&lt;BR /&gt;Adding service 'JIP Border Router'&lt;BR /&gt;Registering Service 'JIP Border Router' on host 'BR_zb0'.&lt;BR /&gt;Message 0x8010 was not handled&lt;BR /&gt;Connected to control bridge version 0x12345678&lt;BR /&gt;eZCB_EstablishComms: Reset control bridge&lt;BR /&gt;Module: ** Control Bridge Reset**&lt;BR /&gt;ZCB_HandleNodeClusterList: Cluster list for endpoint 1, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterList: Cluster list for endpoint 1, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0000, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0000, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0003, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0003, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0004, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0004, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0005, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0005, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0006, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0006, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0008, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0008, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0300, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0300, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0201, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0201, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0405, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0405, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0001, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0001, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0400, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0400, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0402, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0402, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeClusterAttributeList: Cluster attribute list for endpoint 1, cluster 0x0702, profile ID 0x 104&lt;BR /&gt;ZCB_HandleNodeCommandIDList: Command ID list for endpoint 1, cluster 0x0702, profile ID 0x 104&lt;BR /&gt;Network formed on channel 15. Control bridge address 0x0000 (0x00158D00017CF7BA)&lt;BR /&gt;ZCB_HandleNetworkJoined: Node Joined 0x0000 (0x00158D00017CF7BA)&lt;BR /&gt;Control bridge restarted, status 2 (NFN_START)&lt;BR /&gt;Service 'JIP Border Router' successfully established on host 'BR_zb0'.&lt;BR /&gt;main: Got event 0&lt;BR /&gt;psBR_FindJIPNode: Find JIP node matching IEEE Address 0x00158D00017CF7BA, fd04:bd3:80e8:10:15:8d00:17c:f7ba&lt;BR /&gt;psBR_FindJIPNode: JIP Node not found&lt;BR /&gt;Zigbee node 0x0000 (0x00158D00017CF7BA) device ID 0x0840 joined network&lt;BR /&gt;eBR_NodeJoined: Found JIP device type 0x08010010 for ZB Device type 0x0840&lt;BR /&gt;Commissioning server listening on port 1880&lt;BR /&gt;Create JIP device ID 0x08010010 at address fd04:bd3:80e8:10:15:8d00:17c:f7ba.&lt;BR /&gt;main: Network started&lt;BR /&gt;eBR_CheckDeviceComms: Comms test node index 2 / 2 nodes in network&lt;BR /&gt;psBR_FindZigbeeNode: Find Zigbee node matching IPv6 Address fd04:bd3:80e8:10:15:8d00:17c:f7ba&lt;BR /&gt;eZCB_NeighbourTableRequest: Send management LQI request to 0x0000 for entries starting at 0&lt;BR /&gt;Module: Management Lqi Request&lt;BR /&gt;eZCB_NeighbourTableRequest: Received management LQI response. Table size: 1, Entry count: 1, start index: 0&lt;BR /&gt;eZCB_NeighbourTableRequest: Entry 00: Short Address 0x1899, PAN ID: 0x1234567812345678, IEEE Address: 0x00158D00027567C3&lt;BR /&gt;eZCB_NeighbourTableRequest: Type: 1, Permit Joining: 2, Relationship: 1, RxOnWhenIdle: 1&lt;BR /&gt;eZCB_NeighbourTableRequest: Depth: 1, LQI: 255&lt;BR /&gt;eZCB_NeighbourTableRequest: New Node 0x1899 in neighbour table&lt;BR /&gt;eZCB_NeighbourTableRequest: Device join queued&lt;BR /&gt;eZCB_NeighbourTableRequest: ---- befor free: line 792 ----&lt;BR /&gt;eZCB_NeighbourTableRequest: ---- after free: line 792 ----&lt;BR /&gt;eBR_CheckDeviceComms: Node is the control bridge&lt;BR /&gt;main: Got event 2&lt;BR /&gt;main: New device 0x1899&lt;BR /&gt;eZCB_MatchDescriptorRequest: Send Match Desciptor request for profile ID 0x0104 to 0x1899&lt;BR /&gt;eZCB_MatchDescriptorRequest: Input Cluster List:&lt;BR /&gt;eZCB_MatchDescriptorRequest: 0x0006&lt;BR /&gt;eZCB_MatchDescriptorRequest: 0x0201&lt;BR /&gt;eZCB_MatchDescriptorRequest: Output Cluster List:&lt;BR /&gt;eZCB_MatchDescriptorRequest: Send Match Desciptor request for profile ID 0xC05E to 0x1899&lt;BR /&gt;eZCB_MatchDescriptorRequest: Input Cluster List:&lt;BR /&gt;eZCB_MatchDescriptorRequest: 0x0006&lt;BR /&gt;eZCB_MatchDescriptorRequest: 0x0201&lt;BR /&gt;eZCB_MatchDescriptorRequest: Output Cluster List:&lt;BR /&gt;ZCB_HandleMatchDescriptorResponse: Match descriptor request response from node 0x1899 - 1 matching endpoints.&lt;BR /&gt;ZCB_HandleMatchDescriptorResponse: Node rejoined&lt;BR /&gt;ZCB_HandleMatchDescriptorResponse: Queue new node event&lt;BR /&gt;ZCB_HandleMatchDescriptorResponse: Match descriptor request response from node 0x1899 - 1 matching endpoints.&lt;BR /&gt;ZCB_HandleMatchDescriptorResponse: Node rejoined&lt;BR /&gt;ZCB_HandleMatchDescriptorResponse: Queue new node event&lt;BR /&gt;main: Got event 3&lt;BR /&gt;psBR_FindJIPNode: Find JIP node matching IEEE Address 0x00158D00027567C3, fd04:bd3:80e8:10:15:8d00:275:67c3&lt;BR /&gt;psBR_FindJIPNode: JIP Node not found&lt;BR /&gt;main: New device, short address 0x1899, matching requested clusters&lt;BR /&gt;main: Requesting new endpoint simple descriptor&lt;BR /&gt;eZCB_SimpleDescriptorRequest: Send Simple Desciptor request for Endpoint 1 to 0x1899&lt;BR /&gt;eZCB_AddGroupMembership: Send add group membership 0xF00F request to 0x1899&lt;BR /&gt;eZCB_AddGroupMembership: Add group membership 0xF00F on Node 0x1899 status: 138&lt;BR /&gt;main: Adding node 0x1899 to border router&lt;BR /&gt;Zigbee node 0x1899 (0x00158D00027567C3) device ID 0x0101 joined network&lt;BR /&gt;eBR_NodeJoined: Found JIP device type 0x08011175 for ZB Device type 0x0101&lt;BR /&gt;eColourLampInitalise: Set up device&lt;BR /&gt;ColourLampGetGroupsImpl: Lamp was in 0 groups&lt;BR /&gt;eZCB_GetGroupMembership: Send get group membership request to 0x1899&lt;BR /&gt;eZCB_GetGroupMembership: Node 0x1899 is in 1/4 groups&lt;BR /&gt;eZCB_GetGroupMembership: Group ID 0xF00F&lt;BR /&gt;ColourLampGetGroupsImpl: Lamp is now in 1 groups&lt;BR /&gt;ColourLampGetGroupsImpl: Add Group: ff15::f00f - 0xF00F&lt;BR /&gt;ColourLampGetGroupsImpl: Call libJIP get groups function: 0xb6eab471&lt;BR /&gt;Create JIP device ID 0x08011175 at address fd04:bd3:80e8:10:15:8d00:275:67c3.&lt;BR /&gt;main: Got event 3&lt;BR /&gt;psBR_FindJIPNode: Find JIP node matching IEEE Address 0x00158D00027567C3, fd04:bd3:80e8:10:15:8d00:275:67c3&lt;BR /&gt;psBR_FindJIPNode: Found JIP node at 0x45278&lt;BR /&gt;main: Node 0x1899 is already in the JIP network&lt;BR /&gt;eBR_CheckDeviceComms: Comms test node index 3 / 3 nodes in network&lt;BR /&gt;psBR_FindZigbeeNode: Find Zigbee node matching IPv6 Address fd04:bd3:80e8:10:15:8d00:275:67c3&lt;BR /&gt;eZCB_NeighbourTableRequest: Send management LQI request to 0x1899 for entries starting at 0&lt;BR /&gt;Module: Management Lqi Request&lt;BR /&gt;eZCB_NeighbourTableRequest: Received management LQI response. Table size: 1, Entry count: 1, start index: 0&lt;BR /&gt;eZCB_NeighbourTableRequest: Entry 00: Short Address 0x0000, PAN ID: 0x1234567812345678, IEEE Address: 0x00158D00017CF7BA&lt;BR /&gt;eZCB_NeighbourTableRequest: Type: 0, Permit Joining: 2, Relationship: 0, RxOnWhenIdle: 1&lt;BR /&gt;eZCB_NeighbourTableRequest: Depth: 0, LQI: 118&lt;BR /&gt;eZCB_NeighbourTableRequest: Device join queued&lt;BR /&gt;eZCB_NeighbourTableRequest: ---- befor free: line 792 ----&lt;BR /&gt;eZCB_NeighbourTableRequest: ---- after free: line 792 ----&lt;BR /&gt;iBR_DeviceTimedOut: Last successful comms with node 0x1899 was 0 seconds ago, sequential failures: 0&lt;BR /&gt;main: Got event 2&lt;BR /&gt;main: Endpoints of device 0x0000 already known&lt;BR /&gt;main: Got event 3&lt;BR /&gt;psBR_FindJIPNode: Find JIP node matching IEEE Address 0x00158D00017CF7BA, fd04:bd3:80e8:10:15:8d00:17c:f7ba&lt;BR /&gt;psBR_FindJIPNode: Found JIP node at 0x46b78&lt;BR /&gt;main: Node 0x0000 is already in the JIP network&lt;BR /&gt;eBR_CheckDeviceComms: Comms test node index 2 / 3 nodes in network&lt;BR /&gt;psBR_FindZigbeeNode: Find Zigbee node matching IPv6 Address fd04:bd3:80e8:10:15:8d00:17c:f7ba&lt;BR /&gt;eZCB_NeighbourTableRequest: Send management LQI request to 0x0000 for entries starting at 1&lt;BR /&gt;Module: Management Lqi Request&lt;BR /&gt;eZCB_NeighbourTableRequest: Received management LQI response. Table size: 1, Entry count: 1, start index: 0&lt;BR /&gt;eZCB_NeighbourTableRequest: Entry 00: Short Address 0x010F, PAN ID: 0xF000000000110000, IEEE Address: 0x00480020B2480020&lt;BR /&gt;eZCB_NeighbourTableRequest: Type: 0, Permit Joining: 0, Relationship: 0, RxOnWhenIdle: 0&lt;BR /&gt;eZCB_NeighbourTableRequest: Depth: 178, LQI: 16&lt;BR /&gt;eZCB_NeighbourTableRequest: New Node 0x010F in neighbour table&lt;BR /&gt;eZCB_NeighbourTableRequest: Device join queued&lt;BR /&gt;eZCB_NeighbourTableRequest: ---- befor free: line 792 ----&lt;BR /&gt;*** Error in `zigbee-jip-daemon': free(): invalid next size (fast): 0xb22005b8 ***&lt;BR /&gt;Aborted (core dumped)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jul 2019 02:13:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927633#M7055</guid>
      <dc:creator>jshpy</dc:creator>
      <dc:date>2019-07-17T02:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: Error about zigbee-jip-daemon: free()</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927634#M7056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did not make changes to the official protocol stack, but instead used the routine JN-AN-1216 (Zigbee-3-0-IoT-ControlBridge).&lt;/P&gt;&lt;P&gt;The difference is that the gateway application i use is located in JN-AN-1194 (ZigbeeNodeControlBridge), and JN-AN-1216 does not provide such a program.&lt;BR /&gt;So I am still not sure if it is because the gateway application in JN-AN-1194 does not support the Zigbee-3-0-IoT-ControlBridge in JN-AN-1216.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/RHinnen"&gt;RHinnen&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jul 2019 05:18:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927634#M7056</guid>
      <dc:creator>jshpy</dc:creator>
      <dc:date>2019-07-17T05:18:43Z</dc:date>
    </item>
    <item>
      <title>Re: Error about zigbee-jip-daemon: free()</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927635#M7057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is anyone here?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jul 2019 02:30:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927635#M7057</guid>
      <dc:creator>jshpy</dc:creator>
      <dc:date>2019-07-22T02:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: Error about zigbee-jip-daemon: free()</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927636#M7058</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" class="" data-content-finding="Community" data-userid="344757" data-username="jshpy@163.com" href="https://community.nxp.com/people/jshpy@163.com" style="color: #3d9ce7; background-color: #ffffff; border: 0px; font-weight: 200; text-decoration: underline; font-size: 1.286rem;"&gt;旭 张&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The JN-AN-1194 Application Note is now frozen and has been replaced with JN-AN-1222 and JN-AN-1223.&lt;/P&gt;&lt;P&gt;Could you please try with this application notes?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.nxp.com/products/wireless/zigbee/zigbee/zigbee-home-automation:ZIGBEE-HOME-AUTOMATION"&gt;ZigBee Home Automation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mario&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2019 15:27:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/Error-about-zigbee-jip-daemon-free/m-p/927636#M7058</guid>
      <dc:creator>mario_castaneda</dc:creator>
      <dc:date>2019-08-21T15:27:33Z</dc:date>
    </item>
  </channel>
</rss>

