S32g3 Scheck ECC multi-bit error detection fails

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

S32g3 Scheck ECC multi-bit error detection fails

ソリューションへジャンプ
2,827件の閲覧回数
Harish_R
Contributor III

Hi Team,

I have integrated the SAF (scheck) module into our BSW. so, for now, i have enabled only SCHECK_SRAM_0_ECC test during startup. all other things i have integrated based on the SAF example(*_stubs.c). 

so, the Test for single-bit error correction passes but the multi-bit error correction test fails. 

if anyone could support about this issue, it would be helpful.

Thanks in advance!

 

0 件の賞賛
返信
1 解決策
1,672件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi,

Thank you for your reply.

You should view the test results by observing the variable ScheckResultCode. The sCheck_ExecuteStartupTests is a function responsible for performing some tests at startup.

BR

Joey

元の投稿で解決策を見る

0 件の賞賛
返信
13 返答(返信)
2,805件の閲覧回数
Joey_z
NXP Employee
NXP Employee

Hi,Harish_R

Thank you for contacting us.

Could you share more error log information? 

In addition, how do you test single-bit and multi-bit? Could you share more about your testing methods?

BR

Joey

0 件の賞賛
返信
2,778件の閲覧回数
Harish_R
Contributor III

Hi @Joey_z 

Thanks for your time.

im not actually testing manually. so trying to test via scheck module in SAF.

for info im attaching the call stack and point where i lost the control(exception).

 
 

image.png

0 件の賞賛
返信
2,692件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi,Harish_R

Thank you for your reply.

An example how to test is available in SAF demo application provided in the SAF package in folder c:\NXP\S32G_SAF\S32_SAF_Demo. You can refer to and test to see if you have the same problem. Also please check all the conditions/limitations as described in sCheck user manual.

BR

Joey

0 件の賞賛
返信
2,683件の閲覧回数
Harish_R
Contributor III

Hi @Joey_z 

Thank you for the reply,

yes, as you mentioned am referring to the S32_SAF_Demo for implementation. i have integrated according. I'm also integrating the exception.c file like as done in the Demo. but unfortunately, there's a exception for multi bit error test/uncorrectable error test in SRAM. im not sure how to clear the exception. 

for more info im attaching a SS which i tried debugging. 

ECC_multiBitError.png

 

BR,

Harish R

 

0 件の賞賛
返信
2,555件の閲覧回数
Joey_z
NXP Employee
NXP Employee

Hi,Harish_R

Thank you for your reply.

I am discussing your problem with the internal experts; I will reply to you as soon as I get the result.

In addition, do you have more progress and information to share now?

BR

Joey 

0 件の賞賛
返信
2,494件の閲覧回数
Harish_R
Contributor III

Hi @Joey_z 

im trying to debug from my side. but the exception part remains the same. im not sure of passing this address(&sCheck_au8ReservedTcm_0[0]) in SramTest API 

Harish_R_2-1745302811026.png

can you please tell me like what's the purpose of passing &ReservedTCM.  the TCM memory should be configured? for time being i have only SRAM0 test. and in eMceM i have enabled SCHECK_SRAM_ECCSTARTUPTEST_SRAM_0_ECC fault.

 
 

image.png

BR, 

Harish R

タグ(1)
0 件の賞賛
返信
2,459件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi,Harish_R

Thank you reply and information.

Please make sure that the memory allocation complies with the prerequisites in the sCheck User Manual. The chapter 5.3.1.  In particular, DTCM should be configured as executable.

Joey_z_0-1745373746611.png

BR

Joey

0 件の賞賛
返信
2,139件の閲覧回数
Harish_R
Contributor III

Hi @Joey_z 

sorry for the delay,

i have configured DTCM memory and mapped the section(s32_saf_bss_tcm_0) to DTCM (0x2000 0000) but still the behavior is similar. there is hardfault error while sram_read fn is executed. 

is there a way to clear the hardfault? or exception handler in s32g3? 

BR,

Harish R

0 件の賞賛
返信
2,102件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi,Harish_R

The document (SW32G_SAF_2.0.2_QLP01_D2410\eclipse\plugins\sCheck_TS_T40D11M20I2R0\doc\S32G_SAF_SCHECK_UM.pdf) describes the SAF migration method. You can refer to the section 5 Software Integration to further examine your migration method on your software.

Joey_z_0-1747381519254.png

BR

Joey

0 件の賞賛
返信
2,049件の閲覧回数
Harish_R
Contributor III

Hi @Joey_z 

when the debugger is detached, the program runs fine. and when debugger is connected the code is stuck in stack (mapped to DTCM memory).

when it's in runtime. i have read the variable that is passed in scheck_startup test to read error ScheckErrorContainerAggregated. im observed all test are passed.

is this expected?? or the behavior with debugger is different?

0 件の賞賛
返信
2,010件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi,Harish_R

Thank you for your reply.

When connecting to the debugger, what value does "fail" mean to see? Could you share it? Is the observation of whether a sCheck passes or not based on the variable ScheckResultCode?

 

Joey_z_1-1747891492010.png

BR

Joey

 

0 件の賞賛
返信
1,801件の閲覧回数
Harish_R
Contributor III

Hi @Joey_z 

image.png

 that result is still NOT_OK 

 

BR,

Harish R

 

0 件の賞賛
返信
1,673件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi,

Thank you for your reply.

You should view the test results by observing the variable ScheckResultCode. The sCheck_ExecuteStartupTests is a function responsible for performing some tests at startup.

BR

Joey

0 件の賞賛
返信