[meta-xilinx] BOOT.BIN creation with hdf files

Tue Aug 4 22:22:09 PDT 2015

If you use u-boot SPL, you'll have to write the SPL part (called boot.bin) 
into the first QSPI sector(s). Write u-boot.img to the next sectors, at 
CONFIG_SYS_SPI_U_BOOT_OFFS

In the default Zynq, this is at 0x100000 (I have no clue as to why, since the 
SPL is usually less than 64k, u-boot.img can be at 0x10000, and the SPL loader 
cannot exceed 192k anyway, so 0x30000 already allows the largest possible SPL 
loader)

Note that the SPL loader should output a bit of data on the serial port. Did 
you see that?

On 04-08-15 18:30, Kumar Nagaraj wrote:
> Nathan,
>
>                  I had successfully booted  from SD card with  boot.bin,
> core-image-minimal-zc702-zynq7-20150604152438.rootfs.cpio.gz.u-boot,
> u-boot-dtb.img, uImage & zc702-zynq7.dtb generating from  Xilinx yocto kernel
> environment on zc702 evaluation board.
>
> As per our architecture design of  7030, SD card cannot be used as boot device
> because it is connected to SD1 interface, only QSPI flash is available as boot
> device.
>
> Today  I have tried copying ps7_init.c & ps7_init.h files contained in the hdf
> file to
> /yocto/ZC702/tmp/work/zc702_zynq7-poky-linux-gnueabi/fsbl-platform-init/2014.4-r0/git/lib/sw_apps/zynq_fsbl/src
> & generated BOOT.BIN.
>
> I copied BOOT.BIN into QSPI flash & then changed the boot mode to QSPI flash.
> After power ON it is unable to boot from QSPI flash. I am thinking the problem
> might  be due to missing u-boot-dtb.img which is generated in yocto but not in
> petalinux or other SDK environments.
>
> Kindly suggest the steps required for booting from QSPI flash for Xilinx yocto
> environment with a given hdf file.
>
> Thanks & Regards,
>
> Kumar
>
> 

Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans at topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

-----Original Message-----
> From: Nathan Rossi [mailto:nathan at nathanrossi.com]
> Sent: Friday, July 10, 2015 2:04 PM
> To: Magnus Olsson
> Cc: Kumar Nagaraj; meta-xilinx at yoctoproject.org
> Subject: Re: [meta-xilinx] BOOT.BIN creation with hdf files
>
> On Fri, Jul 10, 2015 at 4:47 PM, Magnus Olsson <Mago at hms.se
> <mailto:Mago at hms.se>> wrote:
>
>  > I can only speak for meta-xilinx dizzy branch which is what I use, but
> AFAIK the only boot.bin generation it supports is the one provided by u-boot-xlnx.
>
>  >
>
>  >
>
>  > With meta-xilinx, your boot.bin will contain U-boot SPL and nothing else.
> You can then load FPGA images from U-boot (e.g your fpga.bit). U-boot SPL only
> needs ps7_init.c and ps7_init.h to build.
>
> Note: u-boot-spl is able to load the bitstream during boot. This is very very
> similar functionally to FSBL.
>
>  >
>
>  >
>
>  > If you need to load the FPGA earlier than U-boot in your boot sequence, you
> need to package boot.bin using the Xilinx SDK tool "bootgen". It allows
> packaging FSBL, FPGA image and U-boot. AFAIK there is no support for this in
> meta-xilinx, since it brings in a huge dependency on Xilinx SDK which is not
> easy to package (nor possible due to licenses I think).
>
>  >
>
> FSBL requires a newlib baremetal toolchain. So its technically possible to
> build FSBL without the need for XSDK, however there would be a large amount of
> work to get this working. Secondly the bootgen tool is not available outside
> of XSDK so even if FSBL could be built the other problem would be generating a
> BOOT.BIN image which has the FSBL image tables and content. Since there is an
> (in my opinion,
>
> superior) open source solution to this problem (u-boot-spl) there is
> significantly less interest in having this support in meta-xilinx.
>
>  > ________________________________
>
>  > From: meta-xilinx-bounces at yoctoproject.org
> <mailto:meta-xilinx-bounces at yoctoproject.org>
>
>  > <meta-xilinx-bounces at yoctoproject.org
> <mailto:meta-xilinx-bounces at yoctoproject.org>> on behalf of Kumar Nagaraj
>
>  > <kumarn at hcl.com <mailto:kumarn at hcl.com>>
>
>  > Sent: Wednesday, July 8, 2015 16:59
>
>  > To: meta-xilinx at yoctoproject.org <mailto:meta-xilinx at yoctoproject.org>
>
>  > Subject: [meta-xilinx] BOOT.BIN creation with hdf files
>
>  >
>
>  > Hai,
>
>  >                 I need to generate a custom BOOT.BIN for ZC7030 device with
> provided hdf that consists of the following:
>
>  > Ps7_init.c
>
>  > Ps7_init.h
>
>  > Ps7_init.html
>
>  > Ps7_init.tcl
>
>  > Ps7_init_gpl.c
>
>  > Ps7_init_gpl.h
>
>  > Sysdef.xml
>
>  > Fpga.hwh
>
>  > Fpga_bd.tcl
>
>  > Fpga_reg_if.tcl
>
>  > Fpga.bit
>
>  >
>
>  >
>
>  > ·         Kindly provide the steps required for generating BOOT.BIN using
> hdf file.
>
>  >
>
>  > ·         In the current yocto build environment I noticed that fsbl source
> code is present in the path
> /yocto/ZC702/tmp/work/zc702_zynq7-poky-linux-gnueabi/fsbl-platform-init/2014.4-r0/git/lib/sw_apps/zynq_fsbl/src.
>
> For reference the existence of the fsbl codebase which is grabbed as part of
> the fsbl-platform-init recipe is how the ps7_init_gpl.[ch] is grabbed for the
> zc702, zc706, etc. machines. This recipe will likely disappear in the future
> as u-boot upstream now contains a version of these ps7_init_gpl.[ch] files.
>
> e.g.
> http://git.denx.de/?p=u-boot.git;a=tree;f=board/xilinx/zynq/ZC702_hw_platform;h=fde2238e18a5e8bf99d5eea0fbed5fa01399febd;hb=HEAD
>
> Regards,
>
> Nathan
>
>  >
>
>  > Do I have to copy the above files into this path & issue build command. If
> yes then what is the build command?
>
>  >
>
>  >
>
>  >
>
>  > Thanks & Regards,
>
>  > M.N.Kumar
>
>  > Software Technical Lead
>
>  > HCL Technologies
>
>  > Mobile: 91-9884636236
>
>  > E : kumarn at hcl.com<mailto:kumarn at hcl.com
> <mailto:kumarn at hcl.com%3cmailto:kumarn at hcl.com>>
>
>  > No:73-74,AMB5, South Phase Road,
>
>  > Ambattur Industrial Estate,
>
>  > Chennai- 600058,Tamil nadu, India.
>
>  >
>
>  >
>
>  >
>
>  > ::DISCLAIMER::
>
>  > ----------------------------------------------------------------------
>
>  > ----------------------------------------------------------------------
>
>  > -------- The contents of this e-mail and any attachment(s) are
>
>  > confidential and intended for the named recipient(s) only.
>
>  > E-mail transmission is not guaranteed to be secure or error-free as
>
>  > information could be intercepted, corrupted, lost, destroyed, arrive
>
>  > late or incomplete, or may contain viruses in transmission. The e mail and
> its contents (with or without referred errors) shall therefore not attach any
> liability on the originator or HCL or its affiliates.
>
>  > Views or opinions, if any, presented in this email are solely those of
>
>  > the author and may not necessarily reflect the views or opinions of
>
>  > HCL or its affiliates. Any form of reproduction, dissemination,
>
>  > copying, disclosure, modification, distribution and / or publication of
> this message without the prior written consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error please
> delete it and notify the sender immediately.
>
>  > Before opening any email and/or attachments, please check them for viruses
> and other defects.
>
>  > ----------------------------------------------------------------------
>
>  > ----------------------------------------------------------------------
>
>  > --------
>
>  > --
>
>  > _______________________________________________
>
>  > meta-xilinx mailing list
>
>  > meta-xilinx at yoctoproject.org <mailto:meta-xilinx at yoctoproject.org>
>
>  > https://lists.yoctoproject.org/listinfo/meta-xilinx
>
>
>
> ::DISCLAIMER::
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as
> information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or may contain viruses in
> transmission. The e mail and its contents
> (with or without referred errors) shall therefore not attach any liability on
> the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of the
> author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior written
> consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error please
> delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses and
> other defects.
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>
>