[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Spenser Gilliland]

Bump zedboard defconfig to version 2014.1.  This makes it possible to use
uboot-spl instead of the xilinx specific fsbl.  However, the result is kinda
hacky due to the licensing state of ps7_init.{c,h} needed for building uboot
spl.  Directions for building a proper boot.bin using the new methodolgy is
included in the readme.txt.

Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
---
 board/avnet/zedboard/readme.txt |   26 ++++++++++++++------------
 configs/zedboard_defconfig      |   17 +++++------------
 2 files changed, 19 insertions(+), 24 deletions(-)

diff --git a/board/avnet/zedboard/readme.txt b/board/avnet/zedboard/readme.txt
index 6b6df36..efd076f 100644
--- a/board/avnet/zedboard/readme.txt
+++ b/board/avnet/zedboard/readme.txt
@@ -10,19 +10,21 @@ to the sdcard:
 	zynq-zed.dtb -> devicetree.dtb
 	rootfs.cpio.gz.uboot -> uramdisk.image.gz
 	uImage -> uImage
+	boot.bin -> boot.bin
 
-Uboot Support
+U-Boot SPL Support
 -------------
 
-Uboot is installed in a wrapper file called BOOT.BIN located on the root of
-the SD card.  To create the BOOT.BIN file do the following.
+Due to licensing issues, the files ps7_init.c/h are not able to be
+distributed with the U-Boot source code.  These files are required to make a
+boot.bin file.
+
+If you already have the Xilinx tools installed, the follwing sequence will
+unpack, patch and build the rfs, kernel, uboot, and uboot-spl.
+
+make zedboard_defconfig
+make uboot-patch
+cp ${XILINX}/ISE_DS/EDK/sw/lib/hwplatform_templates/zed_hw_platform/ps7_init.{c,h} \
+output/build/uboot-xilinx-v2014.1/boards/xilinx/zynq/
+make
 
-source <path/to/xilinx/settings.sh>
-cat <<EOF > boot.bif
-{
-   [bootloader]<path/to/fsbl.elf>
-   <path/to/system.bit>
-   <path/to/uboot.elf>
-}
-EOF
-bootgen -image boot.bif -o i BOOT.BIN
diff --git a/configs/zedboard_defconfig b/configs/zedboard_defconfig
index 071ff65..e0e7760 100644
--- a/configs/zedboard_defconfig
+++ b/configs/zedboard_defconfig
@@ -1,33 +1,26 @@
 BR2_arm=y
 BR2_cortex_a9=y
 BR2_ARM_ENABLE_NEON=y
-
-# Lock to 3.8 headers as the kernel is based off 3.8
 BR2_KERNEL_HEADERS_VERSION=y
 BR2_DEFAULT_KERNEL_VERSION="3.8"
 BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_8=y
-
 BR2_TARGET_GENERIC_GETTY_PORT="ttyPS0"
-
-# Kernel
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://github.com/Xilinx/linux-xlnx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="xilinx-v14.5"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="xilinx-v2014.1"
 BR2_LINUX_KERNEL_DEFCONFIG="xilinx_zynq"
 BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x8000"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="zynq-zed"
-
-# Root filesystem
 BR2_TARGET_ROOTFS_CPIO=y
 BR2_TARGET_ROOTFS_CPIO_GZIP=y
 BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
-
-# Bootloader
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BOARDNAME="zynq_zed"
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="git://github.com/Xilinx/u-boot-xlnx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v14.5"
-BR2_TARGET_UBOOT_FORMAT_ELF=y
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="xilinx-v2014.1"
+BR2_TARGET_UBOOT_FORMAT_IMG=y
+BR2_TARGET_UBOOT_SPL=y
+BR2_TARGET_UBOOT_SPL_NAME="boot.bin"
-- 
1.7.1

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Thomas Petazzoni]

Dear Spenser Gilliland,

On Tue, 27 May 2014 16:15:32 -0500, Spenser Gilliland wrote:

