S32K358 Advance the HSE Life Cycle, Debug authorization without source code implementation

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

S32K358 Advance the HSE Life Cycle, Debug authorization without source code implementation

ソリューションへジャンプ
1,513件の閲覧回数
HaiHoangSoftware
Contributor IV

Hi,

I want to test our soft ware in IN_FIELD HSE lifecycle.

The NXP examples shows that the .cmm scripts needs to execute HSE functions from the Demo APP to set HSE attributes for:

  1. Programming/Read ADKP key
  2. Change Debug authorization mode to Challenge-Response
  3. Authorized Debug
  4. Advance HSE Life Cycle

Is this possible to do all these above tasks without source code implementation?

0 件の賞賛
返信
1 解決策
1,491件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @HaiHoangSoftware 

It doesn't matter if HSE services are launched by your code running on MCU or by debugger. The result is the same.

In case of mentioned services, you can take a look at S32K344_CQC_DEMO in HSE Demo Examples:

https://www.nxp.com/webapp/Download?colCode=S32K3_HSE_DemoExamples

c:\NXP\S32K3_HSE_DemoExamples_1_0_0\S32K3_HSE_DemoExamples\Device_Configuration\S32K344_CQC_DEMO\

This demo shows how to set ADKP, how to advance the life cycle etc.

You can write cmm script to do the same by your debugger - just initialize a service descriptor somewhere in RAM and then launch such service by writing to transmit register in MU.

Regards,

Lukas

元の投稿で解決策を見る

0 件の賞賛
返信
3 返答(返信)
1,484件の閲覧回数
law485
Contributor I

Yes, the NXP S32Z280-400EVB supports trace functionality using **Arm CoreSight™ technology**, specifically **ETM** for core program tracing. **Lauterbach TRACE32 debuggers are fully compatible** and commonly used for this, enabling detailed analysis. However, directly programming ADKP keys, changing debug authorization modes, or advancing HSE lifecycle states via just `.cmm` scripts is generally **not possible** without corresponding application-level API calls or dedicated tools. NXP and Lauterbach support can provide further guidance on authorized debug and secure provisioning.

0 件の賞賛
返信
1,426件の閲覧回数
HaiHoangSoftware
Contributor IV
Thanks for the information
0 件の賞賛
返信
1,492件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @HaiHoangSoftware 

It doesn't matter if HSE services are launched by your code running on MCU or by debugger. The result is the same.

In case of mentioned services, you can take a look at S32K344_CQC_DEMO in HSE Demo Examples:

https://www.nxp.com/webapp/Download?colCode=S32K3_HSE_DemoExamples

c:\NXP\S32K3_HSE_DemoExamples_1_0_0\S32K3_HSE_DemoExamples\Device_Configuration\S32K344_CQC_DEMO\

This demo shows how to set ADKP, how to advance the life cycle etc.

You can write cmm script to do the same by your debugger - just initialize a service descriptor somewhere in RAM and then launch such service by writing to transmit register in MU.

Regards,

Lukas

0 件の賞賛
返信