Critical Issue: nRF52-DK, PCA10040 3.0.0 2022.14. Programmer v3.0.3 can not erase and Keil can not identify board and J-LINK Interface.

[LishenTung]

Dear Nordic support team,

I bought 3 piece of nRF52-DK from MOUSER, 1 piece of nRF52-DK version is 2.1.0 , and another 2 piece version is 3.0.0. 

nRF52-DK version 2.1.0, Programmer and Keil test ok.

nRF52 DK, PCA10040 3.0.0 2022.14. Programmer v3.0.3 can not erase and identify board, why?

Keil5 MDK v5.25.2.0, Debug -> Cannot find any J-LINK ??

Thanks,

Lishen

[Simonr]

Hi

Okay, thank you for sharing. From the log, the procedures all seem to finish correctly as there are no errors, and you can see that app protect is enabled as you can see here:

2022-07-18T07:01:28.896Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_ALL
2022-07-18T07:01:28.900Z INFO Parse memory regions for Application core
2022-07-18T07:01:28.902Z INFO Update files regions according to Application core
2022-07-18T07:01:28.902Z INFO Parse memory regions for file
2022-07-18T07:01:28.907Z INFO Device is loaded and ready for further operation
2022-07-18T07:01:28.908Z INFO Skipped reading, since at least one core has app readback protection

You can see that the firmware is written successfully here:

2022-07-18T07:01:51.777Z INFO SoftDevice detected, id 0xAF (S132 v6.1.0)
2022-07-18T07:01:55.305Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core
2022-07-18T07:01:58.909Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
2022-07-18T07:01:58.914Z INFO Device recovery completed
2022-07-18T07:01:58.914Z INFO Writing procedure starts for NRFDL_DEVICE_CORE_APPLICATION core
2022-07-18T07:01:58.979Z INFO Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core
2022-07-18T07:01:59.467Z INFO Uploading image through JLink: 0%
2022-07-18T07:02:02.443Z INFO Uploading image through JLink: 100%
2022-07-18T07:02:02.583Z INFO Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core completed

Next, the reason this is "UNKNOWN" I think is because the Programmer app hasn't been updated to recognize rev. 3.0.0 of the nRF52 DKs. I will contact the developers to confirm this and get back to you with an update.

Best regards,

Simon

[LishenTung]

Dear Simonr,

Q1. Something is serious error, follow the steps I said,

step1.Open Programmer v3.0.0.

step2.switch ON nRF52-DK(PCA10040, v3.0.0)

step3.Select Device "nRF52 DK" in Programmer.

step4.Choose "Erase all".

step5.You will find that Erase ok and No message "Device is protected".

step6.switch OFF nRF52-DK(PCA10040, v3.0.0), wait 10 seconds.

step7.switch ON nRF52-DK(PCA10040, v3.0.0).

step8.Select Device "nRF52 DK" in Programmer.

step9.See "Device is protected" again, why?  PCA10040 v2.1.0 no error message here.

Provide log message:

