Re: [Discuss-gnuradio] rev 6467 make problem
Hi George, Here it is: checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for AIX... no checking for library containing strerror... none required checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking whether C++ has bool... yes checking whether C++ has buggy scoping in for-loops... no checking whether user wants assertions... yes checking whether C++ has std::isnan... yes checking whether user wants warnings... yes checking whether gcc accepts -Wall... yes checking whether g++ accepts -Wall... yes checking whether g++ accepts -Woverloaded-virtual... yes checking whether user wants gprof... no checking whether user wants prof... no checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for a BSD-compatible install... /usr/bin/install -c checking for rm... /bin/rm checking for a sed that does not truncate output... /bin/sed checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking how to recognise dependent libraries... pass_all checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 static flag -static works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes checking dynam
Re: [Discuss-gnuradio] rev 6467 make problem
Hi Hans, This is in my realm, but I don't know the exact answer yet... just tossing out my knowledge to help. But it seems as though the libusrp_inband-qa (QA code for the inband code) is not linking to the PMT library correctly... or the PMT library is never built. Can you report your output of ./configure ? Under "The following GNU Radio components have been successfully configured:" ... you should see "pmt" listed. If you don't, this could be the problem. I believe the PMT library depends on boost, so make sure you have that installed. - George Hans Glitsch wrote: Hi, I got svn rev 6467 of the gnuradio trunk today and it built fine (with no errors) on my Ubuntu desktop machine. Then I tried the same on my Ubuntu server machine and 'make' ended with the following: I deleted the entire `/home/superuser/SM1680/build/gnuradio' directory, did a svn checkout of 6467, ./bootstrap, ./configure, and then make g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.1.2/crtbeginS.o .libs/qa_inband.o .libs/qa_inband_packet_prims.o .libs/qa_inband_usrp_server.o -Wl,--rpath -Wl,/home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs -Wl,--rpath -Wl,/usr/local/lib ./.libs/libusrp_inband.so /usr/lib/libcppunit.so -ldl -L/usr/lib/gcc/i486-linux-gnu/4.1.2 -L/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.1.2/crtendS.o /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crtn.o -pthread -Wl,-soname -Wl,libusrp_inband-qa.so -o .libs/libusrp_inband-qa.so creating libusrp_inband-qa.la (cd .libs && rm -f libusrp_inband-qa.la && ln -s ../libusrp_inband-qa.la libusrp_inband-qa.la) if g++ -DHAVE_CONFIG_H -I. -I. -I../../../.. -DOMNITHREAD_POSIX=1 -I../../../../omnithread -I../../../../pmt/src/lib -I../../../../mblock/src/lib -I../../../../usrp/host/lib/legacy -I../../../../usrp/firmware/include -I./../../apps-inband -g -O2 -Wall -Woverloaded-virtual -pthread -MT test_inband.o -MD -MP -MF ".deps/test_inband.Tpo" -c -o test_inband.o test_inband.cc; \ then mv -f ".deps/test_inband.Tpo" ".deps/test_inband.Po"; else rm -f ".deps/test_inband.Tpo"; exit 1; fi /bin/bash ../../../../libtool --tag=CXX --mode=link g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o test_inband test_inband.o libusrp_inband-qa.la g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o .libs/test_inband test_inband.o ./.libs/libusrp_inband-qa.so -Wl,--rpath -Wl,/usr/local/lib ./.libs/libusrp_inband-qa.so: undefined reference to `pmt_list5(boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr)' /home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs/libusrp_inband.so.0: undefined reference to `pmt_make_any(boost::any const&)' ./.libs/libusrp_inband-qa.so: undefined reference to `PMT_F' /home/superuser/SM1680/build/gnuradio/mblock/src/lib/.libs/libmblock.so: undefined reference to `pmt_is_eof_object(boost::shared_ptr)' ./.libs/libusrp_inband-qa.so: undefined reference to `PMT_T' /home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs/libusrp_inband.so.0: undefined reference to `pmt_any_ref(boost::shared_ptr)' /home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs/libusrp_inband.so.0: undefined reference to `pmt_list6(boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr)' /home/superuser/SM1680/build/gnuradio/mblock/src/lib/.libs/libmblock.so: undefined reference to `pmt_deserialize(std::basic_streambufstd::char_traits >&)' collect2: ld returned 1 exit status make[6]: *** [test_inband] Error 1 make[6]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband' make[5]: *** [all] Error 2 make[5]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host/lib' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/superuser/SM1680/build/gnuradio' make: *** [all] Error 2 thanks for your help, Hans ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] rev 6467 make problem
Hi, I got svn rev 6467 of the gnuradio trunk today and it built fine (with no errors) on my Ubuntu desktop machine. Then I tried the same on my Ubuntu server machine and 'make' ended with the following: I deleted the entire `/home/superuser/SM1680/build/gnuradio' directory, did a svn checkout of 6467, ./bootstrap, ./configure, and then make g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.1.2/crtbeginS.o .libs/qa_inband.o .libs/qa_inband_packet_prims.o .libs/qa_inband_usrp_server.o -Wl,--rpath -Wl,/home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs -Wl,--rpath -Wl,/usr/local/lib ./.libs/libusrp_inband.so /usr/lib/libcppunit.so -ldl -L/usr/lib/gcc/i486-linux-gnu/4.1.2 -L/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.1.2/crtendS.o /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crtn.o -pthread -Wl,-soname -Wl,libusrp_inband-qa.so -o .libs/libusrp_inband-qa.so creating libusrp_inband-qa.la (cd .libs && rm -f libusrp_inband-qa.la && ln -s ../libusrp_inband-qa.la libusrp_inband-qa.la) if g++ -DHAVE_CONFIG_H -I. -I. -I../../../.. -DOMNITHREAD_POSIX=1 -I../../../../omnithread -I../../../../pmt/src/lib -I../../../../mblock/src/lib -I../../../../usrp/host/lib/legacy -I../../../../usrp/firmware/include -I./../../apps-inband -g -O2 -Wall -Woverloaded-virtual -pthread -MT test_inband.o -MD -MP -MF ".deps/test_inband.Tpo" -c -o test_inband.o test_inband.cc; \ then mv -f ".deps/test_inband.Tpo" ".deps/test_inband.Po"; else rm -f ".deps/test_inband.Tpo"; exit 1; fi /bin/bash ../../../../libtool --tag=CXX --mode=link g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o test_inband test_inband.o libusrp_inband-qa.la g++ -g -O2 -Wall -Woverloaded-virtual -pthread -o .libs/test_inband test_inband.o ./.libs/libusrp_inband-qa.so -Wl,--rpath -Wl,/usr/local/lib ./.libs/libusrp_inband-qa.so: undefined reference to `pmt_list5(boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr)' /home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs/libusrp_inband.so.0: undefined reference to `pmt_make_any(boost::any const&)' ./.libs/libusrp_inband-qa.so: undefined reference to `PMT_F' /home/superuser/SM1680/build/gnuradio/mblock/src/lib/.libs/libmblock.so: undefined reference to `pmt_is_eof_object(boost::shared_ptr)' ./.libs/libusrp_inband-qa.so: undefined reference to `PMT_T' /home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs/libusrp_inband.so.0: undefined reference to `pmt_any_ref(boost::shared_ptr)' /home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband/.libs/libusrp_inband.so.0: undefined reference to `pmt_list6(boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr, boost::shared_ptr)' /home/superuser/SM1680/build/gnuradio/mblock/src/lib/.libs/libmblock.so: undefined reference to `pmt_deserialize(std::basic_streambuf >&)' collect2: ld returned 1 exit status make[6]: *** [test_inband] Error 1 make[6]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband' make[5]: *** [all] Error 2 make[5]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host/lib/inband' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host/lib' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp/host' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/superuser/SM1680/build/gnuradio/usrp' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/superuser/SM1680/build/gnuradio' make: *** [all] Error 2 thanks for your help, Hans ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Question about hearing FM station
Hi All, I am completely new in this list and in this project. I just start from the tutorial. When I am following the tutorial and run the example of sudo ./wfm_rcv_gui.py 101.5, I can only hear the noise. However, the example of sudo ./usrp_oscope.py works well. Could someone explain it to me? Appreciated, Ruby Lin - Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV.___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Major trunk repository update in r6466
The GNU Radio trunk repository has been updated with the following changes: * Final gr.top_block and gr.hier_block2 implementation inside gnuradio-core/src/lib/runtime * Implementation of gr.hier_block2 versions of all the old-style blocks in blks. These live in blks2. * Addition of gr.hier_block2 based versions of gr-wxgui blocks * Conversion of all the example code in gnuradio-examples to use this new code * Conversion of all the gr-utils scripts to use the new code The OFDM examples and related hierarchical blocks have not yet been converted. Code in the rest of the tree that is outside the core and example components has also not yet been converted. This has been done in a way that preserves all the existing functionality; you have to try in order to end up using the new style stuff. So existing, unchanged user code *should* not be affected. Release 3.1 will be the stable release that introduces this new code, and will also be the series that allows you to continue to use the old code. In release 3.2, we will be removing the old-style gr.flow_graph and gr.hier_block implementation, so you'll need to have ported your own code by then. Until we have a porting guide written, your best place to understand the changes is to peruse the examples and blks2impl directories. For users who already have a copy of the trunk checked out, compiled, and installed, it is *required* that you do: $ sudo make uninstall $ make distclean $ svn up ...then build from scratch. There have been directory and filename changes; without uninstalling and cleaning first, you will get a mix of old and new on your system. This merge is the last remaining major update to the trunk before release 3.1. Please help to stabilize it by reporting bugs (and I'm sure there will be many) on the list or in Trac. -- Johnathan Corgan Corgan Enterprises LLC http://corganenterprises.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] buffer sizes, timing and overflows
Juha Vierinen wrote: > I am writing a simple program that stores USRP sampled data and stores > it on disk continuously in 1s sized files. I have made a new sink for > this purpose, which is almost identical to gr_filesink, except that > mine blocks in work() while the file is closed and a new one is > created. Blocking in work() is bad. The current GNU Radio runtime scheduler is single threaded, so while your filesystem call is blocking, you're not reading from the USRP. Depending on how long you're blocked, this could result in dropped data. > 1) I would like to get as accurate timestamp as possible to the > beginning of the dump to make later analysis easier. What would be the > best way to estimate the time delay between fg.run() and the moment > when the first sample comes out of the down converter? You'll have to find a way to empirically measure it. Alternatively, when the "in-band signaling" code is ready, the received data from the USRP will be timestamped. > 2) I have managed through trial and error to get a fairly reliable > 8MHz sampling system using the following parameters: > fusb_nblocks=32768,fusb_block_size=1024. Is this a good way to make a > large buffer or should I use some other gnuradio block to create a > large buffer in RAM? I am hoping to write the data at 8MHz on a > networked RAID array and this will cause even larger waiting times for > my filesink, even though the average bandwidth is large enough. While this may work, you're addressing a symptom, not the root problem, which is calling fclose() in work(). Could you stream samples to a single file and cut it up into 1s samples afterwards? > 3) Another question: is there any way to query the driver if a buffer > overflow has occurred and maybe throw an exception? I am going to > sample continuously for long durations and it would be nice to be able > to restart sampling automatically if an overflow is detected due to > some reason. You can call usrp.source_c.noverruns() to get a count. > 4) What happens in an overflow situation? Do I still get the correct > amount of samples, albeit with wrong samples, or are the missing > samples just tossed away? They are tossed away. > Gnuradio and USRP is great! I really prefer your system to labview. Thanks. -- Johnathan Corgan Corgan Enterprises LLC http://corganenterprises.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] swig question
Don Ward wrote: > Instead of the contructor "usrp1_source_base" we have the function > "usrp1_sink_base". This isn't what I would expect. Does swig care? Well, it does, and this is a bug, but it we're lucky that it doesn't cause any apparent harm. Good catch, I'll fix on the trunk. -- Johnathan Corgan Corgan Enterprises LLC http://corganenterprises.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Information RSSI
Hi Calogero, We unfortunately cannot really support in-band signaling until its released, and I was told not to encourage its use until it is :) One reason is... 2) There are two amplifiers. Could you know where their gains are setted when I execute the test "test_usrp_inband_rx"? ... things like this aren't supported yet by the code. It should not be much longer until it is released. The core of the code is complete, we are waiting to fix a performance issue and complete daughterboard control. - George ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] audio source/sink buffer
Hi all, I've put together a simple program that shifts the frequency of an input down so that 252kHz comes out at 12kHz. It seems to be working, but it's very prone to buffer underruns and overruns. The slightest bit of activity on the computer breaks up the output. Is there any way to buffer the data from the audio sink, insulate things a bit? The input is from a BT878 chip @ 896000sps, the output is to a sound card @ 56000sps (actually 48000sps, using plughw). The goal is to feed RTE's DRM signal on 252kHz to another computer running the DRM decoder Dream [1]. The buffer problems are causing Dream to drop the signal almost as soon as it locks on. -Phil [1] http://drm.sourceforge.net/ ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Information RSSI
Hi, I have executed the package "inband-usb" and I have seen the value of RSSI but I don't understand two things: 1) What's the value of the frequency of USRP which is setted of default in the test "test_usrp_inband_rx"? 2) There are two amplifiers. Could you know where their gains are setted when I execute the test "test_usrp_inband_rx"? Thank you very much. Calogero ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
