configs: bump zedboard to 2014.1
PATCH 1/1 configs: bump zedboard to 2014.1
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.
--- board/avnet/zedboard/readme.txt | 26 ++++++++++++++------------ configs/zedboard_defconfig | 17 +++++------------ 2 files changed, 19 insertions(+), 24 deletions(-)
board/avnet/zedboard/readme.txt +14 -12
@@ -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
configs/zedboard_defconfig +5 -12
@@ -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"
Signature · 1 line
1.7.1
PATCH 1/1 configs: bump zedboard to 2014.1
Dear Spenser Gilliland,
board/avnet/zedboard/readme.txt to the sdcard: · line 29
Quoted 12 lines · Spenser Gilliland
board/avnet/zedboard/readme.txt +12
-0+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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 configs: bump zedboard to 2014.1
Quoted 7 lines · Thomas Petazzoni
Dear Spenser Gilliland,
Review
Quoted 2 lines · Spenser Gilliland
(quoted diff) +2
-0+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
Quoted 3 lines
board/avnet/zedboard/readme.txt to the sdcard:
Quoted 3 lines
board/avnet/zedboard/readme.txt +3
-0+boot.bin file. + +If you already have the Xilinx tools installed, the follwing sequence
will
Quoted 5 lines
board/avnet/zedboard/readme.txt to the sdcard:
Quoted 5 lines
board/avnet/zedboard/readme.txt +5
-0+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} \
Quoted 6 lines
board/avnet/zedboard/readme.txt to the sdcard: · line 29
Quoted 2 lines
board/avnet/zedboard/readme.txt +2
-0+output/build/uboot-xilinx-v2014.1/boards/xilinx/zynq/ +makeDoes 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
Quoted 7 lines
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>
PATCH 1/1 configs: bump zedboard to 2014.1
Dear Spenser Gilliland,
Quoted 6 lines · Spenser Gilliland
Quoted 3 lines
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 configs: bump zedboard to 2014.1
Thomas,
Quoted 2 lines
(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
Signature · 3 lines
Spenser Gilliland Computer Engineer Doctoral Candidate
PATCH 1/1 configs: bump zedboard to 2014.1
Dear Spenser Gilliland,
Quoted 6 lines · Spenser Gilliland
Quoted 2 lines
(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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 configs: bump zedboard to 2014.1
Thomas,
Quoted 4 lines
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
Signature · 3 lines
Spenser Gilliland Computer Engineer Doctoral Candidate
PATCH 1/1 configs: bump zedboard to 2014.1
Dear Spenser Gilliland,
Quoted 8 lines · Spenser Gilliland
Quoted 4 lines
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 configs: bump zedboard to 2014.1
Thomas,
Quoted 2 lines
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
Signature · 3 lines
Spenser Gilliland Computer Engineer Doctoral Candidate
PATCH 1/1 configs: bump zedboard to 2014.1
Dear Spenser Gilliland,
Quoted 4 lines · Spenser Gilliland
Quoted 2 lines
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com