> +Due to licensing issues, the files ps7_init.c/h are not able to be
> +distributed with the U-Boot source code.  These files are required to make a
> +boot.bin file.
> +
> +If you already have the Xilinx tools installed, the follwing sequence will
> +unpack, patch and build the rfs, kernel, uboot, and uboot-spl.
> +
> +make zedboard_defconfig
> +make uboot-patch
> +cp ${XILINX}/ISE_DS/EDK/sw/lib/hwplatform_templates/zed_hw_platform/ps7_init.{c,h} \
> +output/build/uboot-xilinx-v2014.1/boards/xilinx/zynq/
> +make

Does this means that the U-Boot build will fail without those files? If
that's the case, then that's not really an acceptable solution, because
this defconfig will continuously fail to build in our Jenkins CI.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Spenser Gilliland]

On May 28, 2014 1:16 AM, "Thomas Petazzoni" <
thomas.petazzoni@free-electrons.com> wrote:
>
> Dear Spenser Gilliland,
>
> On Tue, 27 May 2014 16:15:32 -0500, Spenser Gilliland wrote:
>
> > +Due to licensing issues, the files ps7_init.c/h are not able to be
> > +distributed with the U-Boot source code.  These files are required to
make a
> > +boot.bin file.
> > +
> > +If you already have the Xilinx tools installed, the follwing sequence
will
> > +unpack, patch and build the rfs, kernel, uboot, and uboot-spl.
> > +
> > +make zedboard_defconfig
> > +make uboot-patch
> > +cp
${XILINX}/ISE_DS/EDK/sw/lib/hwplatform_templates/zed_hw_platform/ps7_init.{c,h}
\
> > +output/build/uboot-xilinx-v2014.1/boards/xilinx/zynq/
> > +make
>
> Does this means that the U-Boot build will fail without those files? If
> that's the case, then that's not really an acceptable solution, because
> this defconfig will continuously fail to build in our Jenkins CI.

No, it will not fail during the build.  However, the boot.bin (uboot spl)
binary will not work on the target.

For qemu testing, the u-boot.img image can be used.

Thanks,
Spenser

> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140528/4ce335af/attachment.html>

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Thomas Petazzoni]

Dear Spenser Gilliland,

On Wed, 28 May 2014 01:30:30 -0500, Spenser Gilliland wrote:

> > Does this means that the U-Boot build will fail without those files? If
> > that's the case, then that's not really an acceptable solution, because
> > this defconfig will continuously fail to build in our Jenkins CI.
> 
> No, it will not fail during the build.  However, the boot.bin (uboot spl)
> binary will not work on the target.

Ok, thanks!

(Could you look at replying to my e-mail regarding your remaining
Microblaze related patches in patchwork? Thanks!)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Spenser Gilliland]

Thomas,

> (Could you look at replying to my e-mail regarding your remaining
> Microblaze related patches in patchwork? Thanks!)

In progress, there were several changes that needed to be made plus
I'm in the middle of moving.  I'm running some tests on the new
patches now and will resubmit soon.

Thanks,
Spenser

-- 
Spenser Gilliland
Computer Engineer
Doctoral Candidate

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Thomas Petazzoni]

Dear Spenser Gilliland,

On Wed, 28 May 2014 09:20:14 -0500, Spenser Gilliland wrote:

> > (Could you look at replying to my e-mail regarding your remaining
> > Microblaze related patches in patchwork? Thanks!)
> 
> In progress, there were several changes that needed to be made plus
> I'm in the middle of moving.  I'm running some tests on the new
> patches now and will resubmit soon.

Did you look at Waldemar patches? He upgraded quite a few components of
the Microblaze toolchains. It would be nice to not ping-pong between
patches proposed by you, and then patches proposed by Waldemar, and
then again by you. So please coordinate with Waldemar.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Spenser Gilliland]

Thomas,

> Did you look at Waldemar patches? He upgraded quite a few components of
> the Microblaze toolchains. It would be nice to not ping-pong between
> patches proposed by you, and then patches proposed by Waldemar, and
> then again by you. So please coordinate with Waldemar.

The only patches from Waldemar appears to be
http://patchwork.ozlabs.org/patch/343980/ .  Were they not added to
patchwork?

Thanks,
Spenser
-- 
Spenser Gilliland
Computer Engineer
Doctoral Candidate

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Thomas Petazzoni]

Dear Spenser Gilliland,

On Wed, 28 May 2014 09:45:25 -0500, Spenser Gilliland wrote:

> > Did you look at Waldemar patches? He upgraded quite a few components of
> > the Microblaze toolchains. It would be nice to not ping-pong between
> > patches proposed by you, and then patches proposed by Waldemar, and
> > then again by you. So please coordinate with Waldemar.
> 
> The only patches from Waldemar appears to be
> http://patchwork.ozlabs.org/patch/343980/ .  Were they not added to
> patchwork?

Waldemar patches have been applied, so they are no longer visible in
patchwork as 'New'.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Spenser Gilliland]

Thomas,

> Waldemar patches have been applied, so they are no longer visible in
> patchwork as 'New'.

I'm rebasing on master so his patches should not cause an issue.

Thanks,
Spenser

-- 
Spenser Gilliland
Computer Engineer
Doctoral Candidate

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Thomas Petazzoni]

Dear Spenser Gilliland,

On Wed, 28 May 2014 10:03:19 -0500, Spenser Gilliland wrote:

> > Waldemar patches have been applied, so they are no longer visible in
> > patchwork as 'New'.
> 
> I'm rebasing on master so his patches should not cause an issue.

Ok, but remember we asked some questions on your patches, and I think
you never got back to us with any answers. So a new posting of the
patches will have to have answers to those questions. Especially since
you were changing the gcc/gdb/glibc/binutils versions used for
Microblaze, and they have been changed in the mean time by Waldemar. So
yet another change will have to come with an appropriate justification.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Javier Domingo Cansino]

Hello!

I am trying to use this patch to boot a zedboard, but I can't get it
working, I also tried doing it without the patch, and didn't succeed
neither.

I had started rewriting a more complete readme.txt to make it easier
for people create a buildroot based system[1], but didn't get zedboard
boot with those instructions neither.

Regarding your patch, I followed the specified commands in the readme,
and I noticed a failure on it, the path to copy the sources to has a
typo, needs to be board instead of boards:

>+output/build/uboot-xilinx-v2014.1/boards/xilinx/zynq/
+output/build/uboot-xilinx-v2014.1/board/xilinx/zynq/

The steps I made after make (as stated in the readme) ended, have been

cp output/images/uImage SD/
cp output/images/rootfs.cpio.uboot SD/uramdisk.image
gzip SD/uramdisk.image
cp output/images/boot.bin SD/
cp output/images/zynq-zed.dtb SD/devicetree.dtb

The board doesn't even boot, nor load with the blue led (DONE one).

I will be in #buildroot as txomon or txomon|home , and can have the
card available for testing for one week,

Cheers,

Javier Domingo Cansino

[1] Github buildroot clone: https://github.com/txomon/buildroot ->
doc/zedboard-instructions

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Spenser Gilliland]

Javier,

On Jun 1, 2014 6:49 AM, "Javier Domingo Cansino" <javierdo1@gmail.com>
wrote:
>
> Hello!
>
> I am trying to use this patch to boot a zedboard, but I can't get it
> working, I also tried doing it without the patch, and didn't succeed
> neither.

Thanks for testing my patch!   Please see my comments below for some more
info that may help you get it working.

>
> I had started rewriting a more complete readme.txt to make it easier
> for people create a buildroot based system[1], but didn't get zedboard
> boot with those instructions neither.
>
> Regarding your patch, I followed the specified commands in the readme,
> and I noticed a failure on it, the path to copy the sources to has a
> typo, needs to be board instead of boards:
>
> >+output/build/uboot-xilinx-v2014.1/boards/xilinx/zynq/
> +output/build/uboot-xilinx-v2014.1/board/xilinx/zynq/
>
> The steps I made after make (as stated in the readme) ended, have been
>
> cp output/images/uImage SD/
> cp output/images/rootfs.cpio.uboot SD/uramdisk.image
> gzip SD/uramdisk.image

You should not run gzip this will compress the uboot header which will make
it impossible for uboot to load the rfs.

You will also need to install the u-boot.img binary to the root of the sd
card.

> cp output/images/boot.bin SD/
> cp output/images/zynq-zed.dtb SD/devicetree.dtb
>
> The board doesn't even boot, nor load with the blue led (DONE one).

