Hi All,

The UHD-4.9.0.0 release is now available.\
This release adds support for the USRP B206mini-i and X3xx compatible \
OBX daughtercard. For a complete list of new features, updates and \
bug fixes see the CHANGELOG (see also below).

Tag for the UHD release:\
[https://github.com/EttusResearch/uhd/releases/tag/v4.9.0.0](https://github.com/EttusResearch/uhd/releases/tag/v4.7.0.0)

Tag for the filesystem release:\
[https://github.com/EttusResearch/meta-ettus/releases/tag/v4.9.0.0](https://github.com/EttusResearch/meta-ettus/releases/tag/v4.7.0.0)

Installers for Windows and Fedora:\
[https://files.ettus.com/binaries/uhd/uhd_004.009.000.000-release](https://files.ettus.com/binaries/uhd/uhd_004.007.000.000-release/4.7.0.0/)

PPA for Ubuntu:\
<https://launchpad.net/\~ettusresearch/+archive/ubuntu/uhd>\
Thank you to everyone who has contributed by posting pull requests and filing 
bug reports.

Thanks,\
Marian Koop

CHANGELOG:

#### **UHD 4.9.0.0**

* Highlights / Main Changes

  * Support for USRP B206mini-i

  * Support for OBX daughterboard

* New Features

  * OBX daughterboard and B206mini support added.

  * X3x0: Add support for the gps_iface feature. This allows sending arbitrary\
    commands to the GPS module.

  * rfnoc_modtool: Add a new subcommand, `make-yaml`, that generates a block\
    YAML file from some user inputs. When calling `rfnoc_modtool add` without\
    a valid block YAML file, the tool will now automatically call `make-yaml` 
to\
    generate a new YAML file.

  * Added support for processing multiple samples per cycle in FFT block.

  * LabVIEW/USRP: New repository containing example applications which\
    demonstrate how to use NI LabVIEW with USRP devices via the UHD APIs.\
    (<https://github.com/ni/labview-usrp-examples>)

  * Improved RFNoC OOT Block support:\
    New repository containing official RFNoC OOT Blocks\
    (<https://github.com/EttusResearch/rfnoc-oot-blocks>)

    * Added new RFNoC Aurora Block for TX and RX remote streaming applications\
      to and from Aurora capable compute nodes like FPGA Coprocessors.

  * Enhanced the UHD Windows installer to automatically install Windows\
    driver packages into the OS, eliminating this manual post-installation\
    step for B-Series USB devices.

* API Changes

  * `uhd::math::gcd` and `uhd::math::lcm` are removed from the public\
    headers. Use `std::gcd` and `std::lcm` instead if C++17 is available,\
    or `boost::math::gcd` and `boost::math::lcm` if not.

  * When calling `recv()` on an RX streamer connected to an RFNoC device, we\
    no longer artificially inflate the timeout value. The old behaviour was\
    in some cases abused to detect overruns, but this is not a reliable method\
    and is now explicitly declared unsupported.

* Bug Fixes

  * RFNoC

    * Calling `recv()` on an RX streamer connected to an RFNoC device with a\
      zero timeout value now correctly returns immediately.

    * rfnoc-gain: Moved the fpga/ subdirectory under rfnoc/. This way, the\
      directory structure inside the OOT module is identical to the directory\
      structure after installation.

  * X410:

    * Fixed NCO reset mechanism that caused ADC self-cal errors to occur during\
      reopening of a UHD session when timed tune commands were previously used.

* Removals / Deprecations

  * Removed tools/uhd_dump. This tool is obsolete, the USRP X3x0 is not even\
    compatible with it any more. Dumps can be recorded and analyzed with 
wireshark\
    and the UHD dissectors in here.

  * Removed network_relay example.

* Validated OS Environments\
  (Versions for build and runtime dependencies can be determined from the\
  docker container definitions in the UHD repository at 
[.ci/docker/...](https://github.com/EttusResearch/uhd/tree/v4.9.0.0-rc2/.ci/docker)))

  * Linux:

    * Ubuntu: focal (20.04), jammy (22.04), noble (24.04), plucky (25.04)

    * Fedora: 40, 41, 42

  * Windows: 10 22H2, 11 23H2

  * MacOS: Sequoia (15.2)
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to