Skip to contentSkip to conversation

mail list for Xilinx Zynq platform?

DISCUSSION Andreas Schweigstill 4 participants 12 messages Dec 5, 2012 – Dec 6, 2012

lore
Share & tools
lore
#0 lore raw

Hello!

Quoted 2 lines

I personally have used Philip's meta-zynq layer to build a working u-boot and linux kernel image using Yocto. It works really well.

I have also tried to build a kernel and root filesystem for Zynq but the kernel gets stuck when booting, regardless if on the ZC702 board or on Qemu. I tried Poky denzil and Poky danny.

Also the alternate meta-zynq layer from git.yoctoproject.org shows the same behaviour.

These are the last console messages which I get:
## Booting kernel from Legacy Image at 01000000 ...

   Image Name:   Linux-3.2.11-yocto-standard
   Created:      2012-12-04  20:07:37 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2997472 Bytes = 2.9 MiB

Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01a80000
Booting using the fdt blob at 0x1a80000 Loading Device Tree to 0eff8000, end 0efff185 ... OK Loading Kernel Image ... OK
OK
Loading Device Tree to 0efed000, end 0eff7185 ... OK

Starting kernel ...

Instead of using Linux kernel version 3.5-xilinx I always get Linux-3.2.11-yocto-standard which is obviously missing the Zynq patches.

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

With best regards,
Andreas Schweigstill

​--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/

#1 lore raw

Hi,

Quoted 30 lines · Andreas Schweigstill

I have also tried to build a kernel and root filesystem for Zynq but the kernel gets stuck when booting, regardless if on the ZC702 board or on Qemu. I tried Poky denzil and Poky danny.

Also the alternate meta-zynq layer from git.yoctoproject.org shows the same behaviour.

These are the last console messages which I get:
## Booting kernel from Legacy Image at 01000000 ...

  Image Name:   Linux-3.2.11-yocto-standard
  Created:      2012-12-04  20:07:37 UTC
  Image Type:   ARM Linux Kernel Image (uncompressed)
  Data Size:    2997472 Bytes = 2.9 MiB

Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01a80000
Booting using the fdt blob at 0x1a80000 Loading Device Tree to 0eff8000, end 0efff185 ... OK Loading Kernel Image ... OK
OK
Loading Device Tree to 0efed000, end 0eff7185 ... OK

Starting kernel ...

Instead of using Linux kernel version 3.5-xilinx I always get Linux-3.2.11-yocto-standard which is obviously missing the Zynq patches.

Quoted 6 lines

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

From you messages, I infer that you are using the meta-zynq layer located here:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-zynq/

For my builds, I used Philip Ballister's meta-zynq layer located here for the simple reason that it uses xilinx git repository:

https://github.com/balister/meta-zynq

Also, try to ensure that you don't put both the meta-layers in your bblayers.conf file while building, and ensure that you set machine as follows in your local.conf file

MACHINE ?= "zynq-zc702"

Do let me know how it goes!

Best regards,

Elvis Dowson

#2 lore raw
Quoted 44 lines · Elvis Dowson

Hi,

Quoted 30 lines · Andreas Schweigstill

I have also tried to build a kernel and root filesystem for Zynq but the kernel gets stuck when booting, regardless if on the ZC702 board or on Qemu. I tried Poky denzil and Poky danny.

Also the alternate meta-zynq layer from git.yoctoproject.org shows the same behaviour.

These are the last console messages which I get:
## Booting kernel from Legacy Image at 01000000 ...

   Image Name:   Linux-3.2.11-yocto-standard
   Created:      2012-12-04  20:07:37 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2997472 Bytes = 2.9 MiB

Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01a80000
Booting using the fdt blob at 0x1a80000 Loading Device Tree to 0eff8000, end 0efff185 ... OK Loading Kernel Image ... OK
OK
Loading Device Tree to 0efed000, end 0eff7185 ... OK

Starting kernel ...

Instead of using Linux kernel version 3.5-xilinx I always get Linux-3.2.11-yocto-standard which is obviously missing the Zynq patches.

Quoted 6 lines

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

From you messages, I infer that you are using the meta-zynq layer
located here:

Quoted 6 lines

http://git.yoctoproject.org/cgit/cgit.cgi/meta-zynq/

For my builds, I used Philip Ballister's meta-zynq layer located here for the simple reason that it uses xilinx git repository:

https://github.com/balister/meta-zynq

And in case anyone is wondering, efforts are (still) underway to get a single unified layer for this board (and others), but getting all the moving parts organized is taking a bit longer than expected or than we would like.

Cheers,

Bruce

Quoted 16 lines

