Cannot able to communicate with external target

RE: Cannot able to communicate with external target

Håkon Alseth — Fri, 10 Jan 2025 08:21:35 GMT

Hi,

This thread is quite old. Could you create a separate ticket on your issue?

And be sure to attach logs showing your problem.

Kind regards,

Håkon

RE: Cannot able to communicate with external target

abdosalm — Fri, 10 Jan 2025 03:21:33 GMT

I am kinda facing the same problem, what was the reason for your problem ?

RE: Cannot able to communicate with external target

Håkon Alseth — Wed, 02 Aug 2023 11:44:46 GMT

Hi,

Can you attach the .log file?

Do all your devices behave like this?

Given that the debugger provides generic errors, it can indicate a hardware-wise connection problem between the debugger and the nRF.

Kind regards,

Håkon

RE: Cannot able to communicate with external target

Kushagra12 — Wed, 02 Aug 2023 10:21:47 GMT

Hi,

after adjusting the SWD speed to 125 kHz and running the code nrfjprog --recover -f nrf52 -c 125 I got this

C:\Users\admin>nrfjprog --recover -f nrf52 -c 125
ERROR: Unable to connect to a debugger.
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.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

and after flashing the program

Current Speed: 125 kHz
InitTarget() start
InitTarget() end - Took 136ms
InitTarget() start
InitTarget() end - Took 136ms
Failed to connect to target.

and I am also attaching the log file. Please have a look