The blue led will not come on in the current configuration.  This is
because no bitfile is loaded. You will need to install a bitfile on the
sdcard and load it with the fpga command in uboot or the xdevcfg device in
Linux.

Just for reference, the patch changes the initial boot loader from the
Xilinx fsbl based boot loader to the uboot spl loader.

Thanks,
Spenser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140601/99809939/attachment.html>

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Javier Domingo Cansino]

Hi Spenser,

> You should not run gzip this will compress the uboot header which will make
> it impossible for uboot to load the rfs.
>
> You will also need to install the u-boot.img binary to the root of the sd
> card.

Ok, just for future references and because I finally realized that the
rootfs.cpio.uboot was indeed compressed thought file command didn't
say so, this should be the final SD layout:

cp output/images/uImage SD/uImage
cp output/images/rootfs.cpio.uboot SD/uramdisk.image.gz
cp output/images/boot.bin SD/boot.bin
cp output/images/zynq-zed.dtb SD/devicetree.dtb
cp output/images/u-boot.img SD/u-boot.img

> The blue led will not come on in the current configuration.  This is because
> no bitfile is loaded. You will need to install a bitfile on the sdcard and
> load it with the fpga command in uboot or the xdevcfg device in Linux.
Ok, I had such feeling and this asserts that feeling =)

> Just for reference, the patch changes the initial boot loader from the
> Xilinx fsbl based boot loader to the uboot spl loader.

Yup, I read that, the problem was that I didn't get the previous
configuration working, this makes easier for me to start now with a
base working system =)

I will be looking forward for your patch to get applied, to rebase
mine and improve the docs :)


Javier Domingo Cansino

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Spenser Gilliland]

Javier,

On Jun 1, 2014 9:14 AM, "Javier Domingo Cansino" <javierdo1@gmail.com>
wrote:
>
> Hi Spenser,
>
> > You should not run gzip this will compress the uboot header which will
make
> > it impossible for uboot to load the rfs.
> >
> > You will also need to install the u-boot.img binary to the root of the
sd
> > card.
>
> Ok, just for future references and because I finally realized that the
> rootfs.cpio.uboot was indeed compressed thought file command didn't
> say so, this should be the final SD layout:
>
> cp output/images/uImage SD/uImage
> cp output/images/rootfs.cpio.uboot SD/uramdisk.image.gz
> cp output/images/boot.bin SD/boot.bin
> cp output/images/zynq-zed.dtb SD/devicetree.dtb
> cp output/images/u-boot.img SD/u-boot.img
>

Yes, this is correct.

> > The blue led will not come on in the current configuration.  This is
because
> > no bitfile is loaded. You will need to install a bitfile on the sdcard
and
> > load it with the fpga command in uboot or the xdevcfg device in Linux.
> Ok, I had such feeling and this asserts that feeling =)
>
> > Just for reference, the patch changes the initial boot loader from the
> > Xilinx fsbl based boot loader to the uboot spl loader.
>
> Yup, I read that, the problem was that I didn't get the previous
> configuration working, this makes easier for me to start now with a
> base working system =)

Xilinx isnt currently saying that they fully support this boot pathway but
it is functional and several xilinx devs have made patches to fix bugs and
improve support.

>
> I will be looking forward for your patch to get applied, to rebase
> mine and improve the docs :)

Sounds great.   If your willing to write docs, it may be interesting to
create a wiki page on wiki.xilinx.com that walks through the whole
process.  This would give the buildroot port some additional exposure.

>
> Javier Domingo Cansino

Thanks,
Spenser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140601/d60f6c3e/attachment.html>

[Buildroot] [PATCH 1/1] configs: bump zedboard to 2014.1

[Javier Domingo Cansino]

I am currently trying to integrate Zedboard in Openwrt, mainly because
it is the one I am accustomed to and because I sick when people uses
over 20MB in an embedded system ;).

> Sounds great.   If your willing to write docs, it may be interesting to
> create a wiki page on wiki.xilinx.com that walks through the whole process.
> This would give the buildroot port some additional exposure.

I don't know how much time I will have spare but I will definitely
consider doing it =)

Javier Domingo Cansino