Personal tools

Difference between revisions of "HW/SW Safety and Security"

From iis-projects

Jump to: navigation, search
Line 1: Line 1:
 
We are in the processes of creating a top-level information page, in the meantime please continue directly to the specific subsections below.
 
We are in the processes of creating a top-level information page, in the meantime please continue directly to the specific subsections below.
 
== Real-Time Embedded Systems ==
 
Please continue to [[Real-Time Embedded Systems]] if you are interested in designing hardware or writing software for timing predictable embedded systems.
 
 
<!--
 
<!--
 
== Predictable Execution ==
 
== Predictable Execution ==
Line 8: Line 5:
 
Please continue to [[Predictable_Execution]] if you are interested in timing predictable/safety critical embedded systems.  
 
Please continue to [[Predictable_Execution]] if you are interested in timing predictable/safety critical embedded systems.  
 
-->
 
-->
 +
== Real-Time Embedded Systems ==
 +
<!--
 +
Please continue to [[Real-Time Embedded Systems]] if you are interested in designing hardware or writing software for timing predictable embedded systems.
 +
-->
 +
 +
A real-time computer system is a computer system in which the correctness of the system behavior depends not only on the '''logical results''' of the computations, but also on the '''physical instant''' at  which these results are produced. In fact, a real-time system changes its state as a function of physical time.
 +
 +
The  instant  at  which  a  result of a computation must  be  produced  is  called  a  '''deadline'''. If  a  result  has  utility even after the deadline  has  passed, the deadline is classified as a '''soft deadline''', otherwise  it  is  a '''firm deadline'''. When missing a firm  deadline  results in a system failure (e.g. airplane sensor and autopilot systems, spacecrafts and planetary rovers), the deadline is called '''hard deadline'''.
 +
 +
Hence, in real-time systems guarantees must be given on the finishing of computations before a deadline. This affects the design of hardware (processors, caches, interconnects, peripherals, interrupts, ...) and software stack (operating system, scheduling, compiler guarantees). Key concepts are '''spatial and temporal isolation''' of components, and ''' architecture's predictability'''
  
 
== Cryptography ==
 
== Cryptography ==

Revision as of 15:06, 10 January 2022

We are in the processes of creating a top-level information page, in the meantime please continue directly to the specific subsections below.

Real-Time Embedded Systems

A real-time computer system is a computer system in which the correctness of the system behavior depends not only on the logical results of the computations, but also on the physical instant at which these results are produced. In fact, a real-time system changes its state as a function of physical time.

The instant at which a result of a computation must be produced is called a deadline. If a result has utility even after the deadline has passed, the deadline is classified as a soft deadline, otherwise it is a firm deadline. When missing a firm deadline results in a system failure (e.g. airplane sensor and autopilot systems, spacecrafts and planetary rovers), the deadline is called hard deadline.

Hence, in real-time systems guarantees must be given on the finishing of computations before a deadline. This affects the design of hardware (processors, caches, interconnects, peripherals, interrupts, ...) and software stack (operating system, scheduling, compiler guarantees). Key concepts are spatial and temporal isolation of components, and architecture's predictability

Cryptography

Please continue to Cryptography if you are interested in cryptographic hardware.

Fault Tolerance

Please continue to Fault Tolerance if you are interested in circuits tolerant to radiation-induced soft errors.

Who are we

Robert balas.jpeg

Robert Balas

Aottaviano.jpg

Alessandro Ottaviano

Michaero PULP.jpeg

Michael Rogenmoser

Nwistoff face pulp team.JPG

Nils Wistoff


Projects

All projects are annotated with one or more possible project types (M/S/B/G) and a number of students (1 to 3).

  • M: Master's thesis: 26 weeks full-time (6 months) for one student only
  • S: Semester project: 14 weeks half-time (1 semester lecture period) or 7 weeks full-time for 1-3 students
  • B: Bachelor's thesis: 14 weeks half-time (1 semester lecture period) for one student only
  • G: Group project: 14 weeks part-time (1 semester lecture period) for 2-3 students

Usually, these are merely suggestions from our side; proposals can often be reformulated to fit students' needs.

Available Projects


Projects In Progress


Completed Projects