SAF sCheck SWT_0 and FCCU_NCF test, s32k322

[Marekp]

Hi,
I am experiencing issues with two tests: SWT0 and FCCU_NCF.

---

1. SWT0 Start-up Test:

• The SWT0 Start-up test returns ERROR (0xFFFFFFFF).

• The SWT module is properly disabled before starting the test (SWT->CR.WEN = 0).

• When I use the Wdg_Driver callback, the test fails.

• However, if I manually configure the interrupt (bypassing the SWT driver), the test passes.

Here are the values from the sCheck driver configuration:

• STM Frequency (Hz): 40,000,000

• FXOSC Frequency (Hz): 24,000,000

• FIRC Frequency (Hz): 48,000,000

• CMU Bus Clock Frequency (Hz): 16,000,000

The CMU_FC and CMU_FM tests pass successfully in start-up, runtime, and shutdown phases.

Detailed results:

• sCheck_Swt_RunTestWithIrq → returns u32Signature = 0xA84D0001

• sCheck_Swt_CounterTest → returns u32Signature = 0x48E478

From sCheck_ExecuteStartupTests:

• Signature without using the callback: 0x5F1F0000

• Signature with the callback: 0x5F1F0001

The overall test result is SCHECK_TEST_FAIL (0x0000FFFFUL).



2. 

1. FCCU_NCF Test:

• The FCCU_NCF test returns ERROR (0xFFFFFFFF).

• Where should I look for the root cause?
  (Note: The eMCEM module is not initialized before the start-up tests — sCheck internally configures the necessary FCCU registers.)

Reported signature: 0x20C80000.

The overall test result is SCHECK_TEST_ERROR (0xFFFFFFFFUL).

 

[petervlna]

Hello,

I was talking with author of the tests.

Looks like for FCCU test there is signature error. This is now know issue.

Also he will have a look at SWT test and interrupts and feedback me.

I will inform you ASAP.

Best regards,

Peter

[petervlna · Accepted solution]

Hello,

I see you are already in touch with the Radoslav on safe assurance community.

It is better to discuss the questions there as he can give you most accurate answers on your SAF related questions.

https://community.nxp.com/t5/S32K/sCheck-Test-CMU-FM-ISR-problem/m-p/2091258#M48415

Best regards,

Peter

[petervlna]

Hello,

I see you are using some kind of drivers or it is your own code?

If it is drivers, could you specify which drivers you have used?

Best regards,

Peter

[Marekp]

And SAF -version 1.0.5

[Marekp]

Hi  
of course  ISR (Swt_Ip_Irq.c), Swt_Ip_IrqHandler() - 

/*==================================================================================================

*   Project              : RTD AUTOSAR 4.7

*   Platform             : CORTEXM

*   Peripheral           : Swt

*   Dependencies         : none

*

*   Autosar Version      : 4.7.0

*   Autosar Revision     : ASR_REL_4_7_REV_0000

*   Autosar Conf.Variant :

*   SW Version           : 4.0.0

*   Build Version        : S32K3_RTD_4_0_0_P20_D2403_ASR_REL_4_7_REV_0000_20240315

[Marekp]

Regarding the SWT_0 test, I believe the issue is related to the checking and clearing of the interrupt flag: pSwt->IR.B.TIF = 1U; The interrupt, which is defined in the Swt_Ip_Irq.c driver file, calls the function Swt_Ip_IrqHandler(), where the TIF flag is cleared before the callback is invoked.

Given this behavior, I would kindly like to ask for clarification:

According to the AUTOSAR architecture, should this interrupt be handled entirely by the MCAL driver,
or should it be implemented outside of the MCAL, especially in the context of safety mechanisms such as sCheck???