* mail list for Xilinx Zynq platform?
@ 2012-11-26 8:45 Daniel Martinez Ramos
2012-11-26 13:33 ` Elvis Dowson
0 siblings, 1 reply; 14+ messages in thread
From: Daniel Martinez Ramos @ 2012-11-26 8:45 UTC (permalink / raw)
To: yocto
Hi all,
I've found a bsp layer in Xilinx here
http://forums.xilinx.com/t5/Embedded-Linux/Yocto-BSP-for-ZC-702/td-p/246932,
which is pretty interesting.
Is any mail list under Yocto for the Xilinx Zinq platform?
Best regards,
Daniel Martinez
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-11-26 8:45 Daniel Martinez Ramos
@ 2012-11-26 13:33 ` Elvis Dowson
0 siblings, 0 replies; 14+ messages in thread
From: Elvis Dowson @ 2012-11-26 13:33 UTC (permalink / raw)
To: Daniel Martinez Ramos; +Cc: yocto
Hi Daniel,
As far as I know, there is no specific mailing list for the Xilinx Zynq platform. I use the Xilinx forums to get help at the moment.
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.
Using the Zynq is a little bit different than a standard ARM SOC. If you've worked with the TI OMAP series, you would be familiar with the x-loader component, that runs before u-boot. Well, the only difference here is that you need to use the Xilinx SDK to create a zynq_fsbl (first stage boot loader) project, using the defaults.
Once you've got the zynq_fsbl, you have a couple of options
a. Create a bootable image
Use the SDK create boot image utility to create a bootable image
- zynq_fsbl
- u-boot.bin
- system.bit (hardware bitstream)
You would rename the resultant file as BOOT.bin.
After that, you can drop the linux kernel uImage onto an SD card and boot linux as normal.
b. Download to the target using xmd and a tcl script
Use the xapp792 design files, to see how to download the binaries to the Zynq board using a JTAG cable. The tcl file is located in xapp792/zc702_video_3x_pipeline/ready_for_download/xmd_top.tcl
The whole process takes a couple of days to get used to. Let me know if you get stuck somewhere.
Best regards,
Elvis DOwson
On Nov 26, 2012, at 12:45 PM, Daniel Martinez Ramos <daniel.martinez@sacnet.es> wrote:
> Hi all,
>
> I've found a bsp layer in Xilinx here http://forums.xilinx.com/t5/Embedded-Linux/Yocto-BSP-for-ZC-702/td-p/246932, which is pretty interesting.
>
> Is any mail list under Yocto for the Xilinx Zinq platform?
>
> Best regards,
>
> Daniel Martinez
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
@ 2012-12-05 13:21 Andreas Schweigstill
2012-12-05 14:42 ` Elvis Dowson
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Andreas Schweigstill @ 2012-12-05 13:21 UTC (permalink / raw)
To: yocto
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 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/
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
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:17 ` Philip Balister
2012-12-05 18:23 ` Philip Balister
2 siblings, 1 reply; 14+ messages in thread
From: Elvis Dowson @ 2012-12-05 14:42 UTC (permalink / raw)
To: Andreas Schweigstill; +Cc: yocto
Hi,
On Dec 5, 2012, at 5:21 PM, Andreas Schweigstill <andreas@schweigstill.de> wrote:
> 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?
>
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
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-05 14:42 ` Elvis Dowson
@ 2012-12-05 14:46 ` Bruce Ashfield
2012-12-05 18:15 ` Philip Balister
0 siblings, 1 reply; 14+ messages in thread
From: Bruce Ashfield @ 2012-12-05 14:46 UTC (permalink / raw)
To: Elvis Dowson; +Cc: yocto
On 12-12-05 09:42 AM, Elvis Dowson wrote:
> Hi,
>
> On Dec 5, 2012, at 5:21 PM, Andreas Schweigstill <andreas@schweigstill.de> wrote:
>
>> 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?
>>
>
> 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
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
>
> 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
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-05 14:46 ` Bruce Ashfield
@ 2012-12-05 18:15 ` Philip Balister
2012-12-05 18:30 ` Bruce Ashfield
0 siblings, 1 reply; 14+ messages in thread
From: Philip Balister @ 2012-12-05 18:15 UTC (permalink / raw)
To: Bruce Ashfield; +Cc: yocto
On 12/05/2012 06:46 AM, Bruce Ashfield wrote:
> On 12-12-05 09:42 AM, Elvis Dowson wrote:
>> Hi,
>>
>> On Dec 5, 2012, at 5:21 PM, Andreas Schweigstill
>> <andreas@schweigstill.de> wrote:
>>
>>> 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?
>>>
>>
>> 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
>
> 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
>
> Cheers,
>
> Bruce
>
>>
>> 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
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-05 13:21 mail list for Xilinx Zynq platform? Andreas Schweigstill
2012-12-05 14:42 ` Elvis Dowson
@ 2012-12-05 18:17 ` Philip Balister
2012-12-06 12:57 ` Andreas Schweigstill
2012-12-05 18:23 ` Philip Balister
2 siblings, 1 reply; 14+ messages in thread
From: Philip Balister @ 2012-12-05 18:17 UTC (permalink / raw)
To: Andreas Schweigstill; +Cc: yocto
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 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?
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
>
> 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
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-05 13:21 mail list for Xilinx Zynq platform? Andreas Schweigstill
2012-12-05 14:42 ` Elvis Dowson
2012-12-05 18:17 ` Philip Balister
@ 2012-12-05 18:23 ` Philip Balister
2 siblings, 0 replies; 14+ messages in thread
From: Philip Balister @ 2012-12-05 18:23 UTC (permalink / raw)
To: Andreas Schweigstill; +Cc: yocto
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
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-05 18:15 ` Philip Balister
@ 2012-12-05 18:30 ` Bruce Ashfield
2012-12-05 19:01 ` Philip Balister
0 siblings, 1 reply; 14+ messages in thread
From: Bruce Ashfield @ 2012-12-05 18:30 UTC (permalink / raw)
To: Philip Balister; +Cc: yocto
On 12-12-05 01:15 PM, Philip Balister wrote:
> On 12/05/2012 06:46 AM, Bruce Ashfield wrote:
>> On 12-12-05 09:42 AM, Elvis Dowson wrote:
>>> Hi,
>>>
>>> On Dec 5, 2012, at 5:21 PM, Andreas Schweigstill
>>> <andreas@schweigstill.de> wrote:
>>>
>>>> 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?
>>>>
>>>
>>> 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
>>
>> 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
>
> Philip
>
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> 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
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-05 18:30 ` Bruce Ashfield
@ 2012-12-05 19:01 ` Philip Balister
0 siblings, 0 replies; 14+ messages in thread
From: Philip Balister @ 2012-12-05 19:01 UTC (permalink / raw)
To: Michael Halstead; +Cc: yocto
On 12/05/2012 10:30 AM, Bruce Ashfield wrote:
> On 12-12-05 01:15 PM, Philip Balister wrote:
>> On 12/05/2012 06:46 AM, Bruce Ashfield wrote:
>>> On 12-12-05 09:42 AM, Elvis Dowson wrote:
...
>>
>> 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
>
> Cheers,
>
> Bruce
>
>>
>> Philip
>>
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> 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
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>
>
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-05 18:17 ` Philip Balister
@ 2012-12-06 12:57 ` Andreas Schweigstill
2012-12-06 15:42 ` Elvis Dowson
2012-12-06 20:08 ` Philip Balister
0 siblings, 2 replies; 14+ messages in thread
From: Andreas Schweigstill @ 2012-12-06 12:57 UTC (permalink / raw)
To: yocto
Hello!
Am Mi, 12/05/2012 19:17, hat Philip Balister <philip@balister.org> geschrieben:
> On 12/05/2012 05:21 AM, Andreas Schweigstill wrote:
> > 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.
> 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/
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
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
1 sibling, 1 reply; 14+ messages in thread
From: Elvis Dowson @ 2012-12-06 15:42 UTC (permalink / raw)
To: Andreas Schweigstill; +Cc: yocto
Hi Andreas,
On Dec 6, 2012, at 4:57 PM, Andreas Schweigstill <andreas@schweigstill.de> wrote:
> 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.
> 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
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-06 15:42 ` Elvis Dowson
@ 2012-12-06 16:33 ` Andreas Schweigstill
0 siblings, 0 replies; 14+ messages in thread
From: Andreas Schweigstill @ 2012-12-06 16:33 UTC (permalink / raw)
To: yocto
Dear Elvis!
Am Do, 12/06/2012 16:42, hat Elvis Dowson <elvis.dowson@gmail.com> geschrieben:
> 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/
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: mail list for Xilinx Zynq platform?
2012-12-06 12:57 ` Andreas Schweigstill
2012-12-06 15:42 ` Elvis Dowson
@ 2012-12-06 20:08 ` Philip Balister
1 sibling, 0 replies; 14+ messages in thread
From: Philip Balister @ 2012-12-06 20:08 UTC (permalink / raw)
To: Andreas Schweigstill; +Cc: yocto
On 12/06/2012 04:57 AM, Andreas Schweigstill wrote:
> Hello!
>
> Am Mi, 12/05/2012 19:17, hat Philip Balister <philip@balister.org> geschrieben:
>> On 12/05/2012 05:21 AM, Andreas Schweigstill wrote:
>>> 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.
>
>> 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. ;-)
Thanks for the feedback. Good luck with your evaluation. Let us know if
you have anymore questions.
Philip
>
> 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
>
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2012-12-06 20:08 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- strict thread matches above, loose matches on Subject: below --
2012-11-26 8:45 Daniel Martinez Ramos
2012-11-26 13:33 ` Elvis Dowson
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.