5340 jlink firmware error

RE: 5340 jlink firmware error

Håkon Alseth — Mon, 29 Jan 2024 08:44:44 GMT

Hi,

[quote user="kenlove"]

I tried. The device is not locked, I am going to send DK to FAE.

If there is any other way, I will synchronize it.

[/quote]

As we have tried all other ways of recovering the device, this was going to be my next suggestion as well, ie. to replace the DK.

I'm glad to hear that you have gotten a new DK for development. Let us know if you run into any issues!

Kind regards,

Håkon

RE: 5340 jlink firmware error

kenlove — Mon, 29 Jan 2024 08:10:57 GMT

HI Håkon ,

I tried. The device is not locked, I am going to send DK to FAE.

If there is any other way, I will synchronize it.

During this time, I have got a new DK for development.

Thank you for your support.

Best regards,

Kenlove

RE: 5340 jlink firmware error

Håkon Alseth — Wed, 17 Jan 2024 11:39:22 GMT

Hi Kenlove,

[quote user="kenlove"]Sorry for my late reply because of my vacation earlier.[/quote]

No worries. Hope you had a good vacation!

[quote user="kenlove"]Tried. bat ,But still can't use jlink.[/quote]

Can we try one more thing?

If you open J-Link Commander (from your start-menu), are you able to successfully connect to the device then?

Here's a way to connect using that program:

device nrf52
speed 1000
si 1
connect

This will set the correct device, nrf52 in this case, use 1 MHz speed, select SWD, and lastly: connect.

You can get a pop-up stating that the device is protected, similar to this:

If that happens, please "Yes" to unlock/unsecure the device.

Kind regards,

Håkon

RE: 5340 jlink firmware error

kenlove — Wed, 17 Jan 2024 01:22:16 GMT

HI Håkon ,

Sorry for my late reply because of my vacation earlier.

Tried. bat ,But still can't use jlink.

Best regards,

Kenlove

RE: 5340 jlink firmware error

Håkon Alseth — Fri, 12 Jan 2024 13:54:28 GMT

Hi Kenlove,

The jlink is running as expected.

Could you try to run this recover in a loop using the .bat script that I linked to?

:loop
nrfjprog --recover -f nrf52
goto loop

When the above is running, you should continue to connect/disconnect the jumper connected to nRF current measurement header near the USB connector. This will power on/off the nRF while the debugger tries to recover the chip.

Kind regards,

Håkon

RE: 5340 jlink firmware error

kenlove — Fri, 12 Jan 2024 05:27:46 GMT

HI Håkon ,

Jlink is still not recognized after shorting AIN0 pin.

The code I use is the nRF5SDK saadc, it runs very well.

But I can't download ,recover and erase.

If nrfjprog is used,an example of error reporting is as follows.

Of course, I have also tried nrf connect for desktop.

08:43:04.085
Reading readback protection status for Application core 0%
08:43:04.101
Reading readback protection status for Application core 100%
08:43:04.101
Application core protection status 'NRFDL_PROTECTION_STATUS_ALL'
08:43:04.102
Reading readback protection status for Application core completed
08:43:27.436
Recovering Application core
08:43:27.437
Recovering Application core 0%
08:44:27.887
Failed to recovering application core core. Error: [object Object], message: Batch task recover failed, [jlink] RECOVER_FAILED
08:44:28.115
Error: Failed with exit code 1. One or more batch tasks failed: - [jlink] RECOVER_FAILED, code: Nrfjlink. Message: Batch task recover failed, [jlink] RECOVER_FAILED.

There may be something wrong with jlink(5340) firmware.

What do I need to do to repair jlink firmware?

Best regards,

Kenlove

RE: 5340 jlink firmware error

kenlove — Fri, 12 Jan 2024 00:27:40 GMT

HI Håkon ，

Thank you Håkon . Yes, I'm measuring the current.I will try jumper as soon as possible.

Best regards,

Kenlove

RE: 5340 jlink firmware error

Håkon Alseth — Thu, 11 Jan 2024 13:28:31 GMT

Hi,

If the JLINK is enumerating, the issue is highly likely with the nRF52832.

Q1: Have you ever done any current measurements? If yes, could you add a jumper to the "nRF current measurement" header?

Q2: If the nRF52 device is continuously resetting due to an assert occurring early in the boot-process, it can be hard to recover. What you can do is to run the script mentioned here: RE: nRF52832 not connected anymore after first trying to debug (Keil)

Kind regards,

Håkon