From: Philip Balister <philip@balister.org>
To: Andreas Schweigstill <andreas@schweigstill.de>
Cc: yocto@yoctoproject.org
Subject: Re: mail list for Xilinx Zynq platform?
Date: Wed, 05 Dec 2012 10:23:15 -0800 [thread overview]
Message-ID: <50BF9113.9070300@balister.org> (raw)
In-Reply-To: <1354713685799908500@schweigstill.de>
On 12/05/2012 05:21 AM, Andreas Schweigstill wrote:
> Hello!
>
>> 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
>
> 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
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2012-12-05 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 13:21 mail list for Xilinx Zynq platform? Andreas Schweigstill
2012-12-05 14:42 ` Elvis Dowson
2012-12-05 14:46 ` Bruce Ashfield
2012-12-05 18:15 ` Philip Balister
2012-12-05 18:30 ` Bruce Ashfield
2012-12-05 19:01 ` Philip Balister
2012-12-05 18:17 ` Philip Balister
2012-12-06 12:57 ` Andreas Schweigstill
2012-12-06 15:42 ` Elvis Dowson
2012-12-06 16:33 ` Andreas Schweigstill
2012-12-06 20:08 ` Philip Balister
2012-12-05 18:23 ` Philip Balister [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-26 8:45 Daniel Martinez Ramos
2012-11-26 13:33 ` Elvis Dowson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50BF9113.9070300@balister.org \
--to=philip@balister.org \
--cc=andreas@schweigstill.de \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.