2022-07-19T08:09:01.274Z DEBUG Application data folder: C:\Users\USER\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2022-07-19T08:09:01.332Z INFO Using nrf-device-lib-js version: 0.4.11
2022-07-19T08:09:01.332Z INFO Using nrf-device-lib version: 0.11.8
2022-07-19T08:09:01.332Z INFO Using nrfjprog DLL version: 10.15.4
2022-07-19T08:09:01.332Z INFO Using JLink version: JLink_V7.58b
2022-07-19T08:09:01.363Z DEBUG App pc-nrfconnect-programmer v3.0.3 official
2022-07-19T08:09:01.364Z DEBUG App path: C:\Users\USER\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2022-07-19T08:09:01.364Z DEBUG nRFConnect 3.11.1, required by the app is (^3.11.1)
2022-07-19T08:09:01.364Z DEBUG nRFConnect path: C:\Users\USER\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-07-19T08:09:01.364Z DEBUG HomeDir: C:\Users\USER
2022-07-19T08:09:01.364Z DEBUG TmpDir: C:\Users\USER\AppData\Local\Temp
2022-07-19T08:09:09.414Z DEBUG iface: Wi-Fi
2022-07-19T08:09:09.414Z DEBUG IP4: 172.17.21.181
2022-07-19T08:09:09.414Z DEBUG IP6: fe80::131:f969:f6d6:c2ad
2022-07-19T08:09:09.414Z DEBUG MAC: cc:6b:1e:66:b0:53
2022-07-19T08:09:09.415Z DEBUG Client Id: 413cfbe931258f8b0bbd12108a4145c3515cb9cb
2022-07-19T08:09:10.482Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-07-19T08:09:51.950Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-07-19T08:09:51.951Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25
2022-07-19T08:09:51.951Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"architecture","label":"ia32"}
2022-07-19T08:09:51.954Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25"}
2022-07-19T08:09:51.955Z INFO Device family NRF52
2022-07-19T08:09:51.955Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF52"}
2022-07-19T08:09:51.956Z INFO Device version UNKNOWN
2022-07-19T08:09:51.956Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"UNKNOWN"}
2022-07-19T08:09:51.957Z INFO Board version PCA10040
2022-07-19T08:09:51.957Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10040"}
2022-07-19T08:09:51.958Z INFO Loading readback protection status for Application core
2022-07-19T08:09:51.959Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"jlink"}
2022-07-19T08:09:52.506Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_ALL
2022-07-19T08:09:52.512Z INFO Parse memory regions for Application core
2022-07-19T08:09:52.515Z INFO Update files regions according to Application core
2022-07-19T08:09:52.516Z INFO Parse memory regions for file
2022-07-19T08:09:52.521Z INFO Device is loaded and ready for further operation
2022-07-19T08:09:52.523Z INFO Skipped reading, since at least one core has app readback protection
2022-07-19T08:09:52.526Z INFO Resetting device
2022-07-19T08:11:09.925Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core
2022-07-19T08:11:13.552Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
2022-07-19T08:11:13.554Z INFO Device recovery completed
2022-07-19T08:11:13.557Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-07-19T08:11:13.557Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25
2022-07-19T08:11:13.557Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25"}
2022-07-19T08:11:13.558Z INFO Device family NRF52
2022-07-19T08:11:13.558Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF52"}
2022-07-19T08:11:13.559Z INFO Device version UNKNOWN
2022-07-19T08:11:13.560Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"UNKNOWN"}
2022-07-19T08:11:13.560Z INFO Board version PCA10040
2022-07-19T08:11:13.561Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10040"}
2022-07-19T08:11:13.561Z INFO Loading readback protection status for Application core
2022-07-19T08:11:14.205Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-07-19T08:11:14.846Z INFO Parse memory regions for Application core
2022-07-19T08:11:14.847Z INFO Update files regions according to Application core
2022-07-19T08:11:14.847Z INFO Parse memory regions for file
2022-07-19T08:11:14.851Z INFO Device is loaded and ready for further operation
2022-07-19T08:11:14.852Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core
2022-07-19T08:11:19.696Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core completed
2022-07-19T08:11:19.698Z INFO Parse memory regions for Application core
2022-07-19T08:11:19.701Z INFO Resetting device
2022-07-19T08:11:20.426Z INFO Resetting device completed
2022-07-19T08:12:53.021Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Close device","label":""}
2022-07-19T08:12:53.022Z INFO Target device closed
2022-07-19T08:12:59.453Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-07-19T08:12:59.453Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25
2022-07-19T08:12:59.453Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25"}
2022-07-19T08:12:59.455Z INFO Device family NRF52
2022-07-19T08:12:59.455Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF52"}
2022-07-19T08:12:59.456Z INFO Device version UNKNOWN
2022-07-19T08:12:59.457Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"UNKNOWN"}
2022-07-19T08:12:59.457Z INFO Board version PCA10040
2022-07-19T08:12:59.458Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10040"}
2022-07-19T08:12:59.458Z INFO Loading readback protection status for Application core
2022-07-19T08:12:59.458Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"jlink"}
2022-07-19T08:13:00.137Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-07-19T08:13:00.789Z INFO Parse memory regions for Application core
2022-07-19T08:13:00.790Z INFO Update files regions according to Application core
2022-07-19T08:13:00.791Z INFO Parse memory regions for file
2022-07-19T08:13:00.794Z INFO Device is loaded and ready for further operation
2022-07-19T08:13:00.795Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core
2022-07-19T08:13:05.642Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core completed
2022-07-19T08:13:05.643Z INFO Parse memory regions for Application core
2022-07-19T08:13:05.647Z INFO Resetting device
2022-07-19T08:13:06.355Z INFO Resetting device completed
2022-07-19T08:13:11.283Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Close device","label":""}
2022-07-19T08:13:11.287Z INFO Target device closed
2022-07-19T08:14:02.442Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-07-19T08:14:02.442Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25
2022-07-19T08:14:02.443Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-nRF5340-NordicSemi compiled Jul 2 2021 10:55:25"}
2022-07-19T08:14:02.444Z INFO Device family NRF52
2022-07-19T08:14:02.444Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF52"}
2022-07-19T08:14:02.445Z INFO Device version UNKNOWN
2022-07-19T08:14:02.445Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"UNKNOWN"}
2022-07-19T08:14:02.447Z INFO Board version PCA10040
2022-07-19T08:14:02.447Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10040"}
2022-07-19T08:14:02.448Z INFO Loading readback protection status for Application core
2022-07-19T08:14:02.448Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"jlink"}
2022-07-19T08:14:02.981Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_ALL
2022-07-19T08:14:02.986Z INFO Parse memory regions for Application core
2022-07-19T08:14:02.988Z INFO Update files regions according to Application core
2022-07-19T08:14:02.988Z INFO Parse memory regions for file
2022-07-19T08:14:02.992Z INFO Device is loaded and ready for further operation
2022-07-19T08:14:02.993Z INFO Skipped reading, since at least one core has app readback protection
2022-07-19T08:14:02.995Z INFO Resetting device

Q2. Keil MDK v5.25.2.0 can not identify J-LINK on nRF52-DK(PCA10040, v3.0.0), this is very critical issue. Because I can not load any example code from SDK 15.2.0.

Thanks,

Lishen

[LishenTung]

Hi Simonr,

Another question, Use "Erase and Write" Softdevice hex file to PCA10040 v3.0.0, and Programmer auto Protect device??

Why PCA10040 v2.1.0, Use "Erase and Write", and Programmer "No" Protect device ?

Very Strange!!! Very Strange!!! Very Strange!!!

Thanks,

Lishen

[LishenTung]

Good news,

I download J-link new software manually from SEGGER website, and Keil 5 identify J-LINK OB now.

So I found that Programmer v3.0.3 will always lock nRF52832.  But nRFgo Studio lock or unlock selection by User define.

Thanks,

Lishen