<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Issue with Zigbee flash area</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/110247/issue-with-zigbee-flash-area</link><description>Hello, 
 we are using nrf52840 with nrf5 sdk for thread and Zigbee v4.2.0. In our application, Nordic is the coordinator of Zigbee network. 
 We have a counter that is increased whenever Zigbee handler is triggered with event ZB_BDB_SIGNAL_DEVICE_FIRST_START</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 16 Apr 2024 13:52:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/110247/issue-with-zigbee-flash-area" /><item><title>RE: Issue with Zigbee flash area</title><link>https://devzone.nordicsemi.com/thread/479018?ContentTypeID=1</link><pubDate>Tue, 16 Apr 2024 13:52:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32e822b4-033b-4fa2-97bc-fd06c4264dea</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please provide the application log from the device.&lt;/p&gt;
&lt;p&gt;Another thing you can try is to read the flash of the device and program it on another device with nRF Programmer. It could be something with the NVRAM being corrupted since the device starts running again after they have erased Zigbee flash. It could also be a buffer leak somewhere, causing them to run out of Zigbee buffers.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>