S32R274 SWT TIF Bit not set on SWT timeout

[lakshmikanth]

Hi NXP, 

Does NXP supply 'FCCU' MCAL plugin for EB Tresos. I'm working on S32R274 based autosar MCAL project. And I'm unable to verify RESET action on SWT Timeout. Only 'INTERRUPT' on SWT Timeout works fine.

Is it that: Integrating 'Legacy FCCU configuration' code in to MCAL code the only solution or it can be handled in some other way?

2) Does SWT_TIF bit act as trigger to FCCU ?

Your valuable suggestions are much appreciated. 

Thanks...!

#s32r274‌ #swt‌ #fccu‌ #mcal‌ 

[petervlna · Accepted solution]

Hi,

S32R274 MCAL is developed according to ISO26262 standard.

part of it is also Mcem driver which handles FCCU periphery.

SWT_TIF acts at a trigger for FCCU. When TIF is set it will poll a fault reporting line to FCCU.

Peter

One Tip: If you have already set TIF and the reporting line to FCCU is polled. You have no other choice then reset to clear SWT flag from FCCU NCFSx register.

[lakshmikanth]

Hi Peter,

Thank you for the valuable information.

I'm trying it now. Will get back to you soon on the status.

Regards,

Lakshmi Kanth.

[lakshmikanth]

Hi Peter,

1) As per your suggestion I've configured "MCEM Module" to enable "SWT0_TimeOut Reset" request configuration of FCCU. I have integrated the module to my MCAL Project.

2) During initialization call I.e inside "MCEM_Init()" call, upon execution of the below instruction: (in T32_LauterBach)

             /* Clear all pending faults (W1C) */

             REG_WRITE32(FCCU_NCF_S_ADDR32(uBank),  u32ReadBack);

the "CTRL.OPS" goes to "Aborted" state. I think there is not much in 'MCEM configuration' that I may configure wrongly.

3) So, please let me know the possible reason for this "Aborted" state of FCCU.

Also, same was the case when I previously tried with the "FCCU_Init() function" from your reference code i.e 

"S32R274_Watchdog_example-S32DS" I.e after execution of the OP-1 instruction shown below and during 'while()' the "CTRL.OPS" goes to "Aborted" state.

/* enter config state - OP1 */
FCCU.CTRL.R = 0x1;

/* Verify if state change was sucessful */
while (FCCU.CTRL.B.OPS != 0x3); //operation status successful

4) So, please let me know on this issue (Currently MCAL Code is my priority than legacy) code.

Thanks in advance...! 

#fccu‌ #s32r247‌ #peter vlna‌ #SWT0TimeoutResetGeneration‌ #mcal‌

[petervlna]

I am not familiar with MCAM, however I am expert in FCCU.

3. FCCU report aborted state if its configuration watchdog expires:

a) you step in debugger in while you are in FCCU CONFIG mode.

b) when you execute operation on other module then FCCU while you are in FCCU CONFIG mode

c) when you are too long in FCCU CONFIG state and your FCCU watchdog expired

d) when you ask for mode transtion to CONFIG mode with active faults in NCFSx registers.

For more details you can check my application note on FCCU configuration:

https://www.nxp.com/docs/en/application-note/AN5284.pdf?fsrch=1&sr=2&pageNum=1 

Peter