Yocto自定义BeagleBone BSP中do_kernel_metadata任务执行失败求助

Hey there! First off, kudos for diving into Yocto for your custom BeagleBone board—this stuff can be tricky when you're starting out, so don't beat yourself up over the do_kernel_metadata failure. Let's break down what might be going wrong and how to fix it:

1. Verify Kernel Version Compatibility with Your Yocto Release #

You selected kernel version 4.12, but Yocto's support for older kernel versions drops off as new releases roll out. For example:

• Yocto releases like Thud (2.6) or earlier include official support for 4.12, but newer releases (Dunfell and beyond) focus on more recent kernels (4.14+).
• If you're using a modern Yocto version, either switch to a kernel version supported by your release or downgrade Yocto to a version that works with 4.12.

2. Fix Meta-Layer Configuration Issues #

Double-check your bblayers.conf setup:

• Drop the extra underscores from the layer name (you wrote __meta-biatime__—it should be meta-biatime without the double underscores).
• Confirm the layer path in the BBLAYERS variable is correct, like:

  BBLAYERS += "${TOPDIR}/meta-biatime"
  

• Ensure meta-biatime has a valid conf/layer.conf file (the yocto-bsp tool should generate this, but it's worth a quick check).

3. Correct the CPU Tune Typo #

You mentioned "tune for cortex8"—this is almost certainly a typo. Yocto's valid tune for the BeagleBone's CPU is cortexa8, not cortex8:

• Open meta-biatime/conf/machine/biatime.conf
• Make sure DEFAULTTUNE is set to:

  DEFAULTTUNE = "cortexa8"
  

A wrong tune value breaks kernel metadata parsing by mismatching architecture settings.

4. Inspect Generated Kernel Recipe Files #

The yocto-bsp tool creates kernel-related recipes in meta-biatime/recipes-kernel/linux. Look for common issues:

• Invalid SRC_URI or SRCREV values pointing to non-existent 4.12 kernel sources/branches.
• Malformed .bbappend files that override kernel configurations incorrectly.
  If you're pulling sources from a custom repo, double-check the URL and revision are accurate.

5. Clean Build Artifacts and Retry #

Cached files from previous attempts can cause unexpected failures. Run these commands to reset:

# Clean the kernel recipe's build state
bitbake -c cleansstate linux-biatime

# Or wipe the entire build directory (if you're okay starting fresh)
rm -rf build/

Then re-run your build process to rule out cache-related problems.

6. Dig Into the Error Log for Exact Details #

The most helpful step is to check the full error log from the do_kernel_metadata task. You'll find it at:

tmp/work/biatime-poky-linux-gnueabi/linux-biatime/4.12-r0/temp/log.do_kernel_metadata

Look for lines starting with ERROR or WARNING—these will tell you exactly what's failing (e.g., missing files, invalid syntax, or incompatible kernel options).

Try these steps one by one, and if you can share specific error snippets from the log, we can narrow things down even further. You're already doing great by putting in the work to build a custom BSP—hang in there!

内容的提问来源于stack exchange，提问作者Initerworker