nRF54 Debug Interface During Abrupt Power‑Off

RE: nRF54 Debug Interface During Abrupt Power‑Off

joey — Tue, 08 Sep 2026 13:31:10 GMT

During code execution, accidental corruption of part of the MCUBoot occurred during Flash operations, rendering MCUBoot unable to reboot.

RE: nRF54 Debug Interface During Abrupt Power‑Off

Simonr — Tue, 08 Sep 2026 13:15:43 GMT

Feel free to share the root cause, as that could be helpful to community members with the same type of trouble in the future.

RE: nRF54 Debug Interface During Abrupt Power‑Off

joey — Mon, 07 Sep 2026 01:04:00 GMT

Thanks, I've found the root cause of the issue.

RE: nRF54 Debug Interface During Abrupt Power‑Off

Simonr — Tue, 25 Aug 2026 07:59:34 GMT

Okay, then I think this is due to the UART pins on the DK also being connected to the UART. Can you use the board configurator app and disable the VCOM0 and VCOM1 on the DK and see if that lets you use the TXB module instead.

Best regards,

Simon

RE: nRF54 Debug Interface During Abrupt Power‑Off

joey — Fri, 21 Aug 2026 12:47:31 GMT

On the development board, the UART pins are directly connected to a module equipped with the TXB0108. The TXB0108 module is powered by a separate 3.3 V supply, while the development board itself draws power from its on‑board USB port. During normal operation, if the USB cable of the dev‑board is unplugged abruptly while the TXB0108 module remains powered, the system crashes with high probability.

RE: nRF54 Debug Interface During Abrupt Power‑Off

Simonr — Fri, 21 Aug 2026 11:14:33 GMT

How is the power supply removed here on the nRF54L DK exactly? I think maybe the device could be trigging on the tamper controller, but I need more information on what you're doing exactly. You can check the TAMPC register if it's been triggered.

Can you potentially tell me how I can reproduce this on an nRF54L15 DK on my end so I can read out some registers to see what happens here?

Best regards,

Simon