With the advancement of the times, intelligence and connectivity have become the major trends in the development of automobiles today. Classic AUTOSAR is a software architecture developed based on a highly real-time embedded operating system, which can meet the customized functional requirements of traditional automobiles and perform well. However, once automobiles are connected to the network, there may be delays and interference, which may not meet the strong real-time requirements. In such cases, Classic AUTOSAR is powerless.

Compared with Classic AUTOSAR, Adaptive AUTOSAR has somewhat reduced real-time requirements, but it has greatly improved the support for high-performance processing capabilities on the basis of ensuring a certain level of functional safety, in order to support the development of intelligent and connected application functions. Therefore, C++ will become the main development language for the Adaptive AUTOSAR platform.

Software components running on microprocessors are usually not based on the AUTOSAR Classic standard, but are replaced by AUTOSAR Adaptive, to meet the requirements of modularity, dynamism, and continuous update capabilities. AUTOSAR Adaptive is becoming a generally recognized software standard on high-performance automotive platforms. AUTOSAR Adaptive uses operating systems that comply with POSIX standards, such as Linux, PikeOS, or QNX, and provides functional extensions for its application in the automotive field. AUTOSAR Adaptive also provides functional support for diagnostics, information security, and functional safety.

In AUTOSAR Adaptive projects, the isolation of software and hardware has brought new changes to the task allocation between OEMs and suppliers. In the past, a functional block was usually ordered as a physical device in a car, but now it is completely possible to purchase only software. To achieve this approach, each AUTOSAR Adaptive application is an independent binary file, and application development will be independent of ECU development.

With the vigorous development of unmanned driving technology, the increasing development of vehicle networking and the Internet of everything, and cloud technology, the emergence of Adaptive AUTOSAR can not only meet the current requirements but also the innovative changes in future automotive technology. Because it supports various adaptive deployments, complex microcontrollers, and interactions with various non- AUTOSAR systems, future automobiles will have different types of architectures that complement each other.

ZC.MuNiu SOC product is an ECU development solution that complies with Adaptive AUTOSAR. This solution adopts an SOA architecture design, including a suite of tools from system functional design, ECU function mapping and component configuration, to automatic code generation of the runtime environment, providing a set of practical and verified foundations for developing reusable ECU application software.

TECHNICAL ADVANTAGE

Ø  Support for SOME/IP Protocol: Including ECE protection.

Ø  Support for DoIP Protocol: Capable of performing OTA updates using UDS on IP.

Ø  Increased Security with TLS and SecOC

Ø  Employing Inter-Process Communication (IPC) for better performance and simplified configuration.

Ø  Ensuring service stability through continuous monitoring of TCP connections.

Ø  Reducing network overload with a buffering system for UDP frames.

Ø  Guaranteeing real-time performance for high-priority applications by assigning priorities within IP packets.

Ø  Accelerating startup with an optional static service discovery process.

Ø  Support for XCP Measurement and Calibration

Ø  Support for AutoIP Mechanism

ZC.MuNiu SOC (System on Chip) product is designed based on the SOA (Service-Oriented Architecture) software architecture and is compatible with Adaptive AutoSAR vehicle solutions. It integrates software that has been mass-production verified, open-source software, and third-party software. It also incorporates tools and services that are crucial for the HPC (High-Performance Computing) environment but are not specific to different automobiles.ZC.MuNiu SOC product includes a high-performance functional safety software stack based on Linux and Adaptive AUTOSAR, a real-time safety software stack based on Classic AUTOSAR, a hypervisor, and software for HPC updates and platform health management functions. Additionally, it includes tools and services for automated build and integration.

ZC.MuNiu SOC product facilitates the development of services based on the SOA framework. Its primary applications currently include:

Ø  High-performance ECUs for applications like ADAS, multimedia, and connectivity.

Ø  Systems related to highly automated operations and safety-related functions.

Ø  Development in C++ related to Adaptive AUTOSAR.

Ø  Independent vehicle-related software development.

Ø  Service development related to SOA.

Ø  Rapid SecureBoot solutions for SOC.

ZC.MuNiu SOC divides the entire system into the following parts:：

l  Hardware：The hardware layer, which involves specific chip development boards.

l  BOOTLOADER：The bootloader layer, responsible for booting the OS system.

l  OS Kernel： The operating system kernel layer, which drives various external devices such as Audio, Bluetooth, Wifi, etc. In addition to driving peripherals, the OS Kernel is also responsible for other OS standard functions such as multi-process calls, memory management, disk management, etc.

l  Application：The application layer is responsible for the specific functional implementation, from bottom to top, it implements HAL, Platform API, SW Runtime Framework, and User App:

n  HAL：A virtual layer that abstracts the underlying devices into standard APIs for upper-layer applications to call.

n  Platform API：The Platform API implements the Adaptive platform's basic components, including eleven APIs and four common services:

Ø  Time Synchronzation：Responsible for synchronizing the system clock with an external clock.

Ø  Execution Mangement：Manages program execution and resolves program interdependencies.

Ø  Communication Management：Manages communication, including both external and internal communication management.

Ø  Logging &Tracing：Analyzes system risks through logging and tracing.

Ø  Persitency：Interface for accessing non-volatile storage.

Ø  Identity Acess Management：Manages identities and access, conducting risk management.

Ø  Platform Health Management：Manages platform health, including system load and status.

Ø  Core Types： System common types and functionalities, such as error handling and complex data types.

Ø  Cryptography：Interface for general cryptographic operations and secure key management.

Ø  Diagnostics ：Manages services related to diagnostics.

Ø  RESTFul：Responsible for building RESTful services and specific services.

Four common services：

Ø  Update &Configuration Management：A service for handling software update requests.

Ø  State Management：State management, responsible for all aspects of the platform's operational status, including handling incoming events and determining the priority of these events/requests to set the corresponding internal state.

Ø  Signal To Service Mapping：Signal to service mapping.

Ø  Network Management：Network management service, coordinating the normal operation of the basic network in the internal coordination state machine and the transition between bus sleep mode.

n  SW Runtime Framework：Software runtime framework, generally refers to the system-level program running environment.

User App：User-defined applications, which can run locally or remotely, and interact with the system through API interfaces.

Click to download the product manual