Build a Yocto Image for NXP i.MX95 Verdin

Follow us on:

Share This Page

Facebook Twitter LinkedIn WhatsApp Email Copy Link

Close

Send Email Using

Gmail (Web) Thunderbird (default mail app)

Close

NXP i.MX95 Technical Guide

< >

NXP i.MX95 Technical Guide from RidgeRun

Contents Pin

• Introduction
  • What is i.MX95?
  • Why choosing RidgeRun for your i.MX95 software?
• Carrier Boards
  • Verdin Development Board
    • Toradex Easy Installer
      • Hardware Setup
      • Installing a pre-built image using GUI
      • Offline Installation of a pre-built image using GUI
      • Re-Installing Toradex Easy Installer
    • Torizon OS
      • Overview
      • Installing Torizon OS Pre-Built Image
      • Containers in Torizon OS
      • Torizon Core Builder
      • Customizing an image with Torizon Core Builder
• Yocto Support
  • Setup Yocto Environment
  • Building an image
  • Flashing the Board
  • Getting into the Board
• GStreamer Support
  • Capture & Recording
  • Playback Audio & Video
  • Snapshot
  • Display
  • Video Streaming
    • UDP & RTP Streaming
  • RidgeRun's Products
• Multimedia Support
  • Audio
  • Video Capture
    • Capture Subsystem
    • Testing Camera Capture
• Video Processing Unit-VPU
• Neural Processing Unit-NPU
  • eIQ Neutron NPU overview
  • Machine Learning Software Stack
  • Enabling NPU software with Yocto
  • Testing ML demos
• Camera driver porting for Toradex Verdin i.MX95
• FAQ
• Contact Us

This page shows how to build a Yocto reference image for the Toradex Verdin i.MX95 (also searched as imx95). The tested configuration uses MACHINE = "verdin-imx95" and accepts the NXP/Freescale EULA; choose either Toradex’s minimal or multimedia image recipe and run its documented BitBake command. This Toradex workflow is specific to Verdin i.MX95; NXP EVK and FRDM boards use NXP’s separate BSP and machine configuration.

Scope: Yocto BSPs for NXP i.MX95

Yocto builds combine metadata from OpenEmbedded, the processor vendor, and the board vendor. There is no single board-independent i.MX95 build configuration: the BSP, manifest, machine, and image recipe depend on the target board or System on Module (SoM).

NXP provides its i.MX Yocto BSP for NXP development boards. Toradex maintains a separate BSP and manifest for Toradex modules, including Verdin i.MX95. The detailed build commands below follow RidgeRun’s tested Toradex Verdin workflow. For the build-host and repository setup steps, first follow the Yocto environment setup guide.

Choose the Yocto BSP for your i.MX95 board

Yocto BSP selection by i.MX95 board

Target board or module	BSP documentation to start with	Scope of the RidgeRun workflow here
NXP i.MX95 EVK or FRDM board	NXP i.MX Yocto Project User’s Guide and the board’s NXP getting-started guide	NXP’s machine configuration and image instructions are not the Verdin-specific procedure below.
Toradex Verdin i.MX95	Toradex BSP Reference Documentation	The setup, image-building, flashing, and access links below cover Verdin i.MX95.
Other Toradex i.MX95 modules	Toradex documentation for the exact module and BSP release	Confirm the module’s machine configuration and carrier support before reusing any Verdin-specific steps.

NXP’s current meta-imx documentation lists machine configurations such as imx95-19x19-lpddr5-evk for the EVK and imx95-15x15-lpddr4x-frdm and imx95-19x19-lpddr5-frdm-pro for FRDM boards. Toradex documents separate machine configurations for its i.MX95 modules, including verdin-imx95, aquila-imx95, and toradex-smarc-imx95. Machine names can change between BSP releases, so verify them against the selected release. The RidgeRun build procedure provided below is for Verdin i.MX95; use the matching Toradex instructions for other modules.

