RE: Unable to connect to external SoC using nRF52833 DK

tonivuc — Fri, 08 Apr 2022 11:55:15 GMT

Thanks again Kenneth! It works!!

We now have RESET, SWDCLK, SWDIO, VTG and VDDnRF connected to the MINEW chip from the P20 port. And we connected GND on MINEW to GND on the P1 port. We didn't need GND_DETECT for it to work when having GND on P1 :) It also works when we use VDD on P1 instead of VDDnRF on P20.

RE: Unable to connect to external SoC using nRF52833 DK

Kenneth — Thu, 07 Apr 2022 19:44:32 GMT

And connect vtg to vdd_nrf, and gnd to gnd_detect.

Kenneth

RE: Unable to connect to external SoC using nRF52833 DK

tonivuc — Thu, 07 Apr 2022 15:07:26 GMT

Hi Kenneth

We have done the wiring proper this time (I think??) according to the programming external board description you sent.

We have a much better setup now that allows us to swap things around

But still the output is:

nrfjprog --memrd 0x10000060 --n 8 -f NRF52 --log
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: Unable to connect to a debugger.
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
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.

We tried starting without the RESET pin connected to the DK, tried removing the RESET pin after the DK connected to the PC, and tried with the RESET pin connected. The output is the same in the terminal for all cases.

This is the .log file with reset pin inserted:

devzone.nordicsemi.com/.../with_5F00_reset_5F00_pin.log

Maybe it's a bit sketchy that we are pulling VDD from another part of the board? (yellow cable to the right in the pic)

Really feel like we did it correct this time...

RE: Unable to connect to external SoC using nRF52833 DK

Kenneth — Thu, 07 Apr 2022 14:29:40 GMT

You may try to disconnect the reset pin (P0.18) or at least make sure it's pulled high, if it's low the chip may stay in reset mode. Make sure that you have installed the latest nrfjprog command line tools if you haven't already:
https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download

And finally check the programming external board description:
https://infocenter.nordicsemi.com/topic/ug_nrf52833_dk/UG/dk/ext_programming_support.html

E.g. EXT_GND_DETECT should be connected to GND on the external board.

Kenneth

RE: Unable to connect to external SoC using nRF52833 DK

tonivuc — Thu, 07 Apr 2022 13:48:24 GMT

I can't find a way to edit my post. But I checked continuity with a multimeter and it seems things are wired wrong for the MINEW chips in Attempt 2 and 3.

This is the wiring that the multimeter showed (I didn't bother to check all the wires after I found a few were wrong)

We will try to wire it correct and update the post. We don't have the setup for attempt 1 at hand so things could be wired wrong there as well.