Error while programming nrf52805 module

[Suraj S]

Hello everyone!

While programming nRF52805 module, I am encountering an error in memory reading stage. Logs from the application (both Failure and success cases) are attached below for reference.

Log generated in case of error:

***************THIS LOG IS GENERATED DURING ISSUE***************

2022-11-13T09:26:33.116Z DEBUG Application data folder: C:\Users\***\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2022-11-13T09:26:33.295Z DEBUG App pc-nrfconnect-programmer v3.0.4 official
2022-11-13T09:26:33.296Z DEBUG App path: C:\Users\***\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2022-11-13T09:26:33.296Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2022-11-13T09:26:33.296Z DEBUG nRFConnect path: C:\Users\***\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-11-13T09:26:33.296Z DEBUG HomeDir: C:\Users\***
2022-11-13T09:26:33.296Z DEBUG TmpDir: C:\Users\***\AppData\Local\Temp
2022-11-13T09:26:33.733Z INFO Using nrf-device-lib-js version: 0.4.13
2022-11-13T09:26:33.733Z INFO Using nrf-device-lib version: 0.12.8
2022-11-13T09:26:33.734Z INFO Using nrfjprog DLL version: 10.16.0
2022-11-13T09:26:33.734Z INFO Using JLink version: JLink_V7.66a
2022-11-13T09:26:33.734Z INFO Installed JLink version does not match the provided version (V7.66a)
2022-11-13T09:26:37.132Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-11-13T09:26:37.132Z INFO JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31
2022-11-13T09:26:37.133Z INFO Device family NRF52_FAMILY
2022-11-13T09:26:37.133Z INFO Device version NRF52805_xxAA_REV1
2022-11-13T09:26:37.133Z INFO Board version PCA10040
2022-11-13T09:26:37.134Z INFO Loading readback protection status for Application core
2022-11-13T09:26:38.135Z DEBUG Client Id: 190cb99e-3c75-456a-9700-d057cc92f5cc
2022-11-13T09:26:38.979Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-11-13T09:26:41.063Z INFO Parse memory regions for Application core
2022-11-13T09:26:41.071Z INFO Update files regions according to Application core
2022-11-13T09:26:41.072Z INFO Parse memory regions for file
2022-11-13T09:26:41.089Z INFO Device is loaded and ready for further operation
2022-11-13T09:26:41.094Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core
2022-11-13T09:26:42.891Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-11-13T09:26:45.455Z ERROR Failed to get device memory map: async task failure for id: 2363309243 msg: JLINKARM_DLL_ERROR (Origin: "Error when running fw program.")
2022-11-13T09:26:45.458Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31"}
2022-11-13T09:26:45.468Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF52_FAMILY"}
2022-11-13T09:26:45.475Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"NRF52805_xxAA_REV1"}
2022-11-13T09:26:45.481Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10040"}
2022-11-13T09:26:45.487Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"jlink"}
2022-11-13T09:26:45.492Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"architecture","label":"ia32"}
2022-11-13T09:26:45.498Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Report error","label":"win32; ia32; v3.0.4; Failed to get device memory map: async task failure for id: 2363309243 msg: JLINKARM_DLL_ERROR (Origin: \"Error when running fw program.\")"}
2022-11-13T09:26:45.509Z ERROR Error when reading device

Usually this kind of error doesn't occur while programming the module.

A successful programming iteration produces following log:

***************THIS LOG IS GENERATED IN A SUCCESSFUL ITERATION***************

