Can't connect to custom nrf52 board with J-LINK

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Mon, 15 Jul 2019 07:19:06 GMT

[quote user="mpbn"]How can I determine if device is in such loop? I have a custom board that I was able to program once. [/quote]

If you cannot connect to a board that you have previously been able to connect to, you might have a reset loop in firmware.

Ensure that you have the latest version of the nRF5x command line tools (JLink and nrfjprog), then try to run nrfjprog --recover.

If it does not work, try the below guide. Here's a batch script for windows as well:

https://devzone.nordicsemi.com/f/nordic-q-a/45078/nrf52832-not-connected-anymore-after-first-trying-to-debug-keil/177579#177579

Kind regards,

Håkon

RE: Can't connect to custom nrf52 board with J-LINK

pbn4 — Sun, 14 Jul 2019 13:25:05 GMT

How can I determine if device is in such loop? I have a custom board that I was able to program once.

RE: Can't connect to custom nrf52 board with J-LINK

navarrocantero — Mon, 18 Jun 2018 12:57:49 GMT

Thanks for your reply and your Script.

It has not worked, but was a really solution. I think that if your scripts has not work, my nr5x from my custom boards are died.

If you have something more Im here.

Anyways a lot of thanks !

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Fri, 15 Jun 2018 10:27:15 GMT

If your board is in an assert-loop (RESET loop) occurring very early in the program, it might be hard to recover, as the debugger might not be able to connect fast enough before the nRF does a soft-reset. To avoid this, you should add the "DEBUG" flag when developing, as this would enable blocking assertions instead.

What I would recommend is that you make a small script and loop over "nrfjprog --recover", here in bash (as you're using MacOS):

#!/bin/bash

while [ 1 ]
do
nrfjprog --recover -f NRF52
done

When running this script (CTRL+C to exit it), you continuously toggle the power to your external board (not the DK itself) by connecting/disconnecting the power line from the DK to the custom_board.

Since you have an am-meter connected, you can plug/unplug one of the leads there.

Best regards,

Håkon

RE: Can't connect to custom nrf52 board with J-LINK

navarrocantero — Fri, 15 Jun 2018 08:01:03 GMT

I have several customized boards. And I have been able to code it before but after a process like:
      - recover
      - eraseall
      - programsofdevice

The board stopped responding, so I do not know what state it is in.

I get the impression that the nordic chip is blocked or asleep or something like that.

Yes, I checked the board and it seems that there is no error, as I say it was after a process described above

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Fri, 15 Jun 2018 07:54:37 GMT

If this chip has never been programmed, and is drawing microamps, then there is something wrong. Have you tried checking the internal connections on your custom board to see if there is any issues there?

RE: Can't connect to custom nrf52 board with J-LINK

navarrocantero — Fri, 15 Jun 2018 07:43:11 GMT

Thanks for reply !

The consumption was the one that commented previously!

In idle was 29μA and when i tried the nrjprog --recover or --readregs or other the was between 33μA and 130μA.

I have always had that configuration but I did not know how to explain my measurement configuration

I have oscilloscope also in case it is necessary to make any measurements on the pins of SWDCL and SWDIO or whatever is necessary

Regards !!

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Fri, 15 Jun 2018 07:31:21 GMT

Your setup is good now.

How much current does your board draw now? It should be ~2-3 mA (might be higher if you have a lot of other ICs on your board).

-H

RE: Can't connect to custom nrf52 board with J-LINK

navarrocantero — Thu, 14 Jun 2018 11:49:31 GMT

Yes you are right !!

So, i have a unknown state of my chip, I dont know if have a program inside or are blank.

The vtg measure 0V and vdg 2,85V

So, with the data that i have provided you, and the consumption data in idle and when I tried recover it , can you know anything weird ?

Edit: add pic to clarify the consumption measurement

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Thu, 14 Jun 2018 11:25:11 GMT

It would not be the same to put the am-meter in series with the VTG pin. "VTG" is an input, it does not provide any current to your board. As I previously stated, this is a logic switch for the on-board debugger to use the P20 as the debug out port. This can be confirmed by removing the connection and measuring VTG using your volt-meter, it will then read 0 V.

If you have a blank chip on your custom board, the current consumption you should expect is a couple of milliamps (+ current from any other external ICs that you have on your board).

Best regards,

Håkon

RE: Can't connect to custom nrf52 board with J-LINK

navarrocantero — Thu, 14 Jun 2018 10:47:17 GMT

I dont have measure between VDD and VTG, I was said that VDD and VTG from DK are jumpered, and after, I measured these 2 wires (converted in one wire by the jumper) and my custom board VDD

I was mean before that VDD and VTG are jumpered like this:

↓↓ ↓↓ ↓↓

VDD ------+--<AM-METER>-> VDD CUSTOM BOARD
         /
VTG ----+


And i think that this  would be the same:

VDD --------------+---> VDD
                /
VTG -<AM-METER>---+


And in the vdd I have voltage (2,80 aprox).

As I said is a new DK and stills stocks

regards !!

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Thu, 14 Jun 2018 10:33:21 GMT

Hi,

If you measured between VTG and VDD, then you have measured the current going into the Segger IC, and not the current going into your custom board. "VTG" is an input for the SEGGER IC to use this specific port for programming, as the DK has a total of 3 debug outputs (P19, P20, and on-board nRF).

You should measure the current like this:

VDD ------+--<AM-METER>-> VDD
         /
VTG ----+

GND ------------+-------> GND
               /
GND DETECT ---+

SWD IO -----------------> SWD IO

SWD CLK ----------------> SWD CLK

You could also check if there's voltage on the VDD (in case you've used the board for current measurement on a previous occasion and cut SB9).

Best regards,

Håkon

RE: Can't connect to custom nrf52 board with J-LINK

navarrocantero — Thu, 14 Jun 2018 10:27:46 GMT

Thanks again Håkon.

I have measured the current consumption between the VDD jumpered with VTG from my nRF52-DK and my custom board.

In idle was 29µA and when i tried the nrjprog --recover oscilates between 33µA and 130µA.

The nrf current measurement dosn't have any cut, Its a new development board with factory settings.

I have tried the jlink commander too and here is the log :

regards!

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Thu, 14 Jun 2018 08:53:00 GMT

Hi,

Could you check the current of your external board, by connecting an am-meter in series with the VDD taken from the nRF5x-DK?

Also, could you check that the "nRF current measurement" header, next to the USB header, is shorted (if you have cut the SB9 solder bridge)?

Have you tried using Jlink Commander to see what the output is there?

Kind regards,

Håkon

RE: Can't connect to custom nrf52 board with J-LINK

navarrocantero — Thu, 14 Jun 2018 07:02:34 GMT

Hello, thanks for your reply !!

My custom board is powered with external supply and, i have tested it that i have +3v between VDD and GND

I have connected the custom board with the following configuration on port 20:

nRF52-DK            Custom Board


VDD ------+-------------> VDD
         /
VTG ----+

GND ------------+-------> GND
               /
GND DETECT ---+

SWD IO -----------------> SWD IO

SWD CLK ----------------> SWD CLK

With same behavior, I cant program it.

I also tried:

nRF52-DK            Custom Board


VDD ------+-------------> VDD
         /
VTG ----+

GND DETECT -----+-------> GND
              
SWD IO -----------------> SWD IO

SWD CLK ----------------> SWD CLK

And nothing, here is the nrfjprog --recover --log:

nRF_open_dll

. nRF52_open_dll

. . nRF52_dll_version

nRF_enum_emu_snr

. nRF52_enum_emu_snr

. . nRF52_enum_emu_snr

nRF_enum_emu_snr

. nRF52_enum_emu_snr

. . nRF52_enum_emu_snr

nRF_connect_to_emu_with_snr

. nRF52_connect_to_emu_with_snr

. . nRF52_is_connected_to_emu

. . nRF52_enum_emu_snr

. . nRF52_connect_to_emu_with_snr

. . . nRF52_connect_to_emu_without_snr

. . . nRF52_connect_to_emu_without_snr: JLink: Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20

. . . nRF52_connect_to_emu_without_snr: JLink: Hardware: V1.00

. . . nRF52_connect_to_emu_without_snr: JLink: S/N: 682010721

. . . nRF52_connect_to_emu_without_snr: JLink: TELNET listener socket opened on port 19021

. . . nRF52_connect_to_emu_without_snr: JLink: WEBSRV Starting webserver

