nRF52 Failed to Connect Target. No idcode detected

Question

Hi 
 I working with nRF52832 (E73-2G4M04S1B) Module. Now the nRST pin is default low state. Try to connect target ,but it connected. 
 pullup the nRST the pin, but there is no improvement. 
 
 Thanks & Regards 
 ASK

Abiots · Answer

I faced this issue when I uploaded a code where i was running an infinite loop without much delay in simple words bad programming. This increased the power consumption and due to lack of power to nrf chip, we were getting this error. 
 Solution: Connect the Vdd_nrf pin to 5 volts and erase the flash.

Dano · Answer

Version 2.0.1 
 However I discovered the issue a couple of days ago (I was about to reply to this) - a dirty Debug out connector base. 
 I just couldn't understand why I could talk to each chip separately, but the OB J-Link wouldn't talk to the nRF - almost like the link was broken (!). So I did a visual inspection of the DK board and noticed dirt around the base of the Debug Out - P19... I cleaned this and the DK started working again. I couldn't believe it - such a simple issue. The take away ...... if everything else fails just get the headset on and have a close look at the entire PCB and check for physical issues/damage. 
 I now understand the "no idcode" error means the OB-J cannot find the nRF so Check the connector path completely ... (no really, check the connector!). 
 Perhaps a slight hardware revision to deal with the HV 5v issue... maybe?. Its no huge problem but you need the right external hardware. If a DK user could still see the OB-J but go 5v on HV and nuke the nRF .. that would help IMO. 
 D

nRF52 Failed to Connect Target. No idcode detected

Top Replies