[meta-xilinx] cross-compiling

[Edward Wingate]

I cross-compiled an application to run on Linux on the Zynq-7020.
Trying to execute it gives "No such file or directory" error.

# file app_hello.elf
app_hello.elf: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for
GNU/Linux 4.4.0,
BuildID[sha1]=06498863e79d3eabe670610b2cbb0440272f047e, not stripped

I don't have /lib/ld-linux-armhf.so.3, but I do have
/lib/ld-linux.so.3.  I symlinked ld-linux-armhf.so.3 to ld-linux.so.3
and my application runs fine now.

Where did things go wrong?  Is my Yocto build not properly creating
ld-linux-armhf.so.3?  Or is my application cross-compilation using the
wrong ld-linux?  I'm using Xilinx SDK 2016.2 to cross-compile the
Linux application.

Thanks for any help.

Ed
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] FSBL.elf and BOOT.BIN using bitbake and SDCard booting

[Nathan Rossi]

On Tue, Oct 11, 2016 at 1:17 PM, Giordon Stark  wrote:
> On Mon, Oct 10, 2016 at 9:59 PM Nathan Rossi  wrote:
>>
>> On Tue, Oct 11, 2016 at 12:15 PM, Giordon Stark  wrote:
>>
>> > Thanks, some elaboration below!
>>
>> >
>>
>> > On Mon, Oct 10, 2016 at 8:58 PM Nathan Rossi 
>> > wrote:
>>
>> >>
>>
>> >> On Tue, Oct 11, 2016 at 9:49 AM, Giordon Stark 
>> >> wrote:
>>
>> >>
>>
>> >> > Hi,
>>
>> >>
>>
>> >> >
>>
>> >>
>>
>> >> > I am using bitbake to build on top of a custom machine [eg: using my
>>
>> >>
>>
>> >> > devicetree] and then generating the following files which I renamed
>> >> > into
>>
>> >> > a
>>
>> >>
>>
>> >> > format appropriate for meta-xilinx
>>
>> >>
>>
>> >> >
>>
>> >>
>>
>> >> > -rwxr-xr-x 1 kratsg  59K Oct  5 17:31 BOOT.BIN
>>
>> >>
>>
>> >> > -rw-r--r-- 1 kratsg  22K Oct  5 17:30 devicetree.dtb
>>
>> >>
>>
>> >> > -rw-r--r-- 1 kratsg 3.2M Oct  5 17:30 uImage
>>
>> >>
>>
>> >> > -rw-r--r-- 1 kratsg  26M Oct  5 17:15 uramdisk.image.gz
>>
>> >>
>>
>> >> > -rwxr-xr-x 1 kratsg 2.4M Oct  5 17:30 u-boot.elf
>>
>> >>
>>
>> >> >
>>
>> >>
>>
>> >> > The machine is defined here:
>>
>> >>
>>
>> >> >
>>
>> >> >
>> >> > https://github.com/kratsg/meta-l1calo/blob/master/conf/machine/gfex-prototype2.conf
>>
>> >>
>>
>> >> >
>>
>> >>
>>
>> >> > The image I make (bitbake zynq-base) is defined here:
>>
>> >>
>>
>> >> >
>>
>> >> >
>> >> > https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb
>>
>> >>
>>
>> >> >
>>
>> >>
>>
>> >> > So i'm hoping this is relatively straightforward. Now I get a little
>>
>> >>
>>
>> >> > confused about actually booting this on the board using the SD Card.
>>
>> >>
>>
>> >> > According to the docs
>>
>> >>
>>
>> >> > (https://github.com/Xilinx/meta-xilinx/blob/master/docs/BOOT.sdcard)
>> >> > it
>>
>> >>
>>
>> >> > seems that I need to only use four files generated from bitbake:
>>
>> >>
>>
>> >> > devicetree.dtb, uImage, uramdisk.image.gz, and u-boot.elf; and then
>> >> > use
>>
>> >> > the
>>
>> >>
>>
>> >> > Xilinx SDK to create an FSBL.elf, use the u-boot.elf from bitbake,
>> >> > and
>>
>> >>
>>
>> >> > create a boot image (BOOT.BIN). Why isn't this able to be done using
>>
>> >>
>>
>> >> > bitbake? When I try everything without using the Xilinx SDK, I see
>> >> > the
>>
>> >> > error
>>
>> >>
>>
>> >> > message [1].
>>
>> >>
>>
>> >>
>>
>> >>
>>
>> >> Those docs are a bit old, for the last release I re-wrote the
>>
>> >>
>>
>> >> documentation as README.booting.md in the root of meta-xilinx.
>>
>> >>
>>
>> >>
>>
>> >>
>>
>> >>
>>
>> >>
>> >> https://github.com/Xilinx/meta-xilinx/blob/master/README.booting.md#loading-via-sd
>>
>> >>
>>
>> >>
>>
>> >
>>
>> > Awesome, I was not aware that the docs were rewritten. I didn't even
>> > realize
>>
>> > there was a README.booting.md at the top level. Perhaps that can be
>>
>> > clarified somewhere?
>>
>>
>>
>> It is mentioned in the README, maybe removing the old docs will remove
>>
>> any confusion?
>
>
> That might be best! Or perhaps move that new README.booting into the docs
> directory to replace?
>
>>
>>
>>
>>
>> >
>>
>> >>
>>
>> >>
>>
>> >> Also I am not sure about your question regarding boot.bin generation.
>>
>> >>
>>
>> >> But if you machine provides the ps7_init_gpl* files (your machine is
>>
>> >>
>>
>> >> including zc706, so they are available) it is able to build u-boot-spl
>>
>> >>
>>
>> >> (which does the same job as FSBL) and wrap that in the boot.bin format
>>
>> >>
>>
>> >> for use. If you need FSBL specifically then that is a separate issue.
>>
>> >
>>
>> >
>>
>> > For right now, we are using a custom board with a ZC706. We'll move to
>> > the
>>
>> > Zynq+ in the next generation (as well as bump up versions of everything
>> > from
>>
>> > Jethro). So I imagine we will always have these ps7_init_gpl available
>> > (I
>>
>> > imagine you refer to these:
>>
>> >
>> > https://github.com/Xilinx/meta-xilinx/tree/master/recipes-bsp/platform-init/platform-init/picozed-zynq7).
>>
>>
>>
>> So ZynqMP is a bit different, there is U-Boot SPL support. However
>>
>> this is not exposed yet in meta-xilinx, but will be in the future.
>>
>>
>>
>> The directory you linked has the ps7_init_gpl* files which are
>>
>> specific for the picozed board. The platform-init recipe though would
>>
>> be one of the ways you can supply the ps7_init for your machine should
>>
>> you need to. For zc706 the ps7_init_gpl* files are actually in the
>>
>> U-Boot source tree
>>
>>
>> (http://git.denx.de/?p=u-boot.git;a=tree;f=board/xilinx/zynq;h=2fc205e4e97071b73a16c00dec1d6804e418343f;hb=HEAD).
>>
>>
>
> I see. Interesting I didn't realize this was in the U-Boot source tree. A
> bit confusing where some files are located, but ok.
>
>>
>>
>> >
>>
>> > I do not totally understand how/why this can replace the FSBL entirely?
>>
>> >
>> > http://www.wiki.xilinx.com/U-Boot+Secondary+Program+Loader#Task%20Description-Build%20U-Boot%20SPL
>>
>> > seems to indicate it is not fully supported by Xilinx. In fact, I never
>>
>> 

Re: [meta-xilinx] FSBL.elf and BOOT.BIN using bitbake and SDCard booting

[Giordon Stark]

On Mon, Oct 10, 2016 at 9:59 PM Nathan Rossi  wrote:

> On Tue, Oct 11, 2016 at 12:15 PM, Giordon Stark  wrote:
>
> > Thanks, some elaboration below!
>
> >
>
> > On Mon, Oct 10, 2016 at 8:58 PM Nathan Rossi 
> wrote:
>
> >>
>
> >> On Tue, Oct 11, 2016 at 9:49 AM, Giordon Stark 
> wrote:
>
> >>
>
> >> > Hi,
>
> >>
>
> >> >
>
> >>
>
> >> > I am using bitbake to build on top of a custom machine [eg: using my
>
> >>
>
> >> > devicetree] and then generating the following files which I renamed
> into
>
> >> > a
>
> >>
>
> >> > format appropriate for meta-xilinx
>
> >>
>
> >> >
>
> >>
>
> >> > -rwxr-xr-x 1 kratsg  59K Oct  5 17:31 BOOT.BIN
>
> >>
>
> >> > -rw-r--r-- 1 kratsg  22K Oct  5 17:30 devicetree.dtb
>
> >>
>
> >> > -rw-r--r-- 1 kratsg 3.2M Oct  5 17:30 uImage
>
> >>
>
> >> > -rw-r--r-- 1 kratsg  26M Oct  5 17:15 uramdisk.image.gz
>
> >>
>
> >> > -rwxr-xr-x 1 kratsg 2.4M Oct  5 17:30 u-boot.elf
>
> >>
>
> >> >
>
> >>
>
> >> > The machine is defined here:
>
> >>
>
> >> >
>
> >> >
> https://github.com/kratsg/meta-l1calo/blob/master/conf/machine/gfex-prototype2.conf
>
> >>
>
> >> >
>
> >>
>
> >> > The image I make (bitbake zynq-base) is defined here:
>
> >>
>
> >> >
>
> >> >
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb
>
> >>
>
> >> >
>
> >>
>
> >> > So i'm hoping this is relatively straightforward. Now I get a little
>
> >>
>
> >> > confused about actually booting this on the board using the SD Card.
>
> >>
>
> >> > According to the docs
>
> >>
>
> >> > (https://github.com/Xilinx/meta-xilinx/blob/master/docs/BOOT.sdcard)
> it
>
> >>
>
> >> > seems that I need to only use four files generated from bitbake:
>
> >>
>
> >> > devicetree.dtb, uImage, uramdisk.image.gz, and u-boot.elf; and then
> use
>
> >> > the
>
> >>
>
> >> > Xilinx SDK to create an FSBL.elf, use the u-boot.elf from bitbake, and
>
> >>
>
> >> > create a boot image (BOOT.BIN). Why isn't this able to be done using
>
> >>
>
> >> > bitbake? When I try everything without using the Xilinx SDK, I see the
>
> >> > error
>
> >>
>
> >> > message [1].
>
> >>
>
> >>
>
> >>
>
> >> Those docs are a bit old, for the last release I re-wrote the
>
> >>
>
> >> documentation as README.booting.md in the root of meta-xilinx.
>
> >>
>
> >>
>
> >>
>
> >>
>
> >>
> https://github.com/Xilinx/meta-xilinx/blob/master/README.booting.md#loading-via-sd
>
> >>
>
> >>
>
> >
>
> > Awesome, I was not aware that the docs were rewritten. I didn't even
> realize
>
> > there was a README.booting.md at the top level. Perhaps that can be
>
> > clarified somewhere?
>
>
>
> It is mentioned in the README, maybe removing the old docs will remove
>
> any confusion?
>

That might be best! Or perhaps move that new README.booting into the docs
directory to replace?


>
>
>
> >
>
> >>
>
> >>
>
> >> Also I am not sure about your question regarding boot.bin generation.
>
> >>
>
> >> But if you machine provides the ps7_init_gpl* files (your machine is
>
> >>
>
> >> including zc706, so they are available) it is able to build u-boot-spl
>
> >>
>
> >> (which does the same job as FSBL) and wrap that in the boot.bin format
>
> >>
>
> >> for use. If you need FSBL specifically then that is a separate issue.
>
> >
>
> >
>
> > For right now, we are using a custom board with a ZC706. We'll move to
> the
>
> > Zynq+ in the next generation (as well as bump up versions of everything
> from
>
> > Jethro). So I imagine we will always have these ps7_init_gpl available (I
>
> > imagine you refer to these:
>
> >
> https://github.com/Xilinx/meta-xilinx/tree/master/recipes-bsp/platform-init/platform-init/picozed-zynq7
> ).
>
>
>
> So ZynqMP is a bit different, there is U-Boot SPL support. However
>
> this is not exposed yet in meta-xilinx, but will be in the future.
>
>
>
> The directory you linked has the ps7_init_gpl* files which are
>
> specific for the picozed board. The platform-init recipe though would
>
> be one of the ways you can supply the ps7_init for your machine should
>
> you need to. For zc706 the ps7_init_gpl* files are actually in the
>
> U-Boot source tree
>
> (
> http://git.denx.de/?p=u-boot.git;a=tree;f=board/xilinx/zynq;h=2fc205e4e97071b73a16c00dec1d6804e418343f;hb=HEAD
> ).
>
>
>
I see. Interesting I didn't realize this was in the U-Boot source tree. A
bit confusing where some files are located, but ok.


>
> >
>
> > I do not totally understand how/why this can replace the FSBL entirely?
>
> >
> http://www.wiki.xilinx.com/U-Boot+Secondary+Program+Loader#Task%20Description-Build%20U-Boot%20SPL
>
> > seems to indicate it is not fully supported by Xilinx. In fact, I never
>
> > understood how the FSBL normally worked because I understood the process
> as
>
> > ROM Code -> SPL -> U-BOOT -> Kernel.
>
>
>
> That is the boot flow yes. And correct it is not "supported" by
>
> Xilinx, so you cannot expect to contact Xilinx support channels with
>
> regards to SPL. But support for SPL is definitely available in the
>
> community whether it be here on meta-xilinx or 

Re: [meta-xilinx] FSBL.elf and BOOT.BIN using bitbake and SDCard booting

[Nathan Rossi]

On Tue, Oct 11, 2016 at 12:15 PM, Giordon Stark  wrote:
> Thanks, some elaboration below!
>
> On Mon, Oct 10, 2016 at 8:58 PM Nathan Rossi  wrote:
>>
>> On Tue, Oct 11, 2016 at 9:49 AM, Giordon Stark  wrote:
>>
>> > Hi,
>>
>> >
>>
>> > I am using bitbake to build on top of a custom machine [eg: using my
>>
>> > devicetree] and then generating the following files which I renamed into
>> > a
>>
>> > format appropriate for meta-xilinx
>>
>> >
>>
>> > -rwxr-xr-x 1 kratsg  59K Oct  5 17:31 BOOT.BIN
>>
>> > -rw-r--r-- 1 kratsg  22K Oct  5 17:30 devicetree.dtb
>>
>> > -rw-r--r-- 1 kratsg 3.2M Oct  5 17:30 uImage
>>
>> > -rw-r--r-- 1 kratsg  26M Oct  5 17:15 uramdisk.image.gz
>>
>> > -rwxr-xr-x 1 kratsg 2.4M Oct  5 17:30 u-boot.elf
>>
>> >
>>
>> > The machine is defined here:
>>
>> >
>> > https://github.com/kratsg/meta-l1calo/blob/master/conf/machine/gfex-prototype2.conf
>>
>> >
>>
>> > The image I make (bitbake zynq-base) is defined here:
>>
>> >
>> > https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb
>>
>> >
>>
>> > So i'm hoping this is relatively straightforward. Now I get a little
>>
>> > confused about actually booting this on the board using the SD Card.
>>
>> > According to the docs
>>
>> > (https://github.com/Xilinx/meta-xilinx/blob/master/docs/BOOT.sdcard) it
>>
>> > seems that I need to only use four files generated from bitbake:
>>
>> > devicetree.dtb, uImage, uramdisk.image.gz, and u-boot.elf; and then use
>> > the
>>
>> > Xilinx SDK to create an FSBL.elf, use the u-boot.elf from bitbake, and
>>
>> > create a boot image (BOOT.BIN). Why isn't this able to be done using
>>
>> > bitbake? When I try everything without using the Xilinx SDK, I see the
>> > error
>>
>> > message [1].
>>
>>
>>
>> Those docs are a bit old, for the last release I re-wrote the
>>
>> documentation as README.booting.md in the root of meta-xilinx.
>>
>>
>>
>>
>> https://github.com/Xilinx/meta-xilinx/blob/master/README.booting.md#loading-via-sd
>>
>>
>
> Awesome, I was not aware that the docs were rewritten. I didn't even realize
> there was a README.booting.md at the top level. Perhaps that can be
> clarified somewhere?

It is mentioned in the README, maybe removing the old docs will remove
any confusion?

>
>>
>>
>> Also I am not sure about your question regarding boot.bin generation.
>>
>> But if you machine provides the ps7_init_gpl* files (your machine is
>>
>> including zc706, so they are available) it is able to build u-boot-spl
>>
>> (which does the same job as FSBL) and wrap that in the boot.bin format
>>
>> for use. If you need FSBL specifically then that is a separate issue.
>
>
> For right now, we are using a custom board with a ZC706. We'll move to the
> Zynq+ in the next generation (as well as bump up versions of everything from
> Jethro). So I imagine we will always have these ps7_init_gpl available (I
> imagine you refer to these:
> https://github.com/Xilinx/meta-xilinx/tree/master/recipes-bsp/platform-init/platform-init/picozed-zynq7).

So ZynqMP is a bit different, there is U-Boot SPL support. However
this is not exposed yet in meta-xilinx, but will be in the future.

The directory you linked has the ps7_init_gpl* files which are
specific for the picozed board. The platform-init recipe though would
be one of the ways you can supply the ps7_init for your machine should
you need to. For zc706 the ps7_init_gpl* files are actually in the
U-Boot source tree
(http://git.denx.de/?p=u-boot.git;a=tree;f=board/xilinx/zynq;h=2fc205e4e97071b73a16c00dec1d6804e418343f;hb=HEAD).

>
> I do not totally understand how/why this can replace the FSBL entirely?
> http://www.wiki.xilinx.com/U-Boot+Secondary+Program+Loader#Task%20Description-Build%20U-Boot%20SPL
> seems to indicate it is not fully supported by Xilinx. In fact, I never
> understood how the FSBL normally worked because I understood the process as
> ROM Code -> SPL -> U-BOOT -> Kernel.

That is the boot flow yes. And correct it is not "supported" by
Xilinx, so you cannot expect to contact Xilinx support channels with
regards to SPL. But support for SPL is definitely available in the
community whether it be here on meta-xilinx or with U-Boot itself.

FSBL is actually not a very complex program, all of the complex
register initialization done for DDR, PLL, etc setup is actually
contained in the ps7_init_gpl* code files generated by Vivado (in the
HDF).

If you are interested you can actually see the source for FSBL here
https://github.com/Xilinx/embeddedsw/tree/master/lib/sw_apps/zynq_fsbl/src.
However it is important to note that FSBL is licensed under a
restrictive Xilinx only use license.

>
> We do not necessarily require FSBL so this is fine. Looking at the files
> generated (https://gist.github.com/kratsg/ba23d69a84db769cf8183b3dbc37c2f3)
> with my attached local.conf there -- I do not see this. I'm guessing this is
> in a later release of poky. I can certainly update later to move to this
> workflow soon... unless you suggest I do it now 

Re: [meta-xilinx] FSBL.elf and BOOT.BIN using bitbake and SDCard booting

[Giordon Stark]

Thanks, some elaboration below!

On Mon, Oct 10, 2016 at 8:58 PM Nathan Rossi  wrote:

> On Tue, Oct 11, 2016 at 9:49 AM, Giordon Stark  wrote:
>
> > Hi,
>
> >
>
> > I am using bitbake to build on top of a custom machine [eg: using my
>
> > devicetree] and then generating the following files which I renamed into
> a
>
> > format appropriate for meta-xilinx
>
> >
>
> > -rwxr-xr-x 1 kratsg  59K Oct  5 17:31 BOOT.BIN
>
> > -rw-r--r-- 1 kratsg  22K Oct  5 17:30 devicetree.dtb
>
> > -rw-r--r-- 1 kratsg 3.2M Oct  5 17:30 uImage
>
> > -rw-r--r-- 1 kratsg  26M Oct  5 17:15 uramdisk.image.gz
>
> > -rwxr-xr-x 1 kratsg 2.4M Oct  5 17:30 u-boot.elf
>
> >
>
> > The machine is defined here:
>
> >
> https://github.com/kratsg/meta-l1calo/blob/master/conf/machine/gfex-prototype2.conf
>
> >
>
> > The image I make (bitbake zynq-base) is defined here:
>
> >
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb
>
> >
>
> > So i'm hoping this is relatively straightforward. Now I get a little
>
> > confused about actually booting this on the board using the SD Card.
>
> > According to the docs
>
> > (https://github.com/Xilinx/meta-xilinx/blob/master/docs/BOOT.sdcard) it
>
> > seems that I need to only use four files generated from bitbake:
>
> > devicetree.dtb, uImage, uramdisk.image.gz, and u-boot.elf; and then use
> the
>
> > Xilinx SDK to create an FSBL.elf, use the u-boot.elf from bitbake, and
>
> > create a boot image (BOOT.BIN). Why isn't this able to be done using
>
> > bitbake? When I try everything without using the Xilinx SDK, I see the
> error
>
> > message [1].
>
>
>
> Those docs are a bit old, for the last release I re-wrote the
>
> documentation as README.booting.md in the root of meta-xilinx.
>
>
>
>
> https://github.com/Xilinx/meta-xilinx/blob/master/README.booting.md#loading-via-sd
>
>
>
Awesome, I was not aware that the docs were rewritten. I didn't even
realize there was a README.booting.md at the top level. Perhaps that can be
clarified somewhere?


>
> Also I am not sure about your question regarding boot.bin generation.
>
> But if you machine provides the ps7_init_gpl* files (your machine is
>
> including zc706, so they are available) it is able to build u-boot-spl
>
> (which does the same job as FSBL) and wrap that in the boot.bin format
>
> for use. If you need FSBL specifically then that is a separate issue.
>

For right now, we are using a custom board with a ZC706. We'll move to the
Zynq+ in the next generation (as well as bump up versions of everything
from Jethro). So I imagine we will always have these ps7_init_gpl available
(I imagine you refer to these:
https://github.com/Xilinx/meta-xilinx/tree/master/recipes-bsp/platform-init/platform-init/picozed-zynq7
).

I do not totally understand how/why this can replace the FSBL entirely?
http://www.wiki.xilinx.com/U-Boot+Secondary+Program+Loader#Task%20Description-Build%20U-Boot%20SPL
seems
to indicate it is not fully supported by Xilinx. In fact, I never
understood how the FSBL normally worked because I understood the process as
ROM Code -> SPL -> U-BOOT -> Kernel.

We do not necessarily require FSBL so this is fine. Looking at the files
generated (https://gist.github.com/kratsg/ba23d69a84db769cf8183b3dbc37c2f3)
with my attached local.conf there -- I do not see this. I'm guessing this
is in a later release of poky. I can certainly update later to move to this
workflow soon... unless you suggest I do it now over FSBL?


>
>
>
> >
>
> > My second (less important) question is how to get bitbake to generate the
>
> > filesystem in the right format? Right now, I have to run
>
> >
>
> > mkimage -A arm -T ramdisk -C gzip -d
>
> > zynq-base-gfex-prototype2.cpio.gz.u-boot uramdisk.image.gz
>
>
>
> *.cpio.gz.u-boot == uramdisk.image.gz. They are the same format
>
> (except that i think the default Xilinx images are "ext.gz.u-boot"),
>
> so there is no need to double wrap the ramdisk with two u-boot mkimage
>
> headers :).
>

The default appears to be cpio.gz.u-boot. If I didn't wrap it this way, I
could not get the filesystem loaded using that file. It needed the mkimage
command.


>
>
>
> >
>
> > in order to get the correct uramdisk.image.gz . Is there a way to make
>
> > bitbake generate the right image so I don't need to run this command so
> that
>
> > u-boot understands my image when booting?
>
> >
>
> > Giordon
>
> >
>
> > [1]
>
> > U-Boot SPL 2015.04 (Oct 05 2016 - 13:12:31)
>
>
>
> It looks like you are using the jethro version of OE/meta-xilinx? If
>
> so, the new documentation might not exactly match the process (e.g.
>
> "u-boot-dtb.img" instead of "u-boot.img").
>

Noted. I do have u-boot-dtb.img instead of u-boot.img


>
>
>
> > mmc boot
>
> > reading fpga.bin
>
> > spl_load_image_fat: error reading image fpga.bin, err - -1
>
> > spl: error reading image fpga.bin, err - 1
>
> > reading system.dtb
>
> > spl_load_image_fat_os: error reading image system.dtb, err - -1
>
> > reading u-boot-dtb.img
>
> > spl_load_image_fat: e

Re: [meta-xilinx] FSBL.elf and BOOT.BIN using bitbake and SDCard booting

[Nathan Rossi]

On Tue, Oct 11, 2016 at 9:49 AM, Giordon Stark  wrote:
> Hi,
>
> I am using bitbake to build on top of a custom machine [eg: using my
> devicetree] and then generating the following files which I renamed into a
> format appropriate for meta-xilinx
>
> -rwxr-xr-x 1 kratsg  59K Oct  5 17:31 BOOT.BIN
> -rw-r--r-- 1 kratsg  22K Oct  5 17:30 devicetree.dtb
> -rw-r--r-- 1 kratsg 3.2M Oct  5 17:30 uImage
> -rw-r--r-- 1 kratsg  26M Oct  5 17:15 uramdisk.image.gz
> -rwxr-xr-x 1 kratsg 2.4M Oct  5 17:30 u-boot.elf
>
> The machine is defined here:
> https://github.com/kratsg/meta-l1calo/blob/master/conf/machine/gfex-prototype2.conf
>
> The image I make (bitbake zynq-base) is defined here:
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb
>
> So i'm hoping this is relatively straightforward. Now I get a little
> confused about actually booting this on the board using the SD Card.
> According to the docs
> (https://github.com/Xilinx/meta-xilinx/blob/master/docs/BOOT.sdcard) it
> seems that I need to only use four files generated from bitbake:
> devicetree.dtb, uImage, uramdisk.image.gz, and u-boot.elf; and then use the
> Xilinx SDK to create an FSBL.elf, use the u-boot.elf from bitbake, and
> create a boot image (BOOT.BIN). Why isn't this able to be done using
> bitbake? When I try everything without using the Xilinx SDK, I see the error
> message [1].

Those docs are a bit old, for the last release I re-wrote the
documentation as README.booting.md in the root of meta-xilinx.

https://github.com/Xilinx/meta-xilinx/blob/master/README.booting.md#loading-via-sd

Also I am not sure about your question regarding boot.bin generation.
But if you machine provides the ps7_init_gpl* files (your machine is
including zc706, so they are available) it is able to build u-boot-spl
(which does the same job as FSBL) and wrap that in the boot.bin format
for use. If you need FSBL specifically then that is a separate issue.

>
> My second (less important) question is how to get bitbake to generate the
> filesystem in the right format? Right now, I have to run
>
> mkimage -A arm -T ramdisk -C gzip -d
> zynq-base-gfex-prototype2.cpio.gz.u-boot uramdisk.image.gz

*.cpio.gz.u-boot == uramdisk.image.gz. They are the same format
(except that i think the default Xilinx images are "ext.gz.u-boot"),
so there is no need to double wrap the ramdisk with two u-boot mkimage
headers :).

>
> in order to get the correct uramdisk.image.gz . Is there a way to make
> bitbake generate the right image so I don't need to run this command so that
> u-boot understands my image when booting?
>
> Giordon
>
> [1]
> U-Boot SPL 2015.04 (Oct 05 2016 - 13:12:31)

It looks like you are using the jethro version of OE/meta-xilinx? If
so, the new documentation might not exactly match the process (e.g.
"u-boot-dtb.img" instead of "u-boot.img").

> mmc boot
> reading fpga.bin
> spl_load_image_fat: error reading image fpga.bin, err - -1
> spl: error reading image fpga.bin, err - 1
> reading system.dtb
> spl_load_image_fat_os: error reading image system.dtb, err - -1
> reading u-boot-dtb.img
> spl_load_image_fat: error reading image u-boot-dtb.img, err - -1
> ### ERROR ### Please RESET the board ###

If you follow the documentation I linked above it will mentioned
adding the "u-boot-dtb.img" file to your SD card. This is what you are
missing here, which is why you get the error.

Regards,
Nathan

>
>
> --
> ___
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
>
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] FSBL.elf and BOOT.BIN using bitbake and SDCard booting

[Giordon Stark]

Hi,

I am using bitbake to build on top of a custom machine [eg: using my
devicetree] and then generating the following files which I renamed into a
format appropriate for meta-xilinx

-rwxr-xr-x 1 kratsg  59K Oct  5 17:31 BOOT.BIN
-rw-r--r-- 1 kratsg  22K Oct  5 17:30 devicetree.dtb
-rw-r--r-- 1 kratsg 3.2M Oct  5 17:30 uImage
-rw-r--r-- 1 kratsg  26M Oct  5 17:15 uramdisk.image.gz
-rwxr-xr-x 1 kratsg 2.4M Oct  5 17:30 u-boot.elf

The machine is defined here:
https://github.com/kratsg/meta-l1calo/blob/master/conf/machine/gfex-prototype2.conf

The image I make (bitbake zynq-base) is defined here:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/images/zynq-base.bb


So i'm hoping this is relatively straightforward. *Now I get a little
confused about actually booting this on the board using the SD Card.* According
to the docs (
https://github.com/Xilinx/meta-xilinx/blob/master/docs/BOOT.sdcard) it
seems that I need to only use four files generated from bitbake:
devicetree.dtb, uImage, uramdisk.image.gz, and u-boot.elf; and then use the
Xilinx SDK to create an FSBL.elf, use the u-boot.elf from bitbake, and
create a boot image (BOOT.BIN). Why isn't this able to be done using
bitbake? When I try everything without using the Xilinx SDK, I see the
error message [1].

My second (*less important*) question is how to get bitbake to generate the
filesystem in the right format? Right now, I have to run

mkimage -A arm -T ramdisk -C gzip -d
zynq-base-gfex-prototype2.cpio.gz.u-boot uramdisk.image.gz

in order to get the correct uramdisk.image.gz . Is there a way to make
bitbake generate the right image so I don't need to run this command so
that u-boot understands my image when booting?

Giordon

[1]
U-Boot SPL 2015.04 (Oct 05 2016 - 13:12:31)
mmc boot
reading fpga.bin
spl_load_image_fat: error reading image fpga.bin, err - -1
spl: error reading image fpga.bin, err - 1
reading system.dtb
spl_load_image_fat_os: error reading image system.dtb, err - -1
reading u-boot-dtb.img
spl_load_image_fat: error reading image u-boot-dtb.img, err - -1
### ERROR ### Please RESET the board ###
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] How to make uImage for zynqmp

[Nathan Rossi]

On Mon, Oct 10, 2016 at 8:00 PM, Mike Looijmans  wrote:
> On 10-10-16 11:44, Cai, Chuntian (GE Transportation) wrote:
>>
>> Hi Nathan
>>
>> I am not aware of that uImage is obsoleted for arm64, could you tell me
>> how to use booti command to boot linux?
>>
>> What address and how to set dtb and rootfs?
>
>
> Ah, now we're getting to the real question.
>
> Just looking at the u-boot source code reveils how it's done:
>
> https://github.com/Xilinx/u-boot-xlnx/blob/master/include/configs/xilinx_zynqmp.h#L189
>
> booti $kernel_addr - $fdt_addr
>

Yep, works the same as the other boot* style commands. The following
addresses should work for zynqmp:

tftpboot 0x8 Image
tftpboot 0x600 core-image-minimal-ep108-zynqmp.cpio.gz.u-boot
tftpboot 0x700 Image-zynqmp-ep108.dtb
booti 0x8 0x600 0x700

Regards,
Nathan

>
>
>>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Products
> Materiaalweg 4, NL-5681 RJ Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> E-mail: mike.looijm...@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
>
>
> -Original Message-
>>
>> From: Nathan Rossi [mailto:nat...@nathanrossi.com]
>> Sent: Monday, October 10, 2016 5:31 PM
>> To: Cai, Chuntian (GE Transportation)
>> Cc: meta-xilinx@yoctoproject.org; Mike Looijmans
>> Subject: EXT: Re: [meta-xilinx] How to make uImage for zynqmp
>>
>> On Mon, Oct 10, 2016 at 3:46 PM, Mike Looijmans 
>> wrote:
>>>
>>> On 09-10-16 03:20, Cai, Chuntian (GE Transportation) wrote:
>>>
 I using bitbake build Linux system for zcu102 board.

 I issue bitbake core-image-x11 , then I can found Image file in the
 deploy folder, But I could not find uImage, and I want use uImage
>>
>>
>> uImage is not a valid target for aarch64/arm64 in the kernel (like it is
>> for arm). This is because "uImage" is actually shorthand for u-boot wrapped
>> zImage. And arm64 does not have support for zImage, thus also does not have
>> a uImage target.
>>
>> (arm targets)
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/Makefile?id=refs/tags/v4.8#n365
>> (arm64 targets)
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/Makefile?id=refs/tags/v4.8#n135
>>
>> ---
>>
>> A good question is why do you want to use uImage? If you are not aware it
>> is possible to boot a linux "Image" with the U-Boot "booti"
>> command.
>>
>> However it is possible to wrap the kernel image with mkimage (or a FIT
>> blob if you are prepared to configure the image tree). For wrapping with
>> mkimage the command you will need is similar to:
>>
>> mkimage -A arm64 -O linux -T kernel -C none -a 0x8 -e 0x8 -d Image
>> Image.ub
>>
>> Also if you need mkimage, run the command using the mkimage built by OE
>> from the sysroot relative to the tmp/deploy/images// directory of
>> your build (assuming you are on a x86_64 host):
>>
>> ../../../sysroots/x86_64-linux/usr/bin/mkimage ...
>>


 Could you tell me how to build uImage rather than Image
>>>
>>>
>>>
>>> Just setting KERNEL_IMAGETYPE="uImage" in the kernel recipe or machine
>>> config would do that.
>>>
>>> I think you can even specify multiple types in there.
>>
>>
>> You can, KERNEL_IMAGETYPES += ""
>>
>> Regards,
>> Nathan
>>
>>>
>>>
>>>
>>> Kind regards,
>>>
>>> Mike Looijmans
>>> System Expert
>>>
>>> TOPIC Products
>>> Materiaalweg 4, NL-5681 RJ Best
>>> Postbus 440, NL-5680 AK Best
>>> Telefoon: +31 (0) 499 33 69 79
>>> E-mail: mike.looijm...@topicproducts.com
>>> Website: www.topicproducts.com
>>>
>>> Please consider the environment before printing this e-mail
>>>
>>>
>>>
>>>
>>>
>>> --
>>> ___
>>> meta-xilinx mailing list
>>> meta-xilinx@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-xilinx
>
>
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] How to make uImage for zynqmp

[Cai, Chuntian (GE Transportation)]

Hi Nathan

I am not aware of that uImage is obsoleted for arm64, could you tell me how to 
use booti command to boot linux?

What address and how to set dtb and rootfs?

Thanks.



-Original Message-
From: Nathan Rossi [mailto:nat...@nathanrossi.com] 
Sent: Monday, October 10, 2016 5:31 PM
To: Cai, Chuntian (GE Transportation)
Cc: meta-xilinx@yoctoproject.org; Mike Looijmans
Subject: EXT: Re: [meta-xilinx] How to make uImage for zynqmp

On Mon, Oct 10, 2016 at 3:46 PM, Mike Looijmans  wrote:
> On 09-10-16 03:20, Cai, Chuntian (GE Transportation) wrote:
>
>> I using bitbake build Linux system for zcu102 board.
>>
>> I issue bitbake core-image-x11 , then I can found Image file in the 
>> deploy folder, But I could not find uImage, and I want use uImage

uImage is not a valid target for aarch64/arm64 in the kernel (like it is for 
arm). This is because "uImage" is actually shorthand for u-boot wrapped zImage. 
And arm64 does not have support for zImage, thus also does not have a uImage 
target.

(arm targets) 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/Makefile?id=refs/tags/v4.8#n365
(arm64 targets)
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/Makefile?id=refs/tags/v4.8#n135

---

A good question is why do you want to use uImage? If you are not aware it is 
possible to boot a linux "Image" with the U-Boot "booti"
command.

However it is possible to wrap the kernel image with mkimage (or a FIT blob if 
you are prepared to configure the image tree). For wrapping with mkimage the 
command you will need is similar to:

mkimage -A arm64 -O linux -T kernel -C none -a 0x8 -e 0x8 -d Image 
Image.ub

Also if you need mkimage, run the command using the mkimage built by OE from 
the sysroot relative to the tmp/deploy/images// directory of your 
build (assuming you are on a x86_64 host):

../../../sysroots/x86_64-linux/usr/bin/mkimage ...

>>
>>
>> Could you tell me how to build uImage rather than Image
>
>
> Just setting KERNEL_IMAGETYPE="uImage" in the kernel recipe or machine 
> config would do that.
>
> I think you can even specify multiple types in there.

You can, KERNEL_IMAGETYPES += ""

Regards,
Nathan

>
>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Products
> Materiaalweg 4, NL-5681 RJ Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> E-mail: mike.looijm...@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
>
>
> --
> ___
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] How to make uImage for zynqmp

[Mike Looijmans]

On 10-10-16 11:44, Cai, Chuntian (GE Transportation) wrote:

Hi Nathan

I am not aware of that uImage is obsoleted for arm64, could you tell me how to 
use booti command to boot linux?

What address and how to set dtb and rootfs?


Ah, now we're getting to the real question.

Just looking at the u-boot source code reveils how it's done:

https://github.com/Xilinx/u-boot-xlnx/blob/master/include/configs/xilinx_zynqmp.h#L189

booti $kernel_addr - $fdt_addr






Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail





-Original Message-

From: Nathan Rossi [mailto:nat...@nathanrossi.com]
Sent: Monday, October 10, 2016 5:31 PM
To: Cai, Chuntian (GE Transportation)
Cc: meta-xilinx@yoctoproject.org; Mike Looijmans
Subject: EXT: Re: [meta-xilinx] How to make uImage for zynqmp

On Mon, Oct 10, 2016 at 3:46 PM, Mike Looijmans  wrote:

On 09-10-16 03:20, Cai, Chuntian (GE Transportation) wrote:


I using bitbake build Linux system for zcu102 board.

I issue bitbake core-image-x11 , then I can found Image file in the
deploy folder, But I could not find uImage, and I want use uImage


uImage is not a valid target for aarch64/arm64 in the kernel (like it is for arm). This 
is because "uImage" is actually shorthand for u-boot wrapped zImage. And arm64 
does not have support for zImage, thus also does not have a uImage target.

(arm targets) 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/Makefile?id=refs/tags/v4.8#n365
(arm64 targets)
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/Makefile?id=refs/tags/v4.8#n135

---

A good question is why do you want to use uImage? If you are not aware it is possible to boot a 
linux "Image" with the U-Boot "booti"
command.

However it is possible to wrap the kernel image with mkimage (or a FIT blob if 
you are prepared to configure the image tree). For wrapping with mkimage the 
command you will need is similar to:

mkimage -A arm64 -O linux -T kernel -C none -a 0x8 -e 0x8 -d Image 
Image.ub

Also if you need mkimage, run the command using the mkimage built by OE from the 
sysroot relative to the tmp/deploy/images// directory of your build 
(assuming you are on a x86_64 host):

../../../sysroots/x86_64-linux/usr/bin/mkimage ...




Could you tell me how to build uImage rather than Image



Just setting KERNEL_IMAGETYPE="uImage" in the kernel recipe or machine
config would do that.

I think you can even specify multiple types in there.


You can, KERNEL_IMAGETYPES += ""

Regards,
Nathan





Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail





--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] How to make uImage for zynqmp

[Nathan Rossi]

On Mon, Oct 10, 2016 at 3:46 PM, Mike Looijmans  wrote:
> On 09-10-16 03:20, Cai, Chuntian (GE Transportation) wrote:
>
>> I using bitbake build Linux system for zcu102 board.
>>
>> I issue bitbake core-image-x11 , then I can found Image file in the deploy
>> folder, But I could not find uImage, and I want use uImage

uImage is not a valid target for aarch64/arm64 in the kernel (like it
is for arm). This is because "uImage" is actually shorthand for u-boot
wrapped zImage. And arm64 does not have support for zImage, thus also
does not have a uImage target.

(arm targets) 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/Makefile?id=refs/tags/v4.8#n365
(arm64 targets)
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/Makefile?id=refs/tags/v4.8#n135

---

A good question is why do you want to use uImage? If you are not aware
it is possible to boot a linux "Image" with the U-Boot "booti"
command.

However it is possible to wrap the kernel image with mkimage (or a FIT
blob if you are prepared to configure the image tree). For wrapping
with mkimage the command you will need is similar to:

mkimage -A arm64 -O linux -T kernel -C none -a 0x8 -e 0x8 -d
Image Image.ub

Also if you need mkimage, run the command using the mkimage built by
OE from the sysroot relative to the tmp/deploy/images//
directory of your build (assuming you are on a x86_64 host):

../../../sysroots/x86_64-linux/usr/bin/mkimage ...

>>
>>
>> Could you tell me how to build uImage rather than Image
>
>
> Just setting KERNEL_IMAGETYPE="uImage" in the kernel recipe or machine
> config would do that.
>
> I think you can even specify multiple types in there.

You can, KERNEL_IMAGETYPES += ""

Regards,
Nathan

>
>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Products
> Materiaalweg 4, NL-5681 RJ Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> E-mail: mike.looijm...@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
>
>
> --
> ___
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] How to make uImage for zynqmp

[Cai, Chuntian (GE Transportation)]

Why I cannot set Modify KERNEL_IMAGETYPE to uImage?


From: Thomas Horton, HCL America [mailto:tom.hor...@hcl.com]
Sent: Monday, October 10, 2016 1:27 PM
To: meta-xilinx@yoctoproject.org
Subject: EXT: Re: [meta-xilinx] How to make uImage for zynqmp

New contributor, so hopefully this makes it correctly to the thread.

The way I do it:


1)  Modify KERNEL_IMAGETYPE to "vmlinux" in tune-zynqmp.inc

2)  Execute bitbake.

3)  Source /settings.sh

4)  Export several variables with separate export statements: 
LD_LIBRARY_PATH=/tools/lib, 
LM_LICENSE_FILE=/etc/license/petalinux.lic, 
PETALINUX_ARCH_AARCH64=y, and USERNAME=root

