Arm Community
Arm Community
  • Site
  • User
  • Site
  • Search
  • User
Arm Community blogs
Arm Community blogs
Architectures and Processors blog Meeting the demand for software interoperability on Arm-based hardware
  • Blogs
  • Mentions
  • Sub-Groups
  • Tags
  • Jump...
  • Cancel
More blogs in Arm Community blogs
  • AI blog

  • Announcements

  • Architectures and Processors blog

  • Automotive blog

  • Embedded and Microcontrollers blog

  • Internet of Things (IoT) blog

  • Laptops and Desktops blog

  • Mobile, Graphics, and Gaming blog

  • Operating Systems blog

  • Servers and Cloud Computing blog

  • SoC Design and Simulation blog

  • Tools, Software and IDEs blog

Tell us what you think
Tags
  • Software
  • BSA
  • Software Standards
  • sbsa
  • operating systems
  • SystemReady
  • System architectures
Actions
  • RSS
  • More
  • Cancel
Related blog posts
Related forum threads

Meeting the demand for software interoperability on Arm-based hardware

Dong Wei
Dong Wei
November 1, 2024
4 minute read time.

Hardware vendors across the industry are under pressure to accelerate time to market, reduce total cost of ownership (TCO), and adapt to longer product lifecycles. Changing consumer needs and regulatory pressures are mandating that devices are supported for longer. However, the cost of maintaining multiple platforms is not viable for operating system (OS) providers. As hardware changes, OSs need to remain compatible. A unified approach to OS installation and boot eliminates the cost of customizing and maintaining multiple platform specific processes. This makes device support manageable and lets manufacturers reach a broader addressable market. 

A unified approach for the Arm ecosystem

Arm SystemReady is a compliance program that ensures OS interoperability on Arm-based hardware. Specifically, that the needs of target software are incorporated into silicon design, so software running on the OS remains compatible with new hardware. Implementation accelerates time to market, as developers can build an OS once and deploy it on any compliant Arm-based chip, regardless of the manufacturer. Existing software can move through hardware generations, retaining and potentially expanding its install base.

Arm SystemReady is implemented in alignment with the two OS environment and firmware approaches commonly used today. These are split into the following bands:

  • SystemReady band: This focuses on Advanced Configuration and Power Interface (ACPI) environments where generic operating systems can be installed on either new or old hardware without modification. Old OSs can run on new hardware, and new OSs can run on old hardware, without customization.
  • SystemReady Devicetree band: This optimizes install and boot for embedded systems where Devicetree is the preferred method of describing hardware, with a focus on forward compatibility. These concern Linux distributions and Berkeley Software Distribution (BSD) environments specifically.

With the growing need for compliance, the Arm SystemReady program needs to be both more efficient and easier to integrate into the development process. Manufacturers need a way to incorporate Arm SystemReady that is applicable to the lifetime of a device, and not just a single moment in time. To meet these needs, Arm has simplified the program by:

  • Consolidating the number of Arm SystemReady 'bands' to two; SystemReady and SystemReady Devicetree. These align with the two principal OS and firmware environments used today (ACPI and Devicetree), making it easier for manufacturers and their customers to understand each bands benefit.
  • Invested in automated test suits for both bands so that they are easy to integrate and ensure continuous compliance as software is released.

A move from certification to compliance emphasizes continuous integration and delivery, where standards are maintained throughout the lifetime of a device. Certification only ensured this was the case at a single moment in time. The benefits of a long-term, compliance-based program will be reflected in both product support and reduced troubleshooting over the lifetime of the device.

The move to compliance takes place from November 2024. Manufacturers can now begin to integrate Arm SystemReady test suites into their production processes to ensure firmware remains compliant with the latest versions of the specifications. The roll out of these test suites differs depending on the band required:

  • Manufacturers implementing the SystemReady band, where compliance to the Base System Architecture (BSA) specification and its market segment supplements are critical, will have immediate access to a pre-silicon program to test compliance before production.
  • Testing tools for manufacturers implementing SystemReady Devicetree will be available from November 2024, with further OS testing tools ready in the first half of 2025. Until then, existing test labs will provide support and guide compliance as needed.

As these changes take place, Arm will continue to support the self-declared compliance of Virtual Environments (VE) for cloud instances and virtual platforms.

By making the program more accessible, both barriers to adoption and the time taken to become compliant are lowered. Manufacturers can control more variables during long-term planning, reducing risk. The dissemination of testing suites ensures firmware compliance can be brought in-house, allowing for self-declaration. Alternatively, the expertise of trusted external engineering partners through test labs remains available if preferred.

Some industry certifications require use of the Arm SystemReady Architecture Compliance Suite as part of their program. Arm will ensure this suite remains available for certification providers so they can continue to incorporate and build on the standards it sets.

Continuous investment in Arm SystemReady

Arm continues to invest in Arm SystemReady to meet the growing demand for solutions that accelerate time to market, reduce TCO, and facilitate the need to meet market pressures. With Arm SystemReady, the Arm ecosystem has a unified approach to OS installation and boot. Implementation lowers the cost of production, while ensuring device support in line with changing consumer behavior and regulation.

With Arm SystemReady now more accessible and easier for manufacturers to integrate, the 20 million developers that build software on Arm can be assured that their applications will continue to remain supported on Arm SystemReady compliant devices.

For more information on Arm SystemReady, visit our website.

Visit our website

Anonymous
Architectures and Processors blog
  • Introducing GICv5: Scalable and secure interrupt management for Arm

    Christoffer Dall
    Christoffer Dall
    Introducing Arm GICv5: a scalable, hypervisor-free interrupt controller for modern multi-core systems with improved virtualization and real-time support.
    • April 28, 2025
  • Getting started with AARCHMRS Features.json using Python

    Joh
    Joh
    A high-level introduction to the Arm Architecture Machine Readable Specification (AARCHMRS) Features.json with some examples to interpret and start to work with the available data using Python.
    • April 8, 2025
  • Advancing server manageability on Arm Neoverse Compute Subsystem (CSS) with OpenBMC

    Samer El-Haj-Mahmoud
    Samer El-Haj-Mahmoud
    Arm and 9elements Cyber Security have brought a prototype of OpenBMC to the Arm Neoverse Compute Subsystem (CSS) to advancing server manageability.
    • January 28, 2025