Solved! Go to Solution.
Hi @luhaiou
The S32K3xx device with HSE firmware installed does not necessarily need secure debugger authentication. When installing HSE, the device is initially in lifecycle CUST_DEL, which has debug access open. It is not until advancing the life cycle that secure debugging is required.
Hi @luhaiou
S32K314: during debug entry a hard reset is toggled. Default target.
S32K314-EMU: is no longer available in the latest versions.
S32K314-SECUREBOOT: used when JTAG protection is set or secure boot. Prevents to clear the authentication when enters to debug.
B.R.
VaneB
Now that I've turned on the secure boot feature, I still have S32K314 selected and nxp_s32k341_1x32x256k_hse_enabled.arp selected when debugging.
I didn't choose S32K314-SECUREBOOT, it still debugs normally, is it necessary to choose S32K314-SECUREBOOT?
Hi @luhaiou
The S32K3xx device with HSE firmware installed does not necessarily need secure debugger authentication. When installing HSE, the device is initially in lifecycle CUST_DEL, which has debug access open. It is not until advancing the life cycle that secure debugging is required.