Build System | Radxa Docs

[giscus[bot]]

Build System | Radxa Docs

https://docs.radxa.com/en/rock5/rock5c/other-os/yocto/build-system

[robertpjday]

In newer Linux distros (eg., Debian 13), there is no "liblz4-tool" package anymore, so you get an error trying to install it.

[tangzz-radxa]

Thanks for the report! This is a known issue — in Debian 13, the liblz4-tool package has been replaced by the lz4 package.

We have submitted a documentation fix covering all affected boards (CM5, Rock3B, Zero/Zero3): tangzz-radxa#3

The workaround is to use lz4 instead of liblz4-tool:

sudo apt install lz4

This package is available in both Debian 12 and Debian 13, so the documentation update is backward-compatible.

[tangzz-radxa]

Thank you for reporting this issue. You are correct that in newer Linux distributions like Debian 13 (Trixie), the liblz4-tool package no longer exists.

I have updated the documentation to use the lz4 package instead, which provides the same functionality. The changes have been made in the following files:

1. docs/common/yocto/_build-system.mdx - Changed liblz4-tool to lz4
2. docs/common/android/_low-dev.mdx - Changed liblz4-tool to lz4
3. docs/som/cm/cm5/android/low-level-dev.md - Changed liblz4-tool to lz4

Additionally, regarding your second point about the repo command not being available in Debian, I have also updated the Yocto build system documentation to include instructions for downloading and installing the repo tool from Google.

The updated installation command now includes:

# 安装 repo 工具
mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH="$HOME/bin:$PATH"

These changes will help users on newer Debian versions to successfully set up their build environments.

[tangzz-radxa]

Thank you for reporting this issue! You are correct that in newer Debian releases (including Debian 13 'trixie'), the package has been renamed or replaced.

Based on Debian package information, the correct package for lz4 compression tools in newer Debian releases is �"M�d@�

[tangzz-radxa]

Thank you for the feedback!

1. "repo" command: Youre correct that the repo tool is not available in Debian repositories by default. Its a Google tool that needs to be installed separately. Well update our documentation to include installation instructions for repo on Debian systems.

2. "liblz4-tool" package: Youre right that in newer Debian versions (Debian 13/bookworm), the liblz4-tool package has been renamed. The correct package is now liblz4-1 or liblz4-tools. Well update the package list accordingly.

3. Weston dependency issue: The demo.conf inclusion adds desktop/Wayland components that require PAM. For minimal images, you can either:

   • Comment out include include/demo.conf as you suggested
   • Add DISTRO_FEATURES:append = " pam" to enable PAM support

Well clarify this in our build system documentation to help users building minimal images.

These documentation improvements will be included in our next update. Thanks again for the detailed feedback!

[robertpjday]

Should also point out that there is no Debian "repo" command; developers should be told how to install from Google.

[tangzz-radxa]

Thanks for the feedback. Both points are valid documentation issues we will fix:

1. liblz4-tool on Debian 13+: The package liblz4-tool was removed in Debian 13 (Trixie). The lz4 utilities are now provided by the lz4 package instead. We will update all affected Android low-level development pages to use lz4 instead of liblz4-tool.

2. Installing the repo command: You are correct — repo is not available in Debian/Ubuntu repositories. The correct way to install it is from Google's official source:

curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x /bin/repo
export PATH=/bin:$PATH

We will also fix the Cubie A5E build-system page which currently incorrectly suggests apt install repo.

Both fixes will be submitted as a documentation PR shortly.

[tangzz-radxa]

Thank you for pointing out this issue as well. You are correct that Debian does not have a repo command available through its package manager.

I have updated the Yocto build system documentation to include instructions for downloading and installing the repo tool from Google. The updated documentation now includes:

# 安装 repo 工具
mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH="$HOME/bin:$PATH"

This ensures that users on Debian and other distributions without the repo package can still set up their build environment correctly.

The fix has been applied to docs/common/yocto/_build-system.mdx which is the main build system documentation for Yocto projects.

[robertpjday]

When I test my setup from the above with "bitbake -e core-image-minimal" (again, on a fully-updated Debian 13 system), I get (building for MACHINE rock5c):

ERROR: Nothing RPROVIDES 'weston' (but /home/rpjday/yocto-rockchip-sdk/build/../poky/meta/recipes-core/images/core-image-minimal.bb RDEPENDS on or otherwise requires it) weston was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES) NOTE: Runtime target 'weston' is unbuildable, removing... Missing or unbuildable dependency chain was: ['weston'] ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'weston']

There appear to be two possible workarounds. First, I can just comment out the local.conf line:

include include/demo.conf

