https://devzone.nordicsemi.com/f/nordic-q-a/33238/programming-a-pca10040-with-softdevice-s132-using-keil-v5Hi. I am trying to program the ble beacon application example that requires the S132 softdevice. I am following the instructions that request the device be erased first. This I can do successfully which I assume means that the J-Link OB setup is O.Ken-USTelligent Community 13Thu, 12 Apr 2018 17:44:14 GMThttps://devzone.nordicsemi.com/thread/128125?ContentTypeID=1Thu, 12 Apr 2018 17:44:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:32b8c631-cf48-494e-9107-8e6a103c97e1chrisharley<p>Hi Sigurd.</p> <p>Thank you for this answer. It does make sense.</p> <p>I have another question but shall raise a new ticket.</p> <p>Regards Chris Harley</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/127768?ContentTypeID=1Wed, 11 Apr 2018 09:07:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c820a9f0-99af-4d3f-a3ed-7bc4932b706aSigurd<p>Hi,</p> <p><span>Most likely a SoftDevice have already been flashed to the chip. </span>The Keil flashing-algorithm has a check that stops it from overwriting an existing SoftDevice.</p> <p><span>I recommend using nrfjprog to erase the chip, and then flash the SoftDevice again.</span></p> <p><span><pre class="ui-code" data-mode="text">nrfjprog –-eraseall nrfjprog --program s132_nrf52_6.0.0_softdevice.hex</pre></span></p> <p><span>Note that you can use Keils integrated command line functionality with nrfjprog. See&nbsp;<a href="https://devzone.nordicsemi.com/blogs/856/keil-nrfjprog-true/">this blog post</a>&nbsp;for more information about that.</span></p><div style="clear:both;"></div>