Looking at your configuration, I can identify several potential issues that could be causing the Chromium build failure (1).
Configuration Issues
1. Layer Compatibility Issue
Your bblayers.conf shows you’re missing the Scarthgap compatibility fix. You need to add Scarthgap to the supported Yocto versions of meta-chromium (1):
$ sed -i 's/^\(LAYERSERIES_COMPAT_chromium-browser-layer = ".*nanbield\)/\1 scarthgap/' ../layers/meta-browser/meta-chromium/conf/layer.conf
(1)
2. Missing GPU Acceleration Patches
For GPU-accelerated Chromium v117, you need the NXP patches from meta-imx. Your configuration shows meta-toradex-chromium layer but doesn’t show if you’ve properly copied the GPU acceleration patches (1).
You should have created the patches following these steps (1):
$ cd ../build
$ bitbake-layers create-layer ../layers/meta-toradex-chromium
$ bitbake-layers add-layer ../layers/meta-toradex-chromium
$ rm -rf ../layers/meta-toradex-chromium/recipes-example
$ cp -r ../layers/meta-imx/meta-imx-sdk/dynamic-layers/chromium-browser-layer/recipes-browser ../layers/meta-toradex-chromium
(1)
3. Local.conf Configuration
Your local.conf looks mostly correct, but ensure you have the proper Chromium configuration (1):
CORE_IMAGE_EXTRA_INSTALL += "chromium-ozone-wayland"
LICENSE_FLAGS_ACCEPTED += "commercial_libav commercial_x264"
(1)
Required Steps to Fix
1. Verify meta-clang Layer
Ensure you have the meta-clang layer properly cloned in the Scarthgap branch (1):
$ cd ${LAYERDIR}/meta-openembedded/
$ git clone -b scarthgap https://github.com/kraj/meta-clang.git
(1)
2. Check meta-browser Checkout
For GPU acceleration, you need Chromium v117. Verify your meta-browser is checked out to the correct commit (1):
$ cd meta-browser
$ git checkout dc31889c0899971def535dc1c040edf18bc16691
(1)
3. Verify Layer Structure
Your meta-toradex-chromium should have this structure after copying the NXP patches (1):
.
├── conf
│ └── layer.conf
├── COPYING.MIT
├── README
└── recipes-browser
└── chromium
├── chromium-ozone-wayland
│ ├── 0001-Fixed-chromium-flicker-with-g2d-renderer.patch
│ ├── 0002-chromium-met-EGL-API-GetProcAddress-failures.patch
│ └── [other patches...]
└── chromium-ozone-wayland_%.bbappend
(1)
Build Command
Use the correct build command (1):
$ bitbake tdx-reference-multimedia-image
(1)
Without seeing the specific error message, these are the most common configuration issues that cause Chromium build failures. The GPU acceleration patches and layer compatibility are critical for successful builds.
Best regards, Toradex AI Assistant.
Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.