[meta-xilinx] ['meta-xilinx-tools'] Issues with HDF output file generation: BOOT.bin and DTB not working as expected

[Manjukumar Harthikote Matha]

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Brett R. Nicholas
> Sent: Saturday, May 06, 2017 3:37 PM
> To: meta-xilinx at lists.yoctoproject.org
> Subject: [meta-xilinx] ['meta-xilinx-tools'] Issues with HDF output file generation:
> BOOT.bin and DTB not working as expected
>
> Hi there,
>
> I have two questions about the meta-xilinx-tools ability to generate output files
> based on an HDF file:
>
>
> 1.    I am able to successfully build BOOT.bin from my HDF file, however it does
> not automatically load the bitstream when I boot the device. Is there something else
> that I need to do in order to get BOOT.bin to configure the PL before launching u-
> boot?
FSBL should load the bitstream, please check or provide the intermeditate .bif file generated.

> 2.    I have been struggling to get the meta-xilinx-tools to generate a DTB from
> my HDF file. I am successfully able to build BOOT.bin, however the device tree blob
> that is generated in tmp/deploy/images/zedboard-zynq7 does not contain my PL
> peripheral (it is just the default DTB). I have already verified that the HDF file is
> correct. Is there something else I need to do in order to have meta-xilinx-tools
> create the DTB for my design based on the HDF?
>
By default we put out only in-kernel dtb, to use DTG you have to include device-tree-generation recipe.
You should see the DTS fragments as well in the work area
https://github.com/Xilinx/meta-xilinx-tools/blob/master/recipes-dt/device-tree/device-tree-generation_git.bb#L27-L28

Thanks
Manju

>
> For reference, you can find the relevant sections of my local.conf below. Thanks!
>
> ###########################
> # meta-xilinx-tools configurations
> ###########################
> # Define path to xsct tools (needed for bitfile generation) XILINX_VER_MAIN =
> "2016.4"
> XILINX_SDK_TOOLCHAIN = "/opt/Xilinx/SDK/${XILINX_VER_MAIN}"
>
> # Define path to HDF (TODO: we should be using our project hosted on GIT)
> HDF_BASE = "file://"
> HDF_PATH =
> "/home/brett/Vivado_WS/sha256test/sha256test.sdk/design_1_wrapper.hdf"
>
> #add Boot.bin dependency
> IMAGE_CLASSES += " xilinx-bootbin"
>
> #specify BIF partition attributes required for BOOT.bin BIF_PARTITION_ATTR= "fsbl
> bitstream u-boot"
>
> # specify BIF partition attributes for FSBL # bootloader is FSBL. Location where FSBL
> binary is present and dependency to build FSBL
> BIF_PARTITION_IMAGE[fsbl]="${DEPLOY_DIR_IMAGE}/fsbl-${MACHINE}.elf"
> BIF_PARTITION_DEPENDS[fsbl]="virtual/fsbl"
>
> # specify BIF partition attributes for bitstream # enable bitstream-Note this is not
> enabled by default (missing in BIF_PARTITION_ATTR) # TODO: do we need to get rid
> of download preface?
> BIF_PARTITION_IMAGE[bitstream] ?= "${DEPLOY_DIR_IMAGE}/download-
> ${MACHINE}.bit"
> BIF_PARTITION_DEPENDS[bitstream] ?= "virtual/bitstream"
>
> # specify BIF partition attributes for u-boot # Location where u-boot binary is
> present BIF_PARTITION_IMAGE[u-boot]="${DEPLOY_DIR_IMAGE}/u-boot-
> ${MACHINE}.elf"
>
>
>
> Best,
>
> Brett Nicholas
> Brett.R.Nicholas.TH at dartmouth.edu <mailto:Brett.R.Nicholas.TH at dartmouth.edu>
>
>
>



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.