Attachments (1) Download All
Nordic Case Info
  • Case ID: 303721
Options

nRF52 DK V3.0.0 Debug out for programming external board can't work

xhe

Hello Nordic,

I have been using nRF52-DK to perform a process of programming. Within the process, I need to access the external board's nRF52 and the OB-nRF52 both.(Not at the same time)

I make a schema of connection by simplifying the system:

By turn ON/OFF the Power supply, I can toggle the logic level of pin SELECT/VGT to choose the target of debugger:

  • Power Supply ON: SELECT/VGT is High -> Target of debugger is the external board.
  • Power Supply OFF: SELECT/VGT is Low -> Target of debugger is the OB-nRF52.

This scenario was working well with a DK < rev.2.2.0, but doesn't work at all with the new DK rev.3.0.0.

Problem-1: Incorrect logic level of SELECT/VGT

Always on the above scenario, when the Power supply is ON, the target of debugger is the external board, that's correct.

However, once turning OFF the Power supply, I can't access to the expected target, OB-nRF52, with the following error:

This is the log:

Fullscreen 0525.log.log Download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
[2023-Mar-21 15:58:25] [debug] --------------------------------------------------------------------------------
[2023-Mar-21 15:58:25] [debug] C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe --memrd 0x10001080 --log
[2023-Mar-21 15:58:25] [debug] nrfjprog version 10.19.0 external
[2023-Mar-21 15:58:25] [debug] --------------------------------------------------------------------------------
[2023-Mar-21 15:58:25] [ info] Load library at C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.dll.
[2023-Mar-21 15:58:25] [ info] Library loaded, loading member functions.
[2023-Mar-21 15:58:25] [ info] Member functions succesfully loaded.
[2023-Mar-21 15:58:25] [debug] [ Client] - open
[2023-Mar-21 15:58:25] [debug] [ Client] - start
[2023-Mar-21 15:58:25] [ info] [ Client] - stdout: Jlinkarm nRF Worker ready. Handling sequence 3d6bdbea-747d-4927-b78c-3ad039f44417.
[2023-Mar-21 15:58:25] [debug] [SeggerBackend] - Logger sink registered in Segger backend logger
[2023-Mar-21 15:58:25] [debug] [ JLink] - Logger sink registered in JLink logger
[2023-Mar-21 15:58:25] [debug] [ nRFXX] - open
[2023-Mar-21 15:58:25] [debug] [ nRFXX] - just_check_family
[2023-Mar-21 15:58:25] [debug] [SeggerBackend] - open_dll
[2023-Mar-21 15:58:25] [debug] [SeggerBackend] - No J-Link DLL path was provided. Attempting to auto detect.
[2023-Mar-21 15:58:25] [ info] [SeggerBackend] - Load library at C:\Program Files (x86)\SEGGER\JLink\JLinkARM.dll.
[2023-Mar-21 15:58:25] [trace] [ Client] - Command open executed for 99 milliseconds with result 0
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

With the multimeter, the voltage on pin SELECT/VGT is 0.79V.

Meanwhile, by disconnecting the link (VGT+SWDIO+SWDCLK+GND) between nRF52-DK and the external board, the voltage of pin SELECT/VGT is 0V.

Problem-2: Can not boot on Bootloader mode

Always using the same method that power up the nRF52-DK by pressing the button BOOT/RESET. The DK always boot on JLINK mode, not Bootloader mode.

I tested 2 DK rev.3.0.0 and got the same result. But with DK rev.2.1.0, it booted correctly on Bootloader mode.

Do you have any idea?

Thank you very much

Kind regards

Xiang

Terms of service