C:\Users\admin>nrfjprog --recover -f nrf52 -c 125 --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: [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: 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.

C:\Users\admin>

please suggest.

Kind regards

Kushagra

RE: Cannot able to communicate with external target

Håkon Alseth — Wed, 02 Aug 2023 08:29:14 GMT

Hi,

Could you try to adjust the SWD speed to for instance 125 kHz?

That is done in the project settings in SES:

And with nrfjprog, you can add the -c 125 switch:

nrfjprog --recover -f nrf52 -c 125

You can also flash via nrfjprog if you want:

nrfjprog --program <hex file> --verify -f nrf52 --sectorerase

Kind regards,

Håkon

RE: Cannot able to communicate with external target

Kushagra12 — Tue, 01 Aug 2023 18:20:09 GMT

hello sir,

I did run nrfjprog --recover -f nrf52 --log and got this

C:\Users\admin>nrfjprog --recover -f nrf52 --log
Recovering device. This operation might take 30s.
ERROR: [ JLink] - DAP error while reading AIRCR.
ERROR: [SeggerBackend] - JLinkARM.dll WriteU32 returned error -1.
ERROR: [SeggerBackend] - JLinkARM.dll WriteU32 returned error -1.
ERROR: [SeggerBackend] - JLinkARM.dll WriteU32 returned error -1.
Erasing user code and UICR flash areas.
ERROR: [SeggerBackend] - JLinkARM.dll ReadMemU32 detected a read error 1.
ERROR: [SeggerBackend] - This typically indicates the read was blocked by a memory protection mechanism.

then I run this code nrfjprog --eraseall -f nrf52 and got this

C:\Users\admin>nrfjprog --eraseall -f nrf52
Erasing user available code and UICR flash areas.
Applying system reset.

after that I again run that code nrfjprog --recover -f nrf52 and got this

C:\Users\admin>nrfjprog --recover -f nrf52
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.

after that I tried to (flash) the program in segger embedded and got this

Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘s132_nrf52_6.1.1_softdevice.hex’ to J-Link
Programming 2.7 KB of addresses 00000000 — 00000aff
Programming 144.3 KB of addresses 00001000 — 0002514f
Failed to preserve target RAM @ 0x20000000-0x2000FFFF.
Failed to prepare for programming.
Download failed

and lastly the log file give this

C:\Users\admin>nrfjprog --recover -f nrf52 --log
Recovering device. This operation might take 30s.
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
Erasing user code and UICR flash areas.
ERROR: [SeggerBackend] - JLinkARM.dll WriteU32 returned error -1.
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

please give your inputs what needs to be done. Thanks for giving your time.

kind regards,

Kushagra Agarwal

RE: Cannot able to communicate with external target

Håkon Alseth — Tue, 01 Aug 2023 10:50:55 GMT

Hi,

[quote user="Kushagra12"]
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 7.22/bin/JLink_x64.dll
Firmware Version: J-Link OB-nRF5340-NordicSemi compiled Nov 7 2022 16:22:01
DLL Version: 7.88m
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF52832_XXAA" selected.
Current Speed: 2000 kHz
InitTarget() start
InitTarget() end - Took 2.41ms
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
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
[0][0]: E000E000 CID 00000000 PID 00000000 ???
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM[/quote]

This is a good indication, as the debugger is able to read out the cpu core information.

[quote user="Kushagra12"]sorry for the delay when I am running the nrf--jprog in terminal.. I am getting this[/quote]

oh, it seems the family is not correct.

Could you try this?

nrfjprog --recover -f nrf52

If it does not work, please add the "--log" to the above nrfjprog command and attach the generated "log.log" file.

Kind regards,

Håkon

RE: Cannot able to communicate with external target

Kushagra12 — Fri, 28 Jul 2023 20:16:32 GMT

Hi, now after re-verifying the connections. I am getting this. Please have a look and what it can be done. Please help (last lines of codes)?

Connecting ‘J-Link’ using ‘USB’
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 7.22/bin/JLink_x64.dll
Firmware Version: J-Link OB-nRF5340-NordicSemi compiled Nov 7 2022 16:22:01
DLL Version: 7.88m
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF52832_XXAA" selected.
Current Speed: 2000 kHz
InitTarget() start
InitTarget() end - Took 2.41ms
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
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
[0][0]: E000E000 CID 00000000 PID 00000000 ???
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Failed to preserve target RAM @ 0x20000000-0x2000FFFF.
Failed to prepare for programming.

RE: Cannot able to communicate with external target

Kushagra12 — Fri, 28 Jul 2023 19:06:16 GMT

hi, sorry for the delay when I am running the nrf--jprog in terminal.. I am getting this

RE: Cannot able to communicate with external target

Kushagra12 — Fri, 28 Jul 2023 19:03:57 GMT

yes, it is a pre made module.

RE: Cannot able to communicate with external target

Håkon Alseth — Fri, 07 Jul 2023 09:07:54 GMT

Hi,

Thanks for clarifying.

Those should if you power it, and connect a debugger to the SWD pins.

Can you attach the log file generated after executing "nrfjprog --recover -f nrf53 --log"?

Kind regards,

Håkon

RE: Cannot able to communicate with external target

Kushagra12 — Fri, 07 Jul 2023 08:35:11 GMT

yes it is a pre made module

RE: Cannot able to communicate with external target

Håkon Alseth — Fri, 07 Jul 2023 08:03:22 GMT

Hi,

Your pin numbering does not match the reference layout.

As an example, DEC4 is pin 7 in your picture; but it should be pin 46.

Are you interfacing a pre-made module?

Kind regards,

Håkon

RE: Cannot able to communicate with external target

Kushagra12 — Thu, 06 Jul 2023 15:15:01 GMT

hi sir,

I have gone through the data sheet of the bare die. Using these capacitors, It should work? please have a look

RE: Cannot able to communicate with external target

Håkon Alseth — Wed, 05 Jul 2023 14:06:48 GMT

Hi,

You will need decoupling caps to communicate with the chip reliably over SWD. Here's the reference schematic:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/ref_circuitry.html?cp=5_2_0_52_0#schematic_qfn48_ldo

To run the radio, you'll also need a 32M xtal.

Kind regards,

Håkon

RE: Cannot able to communicate with external target

Kushagra12 — Wed, 05 Jul 2023 13:14:13 GMT

Thanks,

I will use 3V.

yes this is bare die, I thought as I am using DC power supply there is no need of using capacitors? as there is no power supply voltage function.

Thanks for the suggestion. I will add the capacitors and will check the result.

yes, nrfjprog is available in the command line tools. I will run it and will share the result.

Regards,

Kushagra

RE: Cannot able to communicate with external target

Håkon Alseth — Wed, 05 Jul 2023 12:33:51 GMT

Hi,

The power supply should match the DK voltage, ie. 3V.

[quote user="Kushagra12"]I used probe station to connect the necessary pins of the custom board. From the probe station crocodile pins are connected to the respective pins of the NRF board[/quote]

Just to confirm, this is a custom PCB, right? Your picture mentions "bare die" - the nRF requires decoupling caps etc. to operate properly.

[quote user="Kushagra12"]A3: Sir, can you please tell me how to recover the board using nrfjprog --recover? I am not aware of this.[/quote]

You can download nrfjprog from here: https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download

And run this in a terminal: "nrfjprog --recover"

Kind regards,

Håkon

RE: Cannot able to communicate with external target

Kushagra12 — Wed, 05 Jul 2023 12:20:20 GMT

hello Sir,

Thanks for your response.

A1: so I am following this connection, just used an external DC power source so the full connection is (image 2)

connections are good. I used probe station to connect the necessary pins of the custom board. From the probe station crocodile pins are connected to the respective pins of the NRF board

A2: No it never worked. This is the first time I am using this type of setup, though trying to connect it since past one month but was not able to connect.

A3: Sir, can you please tell me how to recover the board using nrfjprog --recover? I am not aware of this.

Please let me know if you need any further information.

Thanks and Regards,

Kushagra

RE: Cannot able to communicate with external target

Håkon Alseth — Wed, 05 Jul 2023 11:23:59 GMT

Hi,

Q1: How is the connection between the nRF52-DK and your custom board?

Q2: Has your current setup worked at some point? Or newer at all?

Q3: Could you try to recover the board using nrfjprog --recover?

Kind regards,

Håkon