S32K312MINI-EVB — Unable to enter debug mode / Cannot halt processor using_board power glitch issue

[User_Embedded]

Hello NXP Support Team,

I am facing an issue with my S32K312MINI-EVB evaluation board where I am unable to enter debug mode or program the
MCU.

Setup:
- Board: S32K312MINI-EVB
- Debug Probe: P&E Multilink Universal Rev C (PEM647663)
- Connection: Multilink connected to J7 (JTAG/SWD header) via ribbon cable, with its own USB cable to PC
- Power Supply: USB-C through J9, jumpers J19 & J20 in position 1-2
- IDE: S32 Design Studio
- Recovery Tool: P&E Kinetis Recovery Utility v0.02 (Interface Libraries Version 1.06)

Problem:
The S32 Design Studio debugger is unable to connect to the S32K312 MCU. To recover the board, I attempted using the
P&E Kinetis Recovery Utility. The tool detects the Multilink probe successfully (Cable Version 341, VERSION 1.06), but
when I click START, it gets stuck at:

"Continuously attempting to halt processor. Please try power cycling your board until this operation is successful."

What I have tried:
1. Repeatedly pressing the SW1 RESET button while the tool attempts to halt — no success
2. Rapidly unplugging and replugging the USB-C cable at J9 for power cycling — the tool crashes/closes when board
power is lost for too long
3. Multiple attempts (50+) with different power cycling speeds — still unable to get "Success. Process halted"
4. I have not been able to use J1 (12V barrel jack) for power cycling as the board does not power on from J1 alone
with J19/J20 at position 2-3

Questions:
1. Is the P&E Kinetis Recovery Utility the correct tool for recovering the S32K312 (Cortex-M7, S32K3 family), or is
there a different recovery procedure for S32K3 devices?
2. Is there an alternative method to mass erase or unlock the S32K312 MCU when the debug port is unresponsive?
3. Could the HSE (Hardware Security Engine) be preventing debug access, and if so, what is the recommended recovery
path?
4. Are there any specific power glitch timing requirements or jumper configurations on the S32K312MINI-EVB for
successful processor halt during recovery?

Any guidance or documentation on recovering the S32K312MINI-EVB from this state would be greatly appreciated. like i have tried the same steps mentioned in nxp doc to recover.

Thank you.

[davidtosenovjan]

1) Is the P&E Kinetis Recovery Utility the correct tool for S32K312?
No. The P&E Kinetis Recovery Utility does not support S32K3 devices. It is intended for Kinetis and S32K1 (Cortex‑M4) parts and cannot recover an S32K312 (Cortex‑M7 with HSE).

2) Is there an alternative method to mass erase or unlock the MCU?
No. On S32K3 devices there is no external mass‑erase or unlock mechanism if debug access is blocked by HSE or by the lifecycle state.

3) Could HSE be preventing debug access?
Yes. Debug access on S32K3 is fully controlled by HSE and the device lifecycle. If debug was disabled or the device moved out of a development lifecycle, SWD/JTAG halt is intentionally blocked.

4) Are there specific power‑glitch timings or jumper settings for recovery?
No. Power cycling, glitch timing, jumper changes, or reset button usage cannot bypass HSE‑based debug restrictions on S32K3 devices.

But the same error is often cause by other reason.

Multilink FX requires its firmware to be up to date. Debugger probe updates itself during its connection, but this may be blocked by firewall or other IT related issues. If this is an issue, consult your IT department.

PeMicro MULTILINK-FX driver that can be downloaded here:

https://www.pemicro.com/downloads/download_file.cfm?download_id=53

Otherwise I would point out to PeMicro support:

https://www.pemicro.com/support/index.cfm

Also customer sometimes expect EVB device is powered over USB even in case it is supposed to be powered over barrel connector – even this may lead into notice about possible secure debug as debugging SW is not capable to distinguish this.

[User_Embedded]

Thank you for your response. Based on your recommendations, we have completed the following actions:

  1. Updated PEMicro Multilink firmware
  - Downloaded USBMultilinkResourcesInstall.exe from the provided PEMicro link
  - Ran PEFirmwareConfig.exe utility
  - Successfully updated Multilink Universal Rev C (Serial: PEM647663) to firmware version 11.52 in ARM configuration
  - "Last Result = Success" confirmed

  2. Verified board power setup
  - Board is properly powered via USB (J9 USB-C connector)
  - All default jumpers verified (J19, J20, J22, J10, J18)
  - Board's power LED is illuminated (blinking)

  3. Retried debug connection with updated firmware

  Unfortunately, the same error persists:
  - SWD connection is established (DAP IDCODE = 0x4A35EE04 readable)
  - Debug power domain fails to power up (DP CTRL/STAT = 0xFFFFFFFF)
  - Error: "The GDB Server was not able to establish a connection to the target processor"

Our questions:

  1. Based on the DP CTRL/STAT = 0xFFFFFFFF behavior along with successful DAP IDCODE reads, can you confirm whether this board is in
   an HSE-locked / lifecycle-advanced state that cannot be recovered externally? as we taken care while flashing the HSE that it would not lock anything on the board and we ensured that not writing anything in PTM memory or something.
  2. Is there any NXP-specific recovery procedure or tool (other than PEMicro) we should try before concluding that the board is
  unrecoverable?