| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Initially the threshold was suitable for the cal tone at the original
frequency of 100 MHz. Since this was changed and because it can be
configured via the cal_freq parameter anyway we need to take care to
allow lower input levels that we might have at different frequencies.
In addition we know that for the background calibration of the chip a
signal of >=-46 dBm is required, so by using -20 dBm (which corresponds
to the 14-bit dbFS value of 1465) we still have some margin to recognize
any broken components.
|
|
|
|
|
|
|
|
|
|
| |
Modify the cal_freq used in the calibration procedure by X440 devices
which use the FBX daughterboard. The new value obeys the rules that are
specified mainly in the PG269 to help the background calibration (BG)
run under better conditions and hence improve our input spur performance.
Signed-off-by: Virendra Kakade <virendra.kakade@ni.com>
Co-authored-by: Volkan Öz <volkan.oez@ni.com>
|
|
|
|
| |
Windows systems will fails due to not having bash
|
|
|
|
| |
set_clock_source for x440 now errors due to potentially decreased spurious performance, the correct way to change clock source now with a new device initialization
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Move pop_host_tasks function call from just x4xx to all MPM devices so it can be safely called from mpmd_mboard_impl
|
|
|
|
|
|
|
|
| |
Replaced newly added paragraph with subsubsection elements that resulted into
an as warning declared build error when buildin on readthedocs.
The build service still uses doxygen 1.8.13, which failed to include content
into the generated html after the warning was reported. Newer version of
doxygen also report the warning/s but continue including content.
|
| |
|
|
|
|
|
|
|
| |
- Updated version string
- Updated CHANGELOG
- Updated Debian-related files
- Updated manifest
|
|
|
|
|
| |
Added short paragraph to daughterboards page and linked in
FBX subpage from USRP X4x0 Series pages.
|
|
|
|
|
|
|
|
|
|
|
| |
- Extended FPGA Image Flavors sections
- Extended MCR and Converter Rates section
- Added Page for FBX daughterboard
- Added FBX_simplified_blockdiagram.png that is referenced by
FBX daughterboard page and represents one transceiver chain.
- Added known issue regarding need for restarting MPM when mcr is
changed and potential of dynamic QSFP28 configurations may getting
lost.
|
|
|
|
|
|
|
|
| |
Change all references to "gps_lock" to "gps_locked" for consistency
across the code base. Fixes incorrect use of "gps_lock" for the sensor
name on X4xx.
Signed-off-by: michael-west <michael.west@ettus.com>
|
| |
|
|
|
|
|
|
| |
- Add section on X4x0 devices, explaining that X440 has 2 timekeepers
- Expand docs on mb_controller::timekeeper
- Provide more context on multi_usrp time-related calls
|
| |
|
| |
|
|
|
|
| |
There is an updated msgpack rpc python package that builds off the previous one for users requiring tornado version >= 6
|
| |
|
| |
|
|
|
|
|
|
| |
Vitis HLS uses its own version of clang that's different from what's
used by UHD. This change clears the clang-format settings for FPGA
code to be compatible with Vitis.
|
| |
|
| |
|
|
|
|
|
| |
- Used clang-format version 14
- Ran ./tools/clang-formatter.sh apply
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds two tools to the ./tools/ subdirectory:
== clang-formatter.sh ==
This is simply a small shell script that can be executed from the top of
the UHD repository, and it will format all files according the the
.clang-format file. It can be executed as such:
$ CLANG_FORMAT=clang-format-14 ./tools/clang-formatter.sh apply
Specifying a clang-format executable is optional, but note that
clang-format 14.0 should be used.
== run-clang-format.py ==
This is a Python script that is a modified version from
https://github.com/gnuradio/clang-format-lint-action/blob/ \
0b0cb14cf220a070d2a8b2610bd74ad1546252a1/run-clang-format.py
It was modified to add --patch-file option.
Alongside this file is a .clang-format-ignore file, which is sourced
from this script. The command can be run as such:
$ ./tools/run-clang-format.py \
--clang-format-executable clang-format-14 \
--extensions c,cpp,h,hpp,hpp.in,ipp \
-r \
--patch-file format.patch \
/path/to/uhd-repo
It will provide both a nice output summary as well as a patch file that
can be consumed with `patch -p0 < format.patch`.
|
|
|
|
|
|
|
|
|
| |
Some files in the source tree need some treatment before clang-format
can automatically be applied to all files.
This commit adds some 'clang-format off' statements and some manual
pre-formatting in order to not cause havoc when clang-format is applied
to the entire source tree.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was done by running clang-format-14 --dump-config -style:file in
the UHD source tree, and use the output to update .clang-format. Some of
the newer options were then hand-modified to more closely match the
coding standard of UHD.
Note that this new config file is not compatible with older versions of
clang-format, so clang-format 14.0 is the minimum.
Also, due to the nature of clang-format, there is a possibility that
newer versions of clang-format will produce different output.
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: michael-west <michael.west@ettus.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes issues caused by e22a2a7395d10f795f5938724ce8aed5424d3ce8.
That commit tried to consolidate the selection of the endpoint based on branch name
in a single shared location. But due to the order that azure pipelines evaluates
things, the endpoints were being authenticated before the stage variables
were evaluated.
From azure docs:
"Resources are authorized before a stage can start running,
so stage- and job-level variables aren't available. Pipeline-level
variables can be used, but only those variables explicitly included in the pipeline."
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
disable test because of stream rate limitations for the 1GbE port
|
| |
|