# Genio Pro 5100 Pre-Release 2

**URL:** <https://genio-community.mediatek.com/t/genio-pro-5100-pre-release-2/3556>\
**Category:** Announcements\
**Tags:** Wi-Fi, Android, AI, Display, IoT-Yocto, Genio-Pro-5100, Camera, Video, GPIO, PCle, Audio, Bootloader, IO-Interface, I2C, Image\
**Created:** [November 17, 2026, 10:29am UTC](https://genio-community.mediatek.com/t/genio-pro-5100-pre-release-2/3556 "2026-11-17T10:29:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pablo.sun](https://avatars.discourse-cdn.com/v4/letter/p/2acd7d/32.png) [@pablo.sun](https://genio-community.mediatek.com/u/pablo.sun)\
**Post date:** [November 17, 2026, 10:29am UTC](https://genio-community.mediatek.com/t/genio-pro-5100-pre-release-2/3556/1 "2026-11-17T10:29:12Z")

</div>

Last Update: 2026-11-17

This guide shows you how to build and flash the development snapshot (Pre-Release 2, PR2) of IoT Yocto **v26.1-dev** for the Genio Pro 5100 (MT8894) EVK and SoC.

> ⚠ **Pre-release — do not use in production**
> 
> PR2 is an unofficial development snapshot for evaluation only, with no support or warranty. It has not been fully tested. Design, features, and APIs are subject to change without notice.

> ℹ For the Genio Pro 5100 EVK, please contact your MediaTek sales representative.

## Overview

The document describes brief steps on how to flash and build the **in-development** IoT Yocto **v26.1-dev** for the Genio Pro 5100 EVK board.

For explanation on topics not mentioned in the document, please refer to [MediaTek IoT Yocto Developer Guide](https://genio.mediatek.com/doc/iot-yocto/latest/index.html) for details. Please note that the documentation is in the **preliminary** phase and is subject to changes without notice.

If you evaluated Pre-Release 1 (PR1), the setup steps are similar; see [What’s New in PR2](#whats-new-in-pr2) and [Heads-up for the v26.1 Release](#heads-up-for-the-v261-release) for the changes.

> **Note on the v26.0 release mechanism change**
> 
> Starting from IoT Yocto v26.0, the access-controlled (NDA) source repositories have migrated from GitLab (`gitlab.com/mediatek/aiot/nda`) to the **MediaTek Git01** service. The public manifest and public recipes remain on GitLab. Because of this change, the account setup flow is now based on a **Genio Developer account + Git01 account** , instead of a plain GitLab NDA account. See the [Genio Developer and Git01 Account Setup](https://genio.mediatek.com/doc/iot-yocto/latest/sw/yocto/get-started/account-setup.html) guide.

## What’s New in PR2

### Three prebuilt images

PR2 provides three prebuilt images for the Genio Pro 5100 EVK, all for `MACHINE=genio-pro-5100-evk`:

| Image | GPU driver stack | Kernel | For |
| --- | --- | --- | --- |
| `gp5100-evk` | Mesa (Panfrost / Panthor) | Linux 7.3-rc5 | General evaluation; **dual-display** output on HDMI and DisplayPort over USB Type-C (DPoC) |
| `gp5100-evk-mali` (new) | Arm Mali DDK (`libmali.so`) | Linux 7.3-rc5 | Better Vulkan and OpenGL ES performance |
| `gp5100-evk-robotic` (new) | Mesa (Panfrost / Panthor) | Linux 7.3-rc5, PREEMPT\_RT | Robotics and real-time: RT Linux (PREEMPT\_RT), with a preview of ROS 2 (`rity-robotic-image-rt`) |

### Main feature updates since PR1

- **AI / NPU** : more supported models for LLM and VLM inference on the NPU. See the [supported models](https://genio.mediatek.com/doc/iot-aihub/ai_hub/model_zoo/litert_gai/supported_models.html) and how to run them in the [AI Hub](https://genio.mediatek.com/doc/iot-aihub/ai_hub/supported_os/yocto/litert_gai.html).
- **Display** : DisplayPort over USB Type-C (DPoC), and dual-display output on HDMI + DPoC.
- **GPU** : the Arm Mali DDK driver stack, in the `gp5100-evk-mali` image; OpenCL on all images.
- **Video** : hardware decode of H.264, H.265 and VP9, and hardware encode of H.264 and H.265, through GStreamer V4L2 elements; MDP color conversion (`v4l2convert`).
- **Audio** : PDM DMIC input, USB Audio Class (UAC 1.0) input and output, ALSA UCM and PipeWire.
- **Ethernet** : 2.5 Gigabit Ethernet (SGMII).
- **USB** : USB 2.0 / 3.0 dual-role switch on the Type-C port.
- **Real-time and robotics** : RT Linux (PREEMPT\_RT) and the SCP (System Companion Processor), in the `gp5100-evk-robotic` image.  
It also includes ROS 2 Jazzy as a preview.
- **Security** : OP-TEE, UFS RPMB access, hardware KDF, and the eFuse customer field with the Linux eFuse writer tool.
- **System and peripherals** : RTC, keypad (power and volume keys).

## Heads-up for the v26.1 Release

### GPU driver configuration

The Genio Pro 5100 GPU has two driver stacks, which are mutually exclusive in one image:

- **Mesa (Panfrost / Panthor)**: the open-source stack, used by the default `gp5100-evk` image in PR2.
- **Arm Mali DDK** : the proprietary stack, used by the `gp5100-evk-mali` image in PR2.

We plan to make the **Arm Mali DDK the default** in the official v26.1 release, because in our measurements it scores better in general in the `glmark2`, `vkpeak` and `clpeak` benchmarks. The Mesa configuration remains supported for Genio Pro 5100 (MT8894).

### Linux kernel version

We plan to base the official v26.1 release and the initial Genio Pro 5100 (MT8894) BSP on the **Linux LTS kernel of 2026**. We currently expect it to be Linux 7.3, but [kernel.org](http://kernel.org) has not announced the 2026 LTS version yet.

PR2 is based on **Linux 7.3-rc5** , and we expect another rebase onto the 7.3.y LTS kernel before v26.1. If you carry your own kernel patches, you may need to forward-port them again for the official v26.1 release.

## PR2 Prebuilt Images

The prebuilt PR2 images for Genio Pro 5100 EVK can be downloaded from:

| Image | Download | md5sum |
| --- | --- | --- |
| `gp5100-evk` | [https://download.mediatek.com/aiot/download/prebuilt/v26.1-pr/scarthgap\_k7.99\_v26.1\_genio-pro-5100-evk\_private\_261117021356\_dev.tar.gz](https://download.mediatek.com/aiot/download/prebuilt/v26.1-pr/scarthgap_k7.99_v26.1_genio-pro-5100-evk_private_261117021356_dev.tar.gz) | `cffd3a48c39884bb0a642185a638ec2f` |
| `gp5100-evk-mali` | [https://download.mediatek.com/aiot/download/prebuilt/v26.1-pr/scarthgap\_k7.99\_v26.1\_genio-pro-5100-evk\_private\_261117045230\_mali.tar.gz](https://download.mediatek.com/aiot/download/prebuilt/v26.1-pr/scarthgap_k7.99_v26.1_genio-pro-5100-evk_private_261117045230_mali.tar.gz) | `77d38d588ecd35944dae662ceebb5027` |
| `gp5100-evk-robotic` | [https://download.mediatek.com/aiot/download/prebuilt/v26.1-pr/scarthgap\_k7.3\_v26.1\_genio-pro-5100-evk\_private\_261117053921\_robotic.tar.gz](https://download.mediatek.com/aiot/download/prebuilt/v26.1-pr/scarthgap_k7.3_v26.1_genio-pro-5100-evk_private_261117053921_robotic.tar.gz) | `10f9c20615bd9e76bac0d7b6b4862781` |

## Flashing

Install the development version of `genio-tools` to support Genio Pro 5100:

```shell
pip install --pre -U genio-tools==1.8.0a3

```

The `--pre` option installs development versions. After installation, check the version:

```shell
genio-flash --version

```

It should be `1.8.0a3`.

To flash the IoT Yocto image to the Genio Pro 5100 EVK board, change directory to the extracted image, then run:

```shell
$ genio-flash

```

If you have connected the audio board, load the corresponding DTBO by running:

```shell
$ genio-flash --load-dtbo audio-board.dtbo

```

- If the FTDI (USB-C UART) is connected and not occupied, `genio-flash` will automatically reset the board into USB Download Mode.
- If it does not enter USB Download Mode automatically, hold down the **Volume Up** key (`SW2802`) on the EVK and press **RESET** once to enter USB DL mode.

### Troubleshooting

If `genio-flash` stops at `< waiting for any device >` the first time you flash a Genio Pro 5100 EVK, open the Windows **Device Manager** and check whether “USB download gadget” shows a yellow warning icon. If so, update its driver to **Android Bootloader Device** as described in the [troubleshooting guide](https://genio.mediatek.com/doc/iot-yocto/latest/sw/yocto/get-started/troubleshooting.html#missing-yocto-device-driver), then flashing will continue.

> **ℹ Info**
> 
> A known issue: after flashing, the `fastboot reboot` command may return `FAILED (Status read failed ...)`, but the board does in fact reboot.

## Booting and Login

After flashing:

1. Connect **UART0 to USB 2.0 Type C** (`CON2801`) to your workstation PC
2. Connect **USB3\_DP TypeC** (`CON5701`) to your workstation PC
3. Configure your serial terminal to use baud rate `921600`.
4. Press the on-board `RST` button to perform a hardware reset

Then:

1. Log in on the **UART0** console using account `root` (no password required).

2. You can also use `adb shell` and `adb push` / `adb pull` to transfer files.

3. The Linux kernel version of the prebuilt image is:

## Scope and Limitations

Pre-Release 2 ( **PR2** ) adds the features listed in [What’s New in PR2](#whats-new-in-pr2) to those of PR1. Feature support will continue to expand towards the official **v26.1** release, planned for the end of December 2026.

### Known limitations

- **Dual-display output only.** PR2 supports at most two display paths at the same time, and they are used for HDMI and DPoC. The other three display interfaces, **eDP** , **DSI** (Raspberry Pi LCM) and **DSI** (touch LCM), are not enabled on any prebuilt image: their display paths need additional patches that are not in PR2. eDP, which PR1 enabled, is disabled in PR2 for this reason. We plan to support all five display outputs simultaneously in the official v26.1 release.
- **Not fully tested.** The prebuilt images are not fully tested, and the test cases in `genio-linux-test` have not all been verified yet, so they can report false alarms.

### Not yet in PR2

These features are planned for the official v26.1 release:

- **Display** : 5-way display output including eDP and DSI outputs together with HDMI and DPoC, and DSI DSC.
- **Video** : hardware JPEG decode and encode.
- **Boot** : booting from serial NOR flash.

### EVK Hardware Ports

The following table lists the physical ports and connectors on the Genio Pro 5100 IoT EVK (RDK) board and their software-enablement status in IoT Yocto. Some ports are out of scope for IoT Yocto and are marked accordingly.

**Legend:**

- ✅ = enabled in PR2.
- v26.1 = planned for the official v26.1 release (end of December 2026).
- ❌ = not enabled / out of scope.

| Category | Port Label (ID) | Enabled |
| --- | --- | --- |
| Power | MINI DIN-DC 12V (CON401) | ✅ |
| Power | 12V for FAN (CON3601) | ✅ |
| Power | Type C for current monitor (CON801) | ❌ |
| Ethernet | 1GbE Ethernet (J4801) | ✅ |
| Ethernet | 2.5Gb Ethernet (CON5001) | ✅ |
| Connectivity | PCIe M.2 Key E For Wi-Fi card (CON3301) | ✅ |
| Connectivity | SMA Conn. (CON5802) | ✅ |
| Connectivity | SMA Conn. (CON5803) | ✅ |
| USB & storage | USB3 TYPE A (CON5301) | ✅ |
| USB & storage | USB3 TYPE A (CON5302) | ✅ |
| USB & storage | USB3 TYPE A (CON5303) | ✅ |
| USB & storage | USB 2.0 Type-A (CON2701) | ✅ |
| USB & storage | USB 2.0 Type-C (CON2601) | ✅ |
| USB & storage | Micro SD (CON4002) | ✅ |
| USB & storage & Display | USB3\_DP TypeC (CON5701) — USB dual-role and DPoC display | ✅ |
| Display & Touch | HDMI Con. (CON501) | ✅ |
| Display & Touch | DSI1 4 lane LCM (CON702) | v26.1 |
| Display & Touch | DSI1 4 lane LCM Touch Connector (CON701) | v26.1 |
| Display & Touch | DSI2 4 lane LCM (CON4101) | v26.1 |
| Display & Touch | EDP 1.4b-4 lane (CON3801) | v26.1 |
| Audio | HDMI Con. (CON501) | ✅ |
| Audio | Audio Board Header (CON5801) | ✅ |
| Audio | Audio (ADC) Board Header (J5802) | ❌ |
| Camera | Camera CSI-2 4 lane (CON4501) | ❌ |
| Camera | Camera CSI-5 4 lane (CON4502) | ❌ |
| Camera | IPEX 30 pin (CON4401) | ❌ |
| Camera | CSI-3 CPHY (CON3901) | ❌ |
| Peripheral | Raspberry Pi HATs (J1919) — RPi UART, GPIO, SPI, I2C, PWM, I2S | ✅ |
| Peripheral | CAN FD (U4604) | ✅ |
| Peripheral | UART2 (CON1809) | ✅ |
| Peripheral | UART3 (CON1808) | ❌ |
| Peripheral | SPI5 (CON4601) | ❌ |
| Keypad | Power Key (SW2801) | ✅ |
| Keypad | Reset Key (SW2804) | ✅ |
| Keypad | Volume up (SW2802) | ✅ |
| Keypad | Volume down (SW2803) | ✅ |
| Debug | UART0 to USB 2.0 Type C (CON2801) | ✅ |
| Debug | Tooling Test Con. (J1401) | ❌ |
| Debug | JTAG (CON1901) | ❌ |
| High Speed External Storage | PCIe M.2 Key M for NVMe (CON3501) | ✅ |
| 5G/GPS | USB3.0 M.2 Key B for 5G/GPS (CON5402) | ❌ |
| 5G/GPS | Nano SIM (CON3401) | ❌ |
| Peripheral Connectivity | SDIO M.2 Key E For WiFi Card (CON3402) | ❌ |

> Note: The three USB3 TYPE A ports (`CON5301` to `CON5303`) require 3rd-party proprietary firmware to work.  
> See **Edit local.conf** section below.

### Known Issues

1. DPoC may randomly disconnect during system power-on. To remedy this, un-plug and re-plug DPoC cable after system initialization.
2. eDP is not enabled in PR2 (see [Known limitations](#known-limitations)): loading `display-edp.dtbo` does not enable it.
3. Raspberry Pi LCM panel is not enabled
4. The **UP** button in Linux does not work as `evtest` event source
5. DPoC display output breaks on the robotic image ( `scarthgap_k7.3_v26.1_genio-pro-5100-evk_private_261117053921_robotic`).

## Build Host Environment Setup

The IoT Yocto codebase is hosted across two services:

- **GitLab** — public repos (including the manifest and public recipes), which can be accessed without special permission.
- **MediaTek Git01** — restricted repos, which require you to create a MediaTek Genio Developer account and sign an NDA before you can access them.

To build the full (NDA) image, you must first set up your Git01 access. Please refer to [Genio Developer and Git01 Account Setup](https://genio.mediatek.com/doc/iot-yocto/latest/sw/yocto/get-started/account-setup.html). In short:

1. Sign up for a **Genio Developer account** and validate it via email.
2. Sign the electronic **NDA for Genio** from the Genio Developer Account Center (“Advanced Resource Access”). Wait until the status shows **Valid**.
3. From your Profile page, use the **Create Account** button under “NDA for Genio” to create a **Git01 account**. Credentials are emailed to you once the account is created.
4. Generate a **Git01 HTTP access token** from the Git01 HTTP Credentials page and store it securely. This token is used as your Git password when fetching over HTTPS.
5. Run the MediaTek-provided `scripts/genio-account-setup.py` (symlinked by the `repo` tool at manifest sync time, or run manually from the project root) to configure your environment for HTTPS fetching from Git01.

Before building the IoT Yocto image, please refer to the following links to correctly set up your build environment:

- [Setup Build Environment](https://genio.mediatek.com/doc/iot-yocto/latest/sw/yocto/get-started/env-setup/build-env-linux.html)

- [Setup Tool Environment](https://genio.mediatek.com/doc/iot-yocto/latest/sw/yocto/get-started/env-setup/flash-env-linux.html)

### Additional Package

More packages need to be installed in addition to packages mentioned in [Setup Build Environment](https://genio.mediatek.com/doc/iot-yocto/latest/sw/yocto/get-started/env-setup/build-env-linux.html):

```shell
$ sudo apt install libssl-dev

```

## Building

### Step 1: Download recipes

The `rity/scarthgap` manifest branch is a development branch that is updated every week, so its tip does **not** correspond to the PR2 snapshot. To reproduce exactly this PR2 pre-release, pin the manifest to the PR2 snapshot tag instead of the branch tip:

```shell
$ mkdir iot-yocto; cd iot-yocto
$ export PROJ_ROOT=`pwd`
$ repo init -u https://gitlab.com/mediatek/aiot/bsp/manifest.git -b refs/tags/rity-scarthgap-v26.1-pr2
$ repo sync -j 12

```

The `rity-scarthgap-v26.1-pr2` tag points at manifest commit [`0760458e75f3794090e20f3d59e0f592d8cdad92`](https://gitlab.com/mediatek/aiot/bsp/manifest/-/commit/0760458e75f3794090e20f3d59e0f592d8cdad92).

> If you prefer to track the latest in-development code instead of this PR2 snapshot, replace `refs/tags/rity-scarthgap-v26.1-pr2` with the branch name `rity/scarthgap`. Note that the branch tip changes weekly and may differ from this pre-release.

> If you have completed the Git01 account setup, `repo sync` will symlink `scripts/genio-account-setup.py` into the project root. Run it once to configure your Git01 HTTPS credentials before the NDA recipes are fetched.

### Step 2: Configure build environment

```shell
$ export TEMPLATECONF=$PROJ_ROOT/src/meta-rity/meta/conf/templates/default
$ source src/poky/oe-init-build-env
$ export BUILD_DIR=`pwd`

```

### Step 3: Edit `local.conf`

```shell
$ echo 'NDA_BUILD = "1"' >> $BUILD_DIR/conf/local.conf
$ echo 'DISTRO_FEATURES:append = " mt8894-apusys"' >> $BUILD_DIR/conf/local.conf
$ echo 'DL_DIR = "${TOPDIR}/../downloads"' >> $BUILD_DIR/conf/local.conf
$ echo 'SSTATE_DIR = "${TOPDIR}/../sstate-cache"' >> $BUILD_DIR/conf/local.conf

```

- `NDA_BUILD = "1"` produces the full image and fetches the private components from Git01 (this requires a valid Git01 account). As of Pre-Release 2, Genio Pro 5100 EVK only supports NDA\_BUILD.
- `mt8894-apusys` is mandatory to enable the NPU (APUSYS) support for Genio Pro 5100 EVK.

To build with the **Arm Mali DDK** GPU driver stack, as in the `gp5100-evk-mali` image, also add:

```shell
$ echo 'DISTRO_FEATURES:append = " mali"' >> $BUILD_DIR/conf/local.conf

```

To build with RTLinux (PREEMPT\_RT) configuration, as in the `gp5100-evk-robotic` image, add:

```shell
$ echo 'PREFERRED_PROVIDER_virtual/kernel = "linux-mtk-rt"' >> $BUILD_DIR/conf/local.conf

```

> Note that for the on-board PCIe to USB hub to work, a commercially licensed proprietary firmware is required.  
> Please visit [https://www.renesas.com/en/products/upd720201?tab=software-tools](https://www.renesas.com/en/products/upd720201?tab=software-tools) to read the license terms and download and install the firmware  
> if you want to enable USB 3.0 Type-A ports `CON5301`, `CON5302` and `CON5303`.
> 
> If and only if you have read and agree to the license terms, accept the license by adding the line `LICENSE_FLAGS_ACCEPTED:append = " commercial-Renesas-EULA"` to your `local.conf` file.

### Step 4: Fetch and build image

The Genio Pro 5100 EVK boots from **UFS** storage and uses a single `MACHINE`:

- `MACHINE=genio-pro-5100-evk`

```shell
$ export MACHINE=genio-pro-5100-evk
$ bitbake rity-demo-image

```

You can also build `rity-bsp-image` instead to reduce the image size:

```shell
$ export MACHINE=genio-pro-5100-evk
$ bitbake rity-bsp-image

```

To build the robotic image, as in the `gp5100-evk-robotic` image, with RT Linux (PREEMPT\_RT) and the ROS 2 preview,  
first add the `linux-mtk-rt` kernel setting from [Step 3](#step-3-edit-localconf), then run:

```shell
$ export MACHINE=genio-pro-5100-evk
$ bitbake rity-robotic-image-rt

```

> **Note** : Genio Pro 5100 v26.1-dev is at development stage. Some subsystems may still be in progress and are subject to change in later pre-releases.  
> Please refer to the release notes and the scope above for the current support status and limitation.

## Hardware Settings

For further hardware details, please refer to the document `MT8894 Evaluation Kit User Guide`.  
The document is not publicly available and is provided separately with the EVK board.

## Major Design Changes and Development Notes

The BSP support for Genio Pro 5100(MT8894) lands in a set of new branches and recipes:

- The Yocto kernel recipe for machine `genio-pro-5100-evk` is `linux-mtk-staging` instead of `linux-mtk`.  
The robotic image uses `linux-mtk-rt`, its PREEMPT\_RT variant.
- The kernel branch name is `mtk-staging` instead of `mtk-v6.6`. In PR2 it is based on Linux 7.3-rc5 (PR1: Linux 7.2-rc3).
- The bootloader is currently packaged into a single FIP binary located in UFS `ufsboot0`, built by recipe `u-boot-fip`.  
The `bootloaders` GPT partition still exists in the disk image but it is currently empty.
- The download agent has changed from recipe `lk` to `u-boot-da`. The implementation of the download agent for MT8894 has changed  
from LK (Little Kernel) to Trusted-Firmware-A and U-Boot.
- The U-Boot branch name is `mtk-staging` instead of `mtk-v2022.10`.
- The Trusted-Firmware-A branch name is also `mtk-staging`.

The branch name `mtk-staging` means that these branches are periodically **rebased** on top of the upstream mainline branch.  
This means the git history of these `mtk-staging` branches is unstable and can change anytime.

IoT Yocto v26.1-dev Pre-Release 2 is still capable of building images for other active Genio SoCs and EVKs, e.g. `genio-720-evk-ufs`.  
However, other Genio SoCs continue to use the same recipes and BSP branches as in v26.0.  
Only the Genio Pro 5100 (MT8894) BSP is supported by the new recipes and branches.