Also, try to ensure that you don't put both the meta-layers in your bblayers.conf file while building, and ensure that you set machine as follows in your local.conf file

MACHINE ?= "zynq-zc702"

Do let me know how it goes!

Best regards,

Elvis Dowson
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#3 lore raw
Quoted 54 lines · Bruce Ashfield
Quoted 53 lines · Elvis Dowson

Hi,

Quoted 33 lines · Andreas Schweigstill

I have also tried to build a kernel and root filesystem for Zynq but the kernel
gets stuck when booting, regardless if on the ZC702 board or on Qemu. I tried
Poky denzil and Poky danny.

Also the alternate meta-zynq layer from git.yoctoproject.org shows the same
behaviour.

These are the last console messages which I get:
## Booting kernel from Legacy Image at 01000000 ...

   Image Name:   Linux-3.2.11-yocto-standard
   Created:      2012-12-04  20:07:37 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2997472 Bytes = 2.9 MiB

Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01a80000
Booting using the fdt blob at 0x1a80000 Loading Device Tree to 0eff8000, end 0efff185 ... OK Loading Kernel Image ... OK
OK
Loading Device Tree to 0efed000, end 0eff7185 ... OK

Starting kernel ...

Instead of using Linux kernel version 3.5-xilinx I always get Linux-3.2.11-yocto-standard which is obviously missing the Zynq patches.

Quoted 6 lines

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

From you messages, I infer that you are using the meta-zynq layer
located here:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-zynq/

For my builds, I used Philip Ballister's meta-zynq layer located here for the simple reason that it uses xilinx git repository:

Quoted 6 lines
Quoted 1 line

https://github.com/balister/meta-zynq

And in case anyone is wondering, efforts are (still) underway to get a single unified layer for this board (and others), but getting all the moving parts organized is taking a bit longer than expected or than we would like.

Thanks! Should we go ahead and set the list up so interested parties can start coordinating our existing work?

Philip

Quoted 30 lines

Cheers,

Bruce

Quoted 10 lines

Also, try to ensure that you don't put both the meta-layers in your bblayers.conf file
while building, and ensure that you set machine as follows in your local.conf file

MACHINE ?= "zynq-zc702"

Do let me know how it goes!

Quoted 8 lines

Best regards,

Elvis Dowson
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#4 lore raw
Quoted 57 lines · Philip Balister
Quoted 56 lines · Bruce Ashfield
Quoted 54 lines · Elvis Dowson

Hi,

Quoted 33 lines · Andreas Schweigstill

I have also tried to build a kernel and root filesystem for Zynq but the kernel
gets stuck when booting, regardless if on the ZC702 board or on Qemu. I tried
Poky denzil and Poky danny.

Also the alternate meta-zynq layer from git.yoctoproject.org shows the same
behaviour.

These are the last console messages which I get:
## Booting kernel from Legacy Image at 01000000 ...

   Image Name:   Linux-3.2.11-yocto-standard
   Created:      2012-12-04  20:07:37 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2997472 Bytes = 2.9 MiB

Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01a80000
Booting using the fdt blob at 0x1a80000 Loading Device Tree to 0eff8000, end 0efff185 ... OK Loading Kernel Image ... OK
OK
Loading Device Tree to 0efed000, end 0eff7185 ... OK

Starting kernel ...

Instead of using Linux kernel version 3.5-xilinx I always get Linux-3.2.11-yocto-standard which is obviously missing the Zynq patches.

Quoted 6 lines

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

From you messages, I infer that you are using the meta-zynq layer
located here:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-zynq/

For my builds, I used Philip Ballister's meta-zynq layer located here for the simple reason that it uses xilinx git repository:

https://github.com/balister/meta-zynq

Quoted 7 lines
Quoted 4 lines

And in case anyone is wondering, efforts are (still) underway to get a single unified layer for this board (and others), but getting all the moving parts organized is taking a bit longer than expected or than we would like.

Thanks! Should we go ahead and set the list up so interested parties can start coordinating our existing work?

I'm good with that. It's no big commitment to anything in particular to have list available, and hopefully it'll serve to draw the right folks into the conversation.

Cheers,

Bruce

Quoted 33 lines

Philip

Quoted 30 lines

Cheers,

Bruce

Quoted 10 lines

Also, try to ensure that you don't put both the meta-layers in your bblayers.conf file
while building, and ensure that you set machine as follows in your local.conf file

MACHINE ?= "zynq-zc702"

Do let me know how it goes!

Quoted 8 lines

Best regards,

Elvis Dowson
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#5 lore raw
Quoted 3 lines · Bruce Ashfield
Quoted 2 lines · Philip Balister
Quoted 1 line · Bruce Ashfield

