# Bitbake GNU radio for Zynq **URL:** \ **Category:** GNU Radio\ **Created:** [May 4, 2015, 4:21am UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818 "2015-05-04T04:21:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\ **Post date:** [May 4, 2015, 4:21am UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818/1 "2015-05-04T04:21:49Z")
Hi, I’m a trying to compile GNU radio for Zynq using the example described here: [https://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq](https://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq) The instructions do have an out of date warning, and I’m just trying to figure out what things to update. From another list posting, there are instructions to checkout the dizzy branch instead of stable in the following line: $ git clone git://github.com/balister/oe-gnuradio-manifest.git -b stable When I reach the bitbake step: $ bitbake gnuradio-dev-image It first fails due a missing meta-python layer. That’s easily solved by modifying the bblayers.conf file to include meta-python. After that, I get the following error: ERROR: ParseError at /home/jeff/Desktop/gnu/oe-repo/oe-core/…/meta-xilinx/recipes-core/meta/external-xilinx-toolchain.bb:1: Could not include required file recipes-core/eglibc/eglibc-package.inc I cannot find any eglibc-package.inc in the file system. Any ideas? Any help would be greatly appreciated! Sorry, I’m a complete GNU radio beginner! Thanks, Jeff ---
**Author:** ![Jeff\_Tu](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/67e7ee/32.png) [@Jeff\_Tu](https://www.ruby-forum.com/u/Jeff_Tu)\ **Post date:** [May 4, 2015, 12:13pm UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818/2 "2015-05-04T12:13:15Z")
Hi Jeff, I think is worth checking that you are using the same branch (dizzy) in all the beta layers that you have. Including openembedded, yocto, meta-sdr… The reason why you were missing meta-python could be that your openembedded layer is newer than the meta-sdr used to create the bblayers.conf file. I would suggest that you try checking out the branch that you want instead of the latest stable one. Cheers, Murray 2015-05-04 3:20 GMT+01:00 Jeff Tu [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): ---
**Author:** ![Jeff\_Tu](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/67e7ee/32.png) [@Jeff\_Tu](https://www.ruby-forum.com/u/Jeff_Tu)\ **Post date:** [May 4, 2015, 4:01pm UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818/3 "2015-05-04T16:01:05Z")
On 05/04/2015 06:11 AM, Murray T. wrote: > Hi Jeff, > > I think is worth checking that you are using the same branch (dizzy) in all > the beta layers that you have. Including openembedded, yocto, meta-sdr… > The reason why you were missing meta-python could be that your openembedded > layer is newer than the meta-sdr used to create the bblayers.conf file. I > would suggest that you try checking out the branch that you want instead of > the latest stable one. Use: $ git clone git://github.com/balister/oe-gnuradio-manifest.git -b dizzy I need to update the manifest and delete “stable” 🙂 Philip ---
**Author:** ![Jeff\_Tu](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/67e7ee/32.png) [@Jeff\_Tu](https://www.ruby-forum.com/u/Jeff_Tu)\ **Post date:** [May 4, 2015, 10:26pm UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818/4 "2015-05-04T22:26:41Z")
Jeff, It looks like eglibc was at some point before dizzy renamed to glibc. daisy: poky/meta/recipes-core/eglibc/eglibc-package.inc dizzy: poky/meta/recipes-core/glibc/glibc-package.inc Recipes from dizzy shouldn’t depend on eglibc. The xilinx layer seems to have change this [https://lists.yoctoproject.org/pipermail/meta-xilinx/2014-September/000751.html](https://lists.yoctoproject.org/pipermail/meta-xilinx/2014-September/000751.html) If you are sure that all your layers are using dizzy and still asks for eglibc, you may get better luck with another branch. It would be interesting to see if you can build a minimal console image. If you can, take a look at the first part of the log printed in the console, it will tell you the branch that the layers are using. Regards, Murray 2015-05-04 17:17 GMT+01:00 Jeff Tu [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): ---
**Author:** ![Jeff\_Tu](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/67e7ee/32.png) [@Jeff\_Tu](https://www.ruby-forum.com/u/Jeff_Tu)\ **Post date:** [May 4, 2015, 6:18pm UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818/5 "2015-05-04T18:18:23Z")
Hi Philip and Murray, Thanks for your help. I mentioned that I was actually working off the dizzy branch. I also went through all the branches available for the meta-xilinx repo and could not find the file: ERROR: ParseError at /home/jeff/Desktop/gnu/oe-repo/oe-core/../meta-xilinx/recipes-core/meta/external-xilinx-toolchain.bb:1: Could not include required file recipes-core/eglibc/eglibc-package.inc Also as a note I’m running on Ubuntu 12.04. Thanks again! Jeff ----- Original Message ----- From: “Philip B.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) To: “Murray T.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid), “Jeff Tu” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Cc: “GNURadio D.ion List” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Sent: Monday, May 4, 2015 6:59:51 AM Subject: Re: [Discuss-gnuradio] Bitbake GNU radio for Zynq On 05/04/2015 06:11 AM, Murray T. wrote: > Hi Jeff, > > I think is worth checking that you are using the same branch (dizzy) in all > the beta layers that you have. Including openembedded, yocto, meta-sdr… > The reason why you were missing meta-python could be that your openembedded > layer is newer than the meta-sdr used to create the bblayers.conf file. I > would suggest that you try checking out the branch that you want instead of > the latest stable one. Use: $ git clone git://github.com/balister/oe-gnuradio-manifest.git -b dizzy I need to update the manifest and delete “stable” 🙂 Philip ---
**Author:** ![Jeff\_Tu](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/67e7ee/32.png) [@Jeff\_Tu](https://www.ruby-forum.com/u/Jeff_Tu)\ **Post date:** [May 5, 2015, 11:42pm UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818/6 "2015-05-05T23:42:39Z")
Hi Guys, Thanks for the help. I can build the kernel and run it on a Zedboard using the dizzy branch exclusively. The additional step of using the zynq-gnuradio-manifest repo to try to include the FIR example is what broke things. That repo manifest replaces the meta-xilinx layer with an older one. My plan was to try out the zynq-fir-filter-example, but I think I’ll just use it as a reference for now. Thanks! Jeff ----- Original Message ----- From: “Murray T.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) To: “Jeff Tu” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Cc: “Philip B.” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid), “GNURadio D.ion List” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Sent: Monday, May 4, 2015 1:25:13 PM Subject: Re: [Discuss-gnuradio] Bitbake GNU radio for Zynq Jeff, It looks like eglibc was at some point before dizzy renamed to glibc. daisy: poky/meta/recipes-core/eglibc/eglibc-package.inc dizzy: poky/meta/recipes-core/glibc/glibc-package.inc Recipes from dizzy shouldn’t depend on eglibc. The xilinx layer seems to have change this [https://lists.yoctoproject.org/pipermail/meta-xilinx/2014-September/000751.html](https://lists.yoctoproject.org/pipermail/meta-xilinx/2014-September/000751.html) If you are sure that all your layers are using dizzy and still asks for eglibc, you may get better luck with another branch. It would be interesting to see if you can build a minimal console image. If you can, take a look at the first part of the log printed in the console, it will tell you the branch that the layers are using. Regards, Murray 2015-05-04 17:17 GMT+01:00 Jeff Tu [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): ---
**Author:** ![Jeff\_Tu](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/67e7ee/32.png) [@Jeff\_Tu](https://www.ruby-forum.com/u/Jeff_Tu)\ **Post date:** [May 6, 2015, 6:49pm UTC](https://www.ruby-forum.com/t/bitbake-gnu-radio-for-zynq/241818/7 "2015-05-06T18:49:23Z")
On 05/05/2015 05:41 PM, Jeff Tu wrote: > Hi Guys, > > Thanks for the help. I can build the kernel and run it on a Zedboard using the > dizzy branch exclusively. The additional step of using the zynq-gnuradio-manifest > repo to try to include the FIR example is what broke things. That repo manifest > replaces the meta-xilinx layer with an older one. My plan was to try out the > zynq-fir-filter-example, but I think I’ll just use it as a reference for now. > Thanks! I would be really nice to update the Zynq FIR ACP co-processor to work with recent builds. Bonus point for integrating with Alfredo’s work on using GNU Radio buffers without the copy (and without magical allocators). [1] Philip [1] [http://gnuradio.org/redmine/projects/gnuradio/wiki/Keystone2](http://gnuradio.org/redmine/projects/gnuradio/wiki/Keystone2)