https://devzone.nordicsemi.com/f/nordic-q-a/89804/sudden-hardfault-when-scanning-s140-softdeviceHello, We&#39;re using a nRF52840 with S140 SoftDevice (v7.3.0) for a Central device but we&#39;re having a disturbing issue when scanning: a hardfault occurs less than 2 seconds after having started scanning. The scan configuration we are using is: ble_gap_scan_params_ten-USTelligent Community 13Mon, 11 Jul 2022 13:00:00 GMThttps://devzone.nordicsemi.com/thread/376435?ContentTypeID=1Mon, 11 Jul 2022 13:00:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0cebef90-9055-42cc-810d-16a9e6add35dMario Amigot<p>Hi Hung,</p> <p>Thanks for your quick response.</p> <p>Indeed, the root cause was the processing of the advertising data in our application.</p> <p>Apparently it is possible to receive an advertising report whose advertising data length is 0 (and we have found that there is a device which advertises no data in our office).&nbsp;The issue was that we had not implemented that case so as soon as this device&#39;s advertising packet was received, a hardfault was triggered.</p> <p>The bug is fixed and the central device is working properly now.</p> <p>Regards,</p> <p>Mario</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/376376?ContentTypeID=1Mon, 11 Jul 2022 09:49:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f36b82ea-3651-47de-a58b-3abcf56b3f00Hung Bui<p>Hi Mario,&nbsp;</p> <p>Could you try to find more information about the hardfault ? There are some guide on how to debug it <a href="https://devzone.nordicsemi.com/f/nordic-q-a/12291/what-can-cause-a-hardfault-and-how-to-catch-it">here.</a></p> <p>We would need to look into how you process the advertising data. I suspect that it could be the reason for a hardfault.&nbsp;</p> <p><br />We do have a very busy BLE environment here in our office and we haven&#39;t seen any issue on our scanner.&nbsp;<br /><br />Do you have the same problem when you test with one of our central examples in the SDK ?&nbsp;</p><div style="clear:both;"></div>