AN4124

Fault: CF and NCF

Doc ID 023294 Rev 2

9/32

4

Fault: CF and NCF

The FAULT state has a higher priority than the ALARM state, in the case of concurrent fault

events (critical and non-critical) that occur in the NORMAL state. In case of concurrent

critical faults, the fault reaction corresponds to the worst case (for example, a long functional

reset is asserted if it has been programmed).

The ALARM to FAULT state transition occurs if a fault (unmasked and with time-out

disabled) is asserted in the ALARM state.

Any critical fault (programmed to react with a hard or soft reaction) that occurs when the

FCCU is already in the FAULT state causes an immediate hard or soft reaction (long or short

functional reset).

The ALARM to NORMAL state transition occurs only if all the non-critical faults (including

the faults that have been collected after entry to ALARM state) have been cleared (SW or

HW recovery). Otherwise the FCCU will remain in the ALARM state.

The FAULT to NORMAL state transition occurs only if all the critical and non-critical faults

(including the faults that have been collected after entry to FAULT/ALARM state) have been

cleared (SW or HW recovery). Otherwise the FCCU remains in the FAULT state (if any

critical fault is still pending) or returns to the ALARM state (if any non-critical fault is still

pending and the time-out has not elapsed).

4.1

Critical fault (CF)

Below is the CF table:

Table 2.

Critical fault

Critical fault

Source

Signal

Short/long/non

e default func.

reset

Set/clear

injection

CF[0]

RCCUO[0]

rcc_out

Long

X

CF[1]

RCCU1[0]

rcc_out

Long

X

CF[2]

RCCUO[1]

rcc_out

Long

X

CF[3]

RCCU1[1]

rcc_out

Long

X

CF[4]

RCCUO[2]

rcc_out

Long

X

CF[5]

RCCU1[2]

rcc_out

Long

X

CF[6]

RCCUO[3]

rcc_out

Long

X

CF[7]

RCCU1[3]

rcc_out

Long

X

CF[8]

RCCUO[4]

rcc_out

Long

X

CF[9]

RCCU1[4]

rcc_out

Long

X

CF[10]

RCCUO[5]

rcc_out

Long

X

CF[11]

RCCU1[5]

rcc_out

Long

X

CF[12]

RCCUO[6]

rcc_out

Long

X