On 12-12-05 09:42 AM, Elvis Dowson wrote:

...

Quoted 7 lines
Quoted 3 lines

Thanks! Should we go ahead and set the list up so interested parties can start coordinating our existing work?

I'm good with that. It's no big commitment to anything in particular to have list available, and hopefully it'll serve to draw the right folks into the conversation.

Micheal, can you set up a mailing list "mete-zynq" for us? Also, please add this to gmane for people that prefer to read via nntp.

Thanks,

Philip

Quoted 41 lines

Cheers,

Bruce

Quoted 33 lines

Philip

Quoted 30 lines

Cheers,

Bruce

Quoted 10 lines

Also, try to ensure that you don't put both the meta-layers in your bblayers.conf file
while building, and ensure that you set machine as follows in your local.conf file

MACHINE ?= "zynq-zc702"

Do let me know how it goes!

Quoted 8 lines

Best regards,

Elvis Dowson
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#6 lore raw
In reply to Andreas Schweigstill
Quoted 35 lines · Andreas Schweigstill

Hello!

Quoted 2 lines

I personally have used Philip's meta-zynq layer to build a working u-boot and linux kernel image using Yocto. It works really well.

I have also tried to build a kernel and root filesystem for Zynq but the kernel gets stuck when booting, regardless if on the ZC702 board or on Qemu. I tried Poky denzil and Poky danny.

Also the alternate meta-zynq layer from git.yoctoproject.org shows the same behaviour.

These are the last console messages which I get:
## Booting kernel from Legacy Image at 01000000 ...

    Image Name:   Linux-3.2.11-yocto-standard
    Created:      2012-12-04  20:07:37 UTC
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    2997472 Bytes = 2.9 MiB
    Load Address: 00008000
    Entry Point:  00008000
    Verifying Checksum ... OK

## Flattened Device Tree blob at 01a80000
Booting using the fdt blob at 0x1a80000 Loading Device Tree to 0eff8000, end 0efff185 ... OK Loading Kernel Image ... OK
OK
Loading Device Tree to 0efed000, end 0eff7185 ... OK

Starting kernel ...

Instead of using Linux kernel version 3.5-xilinx I always get Linux-3.2.11-yocto-standard which is obviously missing the Zynq patches.

Quoted 5 lines

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

Urg, I'll have to take a look at that.

Also, you'll need an updated fsbl in the BOOT.BIN file to work with the later kernels. We should probably post one somewhere, although I wish the fsbl license was a little less restrictive.

Philip

Quoted 15 lines

With best regards,
Andreas Schweigstill

​--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#7 lore raw

Hello!

Am Mi, 12/05/2012 19:17, hat Philip Balister <[email protected]> geschrieben:

Quoted 8 lines · Andreas Schweigstill
Quoted 5 lines

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

Urg, I'll have to take a look at that.

After changing the order of BBLAYERS in build/conf/local.conf to meta, meta-zynq, meta-yocto, meta-yocto-bsp and using Hob to select MACHINE=zynq-zc702, base image=zc702-proto-image everything works fine. Now I get a proper toolchain for Cortex A9 and a kernel named zynq-zc702 3.5.0-14.3-build1-yocto-standard which is properly running on my ZC702 board.

Quoted 3 lines

Also, you'll need an updated fsbl in the BOOT.BIN file to work with the later kernels. We should probably post one somewhere, although I wish the fsbl license was a little less restrictive.

I haven't built a BOOT.BIN file with Yocto based U-Boot yet. Instead I'm using U-Boot from Petalinux 12.9 which is configured to use the QSPI Flash to store its environment.

Currently I boot from QSPI Flash, load kernel und DTB files via TFTP and use a root filesystem stored on a SD card. ;-)

Regards,
Andreas Schweigstill

​--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/

#8 lore raw

Hi Andreas,

Quoted 5 lines · Andreas Schweigstill

After changing the order of BBLAYERS in build/conf/local.conf to meta, meta-zynq, meta-yocto, meta-yocto-bsp and using Hob to select MACHINE=zynq-zc702, base image=zc702-proto-image everything works fine. Now I get a proper toolchain for Cortex A9 and a kernel named zynq-zc702 3.5.0-14.3-build1-yocto-standard which is properly running on my ZC702 board.

I don't add meta-yocto-bsp to my bblayers configuration.

Quoted 6 lines

I haven't built a BOOT.BIN file with Yocto based U-Boot yet. Instead I'm using U-Boot from Petalinux 12.9 which is configured to use the QSPI Flash to store its environment.

