topic Re: S32K311 SECURE DEBUG in S32K

S32K311 SECURE DEBUG

rahupat — Thu, 17 Jul 2025 15:22:17 GMT

Hello NXP Team,

"Secure Debug might be enabled on this device. If so, please unlock the device via PEmicro scripts before attempting to connect again." #s32K3xx #secure debug

Re: S32K311 SECURE DEBUG

VaneB — Thu, 17 Jul 2025 22:09:50 GMT

Hi @rahupat

Is this the first time you are programming the MCU? If so, secure debug should be disabled. This kind of error often comes up when there are communication problems.

Are you using a custom board or an evaluation board (EVB)? If it is a custom board, are they using an SBC? Sometimes the SBC might not be supplying power correctly, which could prevent the MCU from being programmed. You may find this related thread useful.

FS26

Did you program the password and advance the MCU’s lifecycle?

BR, VaneB

Re: S32K311 SECURE DEBUG

rahupat — Fri, 18 Jul 2025 06:10:22 GMT

Hi @VaneB

I have flashed the board previously and didn't get any issues, but yesterday, when I tried flashing after a week, then faced this issue.

It is a custom board and did not program the password or advance the MCU’s lifecycle.

Re: S32K311 SECURE DEBUG

VaneB — Fri, 18 Jul 2025 16:51:56 GMT

Hi @rahupat

What was the last firmware or image you flashed onto your board?

Also, does your custom board include an SBC? Please verify the hardware configuration so we can rule out any potential hardware-related issues.

Re: S32K311 SECURE DEBUG

rahupat — Mon, 21 Jul 2025 06:55:16 GMT

I had previously flashed the Demo code and then flashed the blinking LED code (Example code) provided by NXP, removing the RTD from the flashed code.

Custom board does not include an SBC.

Re: S32K311 SECURE DEBUG

VaneB — Mon, 21 Jul 2025 18:08:08 GMT

Hi @rahupat

To help further investigate the issue and rule out any potential software-related causes, could you please share the last code you flashed to the device?

Additionally, since I am unable to directly review the hardware setup, it would be helpful if you could also verify that aspect to ensure everything is configured correctly on your end.

Re: S32K311 SECURE DEBUG

rahupat — Fri, 25 Jul 2025 13:06:59 GMT

Hi @VaneB

We bought some new MCUs with the same number and replaced them on the hardware, still getting the same warning as the previous MCU. The debugger is working fine, as we are using the debugger with other hardware I also checked the connection fine with DMM continuity from the MCU debug pin to the JTAG connection. Can you please confirm that if we buy a new MCU, will it have any default secure configuration in it, or any issues like this we can get from new MCU

Re: S32K311 SECURE DEBUG

VaneB — Fri, 25 Jul 2025 16:56:42 GMT

Hi @rahupat

Could you please clarify which warning you are referring to? Are you talking about the Secure Debug window? On newer devices, Secure Debug is usually disabled by default.

You mentioned that the parts were replaced. Were you able to successfully flash the new MCU at least once?

Also, do you have access to another board where you could try flashing one of these new MCUs? If possible, could you share a photo of the MCU? That would help us verify the part number and confirm the device.