03130f944a
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 <d.viti@infosolution.it> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
---|---|---|
.. | ||
uboot | ||
readme.txt |
This is the buildroot board support for the Avnet Microzed. The Microzed is a development board based on the Xilinx Zynq-7000 based All-Programmable System-On-Chip. Microzed information including schematics, reference designs, and manuals are available from http://www.zedboard.org . Steps to create a working system for Microzed: 1) make microzed_defconfig 2) make 3) copy files BOOT.BIN, u-boot-dtb.img, rootfs.cpio.uboot, uImage, zynq-zed.dtb into your SD card 4) boot your Microzed The expected output: U-Boot SPL 2015.07 (Sep 15 2015 - 16:10:56) mmc boot reading system.dtb spl_load_image_fat_os: error reading image system.dtb, err - -1 reading u-boot-dtb.img reading u-boot-dtb.img U-Boot 2015.07 (Sep 15 2015 - 16:10:56 +0200) Model: Zynq MicroZED Board I2C: ready DRAM: ECC disabled 1 GiB MMC: zynq_sdhci: 0 Using default environment ... When using an older U-Boot then 2015.07, a working ps7_init.c file is required to be installed into the U-Boot directory structure. From 2015.07, the major Zynq-based boards are supported without any manual intervention. Resulting system ---------------- A FAT32 partition should be created at the beginning of the SD Card and the following files should be installed: /BOOT.BIN /zynq-zed.dtb /uImage /rootfs-cpio.uboot /u-boot-dtb.img All needed files can be taken from output/images/ BOOT.BIN, uImage and u-boot-dtb.img are direct copies of the same files available on output/images/. Note th at the DTB (zynq-zed.dtb) is the same as the one used for the Zedboard, and that this is the recommended solution, see https://forums.xilinx.com/t5/Embedded-Linux/Microzed-default-device-tree-dts/td-p/432856. There is a patch attached that redefines the U-Boot's environment to work with Buildroot out-of-the-box. You can alter the booting procedure by creating a file uEnv.txt in the root of the SD card. It is a plain text file in format <key>=<value> one per line: kernel_image=myimage modeboot=myboot myboot=...