Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello!
It seems you’re encountering a conflict between your custom defconfig and the default one specified by KBUILD_DEFCONFIG. The warnings indicate that the defconfig from SRC_URI is being ignored. Let’s address this so your custom configuration is used.
Here’s what you can do:
-
Unset KBUILD_DEFCONFIG: This will prevent the default in-tree defconfig from taking precedence. Add the following line to your bbappend file:
unset KBUILD_DEFCONFIG -
Ensure Correct File Path Precedence: You’ve already set FILESEXTRAPATHS correctly, which is great. This ensures the build system looks in your custom directory first:
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:" -
Verify KCONFIG_MODE: The
KCONFIG_MODE = "alldefconfig"setting should work for using your custom defconfig. Ensure your defconfig file is correctly named and placed in the expected directory. -
Rebuild the Kernel: After making these changes, clean the state and rebuild your kernel recipe:
bitbake -c cleansstate linux-toradex bitbake linux-toradex
By following these steps, your custom defconfig should be applied during the kernel build process, resolving the warnings and ensuring your modifications are included.
If you have any more questions, feel free to ask!
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
https://git.yoctoproject.org/poky/plain/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb.