Hi Edward,
On Jul 3, 2013, at 11:05 PM, Edward Vidal <[email protected]> wrote:
> Hello,
> I recently built core-image-minimal for zc702.
> This generated a file with a dtb extension that I have not seen before
> uImage--3.8-xilinx+git0+6a0bedad60-r1-zynq-zc702-20130703173428.dtb. Can
> anyone tell me more about the this extension.
The *.dts and *.dtb files are related to the device tree source and binary
formats. When you work with a hardware project using the Xilinx ISE 14.6/Vivado
2013.2 tools, a dts file will be create. This contains the base address and
other parameters for each device peripheral, e.g. serial ports, video
controller, etc.
The yocto build system takes these files and generates the required *.dtb file.
Please refer the Zynq Base TRD 14.6 document, (you can quickly scan through the
document and fast forward to section 8.2, for building a dtb file from a dts
file)
http://www.wiki.xilinx.com/Zynq+Base+TRD+14.6-beta
> Where do you find the boot.scr or uEnv.txt for the zc702? I built this on
> both a CentOS 6.4 and a Fedora18 x86_64 system.
>
> meta-yocto = "(nobranch):04af378874f38d1200bea2fa191beeae94232d6e"
> meta-xilinx
> meta-kc705
> meta-zc702
> meta-zedboard = "(nobranch):b065f091f10060f2bb68b58f1d618e26a966fee2"
> meta-yocto-bsp = "(nobranch):04af378874f38d1200bea2fa191beeae94232d6e"
>
> The latest version of poky that I downloaded
> commit 8a186a6b3853fc1a7dcf342d421c8926c38949c9
> Author: Cristiana Voicu <[email protected]>
> Date: Mon Jul 1 08:09:52 2013 +0000
>
> bitbake: hob: save button from settings called a nonexisting method
>
> The method was removed when the process for saving configuration
> in Hob was changed. Replace the call with the right function.
>
> [YOCTO #4793]
> (Bitbake rev: b6aa2b63d71cbe82850a375381b2dbc750cf1905)
>
> Signed-off-by: Cristiana Voicu <[email protected]>
> Signed-off-by: Richard Purdie <[email protected]>
>
> causes the following error on both CentOS 6.4 and Fedora 18
> . oe-init-build-env
>
> BitBake requires Python 2.7.3 or later
> CentOS 6.4 has a non standard location of python. Does anyone know how to
> tell bitbake of the non standard location of python.
>
> This latest version of poky that I downloaded on fedora18
> causes the following error.
> MACHINE=zc702 bitbake core-image-minimal -vDD
> ERROR: OE-core's config sanity checker detected a potential
> misconfiguration.
> Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
> Following is the list of potential problems / advisories:
>
> Your version of make 3.82 is broken. Please revert to 3.81 or install a
> patched version.
>
> ERROR: Execution of event handler 'check_sanity_eventhandler' failed
>
> This version of poky and meta-xilinx worked okay.
>
> meta
> meta-yocto = "(nobranch):04af378874f38d1200bea2fa191beeae94232d6e"
> meta-xilinx
> meta-kc705
> meta-zc702
> meta-zedboard = "(nobranch):b065f091f10060f2bb68b58f1d618e26a966fee2"
> meta-yocto-bsp = "(nobranch):04af378874f38d1200bea2fa191beeae94232d6e"
>
> MACHINE=zc702 bitbake core-image-minimal -vDD
>
> NOTE: Tasks Summary: Attempted 1530 tasks of which 306 didn't need to be
> rerun and all succeeded.
> We are trying to determine which board to purchase the
> Xilinx Zynq-7000 SoC ZC702 Evaluation Kit
> EK-Z7-ZC702-G
> $895.00 or
> AES-Z7EV-7Z020-G
> ZEDBOARD ZYNQ BOARD
> AES-Z7EV-7Z020-G
> ECCN
> Avnet Design Services - Custom
> $395.00
> Does anyone have any experience with either of these boards?
From a support standpoint, both the ZC702 and Zedboard are supported really
well. You will find that most of the Xilinx reference design and application
notes usually always target the ZC702. If you get a Zedboard you'll need to
take the extra effort to adapt the pin constraints file. Also the ZC702 has two
FMC LPC connectors rather than 1 FMC LPC connector, if that's more important
for you.
My recommendation would be to go in for the ZC702 or the ZC706 if you need more
logic density.
Best regards,
Elvis Dowson
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto