https://devzone.nordicsemi.com/f/nordic-q-a/55625/nrf-connect-for-mac-3-3-0-failureMy target platform is nRF5_SDK_14.2.0_17b948a but I suspect that nRF Connect has independent bin/hex files with which to program the nRF52. I was trying to get the PPK working with nRF52 DK (all three switches = DK) after a few months of non-use (soen-USTelligent Community 13Mon, 16 Dec 2019 12:52:13 GMThttps://devzone.nordicsemi.com/thread/225631?ContentTypeID=1Mon, 16 Dec 2019 12:52:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d98e9012-f9ca-4a1f-9d2d-7826004e8ec0Vidar Berg<p>Hi, I haven&#39;t looked at the implementation of the FW validation mechanism, so not sure what parameters it uses for validation, but have experienced&nbsp;false positives as you&nbsp;described here. Could you try to erase the chip first&nbsp;before you open the&nbsp;Bluetooth Low Energy app and see if you get the same result?&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/225467?ContentTypeID=1Fri, 13 Dec 2019 18:52:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:eab7d111-2bbd-4bd2-89fc-d14a3f093c37jcvandegrift<p>I have two DK&#39;s:</p> <ul> <li>Cut SB9 which is paired with the PPK, and</li> <li>Intact SB9 which I&#39;m using standalone</li> </ul> <p>Both DKs work fine with several of the examples using make erase, make flash_softdevice, make flash sequence.</p><div style="clear:both;"></div>