How to run 'nrfjprog --recover'

[noob_with_ucontrollers]

Hi, 

I am trying to program my custom PCB using nRF 52 DK (I am using PCA10040 , nrf52382) as I have done countless times before. But suddenly embedded studio is giving me the following error : 

"failed to connect to target no idcode detected"  no matter which port I use. 

I do see JLINK(); on my computer. 

I searched the forum and the most common solution is reprogramming the DK using 'nrfjprog --recover'  but I do not know how to run this recover command using embedded studio...? I am using a 64 bit Windows OS and do not see any NRFX command line tool installations for that over here: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrf5x_cltools%2FUG%2Fcltools%2Fnrf5x_installation.html

When I run the nrfjprog --recover command on my Windows command console it's not recognized. 
 

I did write my question as a comment on one of the posts already asking this question but those are old and I"m not sure if anyone's going to see my question. Any suggestions or guidances are much appreciated. 

Thank you! 

[Stian Røed Hafskjold]

Hi, you can find the command line tools here: http://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Command-Line-Tools/Download#infotabs

Download, install and run 'nrfjprog --recover'

[noob_with_ucontrollers]

Hi, thank you for answering my question! 

I did find the folder for 64 bit and install nrfJprog... however in the installation files, I could only find a file nRFjprog, and could not see any nrfjprog --recover application. I ran the nrfjprog application while my PC port was connected to the nrf DK., and it executed. 

However, I still face the same target idcode error. 

When I flash the same code (in same SDK ) using another computer, it works. So i don't think the DK board is the problem anymore... 
I tried reinstalling JLINK and Embedded Studio on my computer but the problem doesn't go away. 

Thank you so much once again for your time and guidance!! 

[Vidar Berg]

Hi,

Would be good to know if programming also fails with nrfjprog. Please try to run nrfjprog --recover as Stian suggested and see if it returns any errors.

Expected output when it everything works: