NRF52840 DK programming problem

[boris bergman1]

I try to upload my hex file with the programmer to a dk board - serial 683782426 - with programmer v3.0.4, but get the following:

10:06:05.783	Recovering NRFDL_DEVICE_CORE_APPLICATION core
10:06:09.100	Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
10:06:09.102	Device recovery completed
10:06:09.102	Writing procedure starts for NRFDL_DEVICE_CORE_APPLICATION core
10:06:09.171	Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core
10:06:09.550	{"chip_erase_mode":"ERASE_ALL","qspi_erase_mode":"ERASE_NONE","reset":"RESET_NONE","verify":"VERIFY_NONE"} 100%
10:06:09.550	Uploading image through JLink: 0%
10:06:09.996	Device programming failed with error: async task failure for id: 1675933569173757 msg: JLINKARM_DLL_ERROR (Origin: "Error when running fw program.")
10:06:09.997	Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core completed
10:06:09.998	Writing procedure ends for NRFDL_DEVICE_CORE_APPLICATION core
10:06:10.559	Resetting device completed
10:06:10.561	Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
10:06:10.561	JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Nov 7 2022 16:21:57
10:06:10.562	Device family NRF52_FAMILY
10:06:10.563	Device version NRF52840_xxAA_REV2
10:06:10.564	Board version PCA10056
10:06:10.565	Loading readback protection status for Application core
10:06:11.061	Readback protection status: NRFDL_PROTECTION_STATUS_NONE
10:06:11.570	Parse memory regions for Application core
10:06:11.571	Update files regions according to Application core
10:06:11.571	Parse memory regions for file
10:06:11.573	Device is loaded and ready for further operation

I've another development board, serial 1050279558, and that one works just fine:

10:17:33.908	Recovering NRFDL_DEVICE_CORE_APPLICATION core
10:17:37.232	Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
10:17:37.234	Device recovery completed
10:17:37.234	Writing procedure starts for NRFDL_DEVICE_CORE_APPLICATION core
10:17:37.295	Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core
10:17:37.686	{"chip_erase_mode":"ERASE_ALL","qspi_erase_mode":"ERASE_NONE","reset":"RESET_NONE","verify":"VERIFY_NONE"} 100%
10:17:37.686	Uploading image through JLink: 0%
10:17:39.791	Uploading image through JLink: 100%
10:17:39.928	Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core completed
10:17:39.928	Writing procedure ends for NRFDL_DEVICE_CORE_APPLICATION core
10:17:40.499	Resetting device completed
10:17:40.500	Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
10:17:40.500	JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Nov 7 2022 16:22:01
10:17:40.501	Device family NRF52_FAMILY
10:17:40.502	Device version NRF52840_xxAA_REV3
10:17:40.502	Board version PCA10056
10:17:40.503	Loading readback protection status for Application core
10:17:41.023	Readback protection status: NRFDL_PROTECTION_STATUS_NONE
10:17:41.544	Parse memory regions for Application core
10:17:41.546	Update files regions according to Application core
10:17:41.546	Parse memory regions for file
10:17:41.548	Device is loaded and ready for further operation

Curious how to get the first board to work.

JLinkarm 7.84f, segger version: 7 nov 2022, both boards.

Ubuntu 22.04

[Simonr]

Okay, seems like the programmer isn't able to find any SEGGER firmware/instance on this DK. Please check out the DK troubleshooting guide here, and specifically step 4 to set the device into bootloader mode and drop the interface MCU firmware (available for download as a .bin file here) into the bootloader folder that opens. That should revert the Software on the debugger if anything has gone awry on that front at least. You can also go through the other steps in the guide as well.

Best regards,

Simon

[boris bergman1]

Sorry, I didn't notice the logfile didn't clear after clearing the log, but at line 1298, you can see the firmware is already in - and the connection to the segger chip is established.

11:16:43.308	Recovering NRFDL_DEVICE_CORE_APPLICATION core
11:16:43.310	[nrfdl][info](11:16:43.308) Loaded plugin /tmp/.mount_nrfconTAmdva/resources/app.asar.unpacked/node_modules/@nordicsemiconductor/nrf-device-lib-js/Release/nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
11:16:44.847	Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
11:16:44.848	Device recovery completed
11:16:44.848	Writing procedure starts for NRFDL_DEVICE_CORE_APPLICATION core
11:16:44.910	Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core
11:16:44.913	[nrfdl][info](11:16:44.846) close plugin dll at path: /tmp/.mount_nrfconTAmdva/resources/app.asar.unpacked/node_modules/@nordicsemiconductor/nrf-device-lib-js/Release/nrfdl-jlink-plugin.nrfdl
11:16:44.932	[nrfdl][info](11:16:44.932) Loaded plugin /tmp/.mount_nrfconTAmdva/resources/app.asar.unpacked/node_modules/@nordicsemiconductor/nrf-device-lib-js/Release/nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
11:16:45.513	{"chip_erase_mode":"ERASE_ALL","qspi_erase_mode":"ERASE_NONE","reset":"RESET_NONE","verify":"VERIFY_NONE"} 100%
11:16:45.513	Uploading image through JLink: 0%
11:16:45.782	[nrfdl][error](11:16:45.782) [jlink] [NRFJPROG][SeggerBackend][] JLinkARM.dll reported "-1", "An unknown error.".
11:16:45.792	[nrfdl][error](11:16:45.792) [jlink] [NRFJPROG][SeggerBackend][] JLinkARM.dll reported "-1", "An unknown error.".
11:16:45.802	[nrfdl][error](11:16:45.802) [jlink] [NRFJPROG][SeggerBackend][] JLinkARM.dll reported "-1", "An unknown error.".
11:16:45.802	[nrfdl][error](11:16:45.802) [jlink] [NRFJPROG][SeggerBackend][] JLinkARM.dll reported "-1", "An unknown error.".
11:16:45.813	[nrfdl][error](11:16:45.812) [jlink] [NRFJPROG][SeggerBackend][] JLinkARM.dll reported "-1", "An unknown error.".
11:16:45.815	[nrfdl][error](11:16:45.812) [jlink] [NRFJPROG][nRF52][] The write access failed, but no cause could be determined.
11:16:45.815	[nrfdl][error](11:16:45.813) [jlink] [NRFJPROG][nRF52][] It may be due to an unaligned access, accessing a nonexistent memory, or a communication issue.
11:16:45.815	[nrfdl][error](11:16:45.813) [jlink] [NRFJPROG][nRF52][] Failed writing to code!
11:16:45.815	[nrfdl][error](11:16:45.813) [jlink] [NRFJPROG][nRF52][] Failed to program flash
11:16:45.815	[nrfdl][error](11:16:45.813) [jlink] [NRFJPROG][nRF52][] Failed while programming file /tmp/temp_program_fw16764562052975850261.hex.
11:16:45.865	[nrfdl][info](11:16:45.865) close plugin dll at path: /tmp/.mount_nrfconTAmdva/resources/app.asar.unpacked/node_modules/@nordicsemiconductor/nrf-device-lib-js/Release/nrfdl-jlink-plugin.nrfdl
11:16:45.865	Device programming failed with error: async task failure for id: 1676456204932647 msg: [jlink] JLINKARM_DLL_ERROR (Origin: "Error when running fw program.")
11:16:45.865	Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core completed
11:16:45.866	Writing procedure ends for NRFDL_DEVICE_CORE_APPLICATION core
11:16:45.868	[nrfdl][info](11:16:45.868) Loaded plugin /tmp/.mount_nrfconTAmdva/resources/app.asar.unpacked/node_modules/@nordicsemiconductor/nrf-device-lib-js/Release/nrfdl-jlink-plugin.nrfdl, starting to resolve symbols
11:16:46.338	Resetting device completed
11:16:46.339	Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
11:16:46.339	JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Nov 7 2022 16:21:57
11:16:46.340	Device family NRF52_FAMILY
11:16:46.341	Device version NRF52840_xxAA_REV2
11:16:46.341	Board version PCA10056

$ JLinkExe 
SEGGER J-Link Commander V7.84f (Compiled Feb  7 2023 16:51:58)
DLL version V7.84f, compiled Feb  7 2023 16:51:27

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Nov  7 2022 16:21:57
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 07m 56s
S/N: 683782426
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
USB speed mode: High speed (480 MBit/s)
VTref=3.300V


Type "connect" to establish a target connection, '?' for help
J-Link>

As the other board just works fine, I suspect it's a faulty board. Altough it has been working before.

Regards.

[Simonr]

Please check out the DK troubleshooting guide here, and specifically step 4 to set the device into bootloader mode and drop the interface MCU firmware (available for download as a .bin file here) into the bootloader folder that opens to make sure that the Interface MCU firmware isn't the issue.

Best regards,

Simon

[boris bergman1]

I already did so yesterday.

[Simonr]

Okay, I didn't get your confirmation on doing so, so I wasn't sure. I have forwarded the log files to the nRF Connect for Desktop team internally so they can review them, and I'll let you know if they have any further ideas on what to try to recover/fix this issue, but it looks very much like the DK has been damaged somehow. You can contact your distributor with details on what to do in order to get a replacement board.

Best regards,

Simon