Trace, Debug, Bist , S32K , Functional Reset

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

Trace, Debug, Bist , S32K , Functional Reset

2,039件の閲覧回数
Higgs_Boson
Contributor I

Hi, Teams,

We are using BIST in the s32k project,  Since bist will cause functional reset after test done. And

1. we wonder how to use debug tool(e.g. trace32) to trace the software when s32k is performed a functional reset.

2. and, how to reinit s32k after functional reset .because I notice the ram is become "???" after the functional reset: 

Higgs_Boson_0-1678782750692.png

Thanks.

0 件の賞賛
返信
3 返答(返信)

2,030件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @Higgs_Boson 

You can use sys.attach command after any reset or after power-on to re-establish debug session without reset (copied from debugger_arm.pdf):

lukaszadrapa_0-1678806573781.png

After functional/destructive reset, the device boots from normal reset vector as usual. Startup files then contains code which initializes the RAM. 

Regards,

Lukas

0 件の賞賛
返信

2,025件の閲覧回数
Higgs_Boson
Contributor I

Hi, 

A Functional Reset will cause RAM content loss? How does "Self Test Done Functional Reset" / "Functional Reset" means.

 

Thanks.

0 件の賞賛
返信

2,017件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @Higgs_Boson 

generally, functional resets will keep SRAM data unchanged by hardware mechanism.
Destructive resets cannot guarantee the SRAM data integrity.

However, SRAM self test cannot keep the SRAM content. It's destructive operation.

Regards,

Lukas

 

0 件の賞賛
返信