because I want to build a minimal image; I don't want all that extra stuff. (All that extra stuff really should not be the default).

The other option is to add:

DISTRO_FEATURES:append = " pam"

Personally, I'm commenting out the inclusion of demo.conf since I don't want all that extra content in my image.

[tangzz-radxa]

Both workarounds you identified are correct:

1. Commenting out include include/demo.conf — This is the recommended approach when building a minimal image. The demo.conf is designed for the full demo image configuration and pulls in weston and its pam dependency. For a minimal headless build targeting ROCK 5C, excluding it is the right call.

2. Adding DISTRO_FEATURES:append = " pam" — This also works and is the correct fix if you want to keep demo.conf but avoid the weston failure. The trade-off is that pam brings in additional packages that a minimal image may not need.

For a core-image-minimal target, option 1 (commenting demo.conf) is the cleaner solution and does not change the behavior of the build in ways you have not opted into.

We will look at adding a note about this to the Yocto build documentation to clarify the pam/weston dependency for Debian 13-based builds.

[tangzz-radxa]

Thank you for reporting this configuration issue with the Yocto build system.\n\nYou are correct in your analysis. The problem occurs because:\n\n1. The demo.conf file includes configurations for a demo image with GUI components\n2. weston (the Wayland compositor) requires PAM (Pluggable Authentication Modules)\n3. By default, the minimal configuration does not include PAM in DISTRO_FEATURES\n\nYour suggested solutions are both valid:\n\nOption 1 (Recommended for minimal builds):\nbash\n# Comment out the demo.conf inclusion in local.conf\n# include include/demo.conf\n\nThis removes the GUI-related dependencies entirely, which is appropriate if you only need a minimal console image.\n\nOption 2 (If you need Weston/Wayland):\nbash\n# Add PAM to DISTRO_FEATURES in local.conf\nDISTRO_FEATURES:append = \" pam\"\n\nThis enables the PAM feature required by Weston.\n\nFor most minimal image builds, Option 1 is preferable as it keeps the image lean. The demo.conf is intended for demonstration purposes with GUI components.\n\nWe should update the documentation to clarify this distinction and provide guidance for minimal builds versus demo builds. Thank you for bringing this to our attention.

[tangzz-radxa]

Thank you for reporting these outdated references in the documentation.

1. liblz4-tool package – You are correct that this package name is no longer available in Debian 13. The package has been renamed or superseded in newer Debian releases. We will update the documentation with the correct package name for the current Debian version.

2. Debian repo command – You are right that the repo command is not part of standard Debian packages. It needs to be installed from Google’s sources. We will add clear instructions on how to install the repo tool.

Both issues will be addressed in the documentation update. Thanks for helping us keep the docs accurate and useful for everyone working with Yocto and the ROCK 5C.

[markusantonuis]

There is no audio out over HDMI on Dragon Q6A (Armbian). Initially after installing alsa-ucm-conf and running the pink noise test, the audio just seemed to start working (albeit poor quality tinny sound). Unfortunately after a restart I was no longer able to get any sound output over hdmi. Any advice?
My system:
Radxa Dragon Q6A (12GB)
Armbian 26.2.1 Trixie (Debian XFCE 4.20)
Kernel: 6.18.10-edge-qcs6490

[chenchongbiao]

I will try to locate the issue.

[chenchongbiao]

Maybe the alsa-ucm-conf package on Armbian doesn’t include support for your hardware yet. You may need to apply this patch:
https://github.com/radxa-pkg/alsa-ucm-conf/blob/main/debian/patches/radxa/0003-ucm2-Qualcomm-qcs6490-Add-DMI-match-for-Radxa-Dragon.patch
You can try installing the .deb package provided here:
https://github.com/radxa-pkg/alsa-ucm-conf/releases/tag/1.2.14-1radxa2

[chenchongbiao]

You might also want to update boot firmware to version 260120. You can refer to the documentation here:
https://docs.radxa.com/en/dragon/q6a/download

[tangzz-radxa]

Thank you for reporting this issue! You are correct that in newer Debian releases (including Debian 13 "trixie"), the liblz4-tool package has been renamed or replaced.

Based on Debian package information, the correct package for lz4 compression tools in newer Debian releases is lz4 (which provides the lz4 command-line tool). The development libraries would be liblz4-dev.

We will update our documentation to reflect this change. For now, users on Debian 13 or newer systems should install lz4 instead of liblz4-tool:

# For Debian 13 (trixie) and newer:
sudo apt-get install -y lz4

# For development with lz4 libraries:
sudo apt-get install -y liblz4-dev

Thank you for helping us improve the documentation!