Issue last version nrfjprog

RE: Issue last version nrfjprog

Naeem Maroof — Wed, 17 Jul 2024 13:01:11 GMT

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

RE: Issue last version nrfjprog

Julien — Tue, 02 Jul 2024 12:22:59 GMT

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

RE: Issue last version nrfjprog

Håkon Alseth — Mon, 17 Jun 2024 08:18:15 GMT

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