Hi Vipin - To get performance counters, you have to rebuild GNU Radio
and enable them specifically via the cmake command addition
"-DENABLE_PERFORMANCE_COUNTERS=ON". Make sure to review the output of
the cmake command to verify that they have been enabled, then once
you're satisfied do the usual
Hello M S Sumi,
The GNU Radio tutorials are a great place to gain an understanding of doing
digital signal processing without hardware connected and then the later
tutorial covers the use of hardware to see actual RF signals.
https://wiki.gnuradio.org/index.php/Guided_Tutorials
Regards,
Derek
Thanks, I'll check it out.
On 30-Oct-2017 16:36, "Derek Kozel" wrote:
> Hello M S Sumi,
>
> The GNU Radio tutorials are a great place to gain an understanding of
> doing digital signal processing without hardware connected and then the
> later tutorial covers the use of
Hi all,
I think the question is all in the subject, but basically, I'm having
trouble with using several USRPs. I think it may be an issue with UHD, or
at least I need to verify it isn't. Does pybombs have a command to install
older releases or specific branch tags from git?
Thanks,
Rich
Thanks for the tip!
I will try htop first and then rebuild if necessary.
On Mon, Oct 30, 2017 at 5:29 AM Michael Dickens
wrote:
> Hi Vipin - To get performance counters, you have to rebuild GNU Radio
> and enable them specifically via the cmake command addition
>
There is also the Linux tool `perf`. I use that instead of the GNU Radio
tools due to library compatibility issues (also thrift is a pita to get
working with GNU Radio in my experience). An example is: `perf top -p
--call-graph=fp` (use sudo if needed). If you want to see everything
you can
You can look at usrp_spectrum_sense script. This sweeps a specified frequency
range, does an FFT, and outputs one line for every bin where the magnitude
exceeds a specified limit.
You could modify it to just write the samples to a file/pipe like uhd_rx_cfile.
--Patrick
I’ve noticed the same on our buildbot setup (and wanted to address this for
a while). `qa_packet_format` is another candidate which seems to randomly
fail. Also compiling on buildbot seems to fail sometimes randomly because
of `M_SQRT2` or `M_LOG2E` undeclared errors.
So, Kevin, without having a
> Generating: '/maint/scripts/top_block.py'
>
> Executing:
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
> -u /maint/scripts/top_block.py
>
> Mac OS; Clang version 8.1.0 (clang-802.0.42); Boost_105900;
>
You can even specify a git revision, by doing something like
$ pybombs -p config --package uhd gitrev release_003_009_006
Then, if you do pybombs rebuild (without the -k), it'll update your git
source. (At least it should -- typing this out from memory).
-- M
On 10/30/2017 03:34 PM, Nicolas
What have I missed ?
sudo port install gnuradio
sudo port install airspy
sudo port install rtl-sdr
sudo port install gr-osmosdr
sudo port install gqrx
sudo port install gqrx-devel
sudo port install libusb
sudo port install libusb-devel
sudo port install hackrf
sudo port install hackrf-devel
Hello,
We have been trying to compile and run GNURadio from source and the make
tests have been failing randomly.
*Machine Details*
*Intel NUC (x86-64 machine)*
*Ubuntu 16.04.03*
*GNU Radio version 3.7.11*
*gcc version 5.4.0 20160609 *
*Commands used*
*git clone --recursive
Hello Richard,
I believe the best way (so far) would be to actually go to the repository
that you want to rebuild and checkout to the different specific branch/tag
and then trigger the rebuild with
$ pybombs -p *your_prefix* rebuild *uhd*
You can rebuild faster by adding the '-k' flag at
13 matches
Mail list logo