• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 25 subscribers
  • Views 276 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 287261
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

Unable to connect to external SoC using nRF52833 DK

user114711

Hi

We are trying to connect to connect to a MINEW MS88SF23 SoC from our nRF52833 DK.

For all tests, nRF power source switch is set to VDD, nRF ONLY switch is set to DEFAULT, and the power switch is set to ON. The DK is powered by USB from a Windows 10 laptop.

We have done a few attempts.

Attempt 1:

Nordic DK and MINEW Chip

We are powering the external board from one of the VDD ports on the development kit (red cable).

Running the command "nrfjprog --memrd 0x10000060 --n 8 -f NRF52" as suggested here produced the same DEVICEID whether the external SoC was connected to the Debug Out P19 10-pin connector or not.

We checked continuity from the board to the pins on the external SoC and it was OK. We also checked that there was a voltage differance between the VDD and GND wires (i think it was 2.9V) but the instant I did the measurement the DK disconnected from the computer. Then the voltage between the pins dropped to 1.6V. We also have a CR 2032 battery on the DK, so I assume it was the power source now that the USB power dissapeared. I don't understand why the DK disconnected because of a voltage measurement with a multimeter.

 

Attempt 2:

We attempted to solder SB47 on the DK to power the SoC directly from the 10-pin P19 connector. Then tried these two newly wired MINEW chips (excuse the bad wiring)

Result was:

nrfjprog --memrd 0x10000060 --n 8 -f NRF52
ERROR: No debuggers were discovered

 

Attempt 3:

We put a 3V CR 2032 battery in for the external SoC and used a DK that did not have SB47 soldered. 

For the SoC pictured to the right in Attempt 2, we got the following:

nrfjprog --memrd 0x10000060 --n 8 -f NRF52
ERROR: Unable to connect to a debugger.ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

For the one to the left we got:

nrfjprog --memrd 0x10000060 --n 8 -f NRF52 --log
ERROR: [SeggerBackend] - 10 second timeout elapsed, no time left to wait for debug port to power up.
ERROR: nrfjprog failed for an unknown reason. Run the same command again with
ERROR: argument --log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.

Which produced the following log:


For the one on the right we got:

 nrfjprog --memrd 0x10000060 --n 8 -f NRF52 --log
ERROR: [SeggerBackend] - 10 second timeout elapsed, no time left to wait for debug port to power up.
ERROR: nrfjprog failed for an unknown reason. Run the same command again with
ERROR: argument --log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.

which produced the following log:

 

What can we do to get closer to being able to connect to the external SoC? The MINEW chips have been used succesfully for a previous master's thesis before using the method in Attempt 1 (but the previous users might have failed to mention something for us)

Parents
  • 0

    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

  • 0 in reply to user2111

    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:

    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...

  • 0 in reply to user114711

    And connect vtg to vdd_nrf, and gnd to gnd_detect.

    Kenneth

  • 0 in reply to user2111

    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.

Reply Children
No Data
Related
Terms of service