2022-11-11T09:23:43.156Z DEBUG Application data folder: C:\Users\***\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2022-11-11T09:23:43.325Z DEBUG App pc-nrfconnect-programmer v3.0.4 official
2022-11-11T09:23:43.325Z DEBUG App path: C:\Users\***\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2022-11-11T09:23:43.325Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2022-11-11T09:23:43.325Z DEBUG nRFConnect path: C:\Users\***\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-11-11T09:23:43.326Z DEBUG HomeDir: C:\Users\***
2022-11-11T09:23:43.326Z DEBUG TmpDir: C:\Users\***\AppData\Local\Temp
2022-11-11T09:23:43.727Z INFO Using nrf-device-lib-js version: 0.4.13
2022-11-11T09:23:43.728Z INFO Using nrf-device-lib version: 0.12.8
2022-11-11T09:23:43.728Z INFO Using nrfjprog DLL version: 10.16.0
2022-11-11T09:23:43.728Z INFO Using JLink version: JLink_V7.66a
2022-11-11T09:23:43.728Z INFO Installed JLink version does not match the provided version (V7.66a)
2022-11-11T09:23:46.687Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-11-11T09:23:46.688Z INFO JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31
2022-11-11T09:23:46.688Z INFO Device family NRF52_FAMILY
2022-11-11T09:23:46.688Z INFO Device version NRF52805_xxAA_REV1
2022-11-11T09:23:46.688Z INFO Board version PCA10040
2022-11-11T09:23:46.688Z INFO Loading readback protection status for Application core
2022-11-11T09:23:48.176Z DEBUG Client Id: 190cb99e-3c75-456a-9700-d057cc92f5cc
2022-11-11T09:23:48.442Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-11-11T09:23:50.309Z INFO Parse memory regions for Application core
2022-11-11T09:23:50.316Z INFO Update files regions according to Application core
2022-11-11T09:23:50.316Z INFO Parse memory regions for file
2022-11-11T09:23:50.327Z INFO Device is loaded and ready for further operation
2022-11-11T09:23:50.332Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core
2022-11-11T09:23:50.830Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-11-11T09:23:56.478Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core completed
2022-11-11T09:23:56.481Z INFO Parse memory regions for Application core
2022-11-11T09:23:56.481Z INFO SoftDevice detected, id 0x125 (S113 v7.3.0)
2022-11-11T09:23:57.896Z INFO Resetting device completed
2022-11-11T09:23:59.282Z INFO Parsing HEX file:  G:\.shortcut-targets-by-id\1qVHXTxpD1Dfh0tWwLsNSdSFwx8f02T9J\BLE Binaries\ble_app_uart_pca10040e_nrf52805_s113.hex
2022-11-11T09:23:59.298Z INFO File was last modified at  9/2/2022, 3:50:51 PM
2022-11-11T09:23:59.320Z INFO Update files regions according to Application core
2022-11-11T09:23:59.320Z INFO Parse memory regions for file
2022-11-11T09:23:59.345Z INFO Parsing HEX file:  G:\.shortcut-targets-by-id\1qVHXTxpD1Dfh0tWwLsNSdSFwx8f02T9J\BLE Binaries\s113_nrf52_7.3.0_softdevice.hex
2022-11-11T09:23:59.346Z INFO File was last modified at  11/23/2021, 7:43:11 PM
2022-11-11T09:23:59.400Z INFO Update files regions according to Application core
2022-11-11T09:23:59.400Z INFO Parse memory regions for file
2022-11-11T09:23:59.400Z INFO SoftDevice detected, id 0x125 (S113 v7.3.0)
2022-11-11T09:24:02.782Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core
2022-11-11T09:24:07.914Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
2022-11-11T09:24:07.918Z INFO Device recovery completed
2022-11-11T09:24:07.919Z INFO Writing procedure starts for NRFDL_DEVICE_CORE_APPLICATION core
2022-11-11T09:24:07.992Z INFO Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core
2022-11-11T09:24:09.245Z INFO {"chip_erase_mode":"ERASE_ALL","qspi_erase_mode":"ERASE_NONE","reset":"RESET_NONE","verify":"VERIFY_NONE"} 100%
2022-11-11T09:24:09.245Z INFO Uploading image through JLink: 0%
2022-11-11T09:24:13.135Z INFO Uploading image through JLink: 100%
2022-11-11T09:24:13.332Z INFO Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core completed
2022-11-11T09:24:13.332Z INFO Writing procedure ends for NRFDL_DEVICE_CORE_APPLICATION core
2022-11-11T09:24:14.715Z INFO Resetting device completed
2022-11-11T09:24:14.719Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-11-11T09:24:14.719Z INFO JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31
2022-11-11T09:24:14.720Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31"}
2022-11-11T09:24:14.722Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF52_FAMILY"}
2022-11-11T09:24:14.724Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"NRF52805_xxAA_REV1"}
2022-11-11T09:24:14.726Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10040"}
2022-11-11T09:24:14.727Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"jlink"}
2022-11-11T09:24:14.729Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"architecture","label":"ia32"}
2022-11-11T09:24:14.731Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31"}
2022-11-11T09:24:14.732Z INFO Device family NRF52_FAMILY
2022-11-11T09:24:14.732Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF52_FAMILY"}
2022-11-11T09:24:14.733Z INFO Device version NRF52805_xxAA_REV1
2022-11-11T09:24:14.734Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"NRF52805_xxAA_REV1"}
2022-11-11T09:24:14.735Z INFO Board version PCA10040
2022-11-11T09:24:14.735Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10040"}
2022-11-11T09:24:14.736Z INFO Loading readback protection status for Application core
2022-11-11T09:24:16.216Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-11-11T09:24:17.588Z INFO Parse memory regions for Application core
2022-11-11T09:24:17.589Z INFO Update files regions according to Application core
2022-11-11T09:24:17.589Z INFO Parse memory regions for file
2022-11-11T09:24:17.590Z INFO SoftDevice detected, id 0x125 (S113 v7.3.0)
2022-11-11T09:24:17.599Z INFO Device is loaded and ready for further operation
2022-11-11T09:24:17.601Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core
2022-11-11T09:24:23.646Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core completed
2022-11-11T09:24:23.648Z INFO Parse memory regions for Application core
2022-11-11T09:24:23.648Z INFO SoftDevice detected, id 0x125 (S113 v7.3.0)
2022-11-11T09:24:25.050Z INFO Resetting device completed

My questions are:

1. What can be possible reasons for this issue?

2. How to resolve this issue? 

Thanks in advance for your kind help

Best Regards,

Suraj S.

[Maria Gilje]

Hello Suraj S.

1. The nRF52805 SoC has two revisions. Revision 2 of nRF52805-CAAA-Bxx has APPROTECT enabled by default.
   Are both the logs from programming a module which has the same revision of nRF52805? The ordering information on the infocenter may be helpful for you to identify the revisions.
2. You can read more about APPROTECT in this blogpost.It provides steps to disable APPROTECT.

Kind Regards,
Maria

[Suraj S]

Hello Maria,

Maria Gilje said:

Are both the logs from programming a module which has the same revision of nRF52805?

Yes, both logs are from same revision of nRF52805. In both the logs attached in the original question, device version is shown to be NRF52805_xxAA_REV1 (exact part code is NRF52805_CAAA-R). I'm not completely sure if this revision has APProtect enabled by default.

Maria Gilje said:

You can read more about APPROTECT in this blogpost.It provides steps to disable APPROTECT.

I'll check the blogpost and try the steps mentioned in it.

Thanks and regards,

Suraj S.

[Maria Gilje]

Hello,

Suraj S said:

Yes, both logs are from same revision of nRF52805. In both the logs attached in the original question, device version is shown to be NRF52805_xxAA_REV1 (exact part code is NRF52805_CAAA-R). I'm not completely sure if this revision has APProtect enabled by default.

Sorry, I missed the logging of the revision number. On revision 1 APPROTECT is not enabled by default.

Q1: Are you able to program the module with west or nrfjprog?

Kind Regards,
Maria