Release 1.1 · September 2026

Getting Started Guide

Edge Platforms · Intel® Core™ Processor (14th Gen), Intel® Processor N150, Intel® Processor N250, and Intel® Core™ 3 Processor N355

This guide provides instructions for building and installing the Android* 16 Base BSP Reference Release for Intel® Core™ Processor (14th Gen) (code named Raptor Lake-S Refresh); and Intel® Processor N150, Intel® Processor N250, and Intel® Core™ 3 Processor N355 (code named Twin Lake).

Note: The versions of the Android Common Kernel and AOSP open-source software components referenced in this release represent the Intel-validated baseline for the platform. Customers are encouraged to evaluate and integrate updates to these open-source components as they become available from the open-source community.
Review the Release Notes before proceeding with this guide.

Prerequisites

Build Host

  • 64-bit workstation running Ubuntu* 22.04 (Jammy Jellyfish)
  • Python 3.6 or later
  • At least 400 GB free disk space
  • High-speed Internet access

Target Hardware

  • Intel® Core™ Processor (14th Gen) (code named Raptor Lake-S Refresh)
  • Intel® Processor N150, Intel® Processor N250, and Intel® Core™ 3 Processor N355 (code named Twin Lake)
  • Minimum 400 GB storage
  • Flashed with the latest IFWI corresponding to the target platform (see table below)
  • High-speed network connectivity
PlatformReference UEFI BIOS/IFWI VersionDocument
Intel® Core™ Processor (14th Gen)7117_51852225
Intel® Processor N150, Intel® Processor N250, and Intel® Core™ 3 Processor N3557113_51919389
Note: Intel recommends building on Ubuntu* 22.04. See Establishing a Build Environment on the AOSP website for other OS configurations.

Set Up the Build Environment

The Android source code is distributed across multiple Git* repositories. The repo tool simplifies managing and synchronizing those repositories. If Git is not yet configured on your build machine, see Git Setup for Build Environment.

Install the repo tool:

mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH=~/bin:$PATH

Install required packages on Ubuntu 22.04 LTS:

sudo apt-get update
sudo apt-get install -y wget openjdk-8-jdk git ccache automake \
   lzop bison gperf build-essential zip curl \
   zlib1g-dev g++-multilib python3-networkx \
   libxml2-utils bzip2 libbz2-dev libbz2-1.0 \
   libghc-bzlib-dev squashfs-tools pngcrush \
   schedtool dpkg-dev liblz4-tool make optipng maven \
   libssl-dev bc bsdmainutils gettext python3-mako \
   libelf-dev sbsigntool dosfstools mtools efitools \
   python3-pystache git-lfs python-is-python3 flex clang libncurses5 \
   fakeroot ncurses-dev xz-utils cryptsetup-bin \
   apt-transport-https ca-certificates curl lsb-release \
   rsync vim python-six kmod glslang-tools \
   software-properties-common cpio python3-pip ninja-build \
   cutils cmake pkg-config xorriso mtools libjson-c-dev file

sudo pip3 install meson==1.8.3 mako==1.1.0 dataclasses pycryptodome ply==3.11

Install the Intel® oneAPI dependencies required by the build environment:

wget -O- https://apt.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS.PUB \
   | gpg --dearmor | sudo tee /usr/share/keyrings/oneapi-archive-keyring.gpg > /dev/null && \
   echo "deb [signed-by=/usr/share/keyrings/oneapi-archive-keyring.gpg] https://apt.repos.intel.com/oneapi all main" \
   | sudo tee /etc/apt/sources.list.d/oneAPI.list

sudo apt-get update

sudo apt install -y \
  intel-oneapi-ipp-devel-2021.10 \
  intel-oneapi-mkl-devel-2021.1.1 \
  intel-oneapi-ipp-devel-32bit-2021.10 \
  intel-oneapi-mkl-devel-32bit-2021.1.1
Note: If you encounter network connectivity issues, use the following commands to bypass the network proxy settings. In some cases, the system may use the default no_proxy configuration; setting a dummy value overrides this behavior.
unset no_proxy
unset NO_PROXY
export no_proxy=localhost
export NO_PROXY=localhost

After updating the no_proxy settings, run apt commands with the -E option:

sudo -E apt update
sudo -E apt install <packages>

Download and Build the Source Code

Manifest for this release: BM_BSP_2026_Q3_V2_A16.xml (GitHub). The release manifests are available in the stable-build/A16 directory.

Download the manifest, and then move it to your home directory:

mv BM_BSP_2026_Q3_V2_A16.xml ~/.

Create a working directory and download the source code:

mkdir ~/rpl-android-bm
cd ~/rpl-android-bm

repo init -u https://github.com/edge-aosp-bsp/manifest.git
mkdir .repo/manifests
cp ~/BM_BSP_2026_Q3_V2_A16.xml .repo/manifests/.
repo init -u https://github.com/edge-aosp-bsp/manifest.git -m BM_BSP_2026_Q3_V2_A16.xml

