2411741_en-US

[#1]

S32K31XEVB-Q100 (S32K311) "Locked device" / Debug Authentication ID Code prompt on first debug

I just received a new S32K31XEVB-Q100 board and connected a Segger J-Link to it for the very first time (via the external 10-pin SWD header, not the onboard debugger). This is a completely fresh board — the only thing I tried so far is a default RTD-generated project (Mcal.h include, stock empty main() loop), nothing related to HSE or security.

On connecting, both SEGGER J-Flash and S32 Design Studio report the device as locked and pop up an "ID Code" authentication prompt:

- Unknown SDA AP Id detected: 0x00000000
- Connect failed. Trying connect under reset...
- -- Identifying target device...
- -- SWD selected. Executing JTAG -> SWD switching sequence...
- -- Identifying target device...
- -- SWD selected. Executing JTAG -> SWD switching sequence...
- Unlocking device if necessary...
- Locked device detected. Proceeding with the unlock procedure...

J-Flash then asks: "Please input the ID Code required for the authentication" (32 hex digits or 16 ASCII chars). I've never set a password on this chip.

Setup: MCU shows correctly as NXP S32K311 / Cortex-M7 in J-Flash, SWD @ 4000 kHz, J-Flash V9.74, J-Link V9.74/V9.26. For comparison, my S32K144 EVB works fine with the same J-Link — no such prompt ever appears there, which I understand is because S32K1 and S32K3 use very different security models.

J-Flash then asks: "Please input the ID Code required for the authentication" (32 hex digits or 16 ASCII chars). I've never set a password on this chip.

Setup: MCU shows correctly as NXP S32K311 / Cortex-M7 in J-Flash, SWD @ 4000 kHz, J-Flash V9.74, J-Link V9.74/V9.26. For comparison, my S32K144 EVB works fine with the same J-Link — no such prompt ever appears there, which I understand is because S32K1 and S32K3 use very different security models.

I found earlier thread with the same symptom on an S32K311, where NXP support explained there's no mass-erase-unsecure path for K3 (unlike K1) and pointed to the HSE_B Firmware Reference Manual (via Secure Files) for recovery.

Questions for the community / NXP:

1. Has anyone else seen a brand-new S32K31XEVB-Q100 arrive already debug-locked like this? Is this a known factory-test artifact on some batches?
2. Is there a documented default/recovery password for evaluation boards specifically, as opposed to production silicon?
3. Any pointers on requesting the HSE_B Firmware Reference Manual?

Regards

Any support will be appreciated: