Issue last version nrfjprog

[Julien]

Hi, 

I encountered an issue since i upgraded nrfjrpog

My previous version was 10.13.0

And now is 10.24.2.

I have a batch file to program my device and until the upgrade, i never had problems.

Now i got this message

 

nrfjprog --family NRF52 --program Final_Hex/Merge_app_nrf52833_RC_Release_V4.2.2.hex --verify --clockspeed 15000 --snr 683856884 --chiperase  --log
[error] [  nRF52] - Failed while erasing device. -102: An unknown error.
[error] [ Worker] - An unknown error.
[error] [ Client] - Encountered error -102: Command erase_file executed for 188 milliseconds with result -102
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.

I add the log file

 log_fail.log

What does this error mean, and why this error occurs now ?

Best Regards,

Julien

[Håkon Alseth]

Hi Julien,

 

Based on the logs, it looks like the issue occurs after a while and during writing.

The initial connection towards the nRF looks to be successful, which is good.

 

Do you see the same issue if you do a "nrfjprog -e" first?

Could you also try to reduce the clock speed, for instance to 500 kHz, to see if this has any impact?

 

Kind regards,

Håkon

[Julien]

Hi,

We do not have the issue using "nrfjprog -e" before program my device.

Why do i need to add this line ?

We have old apllication .exe who do not use this line and so become depreciated with the last nrfjprog version.

Best Regards,

Julien

[Naeem Maroof]

Hi Julien,

There has been several updates and bug fixes from 10.13.0 to 10.24.2. 

As per the latest version, it says that if the target area to program is not erased, the --program operation will fail, unless an erase option is given. I can see you are using --chiperase. Is your chip ap-protected?

Do you have concerns using -e before programming? Is chiperase always failing for you?

(few logs from release notes: In 10.15.0, device-specific behavior issues, for nRF52 Series devices are fixed. Fixed issue where a simultaneous –recover and –program would fail if device was protected.
Fixed issue where certain nrf52 devices weren't treated as having hardened ap-protect when identified as revision FUTURE. Fixed issue where the program to keep hardened ap-protect devices open after recover was not working as intended.)

/br,

Naeem