5)  Execute: petalinux-gen-fitimage --kernel vmlinux --dtb system.dtb 
--output image.ub --kernel_compression gzip --kernel_hash crc32 --kernelconfig 
uImage.config

Note: vmlinux is built in #2, system.dtb is built in #2 as something.dtb, both 
from the bitbake command, uImage.config (my name) can pulled from #2 as well.  
Issue a find command at the build directory "find . -name .config" (if 
multiple, pick the one from the kernel-build-artifacts location).




::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@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] How to make uImage for zynqmp

[Cai, Chuntian (GE Transportation)]

I installed the petaLinux in path /opt/pkg,

Then I run source command to set petaLinux variavle and path

But I could not find petalinx-gen-fitimage ?

[cid:image001.png@01D222FF.6E3F4210]

From: Thomas Horton, HCL America [mailto:tom.hor...@hcl.com]
Sent: Monday, October 10, 2016 1:27 PM
To: meta-xilinx@yoctoproject.org
Subject: EXT: Re: [meta-xilinx] How to make uImage for zynqmp

New contributor, so hopefully this makes it correctly to the thread.

The way I do it:


1)  Modify KERNEL_IMAGETYPE to "vmlinux" in tune-zynqmp.inc

2)  Execute bitbake.

3)  Source /settings.sh

4)  Export several variables with separate export statements: 
LD_LIBRARY_PATH=/tools/lib, 
LM_LICENSE_FILE=/etc/license/petalinux.lic, 
PETALINUX_ARCH_AARCH64=y, and USERNAME=root

5)  Execute: petalinux-gen-fitimage --kernel vmlinux --dtb system.dtb 
--output image.ub --kernel_compression gzip --kernel_hash crc32 --kernelconfig 
uImage.config

Note: vmlinux is built in #2, system.dtb is built in #2 as something.dtb, both 
from the bitbake command, uImage.config (my name) can pulled from #2 as well.  
Issue a find command at the build directory "find . -name .config" (if 
multiple, pick the one from the kernel-build-artifacts location).




::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@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] How to make uImage for zynqmp

[Cai, Chuntian (GE Transportation)]

I got it. But the vmlinux size about 3.8Mb ,so small ,it is right?


From: Thomas Horton, HCL America [mailto:tom.hor...@hcl.com]
Sent: Monday, October 10, 2016 2:12 PM
To: Cai, Chuntian (GE Transportation); meta-xilinx@yoctoproject.org
Subject: EXT: RE: [meta-xilinx] How to make uImage for zynqmp

You will have to call it out from the path (based on your install): 
/opt/pkg/petalinux-v2016.1-final/tools/common/petalinux/utils/petalinux-gen-fitimage

From: Cai, Chuntian (GE Transportation) [mailto:chuntian@ge.com]
Sent: Sunday, October 09, 2016 11:06 PM
To: Thomas Horton, HCL America; 
meta-xilinx@yoctoproject.org
Subject: [meta-xilinx] How to make uImage for zynqmp

I installed the petaLinux in path /opt/pkg,

Then I run source command to set petaLinux variavle and path

But I could not find petalinx-gen-fitimage ?

[cid:image001.png@01D22302.6B3507F0]

From: Thomas Horton, HCL America [mailto:tom.hor...@hcl.com]
Sent: Monday, October 10, 2016 1:27 PM
To: meta-xilinx@yoctoproject.org
Subject: EXT: Re: [meta-xilinx] How to make uImage for zynqmp

New contributor, so hopefully this makes it correctly to the thread.

The way I do it:


1)  Modify KERNEL_IMAGETYPE to "vmlinux" in tune-zynqmp.inc

2)  Execute bitbake.

3)  Source /settings.sh

4)  Export several variables with separate export statements: 
LD_LIBRARY_PATH=/tools/lib, 
LM_LICENSE_FILE=/etc/license/petalinux.lic, 
PETALINUX_ARCH_AARCH64=y, and USERNAME=root

5)  Execute: petalinux-gen-fitimage --kernel vmlinux --dtb system.dtb 
--output image.ub --kernel_compression gzip --kernel_hash crc32 --kernelconfig 
uImage.config

Note: vmlinux is built in #2, system.dtb is built in #2 as something.dtb, both 
from the bitbake command, uImage.config (my name) can pulled from #2 as well.  
Issue a find command at the build directory "find . -name .config" (if 
multiple, pick the one from the kernel-build-artifacts location).




::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@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] How to make uImage for zynqmp

[gmane]

Hi,

On 2016-10-10 01:14, Thomas Horton,  HCL America wrote:

Also suggest you change your link in /bin

Likely set at:  sh -> dash

Modify to: sh -> bash

This will save you a ton of headaches.



With OE/Yocto this used to be the case a long time ago. Nowadays dash 
should work, or in other words bitbake recipes should not rely on 
"bashisms". OE-core even checked against bashism nowadays.[1]


Having said that, if you really really want to change from dash to bash 
on Ubuntu it's better done like this:


sudo dpkg-reconfigure dash
ls -la /bin/sh

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8851

Regards,

Robert
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx