decices selection when debugging s32k314

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

decices selection when debugging s32k314

Jump to solution
736 Views
luhaiou
Contributor II
When I choose NXP s32K3 series device with cyclone and IAR IDE,I found 3 types and what are their differences
s32k314,
s32k314-EMU,
s32k314-SECUREBOOT
0 Kudos
Reply
1 Solution
642 Views
VaneB
NXP TechSupport
NXP TechSupport

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.

View solution in original post

0 Kudos
Reply
3 Replies
707 Views
VaneB
NXP TechSupport
NXP TechSupport

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

0 Kudos
Reply
661 Views
luhaiou
Contributor II

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?

0 Kudos
Reply
643 Views
VaneB
NXP TechSupport
NXP TechSupport

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.

0 Kudos
Reply