We have our own custom board using nRF52832 (via Laird BL652 module). Until recently, we have been programming our application, bootloader and softdevice using the PCA10040 as jlink device. Flashing with Keil debugger, nRFgo Studio and nrfjprog.exe are all working, no issues at all.
Now we've purchased 2 jlink Base programmers from Segger and neither one seems to work reliably. Simply trying to erase rarely succeeds. For example: "nrfjprog.exe -f NRF52 -e" results in ERROR: JLinkARM DLL reported an error. Try again. If error condition ERROR: persists, run the same command again with argument --log, cont ERROR: Semiconductor and provide the generated log.log file to them.
"nrfjprog.exe -f NRF52 -e --log" results in -------------------------------------------------------------------------------- nrfjprog -f NRF52 -e --log nrfjprog verion 9.6.0 -------------------------------------------------------------------------------- FUNCTION: open_dll. JLinkARM.dll OpenEx returned error 'Communication timed out: Requested 4 bytes, received 0 bytes ! Cannot connect to J-Link via USB.'. FUNCTION: close_dll. FUNCTION: close_dll.
We're using the same cable and connector from Segger with Base as with PCA10040, so unlikely to be cabling issue.
Other things I've tried: - update USB driver (was already up-to-date) - update Jlink, now running latest v6.22d - tried second Jlink Base programmer
The odd thing is that maybe one out 10 attempts succeeds, so its not completely broken, just flakey as all get out.
Has anyone else encountered similar issues with the Segger Base programmer? Any insights how to get it to work better?
