sCheck XRDC test - time execution, s32k322 SAF 1.0.5

[Marekp]

Hello, i have problem with sCheck test XRDC. In Scheck manual is information that XRDC test in worts case shall be executed in 43952us. On my platform s32k322 i have time 180ms.

sCheck_ExecuteStartupTests return = 0 this mean TEST is pass. 

Why time execution is too long ? Where i should looking for isiue ? 

1. Start Test

2. Test done

[danielmartynek]

Hi @Marekp,

In the User Manual, the following statement is provided:

"The WCETs below were estimated for set of tests executed on the Master Safety Core, which was running at maximum allowed clock frequency with the instruction and data caches enabled. For the detailed information about the measured test execution times please refer to the profiling reports, which are part of the S32K3 SAF Quality Pack."

What is the configured system clock frequency and cache setup in your current project?

Have you observed similar discrepancies in WCET results when running sCheck on other test targets, aside from XRDC?

Regards,

Daniel

[Marekp]

Hello, frequency of CPU is setting on 160Mhz. And no, i didn't observe problems with others tests but...
I check XRDC  codes from Your library and under 42ms is testing one DOMAIN, so for 3 domains we got ~100 - 120ms. 
I think that this IMPORATNAT information shall be added to MANUAL because it can be confusing.

On screen You can see, that every domain i testing by 35ms

Red dots mean start and stop test on domain 0,1,2.

[Marekp]

I check only when XRDC is enabling in sCheck configuration and time only for XRDC test = 0.139561908s. This is normal ?