buildroot/board/avnet, branch 2019.02-op-build

zynq: unify readme.txt for all Zynq boards

2016-07-30T16:15:26+00:00

The readme.txt for the three boards are almost the same, so merge them into board/zynq/readme.txt. Signed-off-by: Masahiro Yamada Reviewed-by: Matt Weber Signed-off-by: Thomas Petazzoni

zynq_microzed: bump U-Boot to xilinx-v2016.2

2016-07-30T16:13:43+00:00

This is the latest release tag in the Xilinx repository, based on U-Boot v2016.01 in the mainline. To sync with the Zedboard updates, switch over to the Xilinx GitHub repository. Signed-off-by: Masahiro Yamada Reviewed-by: Matt Weber Signed-off-by: Thomas Petazzoni

zynq_zed: bump U-Boot to xilinx-v2016.2

2016-07-30T16:13:01+00:00

This is the latest release tag in the Xilinx repository, based on U-Boot v2016.01 in the mainline. Commit 46d6a561be41 ("zedboard: Generate BOOT.BIN automatically") switched from the Xilinx GitHub repository to the U-Boot mainline, but this commit gets it back to the Xilinx GitHub repository for the following reasons: - This defconfig still relies on the Xilinx's local repository for the kernel. The vendor does the best test for the combination of U-Boot and the kernel with the same release tag (xilinx-v2016.2 in this case). - At the time of commit 46d6a561be41, the u-boot-xlnx still needed manual copy of ps7_init(_gpl).c/h in order to build a working SPL image. So, the mainline U-Boot had advantage in that point of time. However, the improvement in the mainline U-Boot was merged into the u-boot-xlnx at the xilinx-v2015.3 release. Now, the mainline and the u-boot-xlnx are even in this point of view. - The mainline U-Boot defaults to boot FIT, so something must be done; either patch environments around with a local patch to switch to uImage booting (current solution), or build an FIT with a post build script (chromebook snow does this). On the other hand, the Xilinx repository defaults to uImage booting, so it is straightforward, and needs no addition care. This commit does: - Switch to the Xilinx custom git repository, and stick to the xilinx-v2016.2 tag. - Delete the local patch board/avnet/zedboard/uboot/0001... since the Xilinx custom repository can boot uImage by default. - Enable BR2_TARGET_UBOOT_FORMAT_IMG instead of ..._FORMAT_DTB_IMG since all the Zynq boards in U-Boot enable CONFIG_OF_EMBED. - Replace BR2_TARGET_UBOOT_ZYNQ_IMAGE with BR2_TARGET_UBOOT_SPL_NAME since U-Boot can natively generate the Zynq boot image now. The Zynq image support for mkimage tool was upstreamed at v2016.01 (so xilinx-v2016.1 as well), so no additional tool is needed any more. - Update readme.txt Signed-off-by: Masahiro Yamada Reviewed-by: Matt Weber Signed-off-by: Thomas Petazzoni

board/avnet: swap ramdisk and DT load addresses in U-Boot environment

2016-07-24T20:44:07+00:00

As reported in bug #9091, the U-Boot environment we provide for the Microzed and Zedboard platforms loads the ramdisk at 0x2000000 and the DT at 0x3000000. This means that a large enough ramdisk overwrites the DT. It makes more sense to load the DT at 0x2000000 and the ramdisk at 0x3000000. Reported-by: Michael Monaghan Tested-by: Michael Monaghan Signed-off-by: Thomas Petazzoni

configs: rename Zynq defconfig files

2016-03-31T16:40:43+00:00

These three are Zynq boards and the build procedure is almost the same. Having the SoC name prefix "zynq_" would be more consistent. Also, this is the way in which the Linux Device Trees and the U-Boot configuration files do. This commit renames as follows: zedboard_defconfig -> zynq_zed_defconfig microzed_defconfig -> zynq_microzed_defconfig xilinx_zc706_defconfig -> zynq_zc706_defconfig Signed-off-by: Masahiro Yamada Signed-off-by: Thomas Petazzoni

zedboard: uboot: load env earlier

2015-11-16T20:53:48+00:00

By default, with the original patch bootcmd runs sdboot before loading uEnv.txt. Consequently, if the user change modeboot, the user's defined content is updated too late. By loading uEnv.txt before 'run $modeboot' the correct boot mode is used instead of default mode. Signed-off-by: Gwenhael Goavec-Merou Acked-By: Jan Viktorin Signed-off-by: Thomas Petazzoni

microzed: add Avnet Microzed support

2015-09-17T21:54:39+00:00

Changes are based on Zedboard: Xilinx does not provide a specific DTS for Microzed in the kernel tree. It is suggested [1] to use the zynq-zed.dts and change the RAM size [1] https://forums.xilinx.com/t5/Embedded-Linux/Microzed-default-device-tree-dts/td-p/432856 [Thomas: - extend readme.txt to indicate why the same DTB is used for Microzed and the Zedboard. - add a description + Signed-off-by line in the 0001-zynq-Create-microzed-specific-U-Boot-environment.patch, by re-using the description of the same patch for the Zedboard.] Signed-off-by: Davide Viti Signed-off-by: Thomas Petazzoni

zedboard: Switch to U-Boot 2015.07

2015-07-22T12:31:55+00:00

The U-Boot v2015.07 is required for successful out-of-the-box build for common Xilinx Zynq boards (including Zedboard). Signed-off-by: Jan Viktorin Signed-off-by: Thomas Petazzoni

zedboard: Update readme.txt to reflect BOOT.BIN generation

2015-07-18T21:06:52+00:00

Signed-off-by: Jan Viktorin Signed-off-by: Thomas Petazzoni

zedboard: Patch default U-Boot environment for zedboard

2015-07-18T21:06:45+00:00

This patch changes the U-Boot's default environment to boot Zedboard out-of-the-box from SD card. The sdboot procedure tries to load a file system.bit into the Zynq's PL (only if it exists). It is also possible to alter the booting by an uEnv.txt file located on your SD card. The uEnv.txt is a plain text file with = pairs one per line. Signed-off-by: Jan Viktorin Signed-off-by: Thomas Petazzoni