connect failed. Failed to connect to target. No idcode detected.

RE: connect failed. Failed to connect to target. No idcode detected.

Dano — Mon, 01 May 2023 01:30:22 GMT

Did you ever resolve this issue?

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Mon, 08 Jul 2019 12:07:19 GMT

You need to install the nRF-Command-Line-Tools, and either add the directory to your PATH, or run the command from a command line inside the directory.

The DK should be connected to the chip that you want to recover. If this is on the custom PCB, you will have to connect it to this.

RE: connect failed. Failed to connect to target. No idcode detected.

noob_with_ucontrollers — Mon, 08 Jul 2019 03:35:52 GMT

Jørgen Jorgen,

Hi, I am facing a similar issue. I want to run a 'nrfjprog --recover' command but do not know how to do that. How do I do that on my DK?

Can my DK be connected to the custom PCB I am trying to flash while I run nrfjprog --recover?
Thanks a lot!

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Thu, 21 Feb 2019 10:12:14 GMT

I think this is a faulty chip/board. If you send me your address and phone number, I will request a replacement for you. If you want us to check the board further, you will have to ship it to us.

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Mon, 18 Feb 2019 14:05:25 GMT

I had used PEMicro Cyclone ACP FX programmer.

Attached the setup.

SWD programming

Default mode & nRF Only mode
External supply & Debugger power supply

There is always error "cannot enter debug mode."

I had tried supplying 3V , / 5V from the debugger as well.

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Thu, 07 Feb 2019 15:11:24 GMT

Do you have a standalone flasher/debugger that support level shifting (for instance a J-Link model), that you could try? It could be an issue with wrong voltage. Error code -102 mean "not found".

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Fri, 25 Jan 2019 12:06:30 GMT

I had tried mentioned the thread.

But, back to question..

1. nRF52 IC is working. Even driver can recognize that 3V is supplied to the IC.

I also confirmed RESET line is working (pulled down for a moment when I do ERASE command / PROGRAM command)

nRFXX_connect_to_emu_without_snr:	JLink:	 Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
nRFXX_connect_to_emu_without_snr:	JLink:	 Hardware: V1.00
nRFXX_connect_to_emu_without_snr:	JLink:	 S/N: 683904660

Connecting ...
 - Connecting via USB to J-Link device 0
 - J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
 - Device "NRF52840_XXAA" selected.
 - Target interface speed: 200 kHz (Auto)
 - VTarget = 3.300V
 - ERROR: Failed to connect.
Could not establish a connection to target.
J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
Erasing chip ...
 - Connecting ...
    - Device "NRF52840_XXAA" selected.
    - Target interface speed: 200 kHz (Auto)
    - VTarget = 3.300V
    - ERROR: Failed to connect.
Could not establish a connection to target.
 - ERROR: Could not erase chip, not connected

nRFXX_connect_to_emu_without_snr:	JLink:	Device "CORTEX-M4" selected.
nRFXX_connect_to_emu_without_snr:	JLink:	Device "CORTEX-M4" selected.
nRFXX_connect_to_emu_without_snr:	JLink:	  returns 0x00

And then,

nRFXX_connect_to_emu_without_snr:	JLink:	JLINK_ExecCommand("SetRestartOnClose = 0", ...). 
nRFXX_connect_to_emu_without_snr:	JLink:	  returns 0x01

Is this correct??

Also,

nRFXX_connect_to_emu_without_snr:	JLink:	JLINK_ExecCommand("SetDbgPowerDownOnClose = 1", ...). 
nRFXX_connect_to_emu_without_snr:	JLink:	  returns 0x01
...
...
...
nRFXX_is_connected_to_emu:	JLink:	JLINK_IsOpen()
nRFXX_is_connected_to_emu:	JLink:	  returns 0x01

But this one, definitely a fail.

nRFXX_write_debug_port_register:	JLink:	JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
nRFXX_write_debug_port_register:	JLink:	  returns -1
nRFXX_write_debug_port_register:	JLink:	 (0004ms, 0249ms total)  
nRFXX_write_debug_port_register:	JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

nRFXX_power_debug_and_system_regions:	JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

Would you please be able to dig it deeper ?

Even if the IC is bricked / or became READ-ONLY sectors in the flash, debugger / programmers should be a way to recover it during development phase.

What do you say !?

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Mon, 21 Jan 2019 11:26:08 GMT

Calling nrfjprog with the --recover option should normally solve this kind of issue. You can try the suggestion by Håkon in this thread.

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Mon, 21 Jan 2019 10:05:32 GMT

PCA10056

1.0.0

2018.46

1. Even if broken, is there not a debugger or any way to flash the IC nRF52840?

Because IC is still working.

I suppose, I have bricked it or is in non-writable state, something like mass production programming.

2. Via BLE, possible to update firmware?

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Mon, 21 Jan 2019 09:50:02 GMT

It sounds like this board could be broken. Which version of the PCA10056 is this?

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Fri, 18 Jan 2019 14:59:07 GMT

I tried connecting the Debug Out from working DK board to the Debug In - failing DK.

Working board - DEFAULT switch.

Failing board - nRF Only switch, and external powered. (Confirmed the nRF52 is powered)

Now, still it fails to program from SES with the same error.

Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 4.12/bin/JLink_x64.dll
Firmware Version: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
DLL Version: 6.40`
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF52840_XXAA" selected.
connect failed
Failed to connect to target.
No idcode detected.
Please check connection and Target Interface Type

With this setup, I tried nRF Connect PC application -> Bluetooth Low Energy.

It is not able to connect. Error

2019-01-18T15:06:08.557Z INFO Application data folder: C:\Users\pkrishna\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2019-01-18T15:06:08.658Z DEBUG App pc-nrfconnect-ble v2.2.0 official
2019-01-18T15:06:08.658Z DEBUG App path: C:\Users\pkrishna\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2019-01-18T15:06:08.658Z DEBUG nRFConnect 2.6.1 is supported by the app (^2.4.0)
2019-01-18T15:06:08.658Z DEBUG nRFConnect path: C:\Users\pkrishna\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-01-18T15:06:08.658Z DEBUG HomeDir: C:\Users\pkrishna
2019-01-18T15:06:08.658Z DEBUG TmpDir: C:\Users\pkrishna\AppData\Local\Temp
2019-01-18T15:06:08.666Z VERBOSE Could not fetch serial number for serial port at COM1
2019-01-18T15:07:07.537Z INFO Validating connectivity firmware for device with serial number 000683256424...
2019-01-18T15:07:09.089Z ERROR Error while setting up device 000683256424: Error occured when close opened device. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

2019-01-18T15:07:09.092Z INFO Device closed.

Same error when using nRF Connect PC application -> Power Profiler.

In case of nRF Connect PC application -> Programmer, it hangs at trying to detect Device Memory Layout.

2019-01-18T15:13:05.275Z INFO Parsing HEX file:  C:\Nordic\SDK1520\examples\nfc\wake_on_nfc\hex\wake_on_nfc_pca10056.hex
2019-01-18T15:13:05.275Z INFO File was last modified at  9/8/2018, 7:46:16 AM
2019-01-18T15:13:05.286Z INFO Data block: 0x00000000-0x00003A44 (0x00003A44  bytes long)
2019-01-18T15:13:14.893Z INFO Using nrfjprog to communicate with target

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Tue, 15 Jan 2019 12:43:00 GMT

[quote user="Pra_Engr"]I will try this later.[/quote]

Ok, let me know if you make it work.

[quote user="Pra_Engr"]But, may I know, is there any way to use "nRF USB" port for flashing nRF52 ??[/quote]

We have a serial DFU solution that works over the nRF USB port, but this requires you to first flash the serial USB DFU bootloader to the chip.

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Tue, 15 Jan 2019 11:36:59 GMT

>>> connecting a cable from "Debug out" on a working DK to "Debug in" on the failing DK

I will try this later.

But, may I know, is there any way to use "nRF USB" port for flashing nRF52 ??

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Mon, 14 Jan 2019 15:48:36 GMT

I cannot see any obvious issues on your images. Have you tried flashing the DK by connecting a cable from "Debug out" on a working DK to "Debug in" on the failing DK to see if you are able to flash it that way?

When you place the PPK on top of the DK, you are actually flashing the nRF52832 IC on the PPK (when the COM switch is in DK position). This seems to indicate that the J-Link debug chip is working as expected, and that there is some issue with the nRF chip on the DK.

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Mon, 14 Jan 2019 11:50:02 GMT

Additional:

With the same settings I connected the Power Profiler Board (PPK) - PCA63511

In PPK,switches:

DUT Select => DK

Power Select => DK

Attached the picture of setup.

Now, there was no error during "Build & Run" from SES.

I could flash the software ! It says Successful.

I tried Segger JFlash Lite v6.40 => Erase Chip. It is successful.

But it runs the same old software. It did not flash the latest changes. When tested the board, in fact it neither erased, nor flashed the software. !

And removing the PPK, still the same error from SES. !

What could be the reason?

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Mon, 14 Jan 2019 10:57:37 GMT

Please find the attached the picture.

Other side of the board has no change. Only the Coin cell is removed.

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Mon, 14 Jan 2019 10:03:39 GMT

Can you upload a high resolution image of the failing DK?

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Fri, 11 Jan 2019 17:09:26 GMT

Now, it is consistent that:

whenever I am placing any hex in the JLink drive in Windows, there is FAIL log which says Error while connecting to CPU

What is spoiled ?? :(

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Fri, 11 Jan 2019 16:47:15 GMT

Successfully loaded the firmware from the link, and then when using SES debugger for build and run, a popup asked me to update the firmware.

Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 4.12/bin/JLink_x64.dll
Firmware Version: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
DLL Version: 6.40`
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF52840_XXAA" selected.
connect failed
Failed to connect to target.
No idcode detected.
Please check connection and Target Interface Type

Since was doubtful, tried the 2017-07-24 (***170724.bin) version from the link you have given.
This did not help.

And then, using "Segger JLink Configuration", Updated the firmware to the latest.

SEGGER J-Link Configuration V6.40
Logging started @ 2019-01-11 16:22

Updating firmware of 1 emulator:
Updating firmware of emulator 1 of 1 via USB (SN: 683904660)...  Updated successfully, emulator firmware was older than host firmware.
Finished updating 1 emulator!

Now firmware is 2018-07-12. 11:44:41

Still the issue persists.

I have not tested on a different PC, but in the same PC, another board. That board works fine.

I have tested with another USB cable, including other USB ports of the PC (including higher current supply ones).

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Fri, 11 Jan 2019 16:02:13 GMT

Are you seeing the JLINK removable drive on your computer? Have you tried reflashing the J-Link OB firmware to the board by holding IF BOOT/RESET while powering the board and drop the J-Link OB IF MCU firmware from this page to the removable drive BOOTLOADER?

Have you tested on a different PC, or with another USB cable?

RE: connect failed. Failed to connect to target. No idcode detected.

Pra_Engr — Fri, 11 Jan 2019 14:04:06 GMT

Thanks for your support !

Yes, switch was always in Default. So is detected in Windows as JLink drive.

With 'nrfjprog --recover' command, it becomes similar log as above, 'nrfjprog -e'.. with errors,: JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1. JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

Additionally,

1. When I connected the power profiler board PCA63511, with the existing software running in it, I am able to capture nRF Connect PC application => Power Profiler.

2. Now, I have cut SB40. (which is for power profiling). Connected by USB, all the 4 LED's turn on. When I close the SB40 with jumper in P22, LED's go off. (I am not much of hardware person. Sorry).

RE: connect failed. Failed to connect to target. No idcode detected.

Jørgen Holmefjord — Fri, 11 Jan 2019 12:30:52 GMT

Hi,

You will need to have the switch in DEFAUT position for the Segger J-Link chip to be active. Have you tried recovering the board using 'nrfjprog --recover' command?

Best regards,
Jørgen