S32K312 SWT0 interrupt

[jhuang1]

Hello,

   Two products among the whole 700+ products in my project encounterred a problem, the SWT0 interrupt in the two product continue to trigger after the SWT0 had been disabled. I have to disable the  SWT interrupt instead of just disabling the SWT0. Is there a possibility that the SWT interrupt run out of control? 

[danielmartynek]

Hello @jhuang1,

Can you share all the SWT register values while it is in the interrupt routine?

Is the TIF flag set while WEN = 0?

Thank you,

Regards,

Daniel

[jhuang1]

The main registers value in the interrupt routine:

CR:0xFF000006

IR:1

TO:0x100

WN:0

[danielmartynek]

Hi @jhuang1,

Does it trigger periodically as usual or does the flag stays continuously asserted?

Such unpredictable behavior can be expected if the system clock configuration is incorrect.

Is it configured precisely to one of the clock options listed in the RM?

E.g. Table 151. Option A - High Performance mode (CORE_CLK @ 160 MHz).

Thank you

[jhuang1]

The flag stays continuously asserted, and the clock should be fine, the other functions such as uart or spi works fine after the swt interrupt being disabled. There should be some other errors occure if clock configuration is incorrect. 

[danielmartynek]

Hi @jhuang1,

I understand the flag cannot be cleared.

I have been trying to replicate it but with no luck.

Can you make sure the flag is cleared right before the SWT is disabled?

Thank you

[jhuang1]

I think there is no need to call an interrupt flag clear function in the ISR， and i have read the pendding  interrupt flag register, it represent zero at the point of SWT.