The course combines traditional classroom lectures with supervised exercise sessions, providing students with the opportunity to apply the concepts learned in practical scenarios and engage in discussions with the instructor. Additionally, certain topics within the course include dedicated lab sessions, allowing students to observe the practical implementation of related technologies and reinforce their understanding of the concepts covered in the lectures. The course is divided into two main components: classroom lectures and exercises, which account for 6 CFU (Crediti Formativi Universitari), and laboratory sessions, which contribute 2 CFU. Additionally, students will have the opportunity to be tutored for a total of 2 CFU.

Students will acquire knowledge, varying in depth depending on the specific topic, as well as skills and a profound comprehension of the mechanisms and motivations underlying the following technologies and solutions: - Concept of an embedded system. - Understanding of the development tools for embedded systems: cross-compiler, emulator, debug tools, profiling tools, and virtualization tools. - Concept of real-time embedded systems. - Understanding of examples of operating systems for embedded systems. - Skill for developing modules for communication with ad-hoc hardware components. - Understanding security issues in the embedded domain.

- Ability to develop programs in C language. - Knowledge of the architecture of computer-based systems: in particular, knowledge of processor architecture and memory organization. - Knowledge of the interrupt mechanisms and basic knowledge of assembly programming.

Introduction to Embedded Systems (0.5 CFU) - Classification with respect to desktop systems. - Memory technology device. Development tools (0.5 CFU) - Cross-compiler. - Emulator. - Debugger. - Profiler. - Virtual platforms. Operating Systems for Embedded Systems (3 CFU) - Real-time and process scheduling. - Analysis of the architecture and services offered by operating systems for embedded: process scheduler, micriumOS, OSEK/VDX, Embedded Linux. - Anatomy of an operating system for embedded systems. Operating System Security (1 CFU) - HW/SW attack models - Countermeasures Programming of an embedded OS (2 CFU): - I/O management and device drivers. - Use of an evaluation board. - Building an OS for embedded systems: how to use development tools. - Design and development of device drivers for custom devices. Advanced tools for debugging and profiling embedded systems (1 CFU)

The course combines traditional classroom lectures with supervised exercise sessions, providing students with the opportunity to apply the concepts learned in practical scenarios and engage in discussions with the instructor. Additionally, certain topics within the course include dedicated lab sessions, allowing students to observe the practical implementation of related technologies and reinforce their understanding of the concepts covered in the lectures. The course is divided into two main components: classroom lectures and exercises, which account for 6 CFU (Crediti Formativi Universitari), and laboratory sessions, which contribute 2 CFU. Additionally, students will have the opportunity to be tutored for an amount of 2 CFU.

Notes provided by the teacher. Additional reading: A. Berger Embedded Systems Design: An Introduction to Processes, Tools, and Techniques CMP Books, 2001, ISBN-10: 1-57-820073-3 Silbershatz A., Galvin. P., Gagne G. Operating Systems 8th Edition, Wiley, 2009, ISBN: 978-0-470-12872-5

Slides; Esercizi; Esercizi risolti; Esercitazioni di laboratorio; Esercitazioni di laboratorio risolte;

Modalita di esame: Elaborato progettuale in gruppo; Prova scritta in aula tramite PC con l'utilizzo della piattaforma di ateneo;

Exam: Group project; Computer-based written test in class using POLITO platform;

... The examination consists of the following two components: PART 1.1: This part consists of a written test covering all class topics. The test may include various question types, such as open-ended and multiple-choice questions, exercises focusing on specific topics, and the development of small programs. Each question is assigned a score, which is announced during the exam. The exam is delivered on a computer. The maximum score achievable in this part is 18/30, and the test duration is 60 minutes. The threshold to pass this part is 10/30. PART 1.2 (required for students who do not opt for the group project): This part consists of programming exercises on the topics covered during the course. The exam is delivered on a computer and requires the use of the open-source development tools explained in class. The maximum score achievable in this part is 12/30, and the test duration is 60 minutes. PROJECT — optional and substituting PART 1.2 The project emphasizes the application of concepts learned in class and enhances students’ ability to independently find documentation and acquire new skills beyond the scope of the course. Each year, a set of topics will be assigned. Projects MUST be carried out in teams. Once the project is completed, students must present it during an oral exam session, highlighting each team member’s contribution to the results. The oral exam consists of a 20-minute presentation, during which all team members must participate and contribute to the work presented. The presentation will be followed by questions about the developed work, aimed at assessing the contributions of all team members to the project. Finally, a live demo of the developed project will be possible whenever applicable. The project aims to assess: - The student’s proficiency in implementing and developing embedded applications. - The efficiency of the implementation. - The student’s ability to work effectively in a team. - The student’s presentation skills. - The individual contribution of each student to the project. The maximum score in this part is 14/30. The final grade is determined as follows: OPTION 1: exam without project Final grade = PART 1.1 + PART 1.2 OPTION 2: exam with project Final grade = PART 1.1 + PROJECT The highest distinction, “Laude,” is awarded if the total grade equals 32. PART 1.1 and PART 1.2 must be completed in the same attempt, while the project can be discussed at a different time. However, the project must be completed within one year, before the start of the next course edition. The project is assigned during the first academic year in which the student attends the course and cannot be attempted again in subsequent years. If the project is not delivered on time, the student must retake the entire exam under OPTION 1. Any minor changes to these policies or procedures will be communicated to the students in a timely manner.

Gli studenti e le studentesse con disabilita o con Disturbi Specifici di Apprendimento (DSA), oltre alla segnalazione tramite procedura informatizzata, sono invitati a comunicare anche direttamente al/la docente titolare dell'insegnamento, con un preavviso non inferiore ad una settimana dall'avvio della sessione d'esame, gli strumenti compensativi concordati con l'Unita Special Needs, al fine di permettere al/la docente la declinazione piu idonea in riferimento alla specifica tipologia di esame.