Hi @PeterOgden,
Got some progress from yesterday. 
The missing BSP file error from previous comment is caused by a possible bug in the Makefile. Namely the create_bsp.sh is called with the BSP=... parameter, even if there no BSP file present:
BSP_BUILD_$1 := $$(BUILD_ROOT_$1)/petalinux_bsp
BSP_ABS_$1 := $$(patsubst %,$$(BOARDDIR_$1)/%,$$(BSP_$1))
BSP_PROJECT_$1 := xilinx-$$(shell echo $1 | tr A-Z a-z | tr -cd '[:alnum:]')-$$(KERNEL_VERSION)
BSP_TARGET_$1 := $$(BSP_BUILD_$1)/$$(BSP_PROJECT_$1).bsp
# original:
# BSP_ENV_$1 := BSP=$$(BSP_$1) BSP_BUILD=$$(BSP_BUILD_$1) BSP_ABS=$$(BSP_ABS_$1) BSP_PROJECT=$$(BSP_PROJECT_$1)
# quick fix:
BSP_ENV_$1 := BSP_BUILD=$$(BSP_BUILD_$1) BSP_PROJECT=$$(BSP_PROJECT_$1)
$$(BSP_TARGET_$1): | $$(BSP_BUILD_$1)
$$(BSP_ENV_$1) $$(SCRIPT_DIR)/create_bsp.sh $$(BOARDDIR_$1) $$(TEMPLATE_$1)
Then, in the create_bsp.sh script there looks to be some confusion with the directory paths. In order to get it working, I hardcoded the correct path:
+ #petalinux-config --get-hw-description=$BSP_BUILD/hardware_project --silentconfig
+ petalinux-config --get-hw-description=/home/bluetiger/Dev/Xilinx/Pynq/boards/ZCU104/base/ --silentconfig
Now, the project is building except the last step, the SD card image creation:
cp --sparse=always /home/bluetiger/Dev/Xilinx/Pynq/boards/ZCU104/ /home/bluetiger/Dev/Xilinx/Pynq/sdbuild/output/ZCU104-2.6.0.img
cp: -r not specified; omitting directory '/home/bluetiger/Dev/Xilinx/Pynq/boards/ZCU104/'
make: *** [Makefile:339: /home/bluetiger/Dev/Xilinx/Pynq/sdbuild/output/ZCU104-2.6.0.img] Error 1
From the Makefile, it looks like is trying to copy and mount an SD card image, which is missing. Then, the PetaLinux files built previously, would be copied to this:
$$(IMAGE_$1) : $$(BASE_PATH_$1) $$(STAGE4_DEPENDS_$1) $$(BOOT_FILES_$1) $$(MODULES_$1) $$(KERNEL_RPM_$1) | $$(CCACHEDIR)
cp --sparse=always $$(BASE_PATH_$1) $$(IMAGE_$1)
$$(SCRIPT_DIR)/mount_image.sh $$(IMAGE_$1) $$(STAGING_$1)
$$(PACKAGE_ENV_$1) $$(SCRIPT_DIR)/install_packages.sh $$(STAGING_$1) $$(STAGE4_PACKAGES_$1)
sudo cp $$(BOOT_FILES_$1) $$(STAGING_$1)/boot
mkdir -p $$(BUILD_ROOT_$1)/modules
cd $$(BUILD_ROOT_$1)/modules && tar -xf $$(MODULES_$1)
sudo cp -r --no-preserve=ownership $$(BUILD_ROOT_$1)/modules/* $$(STAGING_$1)
rm -rf $$(BUILD_ROOT_$1)/modules
rpm2cpio $$(KERNEL_RPM_$1) | sudo chroot $$(STAGING_$1) cpio -id
sudo chroot $$(STAGING_$1) depmod -a $$(LINUX_VERSION)
$$(SCRIPT_DIR)/resize_umount.sh $$(IMAGE_$1) $$(STAGING_$1)
Do you have an idea what that initial ZCU104-2.6.0.img should be? Now the from path in the cp is a directory, and I did not found any .img files neither in the project, nor in the build directory.
Thanks,
Attila