. . . nRF52_connect_to_emu_without_snr: JLink: (0011ms, 0013ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:005

. . . nRF52_connect_to_emu_without_snr: JLink: WEBSRV Webserver running on local port 19080

. . . nRF52_connect_to_emu_without_snr: JLink: (0012ms, 0014ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:005

. . . nRF52_connect_to_emu_without_snr: JLink: returns O.K.

. . . nRF52_connect_to_emu_without_snr: JLink: (0012ms, 0014ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:017

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_GetHWStatus(...)

. . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00

. . . nRF52_connect_to_emu_without_snr: JLink: (0002ms, 0016ms total)

. . . nRF52_connect_to_emu_without_snr: There is no generic nRF52 device in J-Link, so we select NRF52832_xxAA.

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:019

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("Device = NRF52832_xxAA", ...).

. . . nRF52_connect_to_emu_without_snr: JLink: /Applications/SEGGER/JLink/JLinkDevices.xml evaluated successfully.

. . . nRF52_connect_to_emu_without_snr: JLink: Device "NRF52832_XXAA" selected.

. . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00

. . . nRF52_connect_to_emu_without_snr: JLink: (0250ms, 0266ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:269

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetRestartOnClose = 0", ...).

. . . nRF52_connect_to_emu_without_snr: JLink: returns 0x01

. . . nRF52_connect_to_emu_without_snr: JLink: (0000ms, 0267ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:270

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("DisableFlashDL", ...).

. . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00

. . . nRF52_connect_to_emu_without_snr: JLink: (0000ms, 0267ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:271

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("SetDbgPowerDownOnClose = 1", ...).

. . . nRF52_connect_to_emu_without_snr: JLink: returns 0x01

. . . nRF52_connect_to_emu_without_snr: JLink: (0000ms, 0268ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:271

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_ExecCommand("ExcludeFlashCacheRange 0x0-0xFFFFFFFF", ...).

. . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00

. . . nRF52_connect_to_emu_without_snr: JLink: (0000ms, 0268ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:271

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_TIF_Select(JLINKARM_TIF_SWD)

. . . nRF52_connect_to_emu_without_snr: JLink: returns 0x00

. . . nRF52_connect_to_emu_without_snr: JLink: (0001ms, 0269ms total)

. . . nRF52_connect_to_emu_without_snr: JLink: T89570380 000:272

. . . nRF52_connect_to_emu_without_snr: JLink: JLINK_SetSpeed(4000)

. . . nRF52_connect_to_emu_without_snr: JLink: (0000ms, 0269ms total)

nRF_recover

. nRF52_recover

. . nRF52_is_connected_to_emu

. . nRF52_is_connected_to_emu: JLink: T89570380 000:273

. . nRF52_is_connected_to_emu: JLink: JLINK_IsOpen()

. . nRF52_is_connected_to_emu: JLink: returns 0x01

. . nRF52_is_connected_to_emu: JLink: (0000ms, 0269ms total)

. . nRF52_is_connected_to_device

. . nRF52_is_connected_to_device: JLink: T89570380 000:273

. . nRF52_is_connected_to_device: JLink: JLINK_IsConnected()

. . nRF52_is_connected_to_device: JLink: returns FALSE

. . nRF52_is_connected_to_device: JLink: (0000ms, 0269ms total)

. . nRF52_readback_status

. . . nRF52_is_ctrl_ap_available

. . . . nRF52_read_access_port_register

. . . . . nRF52_coresight_configure

. . . . . nRF52_coresight_configure: JLink: T89570380 000:273

. . . . . nRF52_coresight_configure: JLink: JLINK_CORESIGHT_Configure()

. . . . . nRF52_coresight_configure: JLink: returns 0

. . . . . nRF52_coresight_configure: JLink: (0102ms, 0371ms total)

. . . . . nRF52_power_debug_and_system_regions

. . . . . . nRF52_write_debug_port_register

. . . . . . nRF52_write_debug_port_register: JLink: T89570380 000:377

. . . . . . nRF52_write_debug_port_register: JLink: JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000) ¿Maybe here is the problem?

. . . . . . nRF52_write_debug_port_register: JLink: returns -1

. . . . . . nRF52_write_debug_port_register: JLink: (0002ms, 0374ms total)

. . . . . . nRF52_write_debug_port_register: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

. . . . . nRF52_power_debug_and_system_regions: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

nRF_close_dll

. nRF52_close_dll

. . nRF52_is_connected_to_emu

. . nRF52_is_connected_to_emu: JLink: T89570380 000:380

. . nRF52_is_connected_to_emu: JLink: JLINK_IsOpen()

. . nRF52_is_connected_to_emu: JLink: returns 0x01

. . nRF52_is_connected_to_emu: JLink: (0001ms, 0375ms total)

. . nRF52_disconnect_from_emu

. . . nRF52_is_connected_to_device

. . . nRF52_is_connected_to_device: JLink: T89570380 000:381

. . . nRF52_is_connected_to_device: JLink: JLINK_IsConnected()

. . . nRF52_is_connected_to_device: JLink: returns FALSE

. . . nRF52_is_connected_to_device: JLink: (0001ms, 0376ms total)

. . . nRF52_unpower_debug_and_system_regions

. . nRF52_disconnect_from_emu: JLink: T89570380 000:393

. . nRF52_disconnect_from_emu: JLink: JLINK_Close()

RE: Can't connect to custom nrf52 board with J-LINK

Håkon Alseth — Wed, 13 Jun 2018 13:46:17 GMT

Hi,

Are you using P19 (2x5 pin header, top left corner) or P20 (1x8 pin header, just above the SEGGER IC)?

If using P20, please follow this schematic: https://devzone.nordicsemi.com/f/nordic-q-a/14058/external-programming-using-nrf52-dk/53757#53757

If using P19 (DEBUG OUT), then connect the 10 pin SWD cable, as well as VDD and GND, to your custom board.

Best regards,

Håkon