https://devzone.nordicsemi.com/f/nordic-q-a/33775/busfault-handler-firing-but-only-on-1-device-and-without-debugger-activeThis one is throwing me for a loop. We just did a small build of 40 devices based around the nRF52832. 1 device out of those 40 is behaving very strangely. When the device is running with a debugger attached and running (in other words, actively debuggingen-USTelligent Community 13Wed, 25 Apr 2018 12:33:52 GMThttps://devzone.nordicsemi.com/thread/129761?ContentTypeID=1Wed, 25 Apr 2018 12:33:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0c18d81f-7932-4771-82b2-f70a1b90b440CurtisHx<p>Doh!&nbsp; Looks like that was problem.&nbsp; </p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/129756?ContentTypeID=1Wed, 25 Apr 2018 12:21:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d9cecd90-55be-4382-9c00-0b5f133815f3Vidar Berg<p>Hi,</p> <p>Thank you for the detailed information, it sounds like you are seeing the symptoms of <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.Rev2.errata/dita/errata/nRF52832/Rev2/latest/anomaly_832_108.html?cp=2_1_1_0_1_30">errata 108</a>.&nbsp;The device will enter emulated System ON mode when in debug interface mode, which could explain why it works while you have the debugger attached . Workaround for this errata was implemented in MDK v.8.9.0 / SDK 12.0.0. Please check if&nbsp;it has been implemented in your code.</p> <p>MDK downloads are available on the product page:&nbsp;<a href="http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF52832">http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF52832</a>&nbsp;</p><div style="clear:both;"></div>