https://devzone.nordicsemi.com/f/nordic-q-a/108722/unable-to-recover-nrf5340-after-flashing-nrf9160-code-on-itHi, We have a project that utilizes both an nrf9160 and an nrf5340. Unfortunately, we often find ourselves having programmed the nrf9160 code ( say asset_tracker_v2) onto the nrf5340. (FWIW, we use a segger Jlink, and while it prevents us from programmingen-USTelligent Community 13Sun, 03 Mar 2024 18:33:06 GMThttps://devzone.nordicsemi.com/thread/471921?ContentTypeID=1Sun, 03 Mar 2024 18:33:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:34382954-bf02-447d-b2a3-e4889101aed6Manu<p>Edvin, thanks. Will try this.&nbsp;</p> <p>M</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/471259?ContentTypeID=1Wed, 28 Feb 2024 11:43:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d84f8b57-abfc-411c-9ab5-c4531b3145f5Edvin<p>Hello,</p> <p>You can try the attached .bat script (windows. If you are on Linux, you probably know how to modify it to run there).</p> <p><a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/recover_5F00_script.bat">devzone.nordicsemi.com/.../recover_5F00_script.bat</a></p> <p>Make sure&nbsp;no other DKs are running on your computer. If they are, add --snr &lt;Segger JLink programmer serial number&gt; to the end of line 2.</p> <p>What it does is to continuously try to recover the device. While this is running, power cycle the nRF53 on and off repeatedly, and hopefully, the debugger will be able to hook onto the nRF53 and recover it at some point.</p> <p></p> <p>Best regards,</p> <p>Edvin&nbsp;</p><div style="clear:both;"></div>