Currently I boot from QSPI Flash, load kernel und DTB files via TFTP and use a root filesystem stored on a SD card. ;-)

If you want to build your own version of BOOT.bin, its quite simple. Just take the u-boot.elf file, and use SDK to create a simple zynq_fsbl project. From that create the boot image, using the SDK, and add the system.bit, zynq_fsbl.elf and u-boot.elf binaries. Rename the produce binary to BOOT.bin, and you're good to go.

You can find more information of the boot image creation process on section 3.5, page 29, of the UG821 - Zynq-7000 EPP Software Developers Guide v3.0.

From within SDK, it's pretty straightforward, and it will automatically create the bif file after you've specified all the binaries, and create the bootable image.

Best regards,

Elvis Dowson

#9 lore raw

Dear Elvis!

Am Do, 12/06/2012 16:42, hat Elvis Dowson <[email protected]> geschrieben:

Quoted 1 line

If you want to build your own version of BOOT.bin, its quite simple.

Thank you very much for your instructions regarding the creation of my own BOOT.BIN file. Currently I am only evaluating the different Linux build systems resp. "distributions" being quite happy that I don't have to switch U-Boot together with the Linux/rootfs. In the final project we probably won't use U-Boot at all but instead use a proprietary boot mechanism.

Regards,
Andreas Schweigstill

​--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/

#10 lore raw
In reply to Andreas Schweigstill
Quoted 22 lines · Andreas Schweigstill

Hello!

Am Mi, 12/05/2012 19:17, hat Philip Balister <[email protected]> geschrieben:

Quoted 8 lines · Andreas Schweigstill
Quoted 5 lines

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

Urg, I'll have to take a look at that.

After changing the order of BBLAYERS in build/conf/local.conf to meta, meta-zynq, meta-yocto, meta-yocto-bsp and using Hob to select MACHINE=zynq-zc702, base image=zc702-proto-image everything works fine. Now I get a proper toolchain for Cortex A9 and a kernel named zynq-zc702 3.5.0-14.3-build1-yocto-standard which is properly running on my ZC702 board.

Quoted 3 lines

Also, you'll need an updated fsbl in the BOOT.BIN file to work with the later kernels. We should probably post one somewhere, although I wish the fsbl license was a little less restrictive.

Quoted 6 lines

I haven't built a BOOT.BIN file with Yocto based U-Boot yet. Instead I'm using U-Boot from Petalinux 12.9 which is configured to use the QSPI Flash to store its environment.

Currently I boot from QSPI Flash, load kernel und DTB files via TFTP and use a root filesystem stored on a SD card. ;-)

Thanks for the feedback. Good luck with your evaluation. Let us know if you have anymore questions.

Philip

Quoted 15 lines

Regards,
Andreas Schweigstill

​--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#11 lore raw
In reply to Andreas Schweigstill
Quoted 8 lines · Andreas Schweigstill

Hello!

Quoted 2 lines

I personally have used Philip's meta-zynq layer to build a working u-boot and linux kernel image using Yocto. It works really well.

I have also tried to build a kernel and root filesystem for Zynq but the kernel gets stuck when booting, regardless if on the ZC702 board or on Qemu. I tried Poky denzil and Poky danny.

Also, try these instructions. Note they do not use the meta-yocto shim layer (sorry, my customer has been taunting me again).

I feel like the meta-yocto layer is "forcing" the use of "standard" kernels.

Philip

Quoted 47 lines

Also the alternate meta-zynq layer from git.yoctoproject.org shows the same behaviour.

These are the last console messages which I get:
## Booting kernel from Legacy Image at 01000000 ...

    Image Name:   Linux-3.2.11-yocto-standard
    Created:      2012-12-04  20:07:37 UTC
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    2997472 Bytes = 2.9 MiB
    Load Address: 00008000
    Entry Point:  00008000
    Verifying Checksum ... OK

## Flattened Device Tree blob at 01a80000
Booting using the fdt blob at 0x1a80000 Loading Device Tree to 0eff8000, end 0efff185 ... OK Loading Kernel Image ... OK
OK
Loading Device Tree to 0efed000, end 0eff7185 ... OK

Starting kernel ...

Instead of using Linux kernel version 3.5-xilinx I always get Linux-3.2.11-yocto-standard which is obviously missing the Zynq patches.

meta-zynq/recipes-kernel-linux-zynq contains the following lines:
LINUX_VERSION ?= "3.5"
LINUX_VERSION_EXTENSION ?= "-xilinx"

How can I force Yocto to build kernel 3.5-xilinx?

With best regards,
Andreas Schweigstill

​--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto