Yocto build progress stops at some percentage

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

Regarding Yocto new release of meta-tegra GitHub - OE4T/meta-tegra: BSP layer for NVIDIA Jetson platforms, based on L4T · GitHub

and use github: GitHub - OE4T/tegra-demo-distro: Reference/demonstration distro for meta-tegra · GitHub as demo project,

Follow the build steps of “tegra-demo-distro” (with new meta-tegra meta-tegra in repo)

Steps:

$ git clone GitHub - OE4T/tegra-demo-distro: Reference/demonstration distro for meta-tegra · GitHub

$ cd tegra-demo-distro

$ git submodule update --init

$ . ./setup-env --machine jetson-orin-nx-devkit

$ bitbake -v -D demo-image-full

The Yocto github demo project ‘tegra-demo-distro’ build process issues and cannot complete:

1.It will usually stop at “parse receipes at 99%”..

I’ve found some solution for example: to delete bitbake.lock and rebuilt to get around it. The process will continue.

  1. Build not progress at (attach file)
    current running tasks (783 of 12851) %6 |#####, or
    current running tasks (783 of 12851) %25 |#####, or
    current running tasks (783 of 12851) %49 |#####

It just not going to continue the process, i’hve check the disk/and memory are enough, and use normal user id to build,

how to get around this build suitation.

  1. how to flash the yocto image once the build is complete?

  2. Is there any the Yocto EA BSP release note (2026, april) can be as development/building reference?

    ( attachement : yocto_build_no_progress.txt (747.2 KB))

thanks.

3

Hej Noah,

On which branch are you ? On current `master` machine `jetson-orin-nx-devkit` doesn’t exist (only orin nano and agx-orin devkits). There are `p3509-a02-p3767-0000` and `p3768-0000-p3767-0000` depending on which carrier board for your nano nx you want to build for.

Do you have the full log before ?

A full Yocto build from scratch can take many hours depending on the PC you use and the speed of your disks. So it can be normal that it can look like stuck during some time. Later builds will benefit from the cache and can be very fast.

Yes you must use a normal user id to build, that’s the correct way to do it.

For the later steps, there are flashing scripts in the deploy folder. First let’s get you to build.

Cheers,

/Martin

4

Just a quick update

Build the image

Successfully built `tegra-demo-distro` for `MACHINE=p3509-a02-p3767-0000` on current master (commit `ad7145bc6f28f0449e7501b5987138d167c0eb3b`). This is for orin nx module on the old orin nx devkit baseboard.

If it still doesn’t build for you:

  • git update / git pull to update to latest commit, maybe there was an intermediate commit that didn’t build
  • wait some longer, as it can take a lot of time, especially the `demo-image-full` image. Maybe first build a lighter image like `demo-image-base` or even `core-image-minimal`. Once that done, you can build the heavier ones, a lot of the cache will be reused
  • check your computer installation that all prerequisite software are correctly installed

Flash the image

After successful build, in your `tmp/deploy/images/${MACHINE}/` folder there is a `demo-image-full-${MACHINE}.rootfs.tegraflash-tar.zst` file that you can extract.

Inside it just run the `./doflash.sh` command with your board in recovery mode and it will flash the image.