<?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>Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123315/device-randomly-resets-during-ble-scanning-in-noisy-environments-nrf54l15-ncs-v3-0-2</link><description>Hi all, 
 I&amp;#39;m working on an application using the nRF54L15 with NCS v2.9.0 and Zephyr RTOS. The device performs BLE scanning using the following parameters: 
 
 
 When deployed in a noisy BLE environment (e.g., multiple advertising devices nearby), the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 01 Aug 2025 07:06:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123315/device-randomly-resets-during-ble-scanning-in-noisy-environments-nrf54l15-ncs-v3-0-2" /><item><title>RE: Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/thread/544270?ContentTypeID=1</link><pubDate>Fri, 01 Aug 2025 07:06:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf188a6b-af21-4975-a794-bc11f1be4361</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi Haresh,&lt;/p&gt;
&lt;p&gt;Yes, it&amp;#39;s possible that the buffer overflow was only part of the issue. Have you been able to reproduce the problem after fixing it? The other issue from the linked ticket is still being investigated internally. Hopefully there will be an update on it soon.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/thread/544111?ContentTypeID=1</link><pubDate>Wed, 30 Jul 2025 13:54:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:acdfe38b-d1e9-4bfd-8b27-a425fefb13ef</guid><dc:creator>Haresh05</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I have made the changes and it seems to work but before that I also changed the SCAN_MSG_MAX_LEN macro to 150 and tried but even then it was getting stuck.&lt;br /&gt;So I am not sure what is the final solution for this or this behaviour is due to the issue you mentioned here?&lt;/p&gt;
[quote userid="4240" url="~/f/nordic-q-a/123315/device-randomly-resets-during-ble-scanning-in-noisy-environments-nrf54l15-ncs-v3-0-2/544028"]I was made aware of this issue by a coworker, and it seems to resemble the same issue you&amp;#39;re experiencing: &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/123285/nrfxlib-v3-0-2-ble-scanning-results-stop-being-reported" data-contentid="0e564d3af14448f4b29a2d13c779fd14" data-contenttypeid="46448885d0e64133bbfbf0cd7b0fd6f7" class="ui-contentpeek internal-link"&gt;nrfxlib v3.0.2: BLE scanning results stop being reported&lt;/a&gt;&amp;nbsp;&amp;nbsp;.&amp;nbsp;[/quote]
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Haresh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/thread/544050?ContentTypeID=1</link><pubDate>Wed, 30 Jul 2025 10:12:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:596f83ea-17af-4281-bbf8-e320c4ff1b2b</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Thanks for confirming. In the code you posted it seems like you are passing the wrong length argument to memcpy here:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1753870213657v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Shouldn&amp;#39;t it be:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1753870223985v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;The scan report can exceed 32 bytes when scanning extended adv. packets.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/thread/544032?ContentTypeID=1</link><pubDate>Wed, 30 Jul 2025 08:47:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c3084ae1-b4a5-46d9-aa52-0676fab4b021</guid><dc:creator>Haresh05</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Earlier I was working on v2.9.0 but when I enabled FEM module I got the runtime error in that so I updated to v3.0.2&lt;/p&gt;
&lt;p&gt;so yes currently I am working on v3.0.2 only.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Haresh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/thread/544028?ContentTypeID=1</link><pubDate>Wed, 30 Jul 2025 08:33:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc6eeef6-9a47-46e6-bd4a-bd9ce721b381</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi Haresh,&lt;/p&gt;
&lt;p&gt;I was made aware of this issue by a coworker, and it seems to resemble the same issue you&amp;#39;re experiencing: &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/123285/nrfxlib-v3-0-2-ble-scanning-results-stop-being-reported"&gt;nrfxlib v3.0.2: BLE scanning results stop being reported&lt;/a&gt;&amp;nbsp;&amp;nbsp;.&amp;nbsp;&lt;/p&gt;
[quote user=""]I&amp;#39;m working on an application using the &lt;strong&gt;nRF54L15&lt;/strong&gt; with &lt;strong&gt;NCS v2.9.0&lt;/strong&gt; and Zephyr RTOS. The device performs BLE scanning using the following param[/quote]
&lt;p&gt;Is this a typo, or are you seeing the issue in both v2.9.0 and v3.0.2?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/thread/544014?ContentTypeID=1</link><pubDate>Wed, 30 Jul 2025 07:02:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:71a57d5b-f9e1-4587-a6ba-36c27eaeed60</guid><dc:creator>Haresh05</dc:creator><description>&lt;p&gt;Hi Vidar,&lt;/p&gt;
&lt;p&gt;Thanks for your suggestion.&lt;/p&gt;
&lt;p&gt;I disabled the watchdog and enabled the config you suggested.&lt;br /&gt;After this device does not restart but it stuck. So I enabled the BT log for debugging and found that when the packet length is large at that time device gets stuck.&lt;/p&gt;
&lt;p&gt;Below are the last 2 packets after which device got stuck. I tried multiple times and it got stuck when the len received is 116.&lt;/p&gt;
&lt;p&gt;Let me know what can be done in this case as none of the other device in my environment is doing extended advertising with this much size.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;&lt;pre class="ui-code" data-mode="text"&gt;[2025-07-30 12:05:17] [00:00:10.575,479] &amp;lt;dbg&amp;gt; bt_sdc_hci_driver: event_packet_process: LE Meta Event (0x0d), len (56)
[2025-07-30 12:05:17] [00:00:10.575,497] &amp;lt;dbg&amp;gt; bt_hci_core: bt_recv_unsafe: buf 0x2000d69c len 58
[2025-07-30 12:05:17] [00:00:10.575,534] &amp;lt;dbg&amp;gt; bt_hci_core: rx_work_handler: Getting net_buf from queue
[2025-07-30 12:05:17] [00:00:10.575,541] &amp;lt;dbg&amp;gt; bt_hci_core: rx_work_handler: buf 0x2000d69c type 2 len 58
[2025-07-30 12:05:17] [00:00:10.575,548] &amp;lt;dbg&amp;gt; bt_hci_core: hci_event: event 0x3e
[2025-07-30 12:05:17] [00:00:10.575,557] &amp;lt;dbg&amp;gt; bt_hci_core: hci_le_meta_event: subevent 0x0d
[2025-07-30 12:05:17] [00:00:10.575,566] &amp;lt;dbg&amp;gt; bt_scan: bt_hci_le_adv_ext_report: Adv number of reports 1
[2025-07-30 12:05:17] [00:00:10.575,615] &amp;lt;dbg&amp;gt; bt_scan: le_adv_recv: F7:5E:59:78:6E:59 (public) event 0, len 30, rssi -71 dBm
[2025-07-30 12:05:17] [00:00:10.575,649] &amp;lt;inf&amp;gt; ilumi_scan: Scan msgs recvd: 1

