Safety Element out of Context (SEooC) Assessment according to ISO 26262 (2020)
ฝัง
- เผยแพร่เมื่อ 3 ก.ค. 2024
- ==========================================
FREE WEBINAR - ISO/SAE 21434 - AUTOMOTIVE CYBERSECURITY
www.lordsofcarhackers.com/web...
==========================================
In this episode, Our CEO, Dr. Hasan Ibne Akram has an interesting discussion with Praveen Suvarna, Head of Department - Embedded Development & Autosar at Matrickz GmbH. They talk about Safety Element out of Context (SEooC) Assessment according to ISO 26262.
#ISO26262 #SEooC #ISO21434 #AutonomousVehicles - วิทยาศาสตร์และเทคโนโลยี
FREE WEBINAR - ISO/SAE 21434 - AUTOMOTIVE CYBERSECURITY
www.lordsofcarhackers.com/webinar
Good High level bird eye view of FuSA. Functional safety application (SWC) are guarded with safety mechanism of MCU. Which needs the detailed understanding of MCU as well ( safety and user manual ). Until you make your hand dirty we can learn only theory of FuSA. Real understanding come during the implementation part of FFI, QM and ASIL partitions, RAM, Core, Flash test, Stack integrity, OS safe interrupts, register supervision, program flow monitoring, E2E , Safe state apart from applications algorithms. One thing for sure no system is 100% ASIL complaint there always be Rational or TRA ( technical risk analysis ) to make it compliant. Thanks for the video informative!
Really good video! I miss a bit of graphical description of the explanations provided but still it was a really good video!
When will you do a video for SEooC for HW? :D
Well explained!
Well explained, Thank you very much.
Great talk really interesting
Great talk!!
Best video
A very interesting video. Thanks. Having in mind to do the MCAL SeooC, when you speak about assumptions, could you give hints in such sense. An example which kind of assumptions for ADC, SPI, etc etc....Just to understand the boundaries. Many thanks.
Hi Francesco, Thanks for your comment. Just to name few:
• It is assumed that the MCAL is integrated with a safe OS.
• The MCAL user shall not write or read directly the HW registers that are belonging to the peripherals handled by the MCAL drivers.
• Critical section protection should not be switched off to avoid software misbehavior.
Why do we start the SEooC at the technical safety concept level (with ASIL assumptions) instead of safety concept level where HARA will cover as many potential malfunctions as possible and also help us in the derivation of our safety goal before the development phase?
Hi Aniekan Inyang, Thanks for your question. As we are mainly discussing a software SEooC, the top-level assumptions would normally be system-level assumptions. If the SEooC is a system, then the assumptions about the item definition, the safety goals of the item can be made.
@@praveensuvarna5158 Thank you for your response. one more question: Are assumptions for item definition and safety goals the only approach to this; if no, can you kindly state other approach(es)? Thank you.