FDIR

Description

In this documents possible faults should be adressed and anaylsed in their consequences and possible solutions.

Faults

SEU in flash memory

Possible problems:

• no sign of error (SEU in usused part of memory),
• faulty calculations (SEU in constant part),
• not executing part of the code correctly,
• total loss of subsystem (e.g. processor get stuck, not responding to any command)

Mitigation:

• some kind of bootloader which have smaller memory footprint (probablity of failure is much lower) which will load data from external memory (flash/fram) with some voting (e.g. majority out of 5).

SEU in sram memory

Possible problems:

• no sign of error (SEU in usused part of memory),
• faulty calculations (invalidating calculations),
• stack corruption,
• processor hangs, gets into inifinite loop etc

Mitigation:

• watchdog should periodically check if processor is alive,
• in case of "wrong" calculations processor should be reset to recalculate everything
• processor should be rebooted every TBD hours to prevent errors to build up

Notes: in AVR devices user code cannot access flash memory - no in case of sram corruption flash will be untouched.

SEU in AVR control register

Possible problems:

• no sign of error (SEU in usused part of memory),
• peripherials won't respond/will respond with incorrect results,
• processor hangs, gets into inifinite loop etc

Mitigation:

• watchdog should periodically check if processor is alive,
• in case of "wrong" calculations processor should be reset to recalculate everything
• processor should be rebooted every TBD hours to prevent errors to build up

Notes: