---
title: "What's next"
---

# What's next

The Embedded Linux functions that are not built yet, grouped by the vendor tool or area they replace.

Everything below is **not built**. Nothing on this page can be used today. Beyond these, every built capability still has to run on Windows, against a real build server, on Wind River Linux and on real boards before it moves past modelled (see each page's state).

## Within the areas already built

- Writing kas files (layer changes on a kas build are pointed to the kas file, not written there).
- `bitbake-layers show-cross-depends`, `flatten`, `layerindex-fetch`, `save-build-conf` and `yocto-check-layer`.
- Completion in BitBake recipes.
- Resolving `KERNEL_FEATURES` (Wind River and Yocto kernel-cache `.scc` features); `menuconfig` embedded in the editor.
- `devtool runqemu`.
- `devtool sdk-update` for an extensible SDK; running `devtool ide-sdk` (its CMake preset is already read).
- The LTTng Disk I/O and Kernel Memory views.
- Buildroot `legal-info` in the licence review.
- MISRA C++ checks.
- Memory, disassembly and instruction breakpoints on 64-bit targets (the shared debug session writes 32-bit addresses).

## Wind River Linux, Workbench and Studio

- Platform project setup with `setup.sh` (machines, templates, distros, layers); Wind River Linux is only recognised today.
- Workbench Project Explorer for a platform project.
- User Space Configuration: packages and package groups of the image.
- Workbench-style application debug with several processes (gdbserver debug covers part of it).
- Kernel-mode debug over KGDB.
- On-chip JTAG debug with Wind River probes.
- System Viewer event traces for Linux (the ftrace and LTTng views cover the Linux side).
- Workbench's own Memory Analyzer, Performance Profiler and Code Coverage views (Valgrind, perf and gcov cover the Linux side).
- Linux Assembly Tool (`appsdk`: `genimage`, `gensdk`, `genrpm`, `publishrpm`, `geninitramfs`, `gencontainer`, `genyaml`).
- Binary distribution: RPM or DEB package feeds and OSTree-based images.
- OSTree upgrade of a deployed target.
- meta-wr-sbom SBOM generation run from the editor (reading it is built).
- Wind River Scanning Tool: SBOM upload, CVE dashboard and team triage.
- Rolling cumulative patch layer (RCPL) updates.
- Wind River's per-package CVE database.
- Out-of-tree kernel module projects.
- The build properties dialog (build spec, defines, include paths, toolchain).
- eLxr Pro, Wind River's Debian-derived distribution.
- Import of Workbench's Eclipse keymap, perspectives, launch configurations and target connections.

## Yocto Project

- `devtool menuconfig` for Kconfig-based recipes.
- `devtool build-image`.
- `devtool ide-sdk` per recipe.
- Dependency graphs (`bitbake -g`): why a package is in the image.
- Toaster's functions: projects and New Project; project configuration (machines, distros, layers, image and software recipes, variables); layer import and details; custom images by package selection; the build dashboard; recipes, packages and tasks of a build with shared-state reuse; build time, CPU time and disk I/O per task; image contents and why each package is there; recent and per-project builds; command lines of builds started outside it.
- Extensible SDK workflows (`populate_sdk_ext`, `devtool sdk-update`, `sdk-install`, `build-sdk`).
- Kernel metadata (`KERNEL_FEATURES`, `.scc` files).
- Kernel patches and out-of-tree modules (reachable through devtool, not verified on linux-imx).
- U-Boot recipe work (`UBOOT_MACHINE`, configuration, environment).
- `oe-selftest`.
- Error reports (`report-error` class).

## NXP i.MX

- Config Tools for i.MX: the Pins tool (`.dtsi` output) and the DDR tool.
- Secure boot: HAB and AHAB with `imx-mkimage` and the Code Signing Tool.
- Cortex-M firmware beside Linux through remoteproc.

## TI Processor SDK Linux and Code Composer Studio

- The Yocto build with TI's layer setup.
- The SDK's top-level makefile for kernel, U-Boot and device trees.
- SD card and flash writing (`create-sdcard.sh`, DFU, flash writers).
- SysConfig pinmux to `devicetree.dtsi`.
- Code Composer Studio's Remote Explorer, GDB setup and kernel debugging.
- The R5F and M4F cores beside Linux.
- Secure boot on HS-SE devices (signing, `binman`, OTP keywriter).

## AMD PetaLinux, EDF and Vitis

- `petalinux-create` from a BSP or template, with apps and modules.
- `petalinux-config -c kernel` and `-c u-boot` (the root file system configuration is built).
- Application and module templates, `petalinux-devtool`.
- Device tree: generated PL nodes from the XSA and `system-user.dtsi`.
- Bootgen (`.bif` to `BOOT.BIN`, authentication and encryption).
- Vitis Unified IDE: Linux applications, Target Connections, TCF agent remote debug (gdbserver debug covers part of it).
- RPU (Cortex-R5F) applications with OpenAMP beside Linux.
- XSDB and Vitis JTAG debug of FSBL, U-Boot and the kernel.
- PetaLinux to EDF migration.

## ST OpenSTLinux and STM32Cube tools

- The OpenSTLinux Developer Package (TF-A, OP-TEE, U-Boot and kernel built outside Yocto).
- STM32CubeMX device trees for kernel, U-Boot and TF-A with user sections.
- STM32CubeIDE MPU projects and Linux-side debug (gdbserver debug covers part of it).
- Cortex-M coprocessor firmware loaded through remoteproc.
- Secure boot: key generation, signing tool, OTP programming.

## Renesas RZ

- The RZ/G Verified Linux Package.
- Writing the bootloaders over the serial port (Flash Writer).
- e2 studio with the RZ Multi-OS package (FSP on the Cortex-M33 beside Linux).
- e2 studio Linux application debug (gdbserver debug covers part of it).

## Toradex Torizon

- New projects from the Torizon IDE extension's templates.
- Building the application container and deploying it over SSH.
- Debugging inside the container on the target.
- The extension's workspace settings.
- The device list and connection.
- TorizonCore Builder (`tcbuild.yaml`).
- Torizon Cloud OTA packages and fleet updates.
- Toradex Easy Installer.
- Toradex BSP layers for Yocto builds without Torizon.

## Siemens Embedded and kas

- Sokol Flex OS.
- Sourcery CodeBench (gdbserver debug covers part of it).
- Sourcery Analyzer's synchronised timelines (LTTng traces are read already).
- Isar, Debian-based image builds with BitBake.

## Buildroot

- `menuconfig`, `nconfig`, `xconfig` and `gconfig`.
- `defconfig`, `savedefconfig`, `update-defconfig` and `list-defconfigs`.
- `linux-menuconfig`, `uboot-menuconfig`, `busybox-menuconfig`, `<pkg>-update-defconfig` and `<pkg>-diff-config`.
- `make` and the per-package targets (`<pkg>`, `-rebuild`, `-reconfigure`, `-reinstall`, `-dirclean`, `-source`).
- `BR2_EXTERNAL` trees and out-of-tree output (`O=`).
- `sdk` and `toolchain`.
- `graph-build`, `graph-depends`, `graph-size` and the dependency targets.
- `legal-info`.
- `show-info` for an SBOM.
- `pkg-stats`.
- `source` and `external-deps` for offline builds.
- `printvars` and `show-vars`.

## Lauterbach TRACE32 with Linux awareness

- PowerView connection to the Cortex-A cores for bootloader bring-up.
- The Linux awareness extension and its Linux menu.
- MMU set-up for Linux.
- The process and task list.
- Kernel module debugging with the symbol autoloader.
- Process debugging (Debug New Process, Watch Processes, shared libraries).
- Kernel information displays.
- Task run-time analysis from the trace.
- Off-chip and on-chip trace (ETM or PTM) with process context.
- PRACTICE scripts (`.cmm`) for sessions and CI.
- The TRACE32 remote API and GDB front end.
- Linux on the A cores and an RTOS on the R or M cores in one setup.

## Arm Development Studio

- Linux kernel debug over DSTREAM.
- Linux kernel OS awareness per kernel version.
- Threads and kernel module symbols.
- Linux application debug through Arm DS (gdbserver debug covers part of it).
- Streamline system-wide profiles.
- Boot chain debug on FVP models and boards.
- The Platform Configuration Editor.

## SEGGER J-Link and Ozone

- J-Link GDB Server on a Cortex-A core for SPL and U-Boot bring-up.
- Ozone with a U-Boot or kernel ELF.
- J-Link script files for Cortex-A initialisation.
- J-Flash SPI or J-Link Commander for boot flash.
- Kernel debugging through the J-Link GDB server.

## Linux tools and host services

- KGDB and KDB over a serial console.
- TFTP and NFS root for development.

## Security, updates and test automation

- Vendor secure boot chains in one signing view: NXP HAB and AHAB, TI, AMD Bootgen and ST, and UEFI Secure Boot signing for x86 targets.
- Mender server deployments, device groups and phased roll-out.
- LAVA: job definitions, device dictionaries, results and health checks.
