.oniro-ci/build-generic.yaml

@@ -35,8 +35,8 @@
         echo "CI_ONIRO_MANIFEST_URL: $CI_ONIRO_MANIFEST_URL"
         echo "CI_ONIRO_MANIFEST_NAME: $CI_ONIRO_MANIFEST_NAME"
         echo "CI_ONIRO_MANIFEST_BRANCH: $CI_ONIRO_MANIFEST_BRANCH"
-        repo init --reference \
-           "$CI_ONIRO_RUNNER_PERSISTENT_STORAGE"/pub/git-repo-mirrors/"$CI_ONIRO_MANIFEST_MIRROR" \
+        repo init \
+           $(test -n "${CI_ONIRO_RUNNER_PERSISTENT_STORAGE:-}" && echo --reference "$CI_ONIRO_RUNNER_PERSISTENT_STORAGE"/pub/git-repo-mirrors/"$CI_ONIRO_MANIFEST_MIRROR") \
            --manifest-url "$CI_ONIRO_MANIFEST_URL" \
            --manifest-name "$CI_ONIRO_MANIFEST_NAME" \
            --manifest-branch "$CI_ONIRO_MANIFEST_BRANCH"

.oniro-ci/containers/bitbake-builder/Dockerfile

@@ -26,8 +26,8 @@ RUN apt-get update -qq \
 	bash git-repo git-lfs apt-utils build-essential chrpath cpio diffstat \
 	gawk git sudo wget language-pack-en-base time locales python-is-python3 \
 	python3-distutils python3-pip libssl-dev iproute2 iputils-ping curl jq \
-	lz4 zstd \
- && eatmydata apt-get install -qq -y 'ca-certificates=20210119~20.04.2' \
+	lz4 zstd iptables\
+ && eatmydata apt-get install -qq -y 'ca-certificates=20211016~20.04.1' \
  && eatmydata apt-get clean && rm -rf /var/lib/apt/lists/*
 RUN locale-gen
 RUN pip3 install anybadge
@@ -36,7 +36,12 @@ RUN pip3 install anybadge
 RUN echo "dash dash/sh boolean false" | debconf-set-selections \
  && DEBIAN_FRONTEND=noninteractive dpkg-reconfigure dash
 
-RUN useradd --create-home --uid 1000 --shell /usr/bin/bash builder
+# runqemu command needs sudo permission to create tun device for the
+# communication between host and vm for gcc testing.
+RUN useradd --create-home --uid 1000 --shell /usr/bin/bash builder \
+ && usermod -aG sudo builder\
+ && echo "builder ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
+
 COPY --chown=builder:builder .gitconfig /home/builder/.gitconfig
 USER builder
 WORKDIR /home/builder

docs/hardware-support/boards/arduino-nano-33-ble.rst

@@ -74,6 +74,12 @@ sample application, *blinky*. In order to do so issue the following:
 3. After the build completes, the ``zephyr-philosophers.bin`` and the ``zephyr-blinky.bin``
    file can be found in ``build-oniro-zephyr/tmp-newlib/deploy/images/arduino-nano-33-ble/``.
 
+.. note::
+    By default, both zephyr-blinky and zephyr-philosophers applications will start once the board 
+    is powered on without waiting for a serial console connection.
+    To start an application only when serial console is connected, specify ONIRO_ENABLE_ACM0 = "1".
+    This option may be useful in automated testing environment.
+
 Flashing an Application
 =======================
 

docs/hardware-support/boards/raspberrypi4.rst

@@ -84,7 +84,7 @@ Linux image
    can be found in
    ``build-oniro-linux-raspberrypi4-64/tmp/deploy/images/$MACHINE/``.
    The key file which is needed to flash into the SD card is
-   ``oniro-image-base-raspberrypi4-64.wic.bz2``.
+   ``oniro-image-base-raspberrypi4-64.wic.gz``.
 
 Flashing |main_project_name| Linux image
 ****************************************
@@ -104,7 +104,7 @@ describes booting the board with an SD card option.
 .. code-block:: console
 
    $ cd tmp/deploy/images/raspberrypi4-64
-   $ bmaptool copy oniro-image-base-raspberrypi4-64.wic.bz2 $DEVNODE
+   $ bmaptool copy oniro-image-base-raspberrypi4-64.wic.gz $DEVNODE
 
 2. Put the card to the board and turn it on.
 

docs/hardware-support/boards/seco-intel-b68.rst

@@ -86,7 +86,7 @@ steps:
 .. code-block:: console
 
    $ cd tmp/deploy/images/seco-intel-b68
-   $ bmaptool copy oniro-image-base-seco-intel-b68.wic.bz2 $DEVNODE
+   $ bmaptool copy oniro-image-base-seco-intel-b68.wic.gz $DEVNODE
 
 3. Put the card to the board and turn it on.
 

docs/oniro-quick-build.rst

@@ -72,21 +72,33 @@ cloned using the repo tool. See above.
    could use around 100GB of disk space for downloads, temporary files, and
    build artifacts combined.
 
-Initialize the build directory and run a build:
+Initialize the build directory:
 
 .. code-block:: console
 
     $ TEMPLATECONF=../oniro/flavours/linux . ./oe-core/oe-init-build-env build-oniro-linux
+
+Now that the build is initialized, you have the choice of building a standard
+Oniro image or an OpenHarmony compatible one.
+
+A. Standard Oniro image
+-----------------------
+
+All that is left is to run the build:
+
+.. code-block:: console
+
     $ MACHINE=qemux86-64 bitbake oniro-image-base
 
 .. _Building with OpenHarmony:
 
-Building with OpenHarmony compatibility
-***************************************
+B. Building with OpenHarmony compatibility
+------------------------------------------
 
-To enable OpenHarmony compatibility, before running the last `bitbake` command
-in the section above, you have to add the following to
-`build-oniro-linux/conf/local.conf` file:
+To enable OpenHarmony compatibility features, you need to tweak the
+`local.conf` file before running the build process. You will find this
+configuration in `build-oniro-linux/conf/local.conf` where you'll need to add
+the following:
 
 .. code-block:: sh
 
@@ -98,8 +110,11 @@ in the section above, you have to add the following to
 This will enable OpenHarmony features and add OpenHarmony Standard System
 features to the `oniro-image-base` image.
 
-With that in place, the image can be built with the instructions in the
-:ref:`Building an Oniro image <Building an Oniro image>` section above.
+All that is left is to run the build:
+
+.. code-block:: console
+
+    $ MACHINE=qemuarm bitbake oniro-image-base
 
 Booting a Qemu X86-64 Target with a |main_project_name| image
 *************************************************************

flavours/linux/conf-notes.txt

@@ -26,6 +26,6 @@ or via command line, e.g.:
 
 You can also run generated qemu images with a command:
 
-    $ runqemu qemux86-64 qemuparams="-nographic" oniro-image-base wic ovmf
+    $ runqemu qemux86-64 qemuparams="-nographic" oniro-image-base wic ovmf slirp
 
 Then log in as 'oniro' user with 'oniro' as a password.