https://devzone.nordicsemi.com/f/nordic-q-a/62738/moving-from-pca10056-to-pca10059-unable-to-debug-in-segger-embedded-studioI&#39;m moving a project from pca10056 to pca10059. When programming the pca10059 via the JLink Edu Programmer, the application uploads fine, however it hangs entering debug and doesn&#39;t execute the program when using Segger Embedded Studio. If I take theen-USTelligent Community 13Thu, 18 Jun 2020 03:53:33 GMThttps://devzone.nordicsemi.com/thread/255654?ContentTypeID=1Thu, 18 Jun 2020 03:53:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6c557b8a-b1c3-4337-8963-f3bc8aad7129clell<p>Answering my own foo, this solved it:</p> <p><a href="https://devzone.nordicsemi.com/f/nordic-q-a/34212/howto-flash-bootloader-settings-for-dfu-using-ses-at-debug-time">https://devzone.nordicsemi.com/f/nordic-q-a/34212/howto-flash-bootloader-settings-for-dfu-using-ses-at-debug-time</a></p> <p>Segger requires an extra build step for the settings to be able to debug if an bootloader is present.</p> <p>Contrary to that link, on OSX, I found:</p> <p>1. The installed python3.7.4 worked fine with nrfutil</p> <p>2.&nbsp;/Library/Frameworks/Python.framework/Versions/3.7/bin/nrfutil settings generate --family NRF52840 --application $(ProjectDir)/Output/$(Configuration)/Exe/$(ProjectName).hex &nbsp;--application-version 1 --bootloader-version 1 --bl-settings-version 1 settings.hex</p><div style="clear:both;"></div>