External NRF52832 Program with NRF52DK - Reset not working

relevante gravatar image

asked 2017-07-17 17:28:26 +0200

updated 2017-07-18 14:46:12 +0200


I'm trying to program an external NRF52832 board with the NRF52-DK, per the instructions in this post.

Programming works fine, but the code doesn't execute after reset. I'm using nrfjprog (on OSX) with --chiperase --program and --reset. The code doesn't run until I manually power-cycle the external board. Then, interestingly, if I issue another command with only --reset, the code stops until I power-cycle again.

Any thoughts on what might be causing this?



Using nrfjprog version: 9.4.0, JLinkARM.dll version: 5.10d

--log log.log file

edit retag flag offensive close delete report spam


Which version of nrfjprog are you using? Could you also run the command with the --log option and post the log here?

Bjørn Spockeli ( 2017-07-18 10:28:12 +0200 )editconvert to answer

Thanks for the reply. Added the requested info to the initial post above.

Nick ( 2017-07-18 14:40:11 +0200 )editconvert to answer

There should be a log.log file in the folder where you called nrfjprog from.

Bjørn Spockeli ( 2017-07-18 14:41:33 +0200 )editconvert to answer

Thanks! Updated again.

Nick ( 2017-07-18 14:46:23 +0200 )editconvert to answer

The logs look fine, but could you try to update your nrfjprog to v9.6.0(link ) and JLink to v6.16 (link) and see if that solves the issue. Is the external nRF52832 board a custom board?

Bjørn Spockeli ( 2017-07-18 14:58:45 +0200 )editconvert to answer

OK, thanks, I just updated the software. The nrfjprog link and the link on the website labeled 9.6.0 seem to link to 9.5.0 though. I'm away from the hardware now but I'll let you know when I'm able to try again later today or in the morning at the latest.

Yes, the external board is a custom board, although it was designed by a third party. Is there anything you can think of that I should check for on the hardware side that could cause this?

Nick ( 2017-07-18 20:54:56 +0200 )editconvert to answer

My bad, this should be the correct link. Not other than lengths of the SWD lines on the custom PCB , but if that was the case then you should not have been able to program the external device.

Bjørn Spockeli ( 2017-07-19 16:30:04 +0200 )editconvert to answer

Thanks. Even the 9.6.0 version linked from that page is actually 9.5.0 though.

Programming works fine other than this issue. I tried this morning with the updated software (nrfjprog 9.5.0 and JLink 6.16) with the same results.

Nick ( 2017-07-19 17:51:38 +0200 )editconvert to answer

Hmm, do you have another custom board that you can test with?

Bjørn Spockeli ( 2017-07-20 13:31:43 +0200 )editconvert to answer

I have multiple copies of this one which I've tried, but I don't have one of a different design. Is there one you could recommend to try for testing?

Nick ( 2017-07-20 14:29:40 +0200 )editconvert to answer

No, I was just wondering if you're seeing the same behavior on other identical boards.How have you connected the boards together? Have you connected the EXT_RESET on the Debug Out header(p19) or the SH_RESET pin on P20 to the reset pin of the custom board(P0.21)?

Bjørn Spockeli ( 2017-07-20 15:25:10 +0200 )editconvert to answer

I'm using this arrangement exactly: https://devzone.nordicsemi.com/questi...

Nick ( 2017-07-20 18:12:14 +0200 )editconvert to answer

Could you connected the EXT_RESET on the Debug Out header(p19) or the SH_RESET pin on P20 to the reset pin of the custom board(P0.21) and then try to reset the external board after programming it?

Bjørn Spockeli ( 2017-07-24 14:16:08 +0200 )editconvert to answer