Who is this for?
This is an introductory topic for automotive developers, aimed at helping them accelerate autonomous driving software development before automotive hardware is available.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Understand the SOAFEE architecture and its role in supporting Shift-Left software development strategies to optimize the autonomous driving development process
- Use the Autoware Open AD Kit simulation environment
- Run containerized workloads on Arm Neoverse processors with Docker, supporting execution on both cloud-based and on-premise servers
- Explore advanced configurations and future development prospects
Prerequisites
Before starting, you will need the following:
- An Arm Neoverse cloud instance, or a local Arm Neoverse Linux computer with at least 16 CPUs and 32GB of RAM
- Familiarity with Docker and Docker Compose
Summary
AI-assisted
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication.
Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll deploy a containerized Autoware Open AD Kit simulation on Arm Neoverse using Docker and Docker Compose, within a SOAFEE-aligned Shift-Left workflow. First, you’ll learn about software-defined vehicles (SDVs), SOAFEE, ROS 2, and the Open AD Kit components used in the demo. Then, you’ll prepare an Arm Neoverse Linux system and use Docker Compose to start the Open AD Kit visualizer, planning, and simulation services. By the end, you’ll review a running simulation. The workflow has been tested on both cloud (Amazon EC2) and on-premise Arm Neoverse platforms.
Frequently asked questions
AI-assisted
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication.
Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
The visualizer service starts in detached mode, followed by continuously running planning and simulation services. Active containers for these components indicate the demo is operating as intended.
Where are the ROS 2 commands and service configurations defined?They are defined in the docker/docker-compose.yml file. Reviewing that file shows the launch order, container settings, and ROS 2 commands used by the demo.
Can I run the same workflow on cloud and on-prem Arm Neoverse systems?Yes. The workflow has been tested on Amazon EC2 and an Ampere Altra workstation, so you can choose either a cloud instance or an on-premise Arm Neoverse system.
What should I check before starting the demo to avoid resource-related failures?Verify the Arm Neoverse system provides at least 16 CPUs and 32 GB of RAM. Ensure Docker and Docker Compose are installed and available.
If I stop and restart the demo, do I need to reconfigure anything?No. Docker Compose allows you to start with the previous session’s settings without modifications, so the configuration persists between runs.