build u-boot

if you pull down the source for u-boot-xarm from the Xilinx git server, ref link:

http://wiki.xilinx.com/zynq-uboot

you can perform a grep command to go through the files in the directory for the configuration:

user@computer:~/u-boot-xarm$ grep -H -r "zynq_zc" ./*

This returns the ./boards.cfg file.  You can see there are a few different configurations that are supported.  here is the output I got:

./boards.cfg:zynq_zc770_XM010             arm         armv7       zynq_common         xilinx         zynq       zynq_zc770:ZC770_XM010
./boards.cfg:zynq_zc770_XM011             arm         armv7       zynq_common         xilinx         zynq       zynq_zc770:ZC770_XM011
./boards.cfg:zynq_zc770_XM011_n16b        arm         armv7       zynq_common         xilinx         zynq       zynq_zc770:ZC770_XM011,XILINX_ZYNQ_NAND_BUSWIDTH_16
./boards.cfg:zynq_zc770_XM012             arm         armv7       zynq_common         xilinx         zynq       zynq_zc770:ZC770_XM012
./boards.cfg:zynq_zc770_XM013             arm         armv7       zynq_common         xilinx         zynq       zynq_zc770:ZC770_XM013
./boards.cfg:zynq_zc70x                   arm         armv7       zynq_common         xilinx         zynq

You can see that there is a configuration for zynq_zc70x, but not for the zc702 board directly.  This is because there is a zc706 board available not from Xilinx, ref link:

http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm

Remember that the ARM subsystem is identical across all 4 of the Zynq-7000 devices, thus this allows for the same u-boot image to be used if the code is coming from the same configuration memory.

let me know if that answers your question.

thank you very much, i got a lot of information, but i still have some questions:
(1)if command "make zynq_zc702_config" can't be used, why put it online?http://wiki.xilinx.com/zynq-uboot
(2)i use the u-boot created by "make zynq_zc70x_config" build a BOOT.bin and use it successfully boot up U-boot on board ZC702,but then i use the U-boot to start up linux,it hangs up.so i doubt whether it is beause of u-boot.here is the detailhttp://www.zedboard.org/content/boot-linux-sd-card

jameschennerd,

(1)The way that git works is based on branches and tags.  If you just execute the command provided on the Xilinx wiki you will get the latest branch, which appears to have already moved into the 14.3 release files.  That is why you are seeing the error there.  I do not know what the branch is called for the 14.2 release, but I'll take a look and update the wiki was soon as I do.

(2)Looks like there is definitely a step that you are missing - not sure which one it is though.  Are you compiling your dts file correctly?  If the bit-file you are using does not match up to your dts file then you can hang the Kernel.  In other words, if you are loading in code to the PL that the PS doesn't know about, it can hang the Kernel.  I'll look into this further though and see what I can come up with.

jameschennerd,

Referencing this link: http://wiki.xilinx.com/zynq-uboot

If you scroll just a bit farther on the page, you will see this command:

git checkout -b xilinx-14.2-build1-trd xilinx-14.2-build1-trd

and the text above it: "For users wanting to avoid the new features temporarily, checkout the last 14.2 TRD release branch as shown in the following command."

Xilinx migrated to the zc70x version for the 14.3 tools release, which has already been pushed to the repository.  If you look in the git commit log you see this:

"
commit e52dfe7d236f8faf262ce38d665c18d1fdc3ec7d
Author: Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
Date:   Tue Aug 28 23:55:16 2012 +0530

    Xilinx: ARM: Create zc70x config file to support zc702 and zc706 boards

    Support to detect dual qspi flash memory is based on the MIO's
    configuration is added.
    Therefore, no need to have separate config files for zc702 and zc706.

    Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
"

This is in the master branch, and on Aug 28th.  If you switch to the xilinx-14.2-build1-trd branch, you will see the last commit is:

"
commit b8416f141c46a44a41071125bcf990a044eb0660
Author: Joe Hershberger <joe.hershberger@ni.com>
Date:   Tue Jun 19 09:47:37 2012 -0500

    Xilinx: ARM: nand: Wait for the device to be ready

    Make sure the device is ready in the cases where it should (same as
    Linux now, except that NAND_CMD_ERASE1 should not be here)

    Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
"

This commit is on June 19th - which is before the zc70x change.

Hope this helps to explain things!

TimDuffy,thanks for your detailed answer.
i know the reason why i can not use "make zynq_zc702_config",i find that the u-boot i use is to launch uImage:
"u-boot> fatload mmc 0 0x3000000 uImage
u-boot> fatload mmc 0 0x2A00000 devicetree.dtb
u-boot> fatload mmc 0 0x2000000 uramdisk.image.gz
u-boot> bootm 0x3000000 0x2000000 0x2A00000"
but i use it to launch zImage:
"mmcinfo
fatload mmc 0 0x8000 zImage
fatload mmc 0 0x1000000 devicetree_ramdisk.dtb
fatload mmc 0 0x800000 ramdisk8M.image.gz
go 0x8000"
is this the reason why the linux blocked?
and i didn't compile the dts file, because i didn't add any bitstream.i just used the files
"devicetree_ramdisk.dtb
ramdisk8M.image.gz
zImage
"
in the SD card except the BOOT.bin i built myself.