nRF5340DK IMCU Bricked

RE: nRF5340DK IMCU Bricked

hdiags — Sun, 10 Nov 2024 03:24:08 GMT

Outstanding, many thanks AnujPathak. I used a heat gun and amazingly, it worked. Tested just before heating and the DK did not work, it was entirely bricked. Since heating, I've been using the DK for several hours with no problems.

RE: nRF5340DK IMCU Bricked

hdiags — Sat, 09 Nov 2024 02:20:38 GMT

Just reporting that this has also happened to me. I'm on Linux and checked my dmesg logs. Quite spontaneously, dmesg reports the device disconnecting at a time when my computer was on, but I was out of the house. The device then reconnected and re-disconnected every 15 seconds or so for a few hours before eventually falling silent.

Since this happened while I was away from the computer and without any trigger, looks almost certain the DK has a manufacturing fault. The DK was protected from dust or external interference (dust, etc), both at the time and at all times since I've owned it. The DK is about 1.5 years old.

I've not tried placing it on a heat bed yet, but shall; thanks AnujPathak for sharing how you fixed the issue.

RE: nRF5340DK IMCU Bricked

AnujPathak — Tue, 21 Feb 2023 07:07:29 GMT

Programming IMCU didn't work either. But I was able to recover the DK. Placing nRF5340DK on heat-bed recovered it. I do not have any answer why it occurred, but sharing it to help others having same issue.

RE: nRF5340DK IMCU Bricked

Kazi Afroza Sultana — Wed, 04 Jan 2023 08:42:41 GMT

Ok. Good Luck.

RE: nRF5340DK IMCU Bricked

AnujPathak — Tue, 03 Jan 2023 13:23:33 GMT

I do not have tag connect but from nrf5340dk's schematic, it seems there are touch points (SWDIO/CLK) to enable flashing of IMCU too.
I'll try and revert back

Thanks

RE: nRF5340DK IMCU Bricked

Kazi Afroza Sultana — Tue, 03 Jan 2023 11:53:46 GMT

Hello,

You can try to reflash the nRF5340 program by ''tag connect'' and another debugger.

Tag Connect:

The binary file can be found in C:\Program Files (x86)\SEGGER\JLink\Firmwares (JLink_OB_nRF5340_NordicSemi.bin).

The one end of the tag connect will be connected on the nRF5340-DK. And the other end of the cable, needs to be connected to a different debugger.

RE: nRF5340DK IMCU Bricked

Kazi Afroza Sultana — Mon, 02 Jan 2023 09:53:33 GMT

Hello,

I have asked our team about this issue. I will get back to you whenever there is an update. We were lower staffed during Christmas vacation. Sorry for the late reply.

Thanks.

Kazi

RE: nRF5340DK IMCU Bricked

AnujPathak — Fri, 30 Dec 2022 11:45:11 GMT

I have already tried 3 different USB cables (all cables working fine with 52840DK), on two different systems.
For reference before opening this ticket, I have already looked at all similar threads and tried every solution suggested in other threads

My issue is that IMCU either resets or not booting or is in halt

RE: nRF5340DK IMCU Bricked

Kazi Afroza Sultana — Fri, 30 Dec 2022 11:20:51 GMT

Hi,

It seems like connectivity issue between the PC and the Jlink debugger. You may try to use another usb cable or different usb port on the pc.

RE: nRF5340DK Bricked

AnujPathak — Fri, 30 Dec 2022 09:20:25 GMT

Problem is not the target MCU it is IMCU that seem to be in halt/reset mode and not booting segger jlink ob firmware

But following the output of recover command with DK connected

ERROR: No debuggers were discovered.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

RE: nRF5340DK Bricked

Kazi Afroza Sultana — Fri, 30 Dec 2022 09:16:09 GMT

Hello Anuj,

Can you please try to run this command nrfjprog --recover and see the output?

Thanks.

Best Regards,

Kazi Afroza Sultana