ºÝºÝߣshows by User: AndreiKholodnyi / http://www.slideshare.net/images/logo.gif ºÝºÝߣshows by User: AndreiKholodnyi / Tue, 25 May 2021 10:33:36 GMT ºÝºÝߣShare feed for ºÝºÝߣshows by User: AndreiKholodnyi TSN apps running on VxWorks RTOS as a KVM guest at the intelligent edge /slideshow/tsn-apps-running-on-vxworks-rtos-as-a-kvm-guest-at-the-intelligent-edge/248524634 tsnappsrunningonvxworksrtosasakvmguestattheintelligentedge-210525103336
Time-sensitive networking (TSN) is taking off in just about every market. Robotic arms, motion controller, even vehicles and automobiles have a need for both time sync (coordinated events) and timeliness (timely events) to improve existing real-time capabilities. Combining TSN with the real-time behavior of VxWorks operating system can enable developers to design distributed over deterministic network real-time control systems. Join us for a demonstration and live QA with our expert Andrei. He will show you how to run a TSN application on VxWorks as a KVM (Kernel-based Virtual Machine) guest in parallel with the best effort Linux OS on the same System-on-Chip (SoC). We will feature the decoupling of the control functionality from the sensing and actuation functionality, which usually run together on the embedded device, and move the control part to the intelligent edge. ]]>
Time-sensitive networking (TSN) is taking off in just about every market. Robotic arms, motion controller, even vehicles and automobiles have a need for both time sync (coordinated events) and timeliness (timely events) to improve existing real-time capabilities. Combining TSN with the real-time behavior of VxWorks operating system can enable developers to design distributed over deterministic network real-time control systems. Join us for a demonstration and live QA with our expert Andrei. He will show you how to run a TSN application on VxWorks as a KVM (Kernel-based Virtual Machine) guest in parallel with the best effort Linux OS on the same System-on-Chip (SoC). We will feature the decoupling of the control functionality from the sensing and actuation functionality, which usually run together on the embedded device, and move the control part to the intelligent edge. ]]> Tue, 25 May 2021 10:33:36 GMT /slideshow/tsn-apps-running-on-vxworks-rtos-as-a-kvm-guest-at-the-intelligent-edge/248524634 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) TSN apps running on VxWorks RTOS as a KVM guest at the intelligent edge AndreiKholodnyi Time-sensitive networking (TSN) is taking off in just about every market. Robotic arms, motion controller, even vehicles and automobiles have a need for both time sync (coordinated events) and timeliness (timely events) to improve existing real-time capabilities. Combining TSN with the real-time behavior of VxWorks operating system can enable developers to design distributed over deterministic network real-time control systems. Join us for a demonstration and live QA with our expert Andrei. He will show you how to run a TSN application on VxWorks as a KVM (Kernel-based Virtual Machine) guest in parallel with the best effort Linux OS on the same System-on-Chip (SoC). We will feature the decoupling of the control functionality from the sensing and actuation functionality, which usually run together on the embedded device, and move the control part to the intelligent edge. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/tsnappsrunningonvxworksrtosasakvmguestattheintelligentedge-210525103336-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Time-sensitive networking (TSN) is taking off in just about every market. Robotic arms, motion controller, even vehicles and automobiles have a need for both time sync (coordinated events) and timeliness (timely events) to improve existing real-time capabilities. Combining TSN with the real-time behavior of VxWorks operating system can enable developers to design distributed over deterministic network real-time control systems. Join us for a demonstration and live QA with our expert Andrei. He will show you how to run a TSN application on VxWorks as a KVM (Kernel-based Virtual Machine) guest in parallel with the best effort Linux OS on the same System-on-Chip (SoC). We will feature the decoupling of the control functionality from the sensing and actuation functionality, which usually run together on the embedded device, and move the control part to the intelligent edge.
TSN apps running on VxWorks RTOS as a KVM guest at the intelligent edge from Andrei Kholodnyi
]]> 468 0 https://cdn.slidesharecdn.com/ss_thumbnails/tsnappsrunningonvxworksrtosasakvmguestattheintelligentedge-210525103336-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 How to cross compile ROS2 distro by taken VxWorks RTOS as an example /slideshow/how-to-cross-compile-ros2-distro-by-taken-vxworks-rtos-as-an-example/236471094 howtocross-compileros2distrobytakenvxworksrtosasanexample-200701132349
Even Open Robotics provides pre-built ROS 2 packages for multiple platforms, very often target software and hardware differ from the default one and a cross-compilation becomes a mandatory step: • A different from Linux operating system e.g. VxWorks, QNX, eSol, etc. is deployed on the target hardware • Target hardware (e.g. ARM aarch64) is different from the development host (e.g. Intel x86_64). • Tuning target software for the footprint and performance (e.g. setting -mcpu=cortex-a72 -mfpu=neon-fp-armv8 when building for Raspberry Pi4). • Separating ROS2 host tools (e.g. RViz) from the ROS2 target binaries. This session will explain in detail of how to cross-compile ROS2 distro by taken VxWorks RTOS as an example. Step by step instructions will be given of how to setup a cross-compile development environment, build and deploy ROS2 binaries on the target. As a target QEMU ARM will be used on the Desktop PC.]]>
Even Open Robotics provides pre-built ROS 2 packages for multiple platforms, very often target software and hardware differ from the default one and a cross-compilation becomes a mandatory step: • A different from Linux operating system e.g. VxWorks, QNX, eSol, etc. is deployed on the target hardware • Target hardware (e.g. ARM aarch64) is different from the development host (e.g. Intel x86_64). • Tuning target software for the footprint and performance (e.g. setting -mcpu=cortex-a72 -mfpu=neon-fp-armv8 when building for Raspberry Pi4). • Separating ROS2 host tools (e.g. RViz) from the ROS2 target binaries. This session will explain in detail of how to cross-compile ROS2 distro by taken VxWorks RTOS as an example. Step by step instructions will be given of how to setup a cross-compile development environment, build and deploy ROS2 binaries on the target. As a target QEMU ARM will be used on the Desktop PC.]]> Wed, 01 Jul 2020 13:23:49 GMT /slideshow/how-to-cross-compile-ros2-distro-by-taken-vxworks-rtos-as-an-example/236471094 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) How to cross compile ROS2 distro by taken VxWorks RTOS as an example AndreiKholodnyi Even Open Robotics provides pre-built ROS 2 packages for multiple platforms, very often target software and hardware differ from the default one and a cross-compilation becomes a mandatory step: • A different from Linux operating system e.g. VxWorks, QNX, eSol, etc. is deployed on the target hardware • Target hardware (e.g. ARM aarch64) is different from the development host (e.g. Intel x86_64). • Tuning target software for the footprint and performance (e.g. setting -mcpu=cortex-a72 -mfpu=neon-fp-armv8 when building for Raspberry Pi4). • Separating ROS2 host tools (e.g. RViz) from the ROS2 target binaries. This session will explain in detail of how to cross-compile ROS2 distro by taken VxWorks RTOS as an example. Step by step instructions will be given of how to setup a cross-compile development environment, build and deploy ROS2 binaries on the target. As a target QEMU ARM will be used on the Desktop PC. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/howtocross-compileros2distrobytakenvxworksrtosasanexample-200701132349-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Even Open Robotics provides pre-built ROS 2 packages for multiple platforms, very often target software and hardware differ from the default one and a cross-compilation becomes a mandatory step: • A different from Linux operating system e.g. VxWorks, QNX, eSol, etc. is deployed on the target hardware • Target hardware (e.g. ARM aarch64) is different from the development host (e.g. Intel x86_64). • Tuning target software for the footprint and performance (e.g. setting -mcpu=cortex-a72 -mfpu=neon-fp-armv8 when building for Raspberry Pi4). • Separating ROS2 host tools (e.g. RViz) from the ROS2 target binaries. This session will explain in detail of how to cross-compile ROS2 distro by taken VxWorks RTOS as an example. Step by step instructions will be given of how to setup a cross-compile development environment, build and deploy ROS2 binaries on the target. As a target QEMU ARM will be used on the Desktop PC.
How to cross compile ROS2 distro by taken VxWorks RTOS as an example from Andrei Kholodnyi
]]> 576 0 https://cdn.slidesharecdn.com/ss_thumbnails/howtocross-compileros2distrobytakenvxworksrtosasanexample-200701132349-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Turtlebot3: VxWorks running ROS2 as a real-time guest OS on Hypervisor /slideshow/turtlebot3-vxworks-running-ros2-as-a-realtime-guest-os-on-hypervisor/229599516 vxworksrunningros2asareal-timeguestosonhypervisor-200303155130
This presentation provides an example of the mixed-critical ROS2 stack implementation based on VxWorks RTOS, embedded Linux, and hypervisor from Wind River. Turtlebot3 was selected as a robotic demo platform controlled by the SBC (single board computer) that runs a Hypervisor with several guest OS instances. We demonstrate a hardware-agnostic approach by utilizing two different SBC HW platforms: Xilinx-based ARM board and Intel UP2 board. The hypervisor provides a separation of safety from non-safety and real-time from best-effort applications and allows us to build a mixed-critical system using multicore SBCs. One of the guest OSes is VxWorks - very few solutions available on the market which is already fulfilling safety and real-time requirements. ROS2 dashing release and turtlebot3 ROS2 middleware were ported to the VxWorks. On top, we run a collision-avoidance ROS2 application. Embedded Linux partition serves as a communication gateway to the external world and provides an example of a non-critical software stack. We demonstrate that if the non-critical guest OS fails and gets rebooted the safety-critical part still runs and performs its control functions. The source code of this demo is available on lab.windriver.com.]]>
This presentation provides an example of the mixed-critical ROS2 stack implementation based on VxWorks RTOS, embedded Linux, and hypervisor from Wind River. Turtlebot3 was selected as a robotic demo platform controlled by the SBC (single board computer) that runs a Hypervisor with several guest OS instances. We demonstrate a hardware-agnostic approach by utilizing two different SBC HW platforms: Xilinx-based ARM board and Intel UP2 board. The hypervisor provides a separation of safety from non-safety and real-time from best-effort applications and allows us to build a mixed-critical system using multicore SBCs. One of the guest OSes is VxWorks - very few solutions available on the market which is already fulfilling safety and real-time requirements. ROS2 dashing release and turtlebot3 ROS2 middleware were ported to the VxWorks. On top, we run a collision-avoidance ROS2 application. Embedded Linux partition serves as a communication gateway to the external world and provides an example of a non-critical software stack. We demonstrate that if the non-critical guest OS fails and gets rebooted the safety-critical part still runs and performs its control functions. The source code of this demo is available on lab.windriver.com.]]> Tue, 03 Mar 2020 15:51:30 GMT /slideshow/turtlebot3-vxworks-running-ros2-as-a-realtime-guest-os-on-hypervisor/229599516 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) Turtlebot3: VxWorks running ROS2 as a real-time guest OS on Hypervisor AndreiKholodnyi This presentation provides an example of the mixed-critical ROS2 stack implementation based on VxWorks RTOS, embedded Linux, and hypervisor from Wind River. Turtlebot3 was selected as a robotic demo platform controlled by the SBC (single board computer) that runs a Hypervisor with several guest OS instances. We demonstrate a hardware-agnostic approach by utilizing two different SBC HW platforms: Xilinx-based ARM board and Intel UP2 board. The hypervisor provides a separation of safety from non-safety and real-time from best-effort applications and allows us to build a mixed-critical system using multicore SBCs. One of the guest OSes is VxWorks - very few solutions available on the market which is already fulfilling safety and real-time requirements. ROS2 dashing release and turtlebot3 ROS2 middleware were ported to the VxWorks. On top, we run a collision-avoidance ROS2 application. Embedded Linux partition serves as a communication gateway to the external world and provides an example of a non-critical software stack. We demonstrate that if the non-critical guest OS fails and gets rebooted the safety-critical part still runs and performs its control functions. The source code of this demo is available on lab.windriver.com. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/vxworksrunningros2asareal-timeguestosonhypervisor-200303155130-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This presentation provides an example of the mixed-critical ROS2 stack implementation based on VxWorks RTOS, embedded Linux, and hypervisor from Wind River. Turtlebot3 was selected as a robotic demo platform controlled by the SBC (single board computer) that runs a Hypervisor with several guest OS instances. We demonstrate a hardware-agnostic approach by utilizing two different SBC HW platforms: Xilinx-based ARM board and Intel UP2 board. The hypervisor provides a separation of safety from non-safety and real-time from best-effort applications and allows us to build a mixed-critical system using multicore SBCs. One of the guest OSes is VxWorks - very few solutions available on the market which is already fulfilling safety and real-time requirements. ROS2 dashing release and turtlebot3 ROS2 middleware were ported to the VxWorks. On top, we run a collision-avoidance ROS2 application. Embedded Linux partition serves as a communication gateway to the external world and provides an example of a non-critical software stack. We demonstrate that if the non-critical guest OS fails and gets rebooted the safety-critical part still runs and performs its control functions. The source code of this demo is available on lab.windriver.com.
Turtlebot3: VxWorks running ROS2 as a real-time guest OS on Hypervisor from Andrei Kholodnyi
]]> 497 0 https://cdn.slidesharecdn.com/ss_thumbnails/vxworksrunningros2asareal-timeguestosonhypervisor-200303155130-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 ROS2 on VxWorks - one project on Wind River Labs /slideshow/ros2-on-vxworks-one-project-on-wind-river-labs/204647516 ros2onvxworks-oneprojectonwindriverlabs-191211222225
My talk "ROS2 on VxWorks. one Wind River Labs project" at ROS Industrial conference 2019 hits pain points of the ROS Industrial community. Developer journey from the desktop ROS2 development under Ubuntu to the ROS2 embedded software development is the rocky one. Software engineers face difficulties to migrate their ROS2 code from native to the cross-compile environment and tune system for the performance, real-time, security and safety.   Application developers don't want to deal with the complexity of the embedded system anymore. A lack of embedded software developers and usability difficulties make the productivity crisis in the embedded industry very obvious. Let us stop scaring people with bits, bytes, interrupts, and help them to optimize systems. Wind River has created a platform for innovation called Wind River Labs and provides VxWorks SDK for the download. ROS2 on VxWorks is a port of popular Robotics framework to the RTOS and based on the VxWorks SDK. It provides a possibility for the developers to easily switch between Ubuntu and VxWorks development environments. We plan to make in 2020 the VxWorks and Wind River Linux officially supported OSes by the ROS community. Innovate with us on labs.windriver.com]]>
My talk "ROS2 on VxWorks. one Wind River Labs project" at ROS Industrial conference 2019 hits pain points of the ROS Industrial community. Developer journey from the desktop ROS2 development under Ubuntu to the ROS2 embedded software development is the rocky one. Software engineers face difficulties to migrate their ROS2 code from native to the cross-compile environment and tune system for the performance, real-time, security and safety.   Application developers don't want to deal with the complexity of the embedded system anymore. A lack of embedded software developers and usability difficulties make the productivity crisis in the embedded industry very obvious. Let us stop scaring people with bits, bytes, interrupts, and help them to optimize systems. Wind River has created a platform for innovation called Wind River Labs and provides VxWorks SDK for the download. ROS2 on VxWorks is a port of popular Robotics framework to the RTOS and based on the VxWorks SDK. It provides a possibility for the developers to easily switch between Ubuntu and VxWorks development environments. We plan to make in 2020 the VxWorks and Wind River Linux officially supported OSes by the ROS community. Innovate with us on labs.windriver.com]]> Wed, 11 Dec 2019 22:22:25 GMT /slideshow/ros2-on-vxworks-one-project-on-wind-river-labs/204647516 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) ROS2 on VxWorks - one project on Wind River Labs AndreiKholodnyi My talk "ROS2 on VxWorks. one Wind River Labs project" at ROS Industrial conference 2019 hits pain points of the ROS Industrial community. Developer journey from the desktop ROS2 development under Ubuntu to the ROS2 embedded software development is the rocky one. Software engineers face difficulties to migrate their ROS2 code from native to the cross-compile environment and tune system for the performance, real-time, security and safety.   Application developers don't want to deal with the complexity of the embedded system anymore. A lack of embedded software developers and usability difficulties make the productivity crisis in the embedded industry very obvious. Let us stop scaring people with bits, bytes, interrupts, and help them to optimize systems. Wind River has created a platform for innovation called Wind River Labs and provides VxWorks SDK for the download. ROS2 on VxWorks is a port of popular Robotics framework to the RTOS and based on the VxWorks SDK. It provides a possibility for the developers to easily switch between Ubuntu and VxWorks development environments. We plan to make in 2020 the VxWorks and Wind River Linux officially supported OSes by the ROS community. Innovate with us on labs.windriver.com <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ros2onvxworks-oneprojectonwindriverlabs-191211222225-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> My talk &quot;ROS2 on VxWorks. one Wind River Labs project&quot; at ROS Industrial conference 2019 hits pain points of the ROS Industrial community. Developer journey from the desktop ROS2 development under Ubuntu to the ROS2 embedded software development is the rocky one. Software engineers face difficulties to migrate their ROS2 code from native to the cross-compile environment and tune system for the performance, real-time, security and safety.   Application developers don&#39;t want to deal with the complexity of the embedded system anymore. A lack of embedded software developers and usability difficulties make the productivity crisis in the embedded industry very obvious. Let us stop scaring people with bits, bytes, interrupts, and help them to optimize systems. Wind River has created a platform for innovation called Wind River Labs and provides VxWorks SDK for the download. ROS2 on VxWorks is a port of popular Robotics framework to the RTOS and based on the VxWorks SDK. It provides a possibility for the developers to easily switch between Ubuntu and VxWorks development environments. We plan to make in 2020 the VxWorks and Wind River Linux officially supported OSes by the ROS community. Innovate with us on labs.windriver.com
ROS2 on VxWorks - one project on Wind River Labs from Andrei Kholodnyi
]]> 267 1 https://cdn.slidesharecdn.com/ss_thumbnails/ros2onvxworks-oneprojectonwindriverlabs-191211222225-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 ROS2 on VxWorks - Challenges in porting a modern, software framework to RTOS /slideshow/ros2-on-vxworks-challenges-in-porting-a-modern-software-framework-to-rtos/190966951 roscon2019ros2onvxworks-191106072018
A slim ROS2 design with minimal external dependencies makes it a promising candidate for direct deployment in the mobile robot environment. Such embedded systems are the area where VxWorks RTOS historically plays a leading role. This presentation describes the motivation and challenges of porting the Robot Operating System to VxWorks, gives some recommendations to the ROS2 community and discusses possible next steps.]]>
A slim ROS2 design with minimal external dependencies makes it a promising candidate for direct deployment in the mobile robot environment. Such embedded systems are the area where VxWorks RTOS historically plays a leading role. This presentation describes the motivation and challenges of porting the Robot Operating System to VxWorks, gives some recommendations to the ROS2 community and discusses possible next steps.]]> Wed, 06 Nov 2019 07:20:18 GMT /slideshow/ros2-on-vxworks-challenges-in-porting-a-modern-software-framework-to-rtos/190966951 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) ROS2 on VxWorks - Challenges in porting a modern, software framework to RTOS AndreiKholodnyi A slim ROS2 design with minimal external dependencies makes it a promising candidate for direct deployment in the mobile robot environment. Such embedded systems are the area where VxWorks RTOS historically plays a leading role. This presentation describes the motivation and challenges of porting the Robot Operating System to VxWorks, gives some recommendations to the ROS2 community and discusses possible next steps. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/roscon2019ros2onvxworks-191106072018-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> A slim ROS2 design with minimal external dependencies makes it a promising candidate for direct deployment in the mobile robot environment. Such embedded systems are the area where VxWorks RTOS historically plays a leading role. This presentation describes the motivation and challenges of porting the Robot Operating System to VxWorks, gives some recommendations to the ROS2 community and discusses possible next steps.
ROS2 on VxWorks - Challenges in porting a modern, software framework to RTOS from Andrei Kholodnyi
]]> 803 4 https://cdn.slidesharecdn.com/ss_thumbnails/roscon2019ros2onvxworks-191106072018-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Mixed-critical adaptive AUTOSAR stack based on VxWorks, Linux, and virtualization /slideshow/mixedcritical-adaptive-autosar-stack-based-on-vxworks-linux-and-virtualization/123275925 15andreikholodnyimixed-criticalityadaptiveplatfromstackbased-181117125311
Since the first release of its standard in 2003, AUTOSAR has established itself as one of the primary software development standards for the global automotive industry. As the automotive industry is a now undergoing one of the significant changes in its history toward autonomous driving, connectivity and electrification new standards are needed to handle the complexity regarding software architecture for controlling the high-end processors, Ethernet communication, and over-the-air updates in the cloud-connected automobiles. The recent advent of the Adaptive AUTOSAR standard can help accommodate the extensive and complex requirements of autonomous driving by enabling a flexible, dynamic, and service based platform while still maintaining the integrity of high degree of functional safety standards and also properly engaging with established platforms. The standard itself replies on some technologies which are already established in the industry such as virtualization, POSIX PSE51, C++11/14 for application development, ISO26262/ASIL compliance, etc. This presentation provides example of an implementation of mixed critical Adaptive AUTOSAR stack based on VxWorks RTOS, embedded Linux, and virtualization profile from Wind River. As one of the very few solutions available on the market which is already fulfilling the requirements described above, VxWorks is a strong example of a foundational software platform for Adaptive AUTOSAR-based autonomous driving development. We will also explain what challenges we have encounter with during this process and make some suggestions to the AUTOSAR consortium of how to overcome them in the future.]]>
Since the first release of its standard in 2003, AUTOSAR has established itself as one of the primary software development standards for the global automotive industry. As the automotive industry is a now undergoing one of the significant changes in its history toward autonomous driving, connectivity and electrification new standards are needed to handle the complexity regarding software architecture for controlling the high-end processors, Ethernet communication, and over-the-air updates in the cloud-connected automobiles. The recent advent of the Adaptive AUTOSAR standard can help accommodate the extensive and complex requirements of autonomous driving by enabling a flexible, dynamic, and service based platform while still maintaining the integrity of high degree of functional safety standards and also properly engaging with established platforms. The standard itself replies on some technologies which are already established in the industry such as virtualization, POSIX PSE51, C++11/14 for application development, ISO26262/ASIL compliance, etc. This presentation provides example of an implementation of mixed critical Adaptive AUTOSAR stack based on VxWorks RTOS, embedded Linux, and virtualization profile from Wind River. As one of the very few solutions available on the market which is already fulfilling the requirements described above, VxWorks is a strong example of a foundational software platform for Adaptive AUTOSAR-based autonomous driving development. We will also explain what challenges we have encounter with during this process and make some suggestions to the AUTOSAR consortium of how to overcome them in the future.]]> Sat, 17 Nov 2018 12:53:11 GMT /slideshow/mixedcritical-adaptive-autosar-stack-based-on-vxworks-linux-and-virtualization/123275925 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) Mixed-critical adaptive AUTOSAR stack based on VxWorks, Linux, and virtualization AndreiKholodnyi Since the first release of its standard in 2003, AUTOSAR has established itself as one of the primary software development standards for the global automotive industry. As the automotive industry is a now undergoing one of the significant changes in its history toward autonomous driving, connectivity and electrification new standards are needed to handle the complexity regarding software architecture for controlling the high-end processors, Ethernet communication, and over-the-air updates in the cloud-connected automobiles. The recent advent of the Adaptive AUTOSAR standard can help accommodate the extensive and complex requirements of autonomous driving by enabling a flexible, dynamic, and service based platform while still maintaining the integrity of high degree of functional safety standards and also properly engaging with established platforms. The standard itself replies on some technologies which are already established in the industry such as virtualization, POSIX PSE51, C++11/14 for application development, ISO26262/ASIL compliance, etc. This presentation provides example of an implementation of mixed critical Adaptive AUTOSAR stack based on VxWorks RTOS, embedded Linux, and virtualization profile from Wind River. As one of the very few solutions available on the market which is already fulfilling the requirements described above, VxWorks is a strong example of a foundational software platform for Adaptive AUTOSAR-based autonomous driving development. We will also explain what challenges we have encounter with during this process and make some suggestions to the AUTOSAR consortium of how to overcome them in the future. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/15andreikholodnyimixed-criticalityadaptiveplatfromstackbased-181117125311-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Since the first release of its standard in 2003, AUTOSAR has established itself as one of the primary software development standards for the global automotive industry. As the automotive industry is a now undergoing one of the significant changes in its history toward autonomous driving, connectivity and electrification new standards are needed to handle the complexity regarding software architecture for controlling the high-end processors, Ethernet communication, and over-the-air updates in the cloud-connected automobiles. The recent advent of the Adaptive AUTOSAR standard can help accommodate the extensive and complex requirements of autonomous driving by enabling a flexible, dynamic, and service based platform while still maintaining the integrity of high degree of functional safety standards and also properly engaging with established platforms. The standard itself replies on some technologies which are already established in the industry such as virtualization, POSIX PSE51, C++11/14 for application development, ISO26262/ASIL compliance, etc. This presentation provides example of an implementation of mixed critical Adaptive AUTOSAR stack based on VxWorks RTOS, embedded Linux, and virtualization profile from Wind River. As one of the very few solutions available on the market which is already fulfilling the requirements described above, VxWorks is a strong example of a foundational software platform for Adaptive AUTOSAR-based autonomous driving development. We will also explain what challenges we have encounter with during this process and make some suggestions to the AUTOSAR consortium of how to overcome them in the future.
Mixed-critical adaptive AUTOSAR stack based on VxWorks, Linux, and virtualization from Andrei Kholodnyi
]]> 1475 5 https://cdn.slidesharecdn.com/ss_thumbnails/15andreikholodnyimixed-criticalityadaptiveplatfromstackbased-181117125311-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Developing safety autonomous driving solutions based on the adaptive AUTOSAR standard /slideshow/developing-safety-autonomous-driving-solutions-based-on-the-adaptive-autosar-standard/89370287 developingsafetyautonomousdrivingsolutionsbasedontheadaptiveautosarstandard-hendrawankholodnyi-windr-180302142305
This presentation provides an example of an implementation of Adaptive AUTOSAR implementation based on VxWorks RTOS from Wind River. As one of the very few solutions available on the market, VxWorks RTOS serves as a foundation for the Adaptive AUTOSAR-based autonomous driving development.]]>
This presentation provides an example of an implementation of Adaptive AUTOSAR implementation based on VxWorks RTOS from Wind River. As one of the very few solutions available on the market, VxWorks RTOS serves as a foundation for the Adaptive AUTOSAR-based autonomous driving development.]]> Fri, 02 Mar 2018 14:23:05 GMT /slideshow/developing-safety-autonomous-driving-solutions-based-on-the-adaptive-autosar-standard/89370287 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) Developing safety autonomous driving solutions based on the adaptive AUTOSAR standard AndreiKholodnyi This presentation provides an example of an implementation of Adaptive AUTOSAR implementation based on VxWorks RTOS from Wind River. As one of the very few solutions available on the market, VxWorks RTOS serves as a foundation for the Adaptive AUTOSAR-based autonomous driving development. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/developingsafetyautonomousdrivingsolutionsbasedontheadaptiveautosarstandard-hendrawankholodnyi-windr-180302142305-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This presentation provides an example of an implementation of Adaptive AUTOSAR implementation based on VxWorks RTOS from Wind River. As one of the very few solutions available on the market, VxWorks RTOS serves as a foundation for the Adaptive AUTOSAR-based autonomous driving development.
Developing safety autonomous driving solutions based on the adaptive AUTOSAR standard from Andrei Kholodnyi
]]> 1812 7 https://cdn.slidesharecdn.com/ss_thumbnails/developingsafetyautonomousdrivingsolutionsbasedontheadaptiveautosarstandard-hendrawankholodnyi-windr-180302142305-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Autonomous driving end-to-end security architecture /slideshow/autonomous-driving-end-toend-security-architecture/73470317 autonomousdrivingend-to-endsecurityarchitecture-170322092026
Presentation describes what security challenges automotive industry encounter with towards autonomous driving. What security threats appear and why. Who are the threat agents and what are their objectives. It presents end-to-end data path security threats based on the recent automated driving hardware architectures and propose defense-in-depth to solve approach on ECU and intra-ECU level to mitigate those threats]]>
Presentation describes what security challenges automotive industry encounter with towards autonomous driving. What security threats appear and why. Who are the threat agents and what are their objectives. It presents end-to-end data path security threats based on the recent automated driving hardware architectures and propose defense-in-depth to solve approach on ECU and intra-ECU level to mitigate those threats]]> Wed, 22 Mar 2017 09:20:26 GMT /slideshow/autonomous-driving-end-toend-security-architecture/73470317 AndreiKholodnyi@slideshare.net(AndreiKholodnyi) Autonomous driving end-to-end security architecture AndreiKholodnyi Presentation describes what security challenges automotive industry encounter with towards autonomous driving. What security threats appear and why. Who are the threat agents and what are their objectives. It presents end-to-end data path security threats based on the recent automated driving hardware architectures and propose defense-in-depth to solve approach on ECU and intra-ECU level to mitigate those threats <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/autonomousdrivingend-to-endsecurityarchitecture-170322092026-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Presentation describes what security challenges automotive industry encounter with towards autonomous driving. What security threats appear and why. Who are the threat agents and what are their objectives. It presents end-to-end data path security threats based on the recent automated driving hardware architectures and propose defense-in-depth to solve approach on ECU and intra-ECU level to mitigate those threats
Autonomous driving end-to-end security architecture from Andrei Kholodnyi
]]> 1793 7 https://cdn.slidesharecdn.com/ss_thumbnails/autonomousdrivingend-to-endsecurityarchitecture-170322092026-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-AndreiKholodnyi-48x48.jpg?cb=1722119038 I'm responsible for selecting, evaluating and prototyping new technologies to make Wind River's existing products work better together or to create new ones. My area of interest includes mobile robotics based on ROS2, dependable cyber-physical systems, mixed-critical autonomous driving solutions based on adaptive AUTOSAR, deterministic communication over TSN, active security, and some others. I'm also actively driving collaboration with leading European universities. www.windriver.com https://cdn.slidesharecdn.com/ss_thumbnails/tsnappsrunningonvxworksrtosasakvmguestattheintelligentedge-210525103336-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/tsn-apps-running-on-vxworks-rtos-as-a-kvm-guest-at-the-intelligent-edge/248524634 TSN apps running on Vx... https://cdn.slidesharecdn.com/ss_thumbnails/howtocross-compileros2distrobytakenvxworksrtosasanexample-200701132349-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/how-to-cross-compile-ros2-distro-by-taken-vxworks-rtos-as-an-example/236471094 How to cross compile R... https://cdn.slidesharecdn.com/ss_thumbnails/vxworksrunningros2asareal-timeguestosonhypervisor-200303155130-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/turtlebot3-vxworks-running-ros2-as-a-realtime-guest-os-on-hypervisor/229599516 Turtlebot3: VxWorks ru...