GRC flowgraph examples using bladeRF

[Arlee]

Can anyone post some GRC flowgraph examples using the blade as an osmocom source and one of the instrumentation displays? I thought I'd seen someone do this but cannot locate it now.

Thanks!

Arlee

[drmpeg]

Like so.



Ron

[Arlee]

Thanks for the reply Ron. This is the same flowgraph I constructed in GRC, yet I'm getting a sequence of "O"'s, as shown below;

OOOOOOOOOOOOOOOOOOOO

and then "Done", which I understand to represent a buffer overflow. No display (fft or waterfall) is ever shown. This is through a usb 3.0 connection (short cable), on an Athlon 64 X2 dual core processor machine, running Ubuntu 13.10. So, what gives?

Arlee

[Arlee]

I should add that I tried this "osmocom_fft -a bladerf=0,fpga=/home/lee/Downloads/hostedx115.rbf -s 8000000 -f 446000000" from a terminal and got the error shown below. The osmocom spectrum browser window did launch, but nothing was displayed.

Arlee

osmocom_fft -a bladerf=0,fpga=/home/lee/Downloads/hostedx115.rbf -s 8000000 -f 446000000
linux; GNU C++ version 4.8.1; Boost_105300; UHD_003.005.004-162-g3c7484f9

gr-osmosdr v0.1.0-44-g0d10f5e9 (0.1.1git) gnuradio 3.7.2
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0
[bladeRF source] FPGA is already loaded. Set fpga-reload=1 to force a reload.
[bladeRF source] Using nuand LLC bladeRF #0 SN 4b9efc642b96c669991b7ab58cd4766e FW v1.5.3 FPGA v0.0.0
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOUsing Volk machine: sse3_32_orc
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO*** Error in `/usr/bin/python2': corrupted double-linked list: 0x0bc581f8 ***

[fperal]

Im testing and I can see the spectrum browser



With



I'm using a version of etthus sdr usb stick image wich I've modified to use it in a Vmware machine and added support for NI-USRP-2920 and RTL2832.

I get some OOOOO too.

I'm going to try with GRC


regards

[fperal]

With GRC it also works




Is shows some OOOOOO but only at first moments, if I let it continue adquiring signal there are no more OOO.



regards

[Arlee]

Continuing the discussion of the odd behavior I'm seeing - I was working with jynik on #bladeRF IRC and I used valgrind to help see what was going on, like this;

valgrind osmocom_fft -a bladerf=0 -s 2M -f 446M 2>&1 | tee valgrind.log

With this command, I was able to see the osmocom fft display, and while sluggish with valgrind operating, it did work and respond to clicks on the display buttons. However, if I ran this without valgrind,

osmocom_fft -a bladerf=0 -s 2M -f 446M

I get nothing but "O"'s in the terminal window and the fft display never launches. Trying a simple source/sink flowgraph in GRC also doesn't display anything - no crashes - but I have this in the code window;

Using Volk machine: sse3_32_orc
gr-osmosdr v0.1.0-44-g0d10f5e9 (0.1.1git) gnuradio 3.7.2
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0
[bladeRF source] Using nuand LLC bladeRF #0 SN 4b9efc642b96c669991b7ab58cd4766e FW v1.5.3 FPGA v0.0.0

>>> Done

Arlee

[Arlee]

Following-up with an update on my issues.

I uninstalled and then reinstalled gnuradio, followed by gr-osmosdr. I verified grc worked before installing gr-osmosdr. However, osmocom_fft still does not function and I'm seeing the errors I saw before about "Error in /usr/bin/python2': malloc() memory corruption".

I examined the messages from the gr-osmosdr build, and saw this;

-- checking for module 'gnuradio-fcdproplus'
-- package 'gnuradio-fcdproplus' not found
-- gnuradio-fcdproplus not found.
-- Could NOT find GNURADIO_FCDPP (missing: GNURADIO_FCDPP_LIBRARIES GNURADIO_FCDPP_INCLUDE_DIRS)
-- checking for module 'libosmosdr'
-- package 'libosmosdr' not found
-- libosmosdr not found.

It *appears* to build correctly - thus;

-- ######################################################
-- # gr-osmosdr enabled components
-- ######################################################
-- * Python support
-- * Osmocom IQ Imbalance Correction
-- * FUNcube Dongle
-- * IQ File Source
-- * Osmocom RTLSDR
-- * RTLSDR TCP Client
-- * Ettus USRP Devices
-- * HackRF Jawbreaker
-- * nuand bladeRF
-- * RFSPACE NetSDR
--
-- ######################################################
-- # gr-osmosdr disabled components
-- ######################################################
-- * sysmocom OsmoSDR
-- * FUNcube Dongle Pro+
-- * Osmocom MiriSDR
--
-- Building for version: v0.1.0-44-g0d10f5e9 / 0.1.1git
-- Using install prefix: /opt/gnuradio-3.7.1git
-- Configuring done
-- Generating done
-- Build files have been written to: /home/lee/sandbox/gnuradio-builds/gr-osmosdr/build

But osmocom still does not function. Any suggestions?

Arlee

[Arlee]

Here's the output from this - G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log osmocom_fft -a bladerf=0 -s 2M -f 1G

Arlee

http://pastebin.com/xemx3hU7