Custom machine problems

Hello! i am working on ZEDBOARD build in yocto but i want to make build using my custom xsa and custom machine
Configuration of my external_hdf.bbappend is
FILESEXTRAPATHS:prepend := “${THISDIR}/files:”

HDF_EXT = “xsa”
HDF_BASE:zynq-custom= “file://”
HDF_PATH:zynq-custom= “zedBoard_wrapper.xsa”

MACHINE_BASE = “${@‘-’.join(MACHINE.rsplit(‘-’)[-2:])}”
do_deploy:prepend() {
if [ “${MACHINE_BASE}” != “${MACHINE}” ] &&
[ -d ${WORKDIR}/git/${MACHINE_BASE} ]; then
ln -sf ${MACHINE_BASE} ${WORKDIR}/git/${MACHINE}
fi
}
and my machine is
require conf/machine/zynq-generic.conf

HDF_BASE = “file://”
HDF_PATH = “/home/uroosa/yocto/sources/meta-custom/recipes-bsp/external-hdf/files/zedBoard_wrapper.xsa”

EXTRA_IMAGEDEPENDS += "
u-boot-xlnx-uenv
"
IMAGE_BOOT_FILES += "
boot.bin
uEnv.txt
"
but whenever i make image for my custom machine it build successfully but when i put my sdcard into my board nothing happened . Please help me tackle this problem…

Regards
Uroosa Iftikhar

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Based on the context provided, here are some steps you can take to troubleshoot the issue with your ZEDBOARD not booting:

  1. Verify Boot Files: Ensure that boot.bin and uEnv.txt are correctly generated and placed in the root directory of the SD card. These files are crucial for the boot process, and any misconfiguration or absence can prevent the board from booting.

  2. Check HDF File: Make sure that the zedBoard_wrapper.xsa file is correctly formatted and compatible with the ZEDBOARD hardware. Any issues with this file could lead to boot failures.

  3. Inspect Console Output: Connect to the board’s console and observe the output during the boot process. Look for any error messages or indications of what might be going wrong. This can help determine if the issue is with the image or the hardware setup.

  4. Review Paths and Dependencies: Double-check that the paths specified in HDF_BASE and HDF_PATH are correct and accessible during the build process. Incorrect paths may result in missing files in the final image, which could prevent the board from booting.

  5. Bootloader Configuration: Ensure that the bootloader (u-boot) is correctly configured to load the kernel and other necessary files. If the bootloader is not set up properly, the board will not boot from the SD card, even if the image is built successfully.

By following these steps, you should be able to identify and resolve the issues preventing your ZEDBOARD from booting with the custom image.

Please, also check if these links can help you solve your problem:

Yocto MACHINE customization best practice.

Hi @uroosa

Sorry but we don’t work with ZEDBOARD. You can find our list of supported products here.

You should contact the website where you acquired it.

Also, you may be interested in the Torizon OS.
It’s a ready-to-use and easy-to-use OS with a complete software ecosystem.