Meta-REDHAWK-SDR is an actively-maintained set of Yocto/Open-Embedded recipes for the REDHAWK SDR framework, its dependencies, GPP, other example Devices, all shared libraries (softpkg), and all but 1 CPP Component (DataConvert requires SSE).
NOTE: The most recent version of Yocto tested with this layer is Rocko, 2.4.1.
This repository, along with the base Yocto framework will enable you to build the REDHAWK SDR framework for any hardware platform in which a Board Support Package is available. We at Geon have successfully used this layer on a variety of Zynq targets including:
- ZC706 Evaluation Board
- ZedBoard
- MicroZed
- Ettus Research E310
- iVeia Atlas-I-Z7e
- Several ZC702 -based designs
Note: Only the presently-tagged version is supported by this repository, however we can support some earlier versions if required. Please contact us through our website if this is a need.
The Yocto website provides a list of Official BSPs which include common hardware platforms like the Raspberry Pi, BeagleBoard, BeagleBone, NUC, Intel Atom, etc.
There are plenty of BSPs floating around for other hardware platforms so do some searching before you write your own.
Use the Pyro branch/version as your starting point for searching since it is the most recent version of Yocto that Geon has actively tested this layer against.
The most straight-forward installation is to use Google's repo and a manifest. Complete instructions and our manifest can be found here. The instructions amount to a handful of terminal commands that setup a known-good build as a starting point.
Alternatively, you can clone this layer into your own Yocto source tree:
cd <your work director where other meta* are loaded>
git clone git://github.com/geontech/meta-redhawk-sdr.git
Then edit your build/conf/bblayers.conf to include a reference to meta-redhawk-sdr at the end of the list. See our meta-redhawk-sdr/conf/bblayers.conf.sample as an example.
Note: The processor architecture is set to
armv7lby default. If you need a different processor architecture, set theREDHAWK_PROCESSORvariable in yourbuild/conf/local.conf.
In the contrib/scripts folder is the build-image.sh script, a derivative of a script from Philip Balister (@balister) of Ettus Research who included it with their meta-sdr. The script uses wic to build a single image file that can be directly copied to an SD card (dd) resulting in the appropriate partitions, etc., based on the associated wks file.
To use it, link this script into your build directory, set it to executable, and specify the BUILD_IMAGE and MACHINE environment variables (e.g., qemuarm and redhawk-gpp-image). Then running this script will go through the whole bitbake process for you, automated.
The scripts/spd_utility has two purposes. The first purpose is to take a cpp Component, SoftPkg, or Device that has a defined x86_64 implementation and create a new implementation matching cpp-REDHAWK_PROCESSOR. The output directory, etc. are all changed to match so that the output product will overwrite the original implementation back at the Domain controller, i.e., the second purpose. The second purpose is to take the output product's SPD and merge it with the Domain's SDRROOT. Together with collecting the ComponentHost package, the Domain will be able to distribute your assets in a multi-architecture Domain. See scripts/spd_utility --help for arguments.
NOTE: If you would like to disable this functionality for your package, include
NO_SPD_PATCH = "1"in the recipe.