https://devzone.nordicsemi.com/f/nordic-q-a/108140/failure-to-program-nrf51I have used NRF51 for nearly 10 years and we are using also NRF52 chips in our production environment. Recently I have been having more and more problems programming a hex file on the production samples. I am using Cygwin on Windows 10 pro with aen-USTelligent Community 13Tue, 27 Feb 2024 03:23:41 GMThttps://devzone.nordicsemi.com/thread/470905?ContentTypeID=1Tue, 27 Feb 2024 03:23:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:84533f03-5cd7-4daa-a51b-75f4823bcd32davi9x8<p>Try power cycling the NRF51 chip by disconnecting and reconnecting the power source. This can sometimes reset the device and resolve communication issues. <span style="color:#ffffff;"><a style="color:#ffffff;" href="https://fnafgo.com">fnaf</a></span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/468128?ContentTypeID=1Thu, 08 Feb 2024 18:48:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ab958a50-91f0-42a3-abfb-c815931bb7c4icondev<p>I was able to program one of the boards by uninstalling all JLink/SEGGER items and installing version v7.80c. I will keep this in mind for future reference. Thanks for your assistance in this matter.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/468039?ContentTypeID=1Thu, 08 Feb 2024 12:04:29 GMT137ad170-7792-4731-bb38-c0d22fbe4515:771718b4-2b83-409a-87ab-8acdd4031c8dSigurd<p>Hi!</p> <p>We use by default&nbsp;<span>JLinkARM.dll&nbsp;v7.80c with nrfjprog v10.22.1 , so t</span>ry using that jlink version instead. If that does not work, try downgrading jlink/nrfjprog to an older version. Note that from nrfjprog v10.23.4 we have stopped testing on&nbsp;nRF51 devices.</p><div style="clear:both;"></div>