Hi,
I have nRF5340 nordic devlopment kit for devlopment.
I have programmed Heart Beat Monitoring Program using nRF Connect for Desktop Programmer (Windows 10).
Similarly i programed BL5340 based module using nRF DK using given Port P20.
Connection -
DK BL5340 Module
1.VTG - 3.1V
2.SWD IO - SWDIO
3.SWD CLK - SWDCLK
4.RESET - RESET
5.GND DETECT - GND
Now when again i tried to programme in similar way. IT SHOWS DEVICE PROTECTED. Press ERASE ALL to Remove from protection.
After ERASE ALL. It shows DEVICE CONNECTED. Upon Programming hex files. It again gives error NOT_AVAILABLE_BECAUSE_PROTECTION.
I am not understanding why does it gives error even though i haven't enabled any kind of code protection.
Please help how do i recover it.
Attached in log of nRF connect for desktop programmer.
2022-07-12T11:30:00.664Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-07-12T11:30:00.665Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49
2022-07-12T11:30:00.666Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49"}
2022-07-12T11:30:00.669Z INFO Device family NRF53
2022-07-12T11:30:00.670Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF53"}
2022-07-12T11:30:00.672Z INFO Device version NRF5340_xxAA_ENGD
2022-07-12T11:30:00.673Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"NRF5340_xxAA_ENGD"}
2022-07-12T11:30:00.676Z INFO Board version PCA10095
2022-07-12T11:30:00.677Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10095"}
2022-07-12T11:30:00.679Z INFO Loading readback protection status for Application core
2022-07-12T11:30:00.680Z INFO Loading readback protection status for Network core
2022-07-12T11:30:00.681Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open device","label":"jlink"}
2022-07-12T11:30:01.749Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_ALL
2022-07-12T11:30:02.091Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_ALL
2022-07-12T11:30:02.103Z INFO Parse memory regions for Application core
2022-07-12T11:30:02.103Z INFO Parse memory regions for Network core
2022-07-12T11:30:02.109Z INFO Update files regions according to Application core
2022-07-12T11:30:02.109Z INFO Parse memory regions for file
2022-07-12T11:30:02.110Z INFO Update files regions according to Network core
2022-07-12T11:30:02.110Z INFO Parse memory regions for file
2022-07-12T11:30:02.123Z INFO Device is loaded and ready for further operation
2022-07-12T11:30:02.130Z INFO Skipped reading, since at least one core has app readback protection
2022-07-12T11:30:02.145Z INFO Resetting device
2022-07-12T11:30:12.476Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core
2022-07-12T11:30:19.115Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
2022-07-12T11:30:19.118Z INFO Recovering NRFDL_DEVICE_CORE_NETWORK core
2022-07-12T11:30:25.249Z INFO Recovering NRFDL_DEVICE_CORE_NETWORK core completed
2022-07-12T11:30:25.255Z INFO Device recovery completed
2022-07-12T11:30:25.269Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-07-12T11:30:25.269Z INFO JLink OB firmware version J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49
2022-07-12T11:30:25.270Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink OB version","label":"J-Link OB-nRF5340-NordicSemi compiled Dec 3 2021 15:46:49"}
2022-07-12T11:30:25.273Z INFO Device family NRF53
2022-07-12T11:30:25.275Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device family","label":"NRF53"}
2022-07-12T11:30:25.278Z INFO Device version NRF5340_xxAA_ENGD
2022-07-12T11:30:25.279Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device version","label":"NRF5340_xxAA_ENGD"}
2022-07-12T11:30:25.281Z INFO Board version PCA10095
2022-07-12T11:30:25.282Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Open jlink device board version","label":"PCA10095"}
2022-07-12T11:30:25.285Z INFO Loading readback protection status for Application core
2022-07-12T11:30:25.285Z INFO Loading readback protection status for Network core
2022-07-12T11:30:26.663Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-07-12T11:30:27.289Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-07-12T11:30:29.163Z INFO Parse memory regions for Application core
2022-07-12T11:30:29.163Z INFO Parse memory regions for Network core
2022-07-12T11:30:29.167Z INFO Update files regions according to Application core
2022-07-12T11:30:29.167Z INFO Parse memory regions for file
2022-07-12T11:30:29.168Z INFO Update files regions according to Network core
2022-07-12T11:30:29.168Z INFO Parse memory regions for file
2022-07-12T11:30:29.188Z INFO Device is loaded and ready for further operation
2022-07-12T11:30:29.197Z INFO Reading memory for NRFDL_DEVICE_CORE_APPLICATION core
2022-07-12T11:30:30.696Z ERROR Failed to get device memory map: async task failure for id: 8507722910 msg: NOT_AVAILABLE_BECAUSE_PROTECTION (Origin: "Error when running fw program.")
2022-07-12T11:30:30.697Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Report error","label":"win32; ia32; v3.0.3; Failed to get device memory map: async task failure for id: 8507722910 msg: NOT_AVAILABLE_BECAUSE_PROTECTION (Origin: \"Error when running fw program.\")"}
2022-07-12T11:41:05.975Z DEBUG Sending usage data {"category":"pc-nrfconnect-programmer","action":"Close device","label":""}
2022-07-12T11:41:06.002Z INFO Target device closed
