From: Sébastien bouché [mailto:[email protected]]
Sent: Thursday, April 20, 2017 2:03 PM
To: Manjukumar Harthikote Matha
Cc: [email protected]
Subject: Re: [meta-xilinx] FSBL & BOOT.bin

Sorry Manju but I'm confused.
I know that link, I used it to configure my local.conf.
Here is my config:
#################
# Xilinx specific
#################

XILINX_SDK_TOOLCHAIN = "/opt/Xilinx/SDK/2016.4"
XILINX_VER_MAIN = "2016.4"

#Path to hdf file: ex: HDF_PATH = "/home/user/system.hdf"
HDF_BASE = "file://"
HDF_PATH = "/home/sebo/system.hdf"

#add Boot.bin dependency
IMAGE_CLASSES += " xilinx-bootbin"
#specify BIF partition attributes required for BOOT.bin
BIF_PARTITION_ATTR= "fsbl u-boot"


Hi,



To add bitstream, you need to add the following



BIF_PARTITION_ATTR = "fsbl bitstream u-boot"



# enable bitstream-Note this is not enabled by default (missing in 
BIF_PARTITION_ATTR)

BIF_PARTITION_IMAGE[bitstream] ?= "${DEPLOY_DIR_IMAGE}/download-${MACHINE}.bit"

BIF_PARTITION_DEPENDS[bitstream] ?= "virtual/bitstream"

Thanks
Manju

#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 u-boot
#Location where u-boot binary is present
BIF_PARTITION_IMAGE[u-boot]="${DEPLOY_DIR_IMAGE}/u-boot-${MACHINE}.elf"

Now, I don't understand what's wrong with my command. Prior to run this 
command, the boot.bin was not produced.
Thanks.
/S

-- Sébastien

On Thu, Apr 20, 2017 at 10:50 PM, Manjukumar Harthikote Matha 
<[email protected]<mailto:[email protected]>>
 wrote:


From: Sébastien bouché 
[mailto:[email protected]<mailto:[email protected]>]
Sent: Thursday, April 20, 2017 1:44 PM
To: Manjukumar Harthikote Matha
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [meta-xilinx] FSBL & BOOT.bin

Hi Manju,
Here is the command line I've used:
bitbake linux-xlnx u-boot-xlnx

Hi,

I think you are mixing between u-boot-spl and meta-xilinx-tools fsbl.
u-boot-spl is alternate to fsbl.

Using meta-xilinx-tools to generate boot.bin is documented here
http://www.wiki.xilinx.com/Using+meta-xilinx-tools+layer


Thanks
Manju


Thanks for your help,
S/


-- Sébastien

On Thu, Apr 20, 2017 at 10:35 PM, Manjukumar Harthikote Matha 
<[email protected]<mailto:[email protected]>>
 wrote:


From: 
[email protected]<mailto:[email protected]>
 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of Sébastien bouché
Sent: Thursday, April 20, 2017 12:17 PM
To: [email protected]<mailto:[email protected]>
Subject: [meta-xilinx] FSBL & BOOT.bin

Hello,
I'm currently working on a Yocto project (krogoth) using the meta-xilinx and 
meta-xilnx-tools.
I've successfully built an image and flashed my board (zynqberry from Trenz).
However, the fsbl-zynqberry.elf and the resulting boot.bin are wrong.

Hi,

Can you share details on how you generated the boot.bin? was it using 
meta-xilinx-tools or other methodlogy

Thanks
Manju


Although, I do provide the hdf file to layer.conf
and these settings:

#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"
I do use an extra layer found on github to support the zynberry.

I had to use this procedure on the Xilinx Wiki to solve the issue.

Moreover, how to include the bitfile at this stage?

Thanks for any help here.

-- Sébastien


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.



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.



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.

-- 
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx

Reply via email to