nrfjprog write verify failed

RE: nrfjprog write verify failed

Øyvind — Wed, 08 May 2019 10:58:14 GMT

Very strange behavior! But glad to hear it is working.

I will discuss this with my team and see if I can find the reason.

-Øyvind

RE: nrfjprog write verify failed

Øyvind — Wed, 08 May 2019 10:58:13 GMT

Very strange behavior! But glad to hear it is working.

I will discuss this with my team and see if I can find the reason.

-Øyvind

RE: nrfjprog write verify failed

gaminn — Wed, 08 May 2019 10:46:14 GMT

Yes, --ids lists all debuggers connected to my PC. I also tried to specify correct serial number using -s argument and it produces the same error.

But I have just noticed that --rbp ALL works - my device is protected and I have to recover it when I want to write to it again. So the error message is again somehow confusing...but it works.

RE: nrfjprog write verify failed

Øyvind — Wed, 08 May 2019 08:09:06 GMT

Does is it not work with nrfjprog --ids? Ref. case 228271

-Øyvind

RE: nrfjprog write verify failed

gaminn — Tue, 07 May 2019 21:21:52 GMT

I want to enable readback protection for nrf52 but I get the same error:

"C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe" -f nrf52 -c 1000 --rbp ALL
ERROR: There is no debugger connected to the PC with the given serial number.

Can you please advise what could be wrong in this case?

RE: nrfjprog write verify failed

gaminn — Thu, 02 May 2019 14:36:46 GMT

I use Segger J-link.

To summarize it: nRFgo studio works (don't know what speed it sets), J-Flash works (8 MHz, didn't test more) and nrfjprog works only for nrf51 (-f nrf51; didn't test with speed explicitly set).

nrfjprog with -f nrf52 fails with speed > 1000.

I will try it on different PC also...

RE: nrfjprog write verify failed

Øyvind — Thu, 02 May 2019 14:24:47 GMT

The valid clockspeed for nrfjprog is between 125 kHz and 50000 kHz. What programming tool are you using?

Segger J-Flash is a more developed tool and may have more safety features when it comes to writing flash compared to nrfjprog.

RE: nrfjprog write verify failed

gaminn — Thu, 02 May 2019 13:49:28 GMT

You are right, it is about the speed. I can use max -c 1000 with nrfjprog. When I set -c 1001 and higher it stops working. It is weird as I can set even 8 MHz in J-Flash utility and it programs and verifies it.

My cablee is 20 cm long dupont cable.

Any idea why is nrfjprog sensitive to speed setting and other programming utilities (J-Flash) not?

RE: nrfjprog write verify failed

Øyvind — Thu, 02 May 2019 13:37:32 GMT

[quote user="gaminn"]It failed to verify at 0x3C - 0x3F address.[/quote]

How do you now it failed to verify at this address? I can't see any difference between yours and mine in that address range.
I am however seeing several differences at several addresses, which may be the reason it is failing to verify.

Are you using long cables when programming?
The following command will program and verify with a very low clock frequency (125kHz):

nrfjprog -c 125 --program softdevice.hex --chiperase --verify

This will take a longer time to complete.

-Øyvind

RE: nrfjprog write verify failed

gaminn — Thu, 02 May 2019 12:13:30 GMT

I use J-Flash utility along with nrfjprog. J-Flash is able to program and verify the firmware.

These are the commands I run:

"C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe" -f nrf52 --eraseall
Erasing user available code and UICR flash areas.
Applying system reset.

"C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe" -f nrf52 --program s132_nrf52_6.1.0_softdevice.hex
Parsing hex file.
Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programing device.

"C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe" -f nrf52 --verify s132_nrf52_6.1.0_softdevice.hex
Parsing hex file.
Verifying programming.
ERROR: Write verify failed.

This is the dump: devzone.nordicsemi.com/.../dump.txt

It failed to verify at 0x3C - 0x3F address.

RE: nrfjprog write verify failed

Øyvind — Thu, 02 May 2019 12:05:49 GMT

Hello,

[quote user="gaminn"]I tlash s132_nrf52_6.1.0_softdevice.hex (size 424 030 bytes).[/quote]

Are you able to flash this hex?

[quote user="gaminn"]Yesterday, I mainly received verify error on 0x7C offsets of the flashed file, today I got - 0x7FC, 0x3FC and 0x7C.[/quote]

How do you get this information?

[quote user="gaminn"]These are the commands I run:[/quote]

What do you get when you run these commands?

Can you please run the following command:

nrfjprog --memrd 0x0 --n 0x26000 > dump.txt

And send me this file.

Thanks!
-Øyvind

RE: nrfjprog write verify failed

gaminn — Thu, 02 May 2019 11:30:15 GMT

The device is Raytac's MDBT42 on our custom board. I tried more boards.

I tlash s132_nrf52_6.1.0_softdevice.hex (size 424 030 bytes).

Yesterday, I mainly received verify error on 0x7C offsets of the flashed file, today I got - 0x7FC, 0x3FC and 0x7C.

By offset 0 I mean beginning of the hex, by offset 0xFF I mean 255th byte of the hex (provided that there is one continuous memory region at the beginning of the hex).

These are the commands I run:

"C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe" -f nrf52 --eraseall
"C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe" -f nrf52 --program s132_nrf52_6.1.0_softdevice.hex
"C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe" -f nrf52 --verify s132_nrf52_6.1.0_softdevice.hex

RE: nrfjprog write verify failed

Øyvind — Thu, 02 May 2019 08:38:21 GMT

Can you give more information about the device you are trying to program? Is it a developer kit or custom board?

[quote user=""]I examined it a little and I can see that nrfjprog changes some bytes, mainly at offset 0x7C - 0x7F of the hex, where it programs FF FF FF FF instead of what is in the hex.[/quote]

What do you mean with this offset? Is it always the same address?

Please provide the .hex file so I can test here.

Kind regards,
Øyvind