repo sync -c --force-sync -j16
repo forall -c git lfs pull
Synchronization can take a longer time. This behavior is expected. Adjust -j based on your preferred CPU cores.

Build the Android Image

Supported build targets are caas-userdebug and caas-user. The examples below use caas-userdebug, which is intended for development and debugging, including root access and debug tools. Use caas-user for a release-oriented configuration with reduced debugging capability.

Note: For Intel® Processor N150, Intel® Processor N250, and Intel® Core™ 3 Processor N355, use the Default Build. The Trusty Build is supported only on Intel® Core™ Processor (14th Gen).

Default Build

# Export the Trusty flag before lunch
export ENABLE_TRUSTY=false

source build/envsetup.sh
lunch caas-userdebug
make flashfiles BASE_LINUX_INTEL_LTS2024_KERNEL=true ENABLE_AVF=false -j16

Trusty Build

Supported only on Intel® Core™ Processor (14th Gen).

Step 1: Copy the Trusty binary:

cp lk.bin ~/rpl-android-bm/vendor/intel/fw/trusty-release-binaries/
Note: Contact your Intel representative for access to the Trusty source code and build procedure.

Step 2: Build with Trusty enabled:

# Export the Trusty flag before lunch
export ENABLE_TRUSTY=true

source build/envsetup.sh
lunch caas-userdebug
make flashfiles BASE_LINUX_INTEL_LTS2024_KERNEL=true -j16

Build Output

The generated build output files are available in ~/rpl-android-bm/out/target/product/caas/:

find out -name *.tar.gz
# out/target/product/caas/caas-releasefile-userdebug.iso.tar.gz
# out/target/product/caas/caas-releasefiles-userdebug.tar.gz

Flash and Boot Up the System

Step 1: Flash the Image to a USB Drive

On Windows*, use Rufus to write caas-flashfile-<variant>.iso.zip to a USB drive. On Ubuntu*, use dd:

unzip caas-flashfile-userdebug.iso.zip
dd if=./caas-flashfile-userdebug.iso of=/dev/sdc bs=1024M
Important: Replace /dev/sdc with your actual target USB device node.

Step 2: Boot the System to Android

  1. Insert the USB drive into the board.
  2. Press F2 while booting.
  3. Navigate: Boot Maintenance → Boot Option Menu → Change Boot Order.
  4. Set the USB drive as the first boot option, save (Fn + F4), and continue.
  5. Proceed with installation, and wait for flashing to complete.
  6. Remove the USB drive, and then reboot. Android will start automatically.
You can select NVMe or SATA as the storage target.

BIOS Settings

Verify that the BIOS settings match the values in the following table. These values are the default settings for the supported IFWI versions. Press the appropriate BIOS setup key (for example, F2, Del, or F12) during startup to access the BIOS Setup menu.

SettingMenu PathValue
Intel (VMX) VirtualizationIntel Advanced Menu → CPU ConfigurationEnabled
VT-dIntel Advanced Menu → System Agent (SA) ConfigurationEnabled
Intel® TCC ModeIntel Advanced Menu → Intel® Time Coordinated ComputingDisabled
#AC Split LockIntel Advanced Menu → Intel® Time Coordinated ComputingDisabled
OnBoard NICIntel Advanced Menu → PCH-IO Configuration → EFI NetworkOnBoard NIC
Note: The steps may vary depending on the BIOS. Intel® TCC Mode and #AC Split Lock are disabled by default because they are intended for real-time/deterministic workloads and are not required for standard Android BSP bring-up. Leave them disabled unless your use case specifically requires TCC.

Git Setup for Build Environment

Git must be set up on your build machine to run repo init. Configure Git with your name and email address, and add proxy settings if you are behind a firewall:

cd /home/$USER
vi /home/$USER/.gitconfig

Append the following lines to the .gitconfig file:

[user]
    email = <your email>
    name = <your name>
[http]
    proxy = <http_proxy>
[https]
    proxy = <https_proxy>

If required, create a symbolic link for Python 3 in the /usr/bin directory:

sudo ln -sf /usr/bin/python3 /usr/bin/python

References

DocumentDocument No./Location
Android* 16 Base BSP Reference Release for Edge Platforms (supporting Intel® Core™ Processor (14th Gen), Intel® Processor N150, Intel® Processor N250, and Intel® Core™ 3 Processor N355) - Release NotesRelease Notes
Android Manifest File (BM_BSP_2026_Q3_V2_A16.xml)GitHub
Intel® Core™ Processor (14th Gen) (code named Raptor Lake-S Refresh) for Edge Platforms Reference UEFI BIOS/IFWI (ver. 7117_51)852225
Intel® Processor N150 & N250 and Intel® Core™ 3 Processor N355 for Edge Applications (IPU 2026.3) Firmware Best Known Configuration (BKC)919389
Log in to the Resource and Documentation Center to search for and download the document numbers listed above. Contact your Intel field representative for access.
For complete release information, see the Release Notes, or email to premiersupport.intel.com. For legal notices, see the Disclaimer page. Contact your Intel representative for support.