what do to when you can't flash on the nordic nRF52 DK?

[rharding64]

hello,

below is the error experienced.

nrfjprog --family NRF52 --eraseall
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
Makefile:535: recipe for target 'flash' failed
make: *** [flash] Error 33

does the nRF52 DK have problems in win10 running under a UBUNTU virtual box? that is what i am using.

DUT interfaces via the level shifter to the power pins port. this is a nRF52840 device.

part of log file says it cannot detect the 840 so it defaults to the on board 832 device at that point.

here is portion of the log file;

2019-Sep-13 14:24:25  . . . nRF52_connect_to_emu_without_snr:   Segger logging enabled with callback at 0x140155601208496.

2019-Sep-13 14:24:25  . . . nRF52_connect_to_emu_without_snr:   JLink INFO         ***** Error:
2019-Sep-13 14:24:25  . . . nRF52_connect_to_emu_without_snr:   JLink INFO      Cannot connect to J-Link via USB.
2019-Sep-13 14:24:25  . . . nRF52_connect_to_emu_without_snr:   JLink INFO        returns "Cannot connect to J-Link via USB."
2019-Sep-13 14:24:25  . . . nRF52_connect_to_emu_without_snr:   JLink INFO       (0048ms, 0303ms total)
2019-Sep-13 14:24:25  . . . nRF52_connect_to_emu_without_snr:   JLinkARM.dll Open returned error 'Cannot connect to J-Link via USB.'.

jlinkARM.dll is 6.44e

is this common error and what is your suggestion solution?

thank you

Ron Harding

Plano, Texas

[awneil]

rharding64 said:

does the nRF52 DK have problems in win10 running under a UBUNTU virtual box?

The DK is the little blue board - it's external to Windows, Linux, and VMs!

Segger have native support for J-Link on Linux - have you tried that?

That would narrow it down a bit ...

rharding64 said:

Cannot connect to J-Link via USB

So the problem is in the USB connection from the PC to the J-Link.