Program issue with Segger JLink Base Compact

[chaben1]

Hi,

I'm trying to program my nRF52840 through the nRF Command Line Tool. The commands which I send are the follows:

nrfjprog –recover

nrfjprog -f nrf52 --program MyProgram.hex –chiperase

This works fine as long as I use the Segger JLink Base. I've tried to program the same chip with the same commands with the Segger JLink Base Compact but it doesn't work. My JLinkARM.dll always throws an unknown exeption.

Is it possible, that the recover command doesn't work properly with the JLink Base Compact or is there another issue?

Attached you'll find the generated .log file.

Thanks

5428.log.log

[Amanda Hsieh]

Hi, 

Please try the last version of the Command line tool and provide the log by executing "nrfjprog --recover -f nRF52 --log". 

Regards,
Amanda

[chaben1]

Hi Amanda,

Thanks for your fast reply.

I tried your suggestion and logged the output, once with the JLink Base Compact and once with the JLink Base. I attached both outputs.

Unfortunately it didn't work with the JLink Base Compact.

Thanks for your feedback

Regards,

Livio

logbase.loglogcompact.log

[Amanda Hsieh]

Hi, 

The logcompact.log looks the same as previous. Please provide the log running with nrfjprog version 10.15.1 and  "nrfjprog --recover -f nRF52 --log" command.

-Amanda 

[chaben1]

Hi Amanda,

I've attached the wrong log file, sorry for that. Here is the correct one.

The commandline output also gives me this message:

S C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin> nrfjprog --recover -f nRF52 --log C:\temp\compact
Recovering device. This operation might take 30s.
ERROR: [SeggerBackend] - JLinkARM.dll ReadMemU32 detected a read error 1.
ERROR: [SeggerBackend] - This typically indicates the read was blocked by a memory protection mechanism.
Erasing user code and UICR flash areas.

Thanks

Livio

compact.log

[Amanda Hsieh]

Hi, 

From our expert:

It looks like the J-Link compact is unable to read the CTRL-AP IDR register correctly, and is getting offset or wrong data every two or three reads. This causes likely causes nrfjprog to fail in debug reset. Not sure what the root cause is yet.

Regards,
Amanda