decices selection when debugging s32k314

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

decices selection when debugging s32k314

ソリューションへジャンプ
1,569件の閲覧回数
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 件の賞賛
返信
1 解決策
1,475件の閲覧回数
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 件の賞賛
返信
3 返答(返信)
1,540件の閲覧回数
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 件の賞賛
返信
1,494件の閲覧回数
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 件の賞賛
返信
1,476件の閲覧回数
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 件の賞賛
返信