Hello,
When I use heatmap.py with output from rtl_power I get regularly spaced
vertical lines that do not appear to be related to any signal. They
look they like repeat at the dongle bandwidth (2048000Hz in this case).
The crop option for rtl_power reduces the presence but I am not sure f
that is intended by that option. Even at -c of 70% they are still there
(see attachment).
Is this because of small bin width? If I use a larger bin (32k) they
are still there. In this case there is no frequency legend along top so
can't compare if they happen more often.
Are these lines to be expected?
John
Hi there,
In debian, sdrangelove is having some build issues on mipsel [0].
At first, there was an issue regarding the '-msse2' switch.
If I delete the switch, then another build error happens:
======== 8< ========
[...]
[ 21%] Building CXX object CMakeFiles/sdrbase.dir/sdrbase/dsp/interpolator.cpp.o
/usr/bin/c++ -DQT_CORE_LIB -DQT_GUI_LIB -DQT_MULTIMEDIA_LIB
-DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB
-DUSE_FFTW -Dsdrangelove_EXPORTS -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG
-fPIC -isystem /usr/include/mipsel-linux-gnu/qt5 -isystem
/usr/include/mipsel-linux-gnu/qt5/QtCore -isystem
/usr/lib/mipsel-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/mipsel-linux-gnu/qt5/QtWidgets -isystem
/usr/include/mipsel-linux-gnu/qt5/QtGui -isystem
/usr/include/mipsel-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/mipsel-linux-gnu/qt5/QtMultimedia -isystem
/usr/include/mipsel-linux-gnu/qt5/QtNetwork
-I/tmp/buildd/sdrangelove-0.0.1.20140824/obj-mipsel-linux-gnu
-I/tmp/buildd/sdrangelove-0.0.1.20140824/include
-I/tmp/buildd/sdrangelove-0.0.1.20140824/include-gpl -fPIC -o
CMakeFiles/sdrbase.dir/sdrbase/dsp/interpolator.cpp.o -c
/tmp/buildd/sdrangelove-0.0.1.20140824/sdrbase/dsp/interpolator.cpp
In file included from
/tmp/buildd/sdrangelove-0.0.1.20140824/sdrbase/dsp/interpolator.cpp:4:0:
/tmp/buildd/sdrangelove-0.0.1.20140824/include-gpl/dsp/interpolator.h:4:23:
fatal error: immintrin.h: No such file or directory
#include <immintrin.h>
^
compilation terminated.
[...]
======== 8< ========
Do you have any hint for this?
Thanks, best regards.
PS: Please keep me in CC, i'm not subscribed.
[0] https://buildd.debian.org/status/fetch.php?pkg=sdrangelove&arch=mipsel&ver=…
--
Arturo Borrero González
Hello all,
I had a problem building gr-osmosdr a few days ago (it was looking in
/usr/lib64/lib64), which I worked around by symlinking a couple of files to
where they were being looked for.
However, since an update of boost yesterday, I now get an error complaining
about a boost file I don't have on my system.
"/usr/lib64/lib64/libboost_date_time-d.a"
Any ideas what's going wrong here?
Centos 6.6
Previous boost version: 1.41.0-25
New boost version: 1.41.0-27
$ git clone git://git.osmocom.org/gr-osmosdr
Initialized empty Git repository in /home/calum/src/gr-osmosdr/.git/
remote: Counting objects: 3818, done.
remote: Compressing objects: 100% (2510/2510), done.
remote: Total 3818 (delta 2736), reused 1888 (delta 1270)
Receiving objects: 100% (3818/3818), 926.14 KiB | 1.13 MiB/s, done.
Resolving deltas: 100% (2736/2736), done.
$ cd gr-osmosdr
$ mkdir build ; cd build
$ cmake ..
-- The CXX compiler identification is GNU 4.4.7
-- The C compiler identification is GNU 4.4.7
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Build type not specified: defaulting to release.
-- Found Git: /usr/bin/git (found version "1.7.1")
-- Extracting version information from git describe...
-- Configuring Boost C++ Libraries...
CMake Error at /usr/lib64/boost/Boost.cmake:536 (message):
The imported target "boost_date_time-static-debug" references the file
"/usr/lib64/lib64/libboost_date_time-d.a"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/lib64/boost/Boost.cmake"
but not all the files it references.
Call Stack (most recent call first):
/usr/lib64/boost/BoostConfig.cmake:28 (include)
/usr/share/cmake/Modules/FindBoost.cmake:177 (find_package)
CMakeLists.txt:122 (find_package)
-- Configuring incomplete, errors occurred!
See also "/home/calum/src/gr-osmosdr/build/CMakeFiles/CMakeOutput.log".
$
Hello!
Long story short: hackrf sink code to convert from GR complex to hackrf 8-bit format fails by generating wrong bits on ARM when I do TX on Raspberry PI 2 .
Evil hides here:
lib/hackrf/hackrf_sink_c.cc
outbuf[i] = inbuf[i]*127;
Since on ARM GCC treats all "char" as unsigned(this is chosen implementation) it generates wrong bits, so my advice is to compile on ARM gr-osmocom with flag -fsigned-char. This is probably most effective way to solve this, it solved my TX problems.
Hi there,
I am having trouble building latest version of gr-osmosdr on my Mac. I am
having identical issue with homebrew version (from chleggett tap) as with
cloning from http://git.osmocom.org/gr-osmosdr/. `make` step always fails
with linker error
Undefined symbols for architecture x86_64:
"_rtlsdr_get_index_by_serial", referenced from:
rtl_source_c::rtl_source_c(std::__1::basic_string<char,
std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
rtl_source_c.cc.o
"_rtlsdr_set_agc_mode", referenced from:
rtl_source_c::rtl_source_c(std::__1::basic_string<char,
std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
rtl_source_c.cc.o
rtl_source_c::set_gain_mode(bool, unsigned long) in rtl_source_c.cc.o
non-virtual thunk to rtl_source_c::set_gain_mode(bool, unsigned long)
in rtl_source_c.cc.o
"_rtlsdr_set_direct_sampling", referenced from:
rtl_source_c::rtl_source_c(std::__1::basic_string<char,
std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
rtl_source_c.cc.o
"_rtlsdr_set_offset_tuning", referenced from:
rtl_source_c::rtl_source_c(std::__1::basic_string<char,
std::__1::char_traits<char>, std::__1::allocator<char> > const&) in
rtl_source_c.cc.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
make[2]: *** [lib/libgnuradio-osmosdr.0.1.5git.dylib] Error 1
make[1]: *** [lib/CMakeFiles/gnuradio-osmosdr.dir/all] Error 2
make: *** [all] Error 2
Trying to add -DCMAKE_CXX_FLAGS=-libstd=libstdc++ only results in even more
undefined symbols on top of these. I'm not sure where to proceed from here.
This is my first post to this list, so hello everyone! and Thanks for any
help.
Nils
Hey Nikolay,
Yes, that's what I thought although I'm not familiar enough with cmake to
fix it.
I'm happy to try out any changes though, if someone can suggest something
that I can try?
On 6 August 2015 at 10:57, Calum <caluml(a)gmail.com> wrote:
> Hey Nikolay,
>
> Yes, that's what I thought although I'm not familiar enough with cmake to
> fix it.
> I'm happy to try out any changes though, if someone can suggest something
> that I can try?
>
> On 6 August 2015 at 10:50, Nikolay Dimitrov <picmaster(a)mail.bg> wrote:
>
>> Hi Calum,
>>
>> On 08/06/2015 12:35 PM, Calum wrote:
>>
>>> For the record - the workaround
>>>
>>> mkdir /usr/lib64/lib64/
>>> cd /usr/lib64/lib64/
>>> ln -s ../libboost_system-mt.so.5
>>> ln -s ../libboost_thread-mt.so.5
>>>
>>> allowed me to build it, although it's not ideal.
>>>
>>
>> This looks like an issue with the cmake config file.
>>
>> On 6 August 2015 at 10:28, Calum <caluml(a)gmail.com
>>> <mailto:caluml@gmail.com>> wrote:
>>>
>>> Hello all,
>>>
>>> I have a problem building gr-osmosdr.
>>> Steps followed:
>>>
>>> git clone git://git.osmocom.org/gr-osmosdr
>>> <http://git.osmocom.org/gr-osmosdr> (commit
>>>
>>> 86ad584204762eeb01f07daa683673f1ec3f1df5)
>>> cd gr-osmosdr/
>>> mkdir build
>>> cd build/
>>> ENABLE_FCD=ON ENABLE_FCDPP=ON cmake ../
>>> make
>>> Scanning dependencies of target gnuradio-osmosdr
>>> [ 10%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/source_impl.cc.o
>>> [ 20%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/sink_impl.cc.o
>>> [ 30%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/ranges.cc.o
>>> [ 40%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/device.cc.o
>>> [ 50%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/time_spec.cc.o
>>> [ 60%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/fcd/fcd_source_c.cc.o
>>> [ 70%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/file/file_source_c.cc.o
>>> [ 80%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/rtl_tcp/rtl_tcp_source_f.cc.o
>>> [ 90%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/rtl_tcp/rtl_tcp_source_c.cc.o
>>> [100%] Building CXX object
>>> lib/CMakeFiles/gnuradio-osmosdr.dir/rfspace/rfspace_source_c.cc.o
>>> make[2]: *** No rule to make target
>>> `/usr/lib64/lib64/libboost_thread-mt.so.5', needed by
>>> `lib/libgnuradio-osmosdr-0.1.5git.so.0.0.0'. Stop.
>>> make[1]: *** [lib/CMakeFiles/gnuradio-osmosdr.dir/all] Error 2
>>> make: *** [all] Error 2
>>>
>>> I wonder if anyone can help me with this? Looks like the path to
>>> libboost_thread-mt.so.5 has two lib64s in it.
>>> I'm running CentOS 6.6.
>>>
>>> C
>>>
>>>
>>>
>> Regards,
>> Nikolay
>>
>
>
Hello all,
I have a problem building gr-osmosdr.
Steps followed:
git clone git://git.osmocom.org/gr-osmosdr (commit
86ad584204762eeb01f07daa683673f1ec3f1df5)
cd gr-osmosdr/
mkdir build
cd build/
ENABLE_FCD=ON ENABLE_FCDPP=ON cmake ../
make
Scanning dependencies of target gnuradio-osmosdr
[ 10%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/source_impl.cc.o
[ 20%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/sink_impl.cc.o
[ 30%] Building CXX object lib/CMakeFiles/gnuradio-osmosdr.dir/ranges.cc.o
[ 40%] Building CXX object lib/CMakeFiles/gnuradio-osmosdr.dir/device.cc.o
[ 50%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/time_spec.cc.o
[ 60%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/fcd/fcd_source_c.cc.o
[ 70%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/file/file_source_c.cc.o
[ 80%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/rtl_tcp/rtl_tcp_source_f.cc.o
[ 90%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/rtl_tcp/rtl_tcp_source_c.cc.o
[100%] Building CXX object
lib/CMakeFiles/gnuradio-osmosdr.dir/rfspace/rfspace_source_c.cc.o
make[2]: *** No rule to make target
`/usr/lib64/lib64/libboost_thread-mt.so.5', needed by
`lib/libgnuradio-osmosdr-0.1.5git.so.0.0.0'. Stop.
make[1]: *** [lib/CMakeFiles/gnuradio-osmosdr.dir/all] Error 2
make: *** [all] Error 2
I wonder if anyone can help me with this? Looks like the path to
libboost_thread-mt.so.5 has two lib64s in it.
I'm running CentOS 6.6.
C
Hi everyone,
the new SIMtrace board will be available soon. It is equipped with an
Atmel AT91SAM3 instead of a AT91SAM7 (both chips are pin compatible, so
upgrading by hand by unsoldering the old processor and attaching the new
AT91SAM3 is also possible).
Just for the record, if you want to flash an AT91SAM3, this solution
worked for me: Comment out osmoSDRDetect() return -1 in osmosdr.c, so
that osmoSDRDetect always returns 0. Further adjustment in terms of
addresses:
% diff -Naur src/sam3u.c src/sam3s.c5
--- src/sam3u.c 2015-05-29 15:59:51.697208630 +0200
+++ src/sam3s.c 2015-05-29 15:39:34.331493312 +0200
@@ -139,12 +139,8 @@
switch(bank) {
case 0:
- regBase = 0x400e0800;
- flashBase = 0x80000;
- break;
- case 1:
regBase = 0x400e0a00;
- flashBase = 0x100000;
+ flashBase = 0x400000;
break;
default:
fprintf(stderr, "illegal flash bank");
@@ -192,12 +188,8 @@
switch(bank) {
case 0:
- regBase = 0x400e0800;
- flashBase = 0x80000;
- break;
- case 1:
regBase = 0x400e0a00;
- flashBase = 0x100000;
+ flashBase = 0x400000;
break;
default:
fprintf(stderr, "illegal flash bank");
After adjusting the addresses, compile sam3s.c in the Makefile instead of sam3u.c.
Please also find attached a diff of my locally applied change, which might illustrate the adjustments needed in more clarity.
Regards,
Christina