no-OS's documentation

Welcome to no-OS, Analog Devices' bare-metal software framework.

no-OS started as a result of customers' need to configure ADI's hardware components from bare-metal software environments. What began as a request for software drivers has grown into a complete framework that generates full applications, highly customizable according to users' requirements. It provides:

  • Platform-agnostic device drivers for ADI components that run without an operating system.

  • A hardware abstraction layer so the same driver works across Xilinx, Intel, Maxim, STM32, ADuCM3029, Raspberry Pi Pico and more.

  • Ready-to-build project examples you can flash to supported evaluation boards to get started quickly.

Note

We are in the process of moving the no-OS documentation from wiki.analog.com to analogdevicesinc.github.io/no-OS.

We apologize for any inconvenience that may occur due to this migration.

Getting started

New to no-OS? Start here:

  1. Clone the repository and set up your toolchain by following the No-OS Build Guide for your platform.

  2. Pick a project from the no-OS projects list that matches your evaluation board, then build and flash it.

  3. Explore the drivers you need in the no-OS drivers list, and read the no-OS drivers guide if you plan to write or adapt one.

Clone no-OS (external libraries are fetched automatically at configure time, in-tree under libraries/):

git clone https://github.com/analogdevicesinc/no-OS

Documentation guide

Not sure where to look? Use this map:

  • No-OS Build Guide — set up your toolchain and build no-OS for your platform (Xilinx, Intel, Maxim, STM32, ADuCM3029, Raspberry Pi Pico, Lattice and more), including Windows, macOS and WSL2 instructions.

  • no-OS projects list — browse the ready-to-build project examples, grouped by application area (ADCs, DACs, RF, power, sensors and others).

  • no-OS drivers list — reference documentation for every no-OS device driver, organized by device category.

  • no-OS drivers guide — learn how no-OS drivers are structured and how to create or port one.

  • Contributing to no-OS — the submission checklist and coding style expected for pull requests to the no-OS repository.

Contents

Additional resources