[2025-07-30 12:05:17] [00:00:10.580,496] &amp;lt;dbg&amp;gt; bt_sdc_hci_driver: event_packet_process: LE Meta Event (0x0d), len (116)
[2025-07-30 12:05:17] [00:00:10.580,518] &amp;lt;dbg&amp;gt; bt_hci_core: bt_recv_unsafe: buf 0x2000d404 len 118
[2025-07-30 12:05:17] [00:00:10.580,558] &amp;lt;dbg&amp;gt; bt_hci_core: rx_work_handler: Getting net_buf from queue
[2025-07-30 12:05:17] [00:00:10.580,566] &amp;lt;dbg&amp;gt; bt_hci_core: rx_work_handler: buf 0x2000d404 type 2 len 118
[2025-07-30 12:05:17] [00:00:10.580,572] &amp;lt;dbg&amp;gt; bt_hci_core: hci_event: event 0x3e
[2025-07-30 12:05:17] [00:00:10.580,623] &amp;lt;dbg&amp;gt; bt_hci_core: hci_le_meta_event: subevent 0x0d
[2025-07-30 12:05:17] [00:00:10.580,633] &amp;lt;dbg&amp;gt; bt_scan: bt_hci_le_adv_ext_report: Adv number of reports 1
[2025-07-30 12:05:17] [00:00:10.580,683] &amp;lt;dbg&amp;gt; bt_scan: le_adv_recv: 5F:F6:F6:1C:20:F0 (random) event 5, len 90, rssi -88 dBm&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Haresh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device Randomly Resets During BLE Scanning in Noisy Environments (nRF54L15 + NCS v3.0.2)</title><link>https://devzone.nordicsemi.com/thread/543916?ContentTypeID=1</link><pubDate>Tue, 29 Jul 2025 11:23:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1929a416-8298-4924-a225-1af14743ca5f</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m now aware of any known issues which could explain this issue. Could you please build with&amp;nbsp;&lt;span&gt;CONFIG_RESET_ON_FATAL_ERROR&lt;/span&gt;&lt;span&gt;=n, watchdog disabled, and print&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/d6083cc052dd432938009bb3b12d864824c3c7c1/samples/nfc/system_off/src/main.c#L158"&gt;the reset reason on boot&lt;/a&gt;&amp;nbsp;to make sure you are able to catch any runtime errors?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Vidar&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>