AES - Automotive Embedded Systems

Transcription

1 Coordinating unit: Teaching unit: Academic year: Degree: ECTS credits: ETSETB - Barcelona School of Telecommunications Engineering ENTEL - Department of Network Engineering MASTER'S DEGREE IN TELECOMMUNICATIONS ENGINEERING (Syllabus 2013). (Teaching unit Optional) MASTER'S DEGREE IN ELECTRONIC ENGINEERING (Syllabus 2013). (Teaching unit Optional) 5 Teaching languages: English Teaching staff Coordinator: de la Cruz Llopis, Luis J. Others: Moreno Arostegui, J. Manuel Madrenas Boadas, Jordi Franch Gutiérrez, Xavier Abella Ferrer, Jaume Teaching methodology Lectures Application classes Laboratory classes Laboratory sessions Individual work (not presential) Group work (not presential) Short-answer tests (Control) Short-answer tests (Test) Extended-response tests (Final Exam) Learning objectives of the subject Nowadays there is an evident evolution in the automotive sector towards vehicles that make an exhaustive use of electronic and communications technologies. Vehicles with all kinds of sensors and actuators (temperature, proximity, cameras, driving assistance, parking,...), long and short range communications technologies (4G, 5G, RFID/NFC, WiFi,...) and its associated services (Internet access, infotainment, teleoperation,...) make driving more comfortable, reliable and safe. To provide vehicles with all these new functionalities, there are many companies, both national and international, which focus their efforts on the production of systems that allow vehicle factories to be at the vanguard in the market. These companies are currently an attractive destination for telecommunications and computer engineers with special interest in the development and programming of embedded systems. This subject arises from the need to offer a first specialization for engineers who wish to guide their professional career towards the contribution in the development of these electronic communication systems. It has been designed in collaboration between research groups from different departments of the UPC and working groups of leading companies in the electronics sector for the automotive industry. Its contents include aspects related to embedded software development, real-time operating systems, communication buses and reference architectures. In addition, the processes related to the evaluation, verification, validation and functional safety of the developed software are studied. As a result, an interesting preliminary training is offered that allows graduates to enter with guaranteed success in this exciting industry. 1 / 8

2 Study load Total learning time: 125h Hours large group: 26h 20.80% Hours small group: 13h 10.40% Self study: 86h 68.80% 2 / 8

3 Content 1. Introduction Learning time: 0h 45m Theory classes: 0h 45m 1. Introduction Opening The V Model Emerging concepts Embedded software and telematics Functional safety, software architecture and testing Process assessment Structure of the course. Practicalities. 2. Embedded software. Learning time: 8h 30m Theory classes: 8h 30m 2.1. Embedded software design principles Algorithm design and coding practices Advanced I/O techniques DMA-handled I/O Interrupt-handled I/O MISRA-C design rules and good practices RTOS Introduction Kernel Tasks, multitasking and multithreading Scheduler Inter-process communication The CAN communication protocol Introduction Bus topology CAN messages Physical layer Bit Timing Error handling Protocol versions (2.0A, 2.0B, Open) Laboratory sessions Introduction to the laboratory and the design tools Design of a standalone software application Design of a software application based on an RTOS. 3 / 8

4 3. Autosar. Learning time: 6h 15m Theory classes: 6h 15m 3.1. Reference architectures and their role in software Systems AUTOSAR: a software reference architecture for the automotive industry Goals Chronology. Releases Partnership Background Automotive communication protocols: CAN, LIN, Flexray Diagnostics. UDS ISO Adaptation of UDS to CAN Constituent elements of AUTOSAR The layers Basic software. Dependencies Runtime Environment and its configuration Application layer The Virtual Functional Bus Interfaces AUTOSAR methodology Defining the architecture Development processes Software production. Code generation (model-based) Data interchange Tool support Conclusions. 4 / 8

5 4. Telematics. Learning time: 7h 45m Theory classes: 7h 45m 4.1. V2X communications Intelligent Transportation Systems (ITS) ETSI Architecture Application Layer Facilities Layer Basic Services and Messages Networking and Transport Layer Basic Transport Protocol (BTP) GeoNetworking Acces Layer IEEE p / ITS-G Cellular V2X Embedded Linux on automotive telematics Linux kernel architecture: essential points for adapting the kernel to a custom embedded platform Techniques for right-sizing the system to meet project constraints Yocto Distribution: Cross development environment for embedded projects Bootloaders. Focus on U-Boot and Android Fastboot Flash storage and file systems Developing and debugging applications for the embedded system Laboratory sessions Develop a Linux application for launching and interact with a Qualcomm Linux modem. 5 / 8

6 5. Verification and validation. Learning time: 6h 15m Theory classes: 6h 15m 5.1. Introduction Definition and importance of Software Quality Assurance & Testing Managing risks Testing in Agile & DevOps Software testing economics Test levels (unit testing, system testing, integration testing,...) Ways of testing software The seven principles of testing Software testing levels and responsibilities Software testing types Test methods (black box, white box, grey box,...) V-model and test methods The testing lifecycle Testing Management Defect Management Test cases design Practicing the testing lifecycle (test case design, test case execution and defect reporting) Test automation Introduction to test automation Towards an acceptance test automation framework Recording vs. Layered automation Basic concepts for JUnit+Selenium automation Automated testing for APIs Practicing test cases automation (the 10-levels challenge) Automated testing in mobile devices (demo) Test-driven development The concept of Test-Driven Development Test-First & Acceptance Test-Driven Development Practicing TDD through a small example Conclusions Conclusions. 6 / 8

7 6. Functional safety. Learning time: 5h 30m Theory classes: 5h 30m 6.1. Introduction What is Functional Safety Functional Safety and Product Safety / Cybersecurity Functional safety standards and definitions ISO26262 overview Safety Concepts Hazard & Risk Analysis and determination of ASILs System-level architectures & examples Software safety Safety Requirements Sw Architectural descriptions for functional safety Patterns in Sw Architecture, E-Gas koncept Freedom from Interference concepts Safety Analysis at the sw level Autosar & Functional Safety Software safety process overview. 7. SPICE methodology. Learning time: 4h Theory classes: 4h 7.1. Introduction Process Maturity Models. CMM. SPICE Automotive SPICE Process Groups Work Products Maturity Levels Conclusions. Qualification system - This course has evaluation of theory (80%) and of laboratory (20%). - The theoretical grade consists of a midterm control (40% of the grade of theory) and a final exam (60% of the grade of theory). - The laboratory grade consists of a laboratory control (80% of the laboratory grade) and a subjective grade assigned by the professor (20% of the laboratory grade). 7 / 8

8 Bibliography Basic: Skiena, Steven S. The Algorithm Design Manual. Second Edition. Springer, ISBN MISRA C. Guidelines for the Use of the C Language in Critical Systems. Misra, ISBN ISBN International Organization for Standardization. ISO/DIS Road Vehicles - Functional Safety ETSI. EN , ITS; Vehicular Communications; GeoNetworking; Part 3: Network Architecture Tim Koomen, Leo van der Aalst, Bart Broekman, Michiel Vroon. TMap Next, for result-driven testing. UTN Publishers, ISBN SPICE. Automotive SPICE Process Reference and Assessment Model [on line]. RELEASE Available on: < AUTOSAR [on line]. Available on: < 8 / 8