| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- In general, some comments to clarify the dependencies installation and building process for windows users.
- Add a comment to the required packages for MSCV.
- Provide instructions to install Python requirements.
- Add the instructions of NSIS installation.
- Add comments to the version match between different installers.
- Clarify the instructions of building process using Cmake
- Add a subsection to show how a binary UHD installer can be obtained.
- Correct the URL of Doxygen.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Image name to be provided to bitbake command are named 'developer-image' and 'deployment-image'
i.e. with dash, not with underscore
|
| |
|
|
|
|
| |
The link to the MPM page in the DPDK docs was incorrectly named. This
change links to the correct page name.
|
|
|
|
| |
Fixes issue where Doxygen doesn't recognize a block within N3XX's Salt
subsection as code.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This adds some info about what is happening in the dpdk_zero_copy
transport, especially the fact that there are threads spun off that take
over CPUs.
|
|
|
|
| |
Co-authored-by: Alex Williams <alex.williams@ni.com>
|
|
|
|
|
|
|
| |
Since the N32* is part of the N3XX family, it shares a page with
N300/N310.
Co-authored-by: Mark Meserve <mark.meserve@ni.com>
|
|
|
|
|
|
| |
The TwinRX dboards only support a master clock rate of 200 MHz, which is
now emphasized in the manual. In addition, the meaning of tick rate,
sampling rate, and master clock rate in the TwinRX context is explained.
|
| |
|
|
|
|
|
| |
Adding documentation explaining where the Python API releases the
Python GIL, and what that means for users.
|
|
|
|
| |
The sample rates and the interpolation/decimation limits didn't match.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also updates our coding style file.
Ancient CMake versions required upper-case commands. Later command
names became case-insensitive. Now the preferred style is lower-case.
Run the following shell code (with GNU compliant sed):
cmake --help-command-list | grep -v "cmake version" | while read c; do
echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g'
done > convert.sed \
&& git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' \
'*CMakeLists.txt' | xargs -0 gsed -i -f convert.sed && rm convert.sed
(Make sure the backslashes don't get mangled!)
|
| |
|
| |
|
|
|
|
|
|
| |
- Added more detail on how to use White Rabbit
- Highlight the options with external clock source (with or without
external time source)
|
| |
|
|
|
|
|
|
|
| |
The synchronization source for the N210 MIMO phase alignment needs to
be set to anything other than 'pps' or 'auto' (which is actually
'pps'). 'default' skips the call to `set_time_unknown_pps`, which is
the proper way to synchronize in this sitation.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The C/C++ standards don't define what time_t is, only that it is
arithmetic (and real for C11, and integral for C++). It should not be
used in portable software and is only used as the return value for some
libc calls.
A common definition for time_t is int64_t, so we'll switch to that
permanently in our own APIs. System APIs will of course stick with
time_t.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
You can now change the time/clock source default through device args:
auto usrp = uhd::usrp::multi_usrp::make(
"type=x300,clock_source=external,time_source=external");
This also enables the use of config files for the clock/time source
implicitly.
|
|
|
|
| |
clock_source call
|
|
|
|
|
| |
Adding section in the manual on how to build filesystems and SD card
images.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Specify skip_boot_init=1 to not init during boot. This will increase
boot time for an N310, typically by around 15 seconds.
|
|
|
|
|
|
|
|
|
|
| |
When a device is re-initialized without any changes (e.g.,
master_clock_rate, ref_clock_freq) then we can skip the initialization
sequence and move on. This shaves a significant amount of time from the
init sequence.
Fast re-init can be overridden by providing the `force_reinit=1` device
arg.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Separating exposed Python data structures into logical sections
- Exposes all of the multi_usrp API
- Adds a layer of Python for documentation and adding helper methods
- Adds improvements and fixes to the MultiUSRP object
- Includes additional exposed data structures (like time_spec_t, etc.)
- Add code to release the Python GIL during long C++ calls
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fix typos and reflect updated procedure used with v3.12.0.0-rc1.
|