> On Dec 6, 2017, at 11:14 AM, [email protected] wrote: > >> Make sure that that old version of process JLinkExe is not running anymore. >> Sometimes that process fails to exit, and if itâs still there, itâs >> going to get in >> the way of ânewt loadâ/ânewt debugâ. >> >> Also, the MCU running JTAG adapter on the board might get stuck, in which >> case powering on/off will unwedge it. >> >> > > I have tried to turn on/off it didn't work. I have also make sure no JLinkExe > is running. Still no luck
Next you could try running the commands invoked by newt manually; one one window start the jlink sw with GDB interface: JlinkGDBServer -device nRF52 -speed 4000 -if SWD -port 3333 -singlerun and another window start gdb arm-none-eabi-gdb bin/targets/nrf52_boot/app/apps/boot/boot.elf connect to JlinkGDBserver from gdb: target remote localhost:3333 If this works, then turn on more debugging within download shell script. i.e. add ‘set -x’ somewhere on the top of the hw/bsp/nrf52dk/nrf52dk_download.sh, and then run ‘newt -lDEBUG load nrf52_boot’. I’m guessing you're using MacOS as your dev environment?