Configure the Verdin i.MX95 build

After following the setup guide and sourcing export, edit build/conf/local.conf to target the Verdin i.MX95 and accept the NXP/Freescale EULA. Without the EULA setting, the build fails when building NXP components.

MACHINE = "verdin-imx95"
ACCEPT_FSL_EULA = "1"

The Toradex distribution is normally selected by the BSP configuration. The tdx-xwayland distribution is the usual default, but it can be changed in the DISTRO line:

DISTRO ?= "tdx-xwayland"

The available distribution variants documented for this workflow are tdx-xwayland (downstream kernel, without PREEMPT_RT), tdx-xwayland-rt (downstream with PREEMPT_RT), tdx-xwayland-upstream (upstream kernel, without PREEMPT_RT), and tdx-xwayland-upstream-rt (upstream with PREEMPT_RT). Keep the BSP default unless you specifically need another kernel variant, and verify availability for the BSP release you selected.

Choose and build a reference image

Go to the build directory:

cd build

Then launch the build command with the preferred image flavor. Use the minimal image for a headless command-line system. Choose the multimedia image when you need the graphical and multimedia stack listed below. The multimedia target is larger; in our tests, the first build took several hours and later builds benefit from the build cache.

Toradex reference image choices for Verdin i.MX95

Image recipe	Includes	Tested build command
tdx-reference-minimal-image	Headless system without a graphical interface; systemd, connman, and basic command-line packages	bitbake tdx-reference-minimal-image
tdx-reference-multimedia-image	Minimal-image features plus Weston/Wayland and XWayland, Qt, GStreamer, V4L2 camera framework, and graphical/Qt packages	bitbake -k tdx-reference-multimedia-image

The multimedia command keeps BitBake running after a package fails because it includes -k. This can collect more build errors in one run; inspect the reported failures before treating the build as successful.

Find the image artifacts

After a successful build, look in build/deploy/images/verdin-imx95/ for the artifacts:

Verdin i.MX95 deployment artifacts

Artifact	Recommended tool for installation
Verdin-iMX95_Reference-Minimal-Image-Tezi_<version>.tar or Verdin-iMX95_Reference-Minimal-Image-Tezi.tar	Toradex Easy Installer package for installing the image to eMMC.
Verdin-iMX95_Reference-Minimal-Image.wic.gz and Verdin-iMX95_Reference-Minimal-Image.wic.bmap	SD-card image artifacts for booting from removable storage.

The filename examples above are for the minimal image. Check the actual output filenames in the deploy directory when you build a different target. RidgeRun’s flashing guide recommends the Toradex Easy Installer workflow for eMMC; see Flash the image to the board for installation and SD-card details.

RidgeRun build and boot validation

The images built with the procedure documented on this page booted successfully on our tests. To continue from a successful boot, follow the guide to access the running Verdin i.MX95 system.

FAQ

Which Yocto image should I build for Verdin i.MX95?

Build tdx-reference-minimal-image for a headless command-line system. Choose tdx-reference-multimedia-image when you need the documented graphical and multimedia components.

Why does the Verdin i.MX95 build need ACCEPT_FSL_EULA = "1"?

The documented build requires acceptance of the NXP/Freescale EULA to build NXP components. Without this setting, the build fails when those components are built.

Can I use these commands for an NXP i.MX95 EVK or FRDM?

No. These instructions target the Toradex Verdin i.MX95 with MACHINE = "verdin-imx95". NXP EVK and FRDM boards use NXP’s BSP and board-specific machine configurations.

Where are the generated image files?

Look in build/deploy/images/verdin-imx95/. The exact filenames depend on the selected image recipe and BSP release.

References

• RidgeRun Yocto environment setup for Verdin i.MX95
• RidgeRun guide to flashing the Verdin i.MX95
• RidgeRun guide to accessing the running board
• NXP i.MX Yocto Project User’s Guide
• Toradex BSP Reference Documentation

Back to top ↑ < >