Flashing failed due to protection on the device

RE: Flashing failed due to protection on the device

Amarjith-ck — Wed, 03 Jul 2024 12:12:12 GMT

I resolved this issue by using the Jlink Flash Lite application and selecting the erase function. In both Jlink Flash Lite and Segger Embedded Studio, when attempting to connect, a popup appeared asking whether to unprotect it. I chose this option, and now the issue is resolved.

RE: Flashing failed due to protection on the device

dejans — Wed, 31 Jan 2024 12:20:56 GMT

Hi garrettb ,

--program might require some erase option. You could try to either add erase option to --program or you could try to combine --program with --recover option as shown in this ticket.

Best regards,
Dejan

RE: Flashing failed due to protection on the device

garrettb — Tue, 30 Jan 2024 15:39:17 GMT

Hi Dejan,

Here is what I did just now:

My setup:

VS Code: 1.85.2 (user setup).

nRF Connect for VS Code: v2023.11.301.

NCS: 2.4.1.

Set up steps

Create new applicaiton.

Copy sample: nrf/samples/bluetooth/peripheral uart.

Add to workspace.

Build configuration: nrf5340dk_nrf5340_cpuapp_ns:

default config settings
Configuration: use build system default

Connect nRF5340 DK board.

Select Flash

Result = Fail

Building peripheral_del
west build --build-dir c:/dev/nordic/apps241/peripheral_del/build c:/dev/nordic/apps241/peripheral_del

[0/24] Performing build step for 'tfm'
ninja: no work to do.
[1/5] Performing build step for 'hci_rpmsg_subimage'
ninja: no work to do.
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: nRF Connect: Flash: peripheral_del/build (active) 

