Skip to content
AI OS for Node.js Community
Branch: master
Clone or download
circle ci
Latest commit 5ecfef2 Feb 28, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci add daily build and badges Feb 28, 2019
images update logo Jan 4, 2019
manifests add k18 vsp firmware Jan 28, 2019
tools fix the repo username command Feb 28, 2019
LICENSE Create LICENSE Dec 13, 2018 add daily build and badges Feb 28, 2019


This is a modern operating system for next generation interactive device, and it embraces Web community, uses JavaScript as the application language.

Get Started

To start with compiling YODAOS, a Linux is required, we recommend the followings distributions:

  • Ubuntu 16.04
  • Centos 7

For Ubuntu:

$ apt-get install build-essential subversion libncurses5-dev zlib1g-dev gawk gcc-multilib flex git-core gettext libssl-dev unzip texinfo device-tree-compiler dosfstools libusb-1.0-0-dev

For Centos 7, the install command-line is:

$ yum install -y unzip bzip2 dosfstools wget gcc gcc-c++ git ncurses-devel zlib-static openssl-devel svn patch perl-Module-Install.noarch perl-Thread-Queue
# And the `device-tree-compiler` also needs to install manually:
$ wget
$ rpm -i dtc-1.4.0-1.el6.x86_64.rpm

Download Source

Click, and do register as Rokid Developer.

Then, go SSH Settings to config your local public key.

Install the repo cli

YODAOS uses the repo command-line to manage the source tree:

Repo unifies Git repositories when necessary, performs uploads to the Gerrit revision control system, and automates parts of the Android development workflow. Repo is not meant to replace Git, only to make it easier to work with Git in the context of Android. The repo command is an executable Python script that you can put anywhere in your path.

Follow the below commands to install manually:

$ curl > /usr/local/bin/repo
$ chmod 777 /usr/local/bin/repo

And use repo --help to test if installation is done.


When the repo cli is ready, follow the instruments to get the complete source of YODAOS:

$ repo init -u -m manifest.xml --repo-url= --no-repo-verify
$ .repo/manifests/tools/repo-username -u {your rokid developer username} # set your username to fetch source from gerrit
$ repo sync

The above takes few minutes, just be patient. The next step is to build out the OS image, let's take the example of Raspberry board:

$ cp -r products/yodaos/rbpi-3b-plus/configs/broadcom_bcm2710_rpi3b_plus_defconfig openwrt/.config
$ cd openwrt
$ make defconfig && make

The cp command is to select which board that you would build, the following are the boards config table:

board product config
Raspberry 3b plus raspberry products/yodaos/rbpi-3b-plus/configs/broadcom_bcm2710_rpi3b_plus_defconfig
Kamino18 kamino18 products/rokid/dev3.3/configs/leo_k18_dev33_defconfig

Remember that make defconfig after you redo the copy on the specific board config.

Go compile & run for more details.

Children projects

The YODAOS is a group of children projects open sourced which mainly are:



System Service



  • ShadowNode is the Node.js runtime that implements most of core APIs and N-API-compatible.
  • yodart is the application-layer of YODAOS, it's also the VUI framework for JavaScript.


This section describes how do YODAOS release and its lifecycle.


YODAOS uses Semver 2.0 for versioning management, and we have lifecycles for major and minor.

  • major: one release per 6 month, and all releases are stable.
  • minor: one release per 1 month, and only the even ones are stable, namely 1.0.x, 1.2.x, 1.4.x.

We assume the 3rd Thursday at every month as YodaOS release date.

release requirements

Every release must contain the following parts:

  • Repo manifest commit with specific version, for downloading the source code.
  • Multiple platform images, includes:
    • Rokid Kamino18 soc.
    • AmLogic A113.
  • Changelog describes what changes this updated.

stable and pre-versions

Stable version requires the complete tests on:

  • Compatibility test suite
  • Unit tests of modules and services
  • Functional tests
  • Integration tests

The above workload is in usual 2 weeks for the team, therefore we introduce pre-version, namely release candidates(RC) to track the stable releasing progress.

For stable version, we preserve 2 weeks at least to take the workload of full tests, and create a pre-version branch v1.2.x-rc. Once all the full tests are passed, then create a stable branch(v1.2.x) from release candidate branch(v1.2.x-rc).

Project Team Members

TSC (Technical Steering Committee)



YODAOS is a community-driven project that we accepts any improved proposals, pull requests and issues.

  • For JavaScript development, go yodart for details.
  • For proposal, yodaos-project/evolution is the place where someone can submit pull request to propose something.



Apache 2.0

You can’t perform that action at this time.