Resetting DIF to reduce interface current on nRF52

RE: Resetting DIF to reduce interface current on nRF52

Stian Røed Hafskjold — Wed, 15 Nov 2017 07:38:19 GMT

This should be handled by the JLink automatically. Are you using read back protection? I've only been able to reproduce the issue when read back protection is activated, since you can't do a soft reset. Any info would be helpful so we can track down the cause of this. Can you please post debugger type/version, JLink dll version, JLink FW version, nrfjprog version etc.?

RE: Resetting DIF to reduce interface current on nRF52

samsonc — Wed, 15 Nov 2017 02:08:40 GMT

THANK YOU! This works perfectly. I've been looking for this information for quite a while. I'm guessing it may work with the nRF51 as well, which would be useful for some of my other prototypes.

Perhaps this should be integrated into nrfjprog, the standard gcc makefiles, or debug configuration? I can't think of a reason for why you wouldn't want to do this all the time after you're done flashing or debugging (I have seen the high current even while only flashing the device)

RE: Resetting DIF to reduce interface current on nRF52

Stian Røed Hafskjold — Tue, 14 Nov 2017 15:14:53 GMT

Hi, you can try to write to the DIF directly using JLinkExe and reset it.

Run Jlink.exe (JlinkExe in linux), do not connect to the chip, just make sure that the correct JLink is selected based on the serialnumber. Write this:

SWDSelect
SWDWriteDP 1 0x04000000
exit

That should reset the DIF, and current consumption should go down to normal.

EDIT

I've noticed that this workaround does not work with JLink version 6.16 and higher in combination with the nRF52 DK onboard JLink (FW version 24.jul.17). It is still working with my JLink Lite programmer.

So if people reading this post can't get it to work try to install JLink 6.14a.

www.segger.com/.../JLink_Windows_V614a.exe
www.segger.com/.../JLink_Linux_V614a_x86_64.deb