nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

Unable to connect to external SoC using nRF52833 DK

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

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

Children
No Data
Related