nrfjprog - unable to connect to target

RE: nrfjprog - unable to connect to target

hotyp — Tue, 13 Nov 2018 09:08:39 GMT

Hi,

this solve the problem. What i do not understand is why with other tools everything works fine even with 4 MHz speed.

Best regards

Honza

RE: nrfjprog - unable to connect to target

Håkon Alseth — Tue, 13 Nov 2018 08:49:07 GMT

Hi,

"SWD speed too high. Reduced from 2000 kHz to 1012 kHz for stability"

Could you try to call nrfjprog with the switch "-c 125" to see if this makes a difference? This will turn the SWD clock speed down from 2 MHz to 125 kHz.

Best regards,

Håkon

RE: nrfjprog - unable to connect to target

hotyp — Tue, 13 Nov 2018 08:35:42 GMT

Hi Hakon,

device is powered by power supply. Now i am using JLink Commander itself to flash firmware and also everything works fine, but nRF5x Command Line Tools does not work.

SEGGER J-Link Commander V6.34g (Compiled Sep 26 2018 14:45:38)
DLL version V6.34g, compiled Sep 26 2018 14:45:08

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-STM32F072-128KB-CortexM compiled Sep 27 2018 09:37:50
Hardware version: V1.00
S/N: 760010486
VTref=3.300V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: NRF52832_XXAA
Type '?' for selection dialog
Device><default>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  F) FINE
  I) ICSP
  C) C2
  T) cJTAG
TIF>SWD
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>4000
Device "NRF52832_XXAA" selected.


Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
SWD speed too high. Reduced from 2000 kHz to 1012 kHz for stability
Found SW-DP with ID 0x2BA01477
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.

RE: nrfjprog - unable to connect to target

Håkon Alseth — Tue, 13 Nov 2018 08:19:53 GMT

Hi,

Is your external board powered with 3.3V? If it is battery powered, it might be that the battery itself is depleted.

JLink ODB devices require a set voltage in order to program a device properly.

If you open up JLink Commander, it should report back the voltage of the target.

Kind regards,

Håkon