I just run “repo sync” on my yocto tree for apalis-imx8qm platform. Before I run “repo sync” that tree was be able to bitbake normally. But after I run “repo sync”, the following error message comes out. May I ask what should it do to fix this issue?
ERROR: device-tree-overlays-toradex_5.15-2.2.x-imx+gitAUTOINC+939f660fed-r0 do_deploy: apalis-imx8_hdmi_overlay.dtbo is not installed in your boot filesystem, please make sure it’s in TEZI_EXTERNAL_KERNEL_DEVICETREE or being provided by virtual/dtb.
ERROR: device-tree-overlays-toradex_5.15-2.2.x-imx+gitAUTOINC+939f660fed-r0 do_deploy: ExecutionError(‘/home/tak/workspace/yocto/oe-core-20240212/build/tmp/work/apalis_imx8-tdx-linux/device-tree-overlays/toradex_5.15-2.2.x-imx+gitAUTOINC+939f660fed-r0/temp/run.do_deploy.948819’, 1, None, None)
ERROR: Logfile of failure stored in: /home/tak/workspace/yocto/oe-core-20240212/build/tmp/work/apalis_imx8-tdx-linux/device-tree-overlays/toradex_5.15-2.2.x-imx+gitAUTOINC+939f660fed-r0/temp/log.do_deploy.948819
ERROR: Task (/home/tak/workspace/yocto/oe-core-20240212/build/…/layers/meta-toradex-nxp/recipes-kernel/linux/device-tree-overlays_git.bb:do_deploy) failed with exit code ‘1’
ERROR: linux-toradex-5.15.148+git999-r0 do_compile: oe_runmake failed
ERROR: linux-toradex-5.15.148+git999-r0 do_compile: ExecutionError(‘/home/tak/workspace/yocto/oe-core-20240212/build/tmp/work/apalis_imx8-tdx-linux/linux-toradex/5.15.148+git999-r0/temp/run.do_compile.948683’, 1, None, None)
ERROR: Logfile of failure stored in: /home/tak/workspace/yocto/oe-core-20240212/build/tmp/work/apalis_imx8-tdx-linux/linux-toradex/5.15.148+git999-r0/temp/log.do_compile.948683
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
The error message you’re encountering indicates that the apalis-imx8_hdmi_overlay.dtbo is not installed in your boot filesystem. This is likely causing the do_deploy task to fail. Here are a few steps you can take to resolve this issue:
Check TEZI_EXTERNAL_KERNEL_DEVICETREE: Ensure that the apalis-imx8_hdmi_overlay.dtbo is included in the TEZI_EXTERNAL_KERNEL_DEVICETREE variable. This variable is responsible for specifying which device tree overlays should be included during the build process. You can find this variable in your machine configuration files, such as machine.conf or machine.inc.
Verify Overlay Availability: Make sure that the apalis-imx8_hdmi_overlay.dtbo is available in the expected location. You can check the device tree overlays repository to ensure that the overlay file is present and correctly named.
Update Recipes: If the overlay is not being provided by virtual/dtb, you may need to update your Yocto recipes to ensure that the overlay is being built and deployed correctly. You can write your own bbappends to add your device tree overlays repository if necessary.
Rebuild the Image: After making the necessary changes, try rebuilding your image using bitbake. This will ensure that any changes to the configuration or recipes are applied.
Check Logs: Review the log files mentioned in the error messages for more detailed information about what might be causing the failure. This can provide additional clues on how to resolve the issue.
If these steps do not resolve the issue, you may need to further investigate the specific configuration and setup of your Yocto Project environment to ensure that all necessary components are correctly configured.
Please, also check if these links can help you solve your problem:
In our article about Build a Reference Image with Yocto Project/OpenEmbedded, you can find the steps needed to build an image using Yocto Project. It says the next step after repo sync is to use . export, which will configure the shell environment for the current shell session.
Please, try this and tell me if it works. If it doesn’t work, could you tell me what steps you took before run repo sync?
Thanks for your help and reply. I have already tried . export before but no luck. I did the repo sysc because I needed to add a LTE modem to the board but the /dev/ppp and the other corresponding driver didn’t show up as expected. I search the web and someone mentioned that do repo sync can help. Therefore I tried it and that yocto tree got stuck. Now I temporary move my work to a new tree completely and it work fine. I may go back to see what exact problem of the old tree was and get back to you soon.
