S32K144 MCU config issue

Aishwr — Wed, 15 Jul 2026 10:01:15 GMT

Hello NXP Support Team,

I am working on an S32K144 project using EB tresos / NXP MCAL AUTOSAR 4.2.2. After generating and flashing the MCU configuration, the board stopped responding to the debugger.

Issue Summary:

After flashing the generated MCU configuration:

The board is no longer detected by the debugger.
The debug connection fails.
The LED remains continuously ON.
The board does not seem to recover even after trying debugger connection again.
I suspect the MCU may be stuck in reset, clock failure, PLL lock failure, or a clock monitor reset loop.

Could you please help verify my EB tresos .xdm configuration and confirm:

Whether the SOSC configuration is correct for S32K144.
Whether the SPLL configuration is valid.
Whether enabling SOSC/SPLL clock monitor reset can cause this kind of unrecoverable debug issue.
Whether my RUN/SYS/CORE/BUS/FLASH clock reference configuration is correct.
What exact EB tresos settings should be used for a safe recovery configuration using only FIRC 48 MHz.
How to recover the board if debug access is failing.

I tried reconnecting the debugger, but the board is not recovering. Please suggest the exact recovery procedure for S32K144, such as:
-Connect under reset
-Mass erase
-Recover secured device
-Disable user code execution during connect
-PEMicro / OpenSDA / J-Link recovery steps

Regards,

Aishwarya

topic S32K144 MCU config issue in Using Our Community

S32K144 MCU config issue