Flashing build to 1050071243
west flash -d c:\dev\nordic\apps241\peripheral_del\build --skip-rebuild --dev-id 1050071243

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex
-- runners.nrfjprog: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
[ #################### ]  12.505s | Erase file - Done erasing                                                          
[ #################### ]   1.266s | Program file - Done programming                                                    
[ #################### ]   1.285s | Verify file - Done verifying                                                       
[ #################### ]   7.297s | Erase file - Done erasing                                                          
[error] [ Client] - Encountered error -102: Command program_file executed for 235 milliseconds with result -102        
[error] [  nRF53] - The write access failed, but no cause could be determined.
[error] [  nRF53] - It may be due to an unaligned access, accessing a nonexistent memory, or a communication issue.
[error] [  nRF53] - Failed while performing 'Write' operation on target address 0x00000000. 
-102: An unknown error.
[error] [  nRF53] - Failed while reading device information.
[error] [ Worker] - An unknown error.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program 'c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex' --sectorerase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 1050071243

 *  The terminal process terminated with exit code: 33. 
 *  Terminal will be reused by tasks, press any key to close it.

Ran the recover script:

nrfjprog --recover

Recovering device. This operation mig
Erasing user code and UICR flash area
Writing image to disable ap protect.

Select Flash

Result = Success

 *  Executing task: nRF Connect: Build: peripheral_del/build (active) 

Building peripheral_del
west build --build-dir c:/dev/nordic/apps241/peripheral_del/build c:/dev/nordic/apps241/peripheral_del

[0/24] Performing build step for 'tfm'
ninja: no work to do.
[1/5] Performing build step for 'hci_rpmsg_subimage'
ninja: no work to do.
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: nRF Connect: Flash: peripheral_del/build (active) 

Flashing build to 1050071243
west flash -d c:\dev\nordic\apps241\peripheral_del\build --skip-rebuild --dev-id 1050071243

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex
-- runners.nrfjprog: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
[ #################### ]  12.571s | Erase file - Done erasing                                                          
[ #################### ]   1.263s | Program file - Done programming                                                    
[ #################### ]   1.285s | Verify file - Done verifying                                                       
[ #################### ]   7.190s | Erase file - Done erasing                                                          
[ #################### ]   1.359s | Program file - Done programming                                                    
[ #################### ]   1.208s | Verify file - Done verifying                                                       
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050071243 flashed successfully.
 *  Terminal will be reused by tasks, press any key to close it.

Select Flash

Result = Fail

-- runners.nrfjprog: Flashing file: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex
-- runners.nrfjprog: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
[ #################### ]  12.533s | Erase file - Done erasing                                                          
[ #################### ]   1.264s | Program file - Done programming                                                    
[ #################### ]   1.286s | Verify file - Done verifying                                                       
[ #################### ]   7.279s | Erase file - Done erasing                                                          
[error] [ Client] - Encountered error -102: Command program_file executed for 204 milliseconds with result -102        
[error] [  nRF53] - The write access failed, but no cause could be determined.
[error] [  nRF53] - It may be due to an unaligned access, accessing a nonexistent memory, or a communication issue.
[error] [  nRF53] - Failed while performing 'Write' operation on target address 0x00000000. 
-102: An unknown error.
[error] [  nRF53] - Failed while reading device information.
[error] [ Worker] - An unknown error.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 33: nrfjprog --program 'c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex' --sectorerase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 1050071243

 *  The terminal process terminated with exit code: 33. 
 *  Terminal will be reused by tasks, press any key to close it.

Ran the recover script:

nrfjprog --recover

Recovering device. This operation mig
Erasing user code and UICR flash area
Writing image to disable ap protect.

Select Flash

Result = Success

I repeated these steps - and it failed every second time, etc.

At one stage, I was prompted to recover the device and reflash.

If I select Yes - the flash succeeds but fails next time.

However, if I select "Always in this session", then it succeeds for the next three flashes (I didn't try any more).

However, when I then select Debug, instead of Flash, it fails again:

 *  Executing task: nRF Connect: Flash: peripheral_del/build (active) 

Flashing build to 1050071243
west flash -d c:\dev\nordic\apps241\peripheral_del\build --skip-rebuild --dev-id 1050071243

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex
-- runners.nrfjprog: c:\dev\nordic\apps241\peripheral_del\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and c:\dev\nordic\apps241\peripheral_del\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
[ #################### ]  11.502s | Erase file - Done erasing                                                          
[ #################### ]   1.254s | Program file - Done programming                                                    
[ #################### ]   1.280s | Verify file - Done verifying                                                       
[ #################### ]   5.929s | Erase file - Done erasing                                                          
[error] [  nRF53] - The write access failed, but no cause could be determined.                                         
[error] [  nRF53] - It may be due to an unaligned access, accessing a nonexistent memory, or a communication issue.
[error] [  nRF53] - Failed while performing 'Write' operation on target address 0x00000000. 
-102: An unknown error.

RE: Flashing failed due to protection on the device

dejans — Tue, 30 Jan 2024 12:12:23 GMT

Hi garrettb ,

Could you provide all required steps for reproducing the issue?

Best regards,
Dejan

RE: Flashing failed due to protection on the device

garrettb — Mon, 29 Jan 2024 22:16:55 GMT

I have a similar issue.

I am working with an nRF5340 DK (PCA10095 - 2.0.0 - 2022.4).

I have to use "nrfjprog --recover" every 2nd time. In other words, it fails the first flash, then after the recover, it usually flashes successfully, once. Then next time it will fail.

And trying to use Debug is almost impossible.

RE: Flashing failed due to protection on the device

dejans — Mon, 22 Jan 2024 13:03:13 GMT

Hi Garvit,

Thank you for providing required information.

I am not able to reproduce your issue.

Have you tried to recover your boards before flashing?

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Garvit Periwal — Mon, 22 Jan 2024 05:31:40 GMT

Hi Dejan,

Apologies for late response.

nRF Command Line Tools - 10.23.4

nRF Connect for Desktop - 4.3

and VS Code - 1.85.1

Yes, I tried on 3rd board as well after reinstalling the software, same issue still persists when I repeated the steps mentioned in previous reply.

Thanks,

Garvit

RE: Flashing failed due to protection on the device

dejans — Fri, 12 Jan 2024 09:06:53 GMT

Hi Garvit,

Which versions of nRF Command Line Tools, nRF Connect for Desktop, and VS Code do you use?

What happens with your third nrf5340-dk board? Do you see the same "Flashing failed" problem with it or not?

Please let me know the result after you reinstall/update all required tools.

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Garvit Periwal — Fri, 12 Jan 2024 05:25:44 GMT

Hi Dejan,

After installing the nrf command line tools, nrf connect for desktop, visual studio code, I went to create a new application and clicked on copy a sample.

searched for blinky example and clicked on first blinky sample

After this

Now I received this error, highlighted in yellow -

In terminal added the an exception as suggested in output window,

After that created a build configuration with following inputs-

After that tried flashing the board and received the error as mentioned in original question asked,

I have tried pressing yes and always in this session option but I end up on same error again and again.

Also, I have 3 boards of same nrf5340 dk , Tried flashing 2 boards with this method and I am receiving this same error on both. At start, I believed this might be happening due to no write access on external disk on company provided laptop but I tried on my personal laptop and enabled the access on company laptop as well but still facing same issue.

Please ignore the warnings in output terminal in above images regarding the nrf command line tool, I am in process of reinstalling all the software's, I know there is very less probability that the error would resolve by doing this but still worth a try.

Thanks,

Garvit

RE: Flashing failed due to protection on the device

dejans — Thu, 11 Jan 2024 09:07:04 GMT

Hi Garvit,

Thank you. This is exactly what I asked for.

Could you provide steps necessary for reproducing the issue?

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Garvit Periwal — Thu, 11 Jan 2024 06:25:52 GMT

Number is - PCA10095 2.0.2 2023.22 1050088170

Apologies, if I am missing basic points here, I am an absolute beginner in this field.

Thanks,

Garvit

RE: Flashing failed due to protection on the device

dejans — Wed, 10 Jan 2024 13:50:44 GMT

Hi Garvit,

I am sorry for not being clear enough. The placing of the label might differ from one version to another. I asked you for the version of the DK which you can find on the white sticker on the front side of the board.

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Garvit Periwal — Wed, 10 Jan 2024 12:24:19 GMT

Number Displayed is - N5340QKAAD02240CC

RE: Flashing failed due to protection on the device

dejans — Wed, 10 Jan 2024 12:02:11 GMT

Hi Garvit,

Thank you for providing required information.

NCS is abbreviation for nRF Connect SDK.

You can find board version number on the label marked red in the picture below.

Please provide information for reproducing your issue.

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Garvit Periwal — Wed, 10 Jan 2024 11:04:16 GMT

Hi Dejans,

I am working on windows 10 OS

VS Code version - 1.85.1

I am new to Nordic development environment, Is NCS short form for nRF Connect SDK ?

nRF Connect SDK version - v2.5.0

Apologies, I don't see any other number on the boards - nRF5340-DK (If required I can upload a picture for same)

Purchase link for boards - Link

I am trying to flash the board with blinky example as of now without any modifications in the sample code.

Thanks,

Garvit

RE: Flashing failed due to protection on the device

dejans — Wed, 10 Jan 2024 09:01:29 GMT

Hi Garvit,

Which operating system, and versions of nrf5340-dk board, NCS and VS Code do you use?

Could you please provide all necessary steps for reproducing your issue?

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Garvit Periwal — Wed, 10 Jan 2024 07:07:57 GMT

Hi,

Was this issue resolved?

I am facing same issue in nrf5340 dk

Thanks,

Garvit

RE: Flashing failed due to protection on the device

dejans — Wed, 12 Apr 2023 09:13:48 GMT

Hi,

[quote user="bryano"]I have contacted my local FAE. I am planning to hand one of my nRF52833 DKs to him so he can do some direct failure analysis, which obviously you can not do.[/quote]

Thank you for this information.

[quote user="bryano"]I will definitely send an update when I have more information. [/quote]

Thank you. I hope that the issue with your boards will be resolved soon.

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Bryan — Tue, 11 Apr 2023 14:27:56 GMT

dejans,

Thank you for your support. I have contacted my local FAE. I am planning to hand one of my nRF52833 DKs to him so he can do some direct failure analysis, which obviously you can not do. I will definitely send an update when I have more information.

RE: Flashing failed due to protection on the device

dejans — Tue, 11 Apr 2023 08:07:12 GMT

Hi,

It is unfortunate that your issue has not yet been resolved. Since I was not able to reproduce the issue, you could contact your local FAE for assistance regarding your specific boards. I would appreciate it if you could afterwards provide an update regarding your issue.

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Bryan — Thu, 06 Apr 2023 16:38:24 GMT

No, it was never resolved. I have been side tracked with other issues.

I have updated to the latest tools and still have the issue. Even if I try to debug the most basic of applications (hello world) I can not go into debug mode.

VS Code: 1.77.1
NCS: 2.3.0
OS: Windows 10

I believe there is something wrong with the DK or the interaction with VS Code.

I still want to find the solution. I am going to reach out to my local FAE (we live in the same town) and give him one of the failing boards.

RE: Flashing failed due to protection on the device

rm_89 — Thu, 06 Apr 2023 02:16:54 GMT

Hey Bryan,

Did you ever resolve this issue? I am now experiencing this same problem with an NRF52833DK V1.1.0, while my older V1.0.1 board is working fine.

RE: Flashing failed due to protection on the device

dejans — Thu, 23 Mar 2023 09:23:17 GMT

Hi,

[quote user="bryano"]Did either of your boards exhibit the behavior I am seeing?[/quote]

No, my boards did not exhibit the same behavior as yours. I have tested again with nRF52833-DK v1.1.0 (NCS v2.0.0). I have flashed multiple times but I could not reproduce your issue.

Best regards,
Dejan

RE: Flashing failed due to protection on the device

Bryan — Wed, 22 Mar 2023 14:22:08 GMT

No problem. I am still not quite clear. Did either of your boards exhibit the behavior I am seeing?

As I mentioned, it seems to be random. I had one board exhibit the behavior the very first time and others it took numerous flashing before it starting doing it.

RE: Flashing failed due to protection on the device

dejans — Tue, 21 Mar 2023 13:36:33 GMT

Hi,

[quote user="bryano"] Just to be clear, you were able to reproduce the error on the nRF52-DK?[/quote]

Thank you for pointing this out and asking for clarification. I made a typing mistake. I am sorry for the confusion. Both boards I was testing on were nRF52833-DK v1.1.0 and not nRF52-DK v1.1.0.

Best regards,
Dejan