JLinkARM DLL reported an error

RE: JLinkARM DLL reported an error

Håkon Alseth — Fri, 20 May 2022 13:19:50 GMT

Hi,

on HPDesktop*.log and Acer*.log, you have these lines:

[2022-May-20 07:23:29] [error] [SeggerBackend] - This typically indicates the read was blocked by a memory protection mechanism.

If you have newer revisions of the device, you should recompile your firmware with newer startup files, as described in this informational notice:

https://infocenter.nordicsemi.com/pdf/in_150_v1.0.pdf

As described in one of the steps here:

Program code compiled with MDK 8.40.2 or later

The MDK is available for download here: https://www.nordicsemi.com/Products/Development-tools/nRF-MDK/Download?lang=en#infotabs

Could you ensure that you have v8.40.2 or newer with the image you're programming onto the device?

Kind regards,

Håkon

RE: JLinkARM DLL reported an error

FluxRose01 — Fri, 20 May 2022 06:41:45 GMT

Hi Hakon,

I have updated all PCs to latest command line and all still have an issue, I have attached a log from each PC using the same hardware and target, that has previously programmed OK.devzone.nordicsemi.com/.../HPGry200522.log devzone.nordicsemi.com/.../HPDesktop200522.log devzone.nordicsemi.com/.../HPWhite200522.log devzone.nordicsemi.com/.../AcerBlk200522.log

RE: JLinkARM DLL reported an error

Håkon Alseth — Thu, 19 May 2022 13:39:17 GMT

Hi,

Sorry for not seeing the timestamps. Yes, these commands should only take a matter of seconds, not minutes.

In the working logs, you're using a newer version of nrfjprog than in the non-working logs. Could you try with nrfjprog v10.15.4 on the other PCs as well to see if this solves the issue?

Kind regards,

Håkon

RE: JLinkARM DLL reported an error

FluxRose01 — Thu, 19 May 2022 08:19:13 GMT

Hi,

I'm not an expert on the log output but it takes a very long time to produce this output from 4 commands. This is not normal, it usually takes seconds and I read "JLINK_HasError()" many times in that log, the EraseAll takes a long time and then the Program command takes a long time before it fails. The below log is a successful programming cycle using the same commands.

devzone.nordicsemi.com/.../190522.log

RE: JLinkARM DLL reported an error

Håkon Alseth — Thu, 19 May 2022 07:59:06 GMT

Hi,

The log is quite long, and does not really show anything bad, meaning; there is no communication problem, as far as I see.

Could you elaborate on which step fails?

Kind regards,

Håkon

RE: JLinkARM DLL reported an error

FluxRose01 — Wed, 18 May 2022 15:09:19 GMT

I updated and I still have an issue, maybe not the same issue but it is consistent now across 3 PCs. This is the result of the following 4 instructions:

nrfjprog --reset --log
nrfjprog --eraseall --log
nrfjprog --program fw_365.hex -- verify --log
nrfjprog --reset --log

devzone.nordicsemi.com/.../180522_5F00_log.txt

RE: JLinkARM DLL reported an error

Håkon Alseth — Wed, 18 May 2022 14:29:11 GMT

Hi,

[quote user=""][2022-May-17 14:38:25] [ info] [Backend] - Segger dll version 6.94.d loaded.[/quote]

This is quite an old segger .dll.

Could you try updating to the latest drivers that we bundle with the nrf command line tools (which also includes nrfjprog)?

https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download

Kind regards,

Håkon

RE: JLinkARM DLL reported an error

FluxRose01 — Tue, 17 May 2022 14:17:47 GMT

Nordic programmer is not recognising the programmer now, brand new Segger J-Link compact.