eMcem_init issue

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

eMcem_init issue

1,722件の閲覧回数
Chengchun
Contributor I

In eMcem_init, the function status return is E_NOT_OK.Through the useing step debug find eMcem_Fccu_ReadFaultStatus return FCCU_FAULT_ASSERTED, so eMcem_init return is E_NOT OK.But if starting the eMcem_init start to step debug run function, eMcem_init return is E_OK.

Please anyone know how to resolve this issue, Thanks.
タグ(2)
0 件の賞賛
3 返答(返信)

1,686件の閲覧回数
RadoslavB
NXP Employee
NXP Employee

Hello,

please could you specify which SAF release are you using and if this is tested within customer application or SAF demo?
Are you using Lauterbach or different debugger?

Kind regards,
Radoslav

0 件の賞賛

1,668件の閲覧回数
Chengchun
Contributor I

The version is S32K3_SAF_1.0.4, in debugger tool is PLS, and the test result of SAF demo code and application code is same.

0 件の賞賛

1,648件の閲覧回数
RadoslavB
NXP Employee
NXP Employee

Hello,

I tried on my side with K344 device and SAF Demo code 1.0.4 but can't observe this issue even if I do Steb by step debugging through the eMcem_Init().

Please could you specify derivative you are using and chip revision? 
You can paste MIDR1 register from SIUL2:

RadoslavB_0-1715604381789.png

After eMcem_init(), could you execute:  eMcem_GetExtDiagData( &extDiagData );
and paste the content of the extDiagData structure?

When the fault is asserted could you paste NCF S0 status and associated DCMROD registers (in eMcem UM you can find table 'Fault List' where it is depicted which DCM belong under specific NCF channel).
Once we know which DCM fault is being asserted when you do step into debug, we can investigate further.

Kind Regards,
Radoslav

 

0 件の賞賛