| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
We don't need to assert error if there are not enough fifo ports to connect
to radio. Radio ports still can be connected to all available fifo ports until they're running
out.
|
|
|
|
|
|
| |
The selection of frontend modes (AB, A, B, BA) is now enabled on X3x0.
Unlike older USRPs, switching the frontend is done through the antenna
API (e.g., usrp->set_rx_antenna("A")).
|
| |
|
|
|
|
|
|
|
|
| |
- Removal of some Boostisms
- Proper use of lambdas
- Replace magic constants with constexpr's
No functional changes.
|
|
|
|
|
|
| |
- Internal clock/time references
- External clock/time references
- White Rabbit-based clock/time references
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are cases when the first sample after an overrun has an earlier
timestamp than the timestamp of the error package. In this case,
benchmark_rate would incorrectly determine the number of dropped
samples, causing it to display a very large number.
This is not a fix of the negative offset issue, but will avoid
displaying overly pessimistic numbers dropped samples.
An error message is still displayed when this happens, which aids in
debugging this situation.
|
|
|
|
|
|
| |
The main thread sleeps while the receiver and transmitter threads are
going on. This fixes the calculated time it takes in single-channel
scenarios.
|
|
|
|
|
|
|
|
|
|
|
| |
When too many overruns, underruns, or dropped packets are detected,
benchmark_rate will now return EXIT_FAILURE. This allows to use it for
automated tests.
The thresholds are set very high by default, but can be manually tuned
by using new command line arguments:
$ benchmark_rate --overrun-threshold 0 # Fail on any number of Os
|
|
|
|
|
|
|
| |
Replaced with initialization lists.
Note: uhd::dict does not work with initializer lists without making
changes to said data structure. This commit has no functional changes,
so keeping the boost::assigns for uhd::dict.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In MPM devices, daughterboard EEPROMs now use eeprom_map_t instead of
dboard_eeprom_t. The eeprom also is under rfnoc path.
This change will allow ?x_info() to reach that rfnoc path and pull
information from the new eeprom_map_t.
|
|
|
|
| |
Replace with std::this_thread::sleep_for().
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We need a separate RPC connection for the claim loop such that it is not
blocked by other long executions of rpc calls.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Allows full bandwidth range to user.
Reviewed-by: Michael West <michael.west@ettus.com>
Reviewed-by: Martin Braun <martin.braun@ettus.com>
|
|
|
|
|
|
| |
- Fixes an issue with compile time disabling as well
- An UHD_LOG_FASTPATH_DISABLE=1 env var will make it that O/U/S/D won't
be printed
|
| |
|
|
|
|
|
|
|
| |
- Remove all use of boost::bind and boost::function
- Demote some log messages to DEBUG
- Change some formatting to match coding guidelines
- B2xx/E310: Match changes in loopback function
|
| |
|
| |
|
|
|
|
| |
This was replaced with the manifest.
|
|
|
|
|
| |
Removes boost::bind and all Boost time types from this example.
Re-enables compatibility with Boost 1.67.
|
|
|
|
| |
Need to skip zero gain step
|
|
|
|
|
| |
For every frequency point, the cal utils will detect underruns and retry
a calibration measurement up to 10 times before failing.
|
| |
|
|
|
|
|
| |
Some uses of boost::posix_time were incorrect and would cause compiler
errors on Boost 1.67.
|
|
|
|
| |
This avoids having to redeclare the static const to avoid linker errors.
|
|
|
|
| |
Use std::this_thread::sleep_for() instead.
|
|
|
|
| |
Use std::this_thread::sleep_for() instead.
|
|
|
|
| |
Use std::this_thread::sleep_for() instead.
|
|
|
|
|
|
| |
Static const attributes were causing linker issues the way there were
being used, but they were only used in niusrprio_session.cpp and thus
could be factored out.
|
| |
|
|
|
|
|
| |
The bit shift for power down is one off with respect to the
ADF4001/ADF4002 data sheet
|
| |
|
|
|
|
|
|
|
|
|
| |
- Fixes: cmake -DUHD_LOG_FILE wasn't respected
- Fixes: UHD_LOG_FILE and UHD_FILE_LOG_LEVEL had to both be set for
either to take effect
- Fixes: Use of unnecessary boost::make_shared<>
- Also factored out setting up console- and file logger into their own
locations in an attempt to improve readability
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The previous 0.1s fill time occasionally prevented rx from starting on time when
settling is set to the same 0.1s time. It was increased to 0.5s.
|
| |
|