REDHAWK SDR 2.2.1

This release includes:

• Support for REDHAWK SDR 2.2.1
• Large reorganization of code base to facilitate supporting multiple release versions in the branch going forward
• Integration tool in scripts to facilitate producing target SPD implementations and package structures that can be easily installed into non-target Domains (making multi-implementation domains easier)
• Reverting back to pulling individual repositories rather than the super submodule repository to decrease build times by not unpacking it repeatedly.
• The qemuarm64 and redhawk-test-image can now be used to "smoke test" the build environment, as the resulting image will auto-start a stand-alone domain and GPP with all omni services running. Change the omniORB configuration to the runtime IP address and reboot to access the device from the x86 IDE.

NOTE: We're open for a community discussion on what to do with our versioning system once we port-forward 2.0.x back into master so that we have both LTS releases going forward.

REDHAWK SDR 2.1.3

Release adds support for REDHAWK SDR 2.1.3 (pre-release).

REDHAWK 2.0.8 support and Rocko 2.4.1 tested

In this release are:

• Rolled REDHAWK versions to 2.0.8
• Addressed the REDHAWK_PROCESSOR duplication issue by making it global scope. Also added support for automatically mapping the zynqmp (ZCU102) to aarch64.
• Tested the build on a ZCU102 Evaluation Board using Yocto Rocko 2.4.1

REDHAWK v2.0.6 -- Pyro, and More

Important: This release replaces the old -1 and -2 releases which were errors. A silent failure because of a typo in the manifest resulted in a build developed against krogoth, not pyro, as this new tag has been developed against.

REDHAWK 2.0.6, tested on Pyro (Yocto/OE 2.3)

• Added all basic SoftPKGs (new class added, other patches, to re- Fix #7)
• Added most basic Components (CPP)
• Corrected IDL-related packages to fix the python sandbox
• Patched uuid in ossie.utils to use the python package (vs. shell call)
• Patched GPP to account for no 'ps -eo' (thanks @rodrigo455, Fixes #9)
• Patched GPP to remove second node generation
• Added 'redhawk-test-image' which instantiates omni services, domain, and GPP (stand-alone system config)
• Updated all packages to use a new uname-machine recipe which sources the UTS_MACHINE from the built virtual/kernel for a given MACHINE and uses that value in SPDs, etc. to dynamically patch in the expected processor architecture. No more hard-coded arch.
• Patched 'redhawk.m4' autotool script to support redhawk-softpkg better
• Refactored package names to be closer to program-released RPM names
• Added domain init.d script
• Removed redundant patches in favor of config_prepend functions to globally patch things like missing README, NEWS, etc. in the core framework.
• All redhawk repos related to this are now sourced directly from the master repo rather than their separate submodules.

NOTE: Unlike the previous -1 and -2, this release will likely not work with krogoth because of the fftw package naming. If anyone successfully builds this against krogoth, please do let us know, otherwise if you need back-porting of this relase, please submit an issue against the krogoth branch.

REDHAWK v2.0.6 Initial Release

Updated to REDHAWK 2.0.6 sources including USRP_UHD 5.0.

Various other enhancements include XSD 4.0.0 support and use of the common repository.

REDHAWK v2.0.5

Version bump to REDHAWK 2.0.5 as well as a few bug fixes to facilitate building on a host OS that has REDHAWK SDR installed in the typical location as well as corrections for not having the python packages installed by default. Other changes include splitting off the omniorb and omnievents init.d scripts into separate packages (omniorb-init, for example).

Build scripting minor patch

The build script provided in contrib was patched to search for meta-redhawk-sdr in the parent folder. This will allow the old and new (meta-redhawk-sdr-manifests, Poky) filesystem styles to work by linking this same script into your ./build folder. The script facilitates bitbaking and then deploying the build as a single image file describing a dual-partition setup. (Results will still vary based on what BSP you've targeted. For example, Xilinx's BSPs still require you to make U-BOOT environment changes to boot from the SD card with a non-volatile root partition.)

REDHAWK v2.0.4 and Yocto Krogoth support

See #2 for details on this release.