Re: [Discuss-gnuradio] detecting spectrum holes
John, may I ask you to be a bit more patient with GNU Radio beginners in general, and in particular with those whose mother tongue is not English? On top of that, the tiny hairs on my spine just got triggered, and that's caused by an adrenaline rush in reaction to potentially rude language ;) Back to the facts: Google has 32.1 million hits for "spectrum hole", and about every second one on the first page seems to be an academic paper. So maybe some defined the term, but this won't change the fact that it's used in real life, even by academics. Your point reminds me of my physics teacher complaining that we shouldn't use the term "weight" together with kilograms, because kilogram is the unit of mass and weight is measured in Newton. You will never get rid of colloquial language entirely. Can we please get back to a constructive discussion now and help Ahmed with his problem? @Ahmed: Problem 1: Please describe your hardware setup so that we can help: a) What USRP model are you using? What GNUradio version, did you install the distribution package on Ubuntu 8.04 or upgrade to 11.10 as suggested? What was the exact command line you used for usrp_spectrum_sense.py and usrp_fft.py? b) What daughterboard did you install inside the USRP? How did you connect it to the USB port of your laptop, and how to the antenna? c) Is the USRP powering up? d) After a power cycle (everything just switched on), does uhd_find_devices still give you nothing? what about lsusb -v? In case you managed to get up to d) and have the USRP and daughterboard(s) detected correctly, e) Did you connect the antenna to the appropriate RX channel of your daughterboard? When using WBX, there's an RX and an RX/TX port, so if you connect the antenna to the wrong port, you might only see noise except for a few *very* strong local sources. Try tuning to a local FM radio station... Any antenna should do for this purpose, even a paperclip - but don't torture the gold plated SMA connectors of the USRP with that :) Problem 3 is probably caused by Problem 2. I also noticed that sometimes the USB stack seems to get messed up, so you might want to try a) power cycling your USRP and if that doesn't help, b) power cycling the laptop connected to the USRP. I'm only a beginner myself, but that's what came to my mind because I ran into similar issues myself. If this doesn't help, please make sure you're at least on Ubuntu 11.10 and then we can compare results... cheers Alex On 03/22/2012 11:25 AM, John Ewan wrote: I have had enough about this. What the heck is a spectrum hole. I am pretty sure this is probably a term brought up by some There are NO spectrum holes. Learn about black body radiation and KTB Sorry folks. the term has always erked me. We can talk about white space.that I can take. On 3/21/12, Abdelrahman Ahmed wrote: 2012/3/19 Alexander List ** On 01/-9/-28163 03:59 AM, Abdelrahman Ahmed wrote: i'm new to this ,i need your help on how to start detecting spectrum in TV band and holes in this spectrum. Ahmed, though others will probable be able to give you more in-depth directions wrt spectrum sensing, just out of curiosity, what's your use case? Are you looking into TV white spaces? [1] Most likely you'll want to use the USRP1 with WBX because I assume it has better sensitivity than TVRX. Why would you want to transmit anything if you're just looking into analyzing spectrum usage in TV channels? LP0410 is covering the right frequency band for UHF (400 MHz to 1 GHz), but it is a directional antenna. Is that what you want? Otherwise, you might be better off using an omni antenna, preferably on a roof... Here are a few pointers to papers on TV white spaces: http://www.openspectrum.eu/drupal6/node/23 I've posted some of the key issues on this list two years ago: http://www.ruby-forum.com/topic/205328 Dyspan has some nice papers on spectrum sensing as well: http://www.ieee-dyspan.org/2010/ http://cms.comsoc.org/eprise/main/SiteGen/DYSPAN_2010/Content/Home/Technical_and_Policy_Program.html Now to the setup: *Hardware / sample data* I have a USRP1, two WBX, USRP1 N210 and an PC hardware available as well, so unless you're in a closed source / NDA environment, we could set up a code repository on github, and I could provide you with sample recordings from Hong Kong to cross-check detectors. *Regulatory environment / signals too look for* What is your location? From your signature, I assume you're in the Middle East, and I guess we're talking mostly about DVB-T signals. Is there still analog TV transmission around, wireless microphones, ...? *gnuradio packages on Ubuntu* The gnuradio packages that come with Ubuntu 10.04 are most likely a bit outdated, so you might want to upgrade your laptops to 11.10 first. 10.04 contains 3.0.4-2
Re: [Discuss-gnuradio] detecting spectrum holes
On 01/-9/-28163 03:59 AM, Abdelrahman Ahmed wrote: i'm new to this ,i need your help on how to start detecting spectrum in TV band and holes in this spectrum. Ahmed, though others will probable be able to give you more in-depth directions wrt spectrum sensing, just out of curiosity, what's your use case? Are you looking into TV white spaces? [1] Most likely you'll want to use the USRP1 with WBX because I assume it has better sensitivity than TVRX. Why would you want to transmit anything if you're just looking into analyzing spectrum usage in TV channels? LP0410 is covering the right frequency band for UHF (400 MHz to 1 GHz), but it is a directional antenna. Is that what you want? Otherwise, you might be better off using an omni antenna, preferably on a roof... Here are a few pointers to papers on TV white spaces: http://www.openspectrum.eu/drupal6/node/23 I've posted some of the key issues on this list two years ago: http://www.ruby-forum.com/topic/205328 Dyspan has some nice papers on spectrum sensing as well: http://www.ieee-dyspan.org/2010/ http://cms.comsoc.org/eprise/main/SiteGen/DYSPAN_2010/Content/Home/Technical_and_Policy_Program.html Now to the setup: *Hardware / sample data* I have a USRP1, two WBX, USRP1 N210 and an PC hardware available as well, so unless you're in a closed source / NDA environment, we could set up a code repository on github, and I could provide you with sample recordings from Hong Kong to cross-check detectors. *Regulatory environment / signals too look for* What is your location? From your signature, I assume you're in the Middle East, and I guess we're talking mostly about DVB-T signals. Is there still analog TV transmission around, wireless microphones, ...? *gnuradio packages on Ubuntu* The gnuradio packages that come with Ubuntu 10.04 are most likely a bit outdated, so you might want to upgrade your laptops to 11.10 first. 10.04 contains 3.0.4-2ubuntu1 (http://packages.ubuntu.com/hardy/gnuradio) 11.10 contains 3.2.2.dfsg-1ubuntu7 (http://packages.ubuntu.com/oneiric/gnuradio) Once you've got 11.10 with the latest packages installed, you might want to test your setup with some of the gnuradio examples, like a basic FM receiver to tune in a local radio station. Hope this helps for a start - please let us/me know on the mailing list if you need more input :) Alex [1] http://en.wikipedia.org/wiki/White_spaces_(radio) ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNURadio Pre Configured Virtual Image with GUI Front End
Ali, given that you haven't received any responses so far, I guess this means there are not so many people out there who are willing to share their images ;) It might be useful to create such an image, but in the free software world, you're more likely to find people using KVM or Xen instead of VMware or Parallels. What exactly is it that you would like to do with GNUradio? Why does it have to be in a VM instead of directly installing on your Mac (I assume you have a MAC, given that you mention Parallels)? Are you aware that some stuff you might to do with GNU radio is latency sensitive, so your mileage using a VM might vary... Alex On 01/-9/-28163 03:59 AM, ali sajjad wrote: Hi everyone i am newbie to GNURadio and wish to have Pre Configured GNURadio vmware or Parallels image please share the information thanks in advance Best Regards Bye ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] gr-air-modes: problem with uhd and USRP1
Hi,
maybe the API has changed since gr-air-modes was written, or I'm doing
something stupid, but I tried:
$ ./uhd_modes.py -g 60
linux; GNU C++ version 4.4.5; Boost_104200; UHD_0001.20101124180824.2568efd
Traceback (most recent call last):
File "./uhd_modes.py", line 167, in
fg = adsb_rx_block(options, args, queue)
File "./uhd_modes.py", line 57, in __init__
self.u = uhd.simple_source("", uhd.io_type_t.COMPLEX_FLOAT32)
AttributeError: 'module' object has no attribute 'simple_source'
I've used the latest "next" branch of gnuradio, installed and
successfully tested UHD. My prefix for all three packages is /opt/gnuradio.
According to
/opt/gnuradio/lib/python2.6/site-packages/gnuradio/uhd/uhd_swig.py,
there is indeed no simple_source, there are single_usrp_source and
multi_usrp_source, but they have a different interface...
Any hints?
Alex
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Lyric probability CPU
Hi, I think these GP5s will have some interesting applications in signal processing as well... http://www.hardwarecentral.com/hardwarecentral/news/article.php/3899206 [...] After LEC, Lyric said its next focus is the development of a general-purpose programmable probability processing platform that it calls GP5. It will run code written in Lyric's own probability programming language called Probability Synthesis to Bayesian Logic (PSBL), which Lyric said is an expressive computer programming language for working with probability-based computations. Lyric aims to begin sampling the first GP5 in 2013. [...] Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Gnu Radio built on Sheeva Plug
Rafael Diniz wrote: > Let us know what you could do using the sheeva plug! > It's probably one of the smallest devices with the lowest power consumption able to run Ubuntu and featuring USB2.0 and a Gigabit NIC, the minimum requirements to run GNU Radio with USRP1/2. See http://en.wikipedia.org/wiki/SheevaPlug for details. I can give it a shot if you want... and compare a quadcore i7 with the SheevaPlug sampling DVB-T signals... Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] solved: USRP1 "hangs", benchmark doesn't continue
On 3/9/10 1:36 AM, Alexander List wrote: > I hope I haven't killed the oscillator? I connected the output of X2 to > each of the daugherboard connector's clock lines (clock db a p) with 47 > Ohms in front of each connector. > D'oh. I'll never solder on SMD PCBs again when I have a hangover. I shorted pins 10 and 12 of J667, connecting the clock to DVDD:1 ... Thanks for the hint with the clock! Alex signature.asc Description: OpenPGP digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP1 "hangs", benchmark doesn't continue
On 3/9/10 1:19 AM, Matt Ettus wrote: > Sounds like there is a clock problem. Can you measure the clock with > an oscilloscope? What about when you remove the daughterboards? I don't have one at home, but I guess I'll find someone in Zurich who has ;) Removing the daughterboards yields no change with usrp_benchmark_usb :( I hope I haven't killed the oscillator? I connected the output of X2 to each of the daugherboard connector's clock lines (clock db a p) with 47 Ohms in front of each connector. Alex signature.asc Description: OpenPGP digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP1 "hangs", benchmark doesn't continue
Hi,
* I've installed the latest and greatest gnuradio from git, everything
compiled fine.
* I have a pre-500 USRP1, and fixed the wiring of the clock to the four
daughterboard sockets.
* I've been running gnuradio on this hardware ~2 weeks ago successfully.
Now, when I try to run anything that connects to the USRP, it just
"hangs". It downloads the firmware (blinking gets slower), it identifies
my two WBX boards correctly, but:
---8<---
$ /opt/gnuradio/HEAD/share/gnuradio/examples/usrp/usrp_benchmark_usb.py
Testing 2MB/sec...
---8<---
...and that's where it ends. It just hangs there.
If I try usrp_oscope.py on a local radio station, I see *nothing*.
I also tried usrp_wfm_rcv_nogui.py:
$ usrp_wfm_rcv_nogui.py -f 100.6e6 -O plughw:0,0 -g 30
When I strace the process, I only see
select(0, NULL, NULL, NULL, {0, 2000}) = 0 (Timeout)
select(0, NULL, NULL, NULL, {0, 4000}) = 0 (Timeout)
select(0, NULL, NULL, NULL, {0, 8000}) = 0 (Timeout)
select(0, NULL, NULL, NULL, {0, 16000}) = 0 (Timeout)
Any hints?
Alex
signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] White space sensing efforts
Hi everyone! I've set up my USRP1 with 2 WBX, a dipole antenna - originally for FM radio - connected to one WBX, and a 450 MHz omni antenna to the other WBX. The connected PC is running Ubuntu 9.10 x86_64, build dependencies for GNU Radio are installed, GNU Radio builds and runs fine. Now what I'd like to do is implement sensing for white space devices[1], entirely in free software, with hardware available from Ettus Research. To my knowledge, this is what has happened so far: * Microsoft presented a prototype to the FCC that was implemented using 802.11 cards in combination with 2.4 GHz -> UHF downconversion, and yes, they're using the USRP and GNU Radio. [2] * Philips Research prestented a prototype to the FCC as well. Monisha Ghosh is going to present their most recent results regarding DVB-T sensing at DySpan 2010. Is anybody else already working in this area? The challenges are: * different TV/DTV standards in different regions (NTSC/ATSC in North America, PAL/SECAM/DVB-T in Europe, ...) * wirless microphones also need to be detected (but that can be implemented later...) * sensing has to be reliable even below the noise floor (FCC requires -114 dBm, ETSI WG SE 43 is currently discussing the hidden node margin for Europe...) * we might have to circumvent or challenge patents or patent applications in this area What I can offer: * time for coding bits and pieces needed for detection of incumbent users * samples taken with my hardware * Eventually: remote access to my hardware, but that requires that we've physically met before. I need to trust you not to do something illegal with the WBX... Some constraints I think are necessary for fairness: * all the results are shared, of course with proper credits given * all the results will be published under GPLv3 and copyright assigned to the FSF (or whatever is necessary to include it in GNU Radio trunk) I'd like to collaborate with others instead of re-inventing the wheel ;). So far, we are already some folks over here in Europe who are working on this ... anybody else? Please speak up! 73 Alex HB9/OE9LAJ [1] http://en.wikipedia.org/wiki/White_spaces_%28radio%29 [2] http://research.microsoft.com/apps/pubs/default.aspx?id=80952 (ACM SIGCOMM Best Paper Award) signature.asc Description: OpenPGP digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Clear my fundamentals
discuss-gnuradio-requ...@gnu.org wrote: Message: 2 Date: Sun, 01 Nov 2009 10:17:59 -0800 From: Josh Blum Subject: Re: [Discuss-gnuradio] Clear my fundamentals :) To: Blue Boy Cc: discuss-gnuradio@gnu.org Message-ID: <4aedd0d7.1080...@joshknows.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Blue Boy wrote: Hello Everyone, My first post: I am a windows kernel programmer by profession.Recently my interest has grown for SDR gnuradio.I an new to this field so I have newbie doubts.I would welcome if you just point to some links for my answers. 1] What is usrp cfile format? complex/float but whats stored in numbers like amplitude/intensity/phase difference etc. Its a binary file containing 64-bit complex numbers where each 64 bit complex number is 2 32-bit floating point numbers corresponding to to the real and imaginary parts of a complex number. 2] Is frequency also stored in the cfile ? or we have to assume frequency from file name? How to reconstruct complete/sampled signal from Cfile ? You need to know the sampling rate and baseband frequency, the file is just raw data samples without any context. Hi Josh, I have a related question: Is there anything like an (upcoming) industry standard for recorded SDR samples, *including* the metadata? I guess that would make it a lot easier to exchange recordings between different platforms, and would also save people from the hassle of encoding metadata in the filename or an external data source. I guess NetCDF would be one possible way - it's widely used e.g. in the geosciences: http://www.unidata.ucar.edu/software/netcdf/usage.html http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#whatisit Of course we would have to define the schema for SDR data... Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign
'doh... Forgot to reinstall swig after my Macbook reinstall. Did that, removed the files as suggested, svn up, bootstrap etc. and it built fine... added script to my MacPorts package install script so I don't forget it next time... Now I'm running into some Python library version conflicts when trying to run grc, but at least I have binaries ;-) Will bother the list again if I'm stuck. Thanks a lot for your help! Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign
Alexander List wrote: > Michael Dickens wrote: > >> Hi Alex - In the file 'gnuradio-core/src/lib/Makefile.am', remove the >> entry "missing/libmissing.la" from the entry for >> "libgnuradio_core_qa_la_LIBADD". Here's the "svn diff". Let me / the >> list know if this works. - MLD >> > Yep, that worked, thanks. But now I get another error for which I found > no solution on Google, and simply removing it from the Makefile didn't > help this time... > > ---8<--- > make[5]: *** No rule to make target `gnuradio_swig_py_runtime.h', needed > by `all'. Stop. > > This is how I ran configure: > > $ ./configure --prefix=/Users/alex/Documents/work/nc-projects/gr > --disable-all-components --enable-gnuradio-core --enable-usrp > --enable-gr-usrp --enable-gr-wxgui --enable-gr-audio-osx > --enable-gnuradio-examples --enable-gr-utils > --enable-gr-how-to-write-a-block --enable-omnithread --enable-gruel > --enable-mblock --enable-pmt --enable-grc > > ---8<--- > OK, I reinstalled my MacBook with OS X 10.5.7, installed MacPorts and dependencies according to instructions in http://de.pastebin.ca/1417306, same story: ---8<--- libtool: link: g++ -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o .libs/libgnuradio-core-qa.0.dylib .libs/bug_work_around_6.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_ccomplex_dotprod_x86.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_complex_dotprod_x86.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_dotprod_x86.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_filter.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_float_dotprod_x86.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_ccc.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_ccf.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_fcc.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_fff.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_scc.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_rotator.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gri_mmse_fir_interpolator.o .libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gri_mmse_fir_interpolator_cc.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_general.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_circular_file.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_firdes.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_fxpt.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_fxpt_nco.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_fxpt_vco.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_math.o .libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gri_lfsr.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_block.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_buffer.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_flowgraph.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_hier_block2.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_hier_block2_derived.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_io_signature.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_top_block.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_vmcircbuf.o .libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_runtime.o -L/Users/alex/Documents/work/nc-projects/gr/lib -L/opt/local/lib ./.libs/libgnuradio-core.dylib /Users/alex/Documents/work/nc-projects/gr/gnuradio-3.2/omnithread/.libs/libgromnithread.dylib /Users/alex/Documents/work/nc-projects/gr/gnuradio-3.2/gruel/src/lib/.libs/libgruel.dylib -lboost_thread-mt-s /opt/local/lib/libfftw3f.dylib /opt/local/lib/libgsl.dylib /opt/local/lib/libgslcblas.dylib -lcblas /opt/local/lib/libcppunit.dylib -lm -ldl -Wl,-dylib_file -Wl,/Users/alex/Documents/work/nc-projects/gr/lib/libgromnithread.0.dylib:/Users/alex/Documents/work/nc-projects/gr/gnuradio-3.2/omnithread/.libs/libgromnithread.dylib -Wl,-dylib_file -Wl,/Users/alex/Documents/work/nc-projects/gr/lib/libgruel.0.dylib:/Users/alex/Documents/work/nc-projects/gr/gnuradio-3.2/gruel/src/lib/.libs/libgruel.dylib -install_name /Users/alex/Documents/work/nc-projects/gr/lib/libgnuradio-core-qa.0.dylib -compatibility_version 1 -current_version 1.0 -Wl,-single_module libtool: link: dsymutil .libs/libgnuradio-core-qa.0.dylib || : libtool: link: (cd ".libs" && rm -f "libgnuradio-core-qa.dylib" && ln -s "libgnuradio-core-qa.0.dylib" "libgnuradio-core-qa.dylib") libtool: link: rm -fr .libs/libgnuradio-core-qa.lax libtool: link: ( cd ".libs" && rm -f "libgnuradio-core-qa.la" && ln -s "../libgnuradio-core-qa.la" "libgnuradio-core-qa.la" ) Making all in swig make[5]: *** No rule to make target `gnuradio_swig_py_runtime.h', needed by `all'. Stop. make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 mak
Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign
Michael Dickens wrote: > Hi Alex - In the file 'gnuradio-core/src/lib/Makefile.am', remove the > entry "missing/libmissing.la" from the entry for > "libgnuradio_core_qa_la_LIBADD". Here's the "svn diff". Let me / the > list know if this works. - MLD Yep, that worked, thanks. But now I get another error for which I found no solution on Google, and simply removing it from the Makefile didn't help this time... ---8<--- make[5]: *** No rule to make target `gnuradio_swig_py_runtime.h', needed by `all'. Stop. This is how I ran configure: $ ./configure --prefix=/Users/alex/Documents/work/nc-projects/gr --disable-all-components --enable-gnuradio-core --enable-usrp --enable-gr-usrp --enable-gr-wxgui --enable-gr-audio-osx --enable-gnuradio-examples --enable-gr-utils --enable-gr-how-to-write-a-block --enable-omnithread --enable-gruel --enable-mblock --enable-pmt --enable-grc ---8<--- Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] build error on OS X 10.4: ld: multiple definitions of symbol _posix_memalign
Hi,
trying to build gnuradio on OS X 10.4, I get
---8<---
Extracting
/Users/alex/Documents/work/nc-projects/gr/gnuradio/gnuradio-core/src/lib/missing/.libs/libmissing.a
(cd .libs/libgnuradio-core-qa.lax/libmissing.a && ar x
/Users/alex/Documents/work/nc-projects/gr/gnuradio/gnuradio-core/src/lib/missing/.libs/libmissing.a)
g++ -dynamiclib -single_module ${wl}-flat_namespace ${wl}-undefined
${wl}suppress -o .libs/libgnuradio-core-qa.0.0.0.dylib
.libs/bug_work_around_6.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_ccomplex_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_complex_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_filter.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_float_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_ccc.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_ccf.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_fcc.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_fff.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_scc.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_rotator.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gri_mmse_fir_interpolator.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gri_mmse_fir_interpolator_cc.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_general.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_circular_file.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_firdes.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_fxpt.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_fxpt_nco.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_fxpt_vco.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gr_math.o
.libs/libgnuradio-core-qa.lax/libgeneral-qa.a/qa_gri_lfsr.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_block.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_buffer.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_flowgraph.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_hier_block2.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_hier_block2_derived.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_io_signature.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_top_block.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_gr_vmcircbuf.o
.libs/libgnuradio-core-qa.lax/libruntime-qa.a/qa_runtime.o
.libs/libgnuradio-core-qa.lax/libmissing.a/bug_work_around_8.o
.libs/libgnuradio-core-qa.lax/libmissing.a/posix_memalign.o
-L/Users/alex/Documents/work/nc-projects/gr/lib -L/opt/local/lib
./.libs/libgnuradio-core.dylib
/Users/alex/Documents/work/nc-projects/gr/gnuradio/omnithread/.libs/libgromnithread.dylib
/Users/alex/Documents/work/nc-projects/gr/gnuradio/gruel/src/lib/.libs/libgruel.dylib
/opt/local/lib/libfftw3f.dylib /opt/local/lib/libgsl.dylib
/opt/local/lib/libgslcblas.dylib /opt/local/lib/libcppunit.dylib -ldl
-install_name
/Users/alex/Documents/work/nc-projects/gr/lib/libgnuradio-core-qa.0.dylib
-Wl,-compatibility_version -Wl,1 -Wl,-current_version -Wl,1.0
ld: multiple definitions of symbol _posix_memalign
.libs/libgnuradio-core-qa.lax/libmissing.a/posix_memalign.o definition
of _posix_memalign in section (__TEXT,__text)
./.libs/libgnuradio-core.dylib(single module) definition of _posix_memalign
/usr/bin/libtool: internal link edit command failed
make[1]: *** [libgnuradio-core-qa.la] Error 1
make: *** [all-recursive] Error 1
---8<---
$ svn info
Path: .
URL: http://gnuradio.org/svn/gnuradio/trunk
Repository Root: http://gnuradio.org/svn
Repository UUID: 221aa14e-8319-0410-a670-987f0aec2ac5
Revision: 11082
Node Kind: directory
Schedule: normal
Last Changed Author: jcorgan
Last Changed Rev: 11082
Last Changed Date: 2009-05-21 18:21:10 +0200 (Thu, 21 May 2009)
$ uname -a
Darwin computer.local 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10
18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386
Tried with 3.2 as well, same story:
---8<---
Extracting
/Users/alex/Documents/work/nc-projects/gr/gnuradio-3.2/gnuradio-core/src/lib/missing/.libs/libmissing.a
(cd .libs/libgnuradio-core-qa.lax/libmissing.a && ar x
/Users/alex/Documents/work/nc-projects/gr/gnuradio-3.2/gnuradio-core/src/lib/missing/.libs/libmissing.a)
g++ -dynamiclib -single_module ${wl}-flat_namespace ${wl}-undefined
${wl}suppress -o .libs/libgnuradio-core-qa.0.0.0.dylib
.libs/bug_work_around_6.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_ccomplex_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_complex_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_filter.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_float_dotprod_x86.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_ccc.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_ccf.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_fcc.o
.libs/libgnuradio-core-qa.lax/libfilter-qa.a/qa_gr_fir_fff.o
.libs/libgnuradio-core
Re: [Discuss-gnuradio] DECT anyone?
Sorry for the long delay replying... Eric Blossom wrote: > If you're serious about this as a project for your master's thesis > and you're willing to contribute the code to the project, we can > probably find some way to get you a daugtherboard. Will the > university pay for the daughterboard? > > Will try to convince them. Otherwise I'll sell my car ;-) Johnathan Corgan wrote: > I had started a receiver module in examples/python/dect, but didn't get > very far. What's there will tune to a supplied frequency, apply the > appropriate channel filter, demodulate the GMSK to (unpacked) bits, then > record to a file. I was able to "grep" the bits for DECT > pre-amble/synchronization codes and see them. > > Well, at least a starting point... > This was to be a "service monitor" type of application, not a base > station or handset. So none of the TDMA aspects were considered. We > still need (ahem) mblocks and in-band signaling to properly implement > either end of the protocol. > > Is there an ETA for the mblocks? I'm not that much in a hurry, I won't be able to start my thesis before next summer anyway. And I'll be happy to discuss something like a roadmap with you folks before proposing this project to a supervisor over here. No idea if it's too big for a MSc thesis ... > A base station stack that could handle a single DECT TDMA carrier would > be able to support 12 cordless phones full-duplex. Wrap it up in an > Asterisk channel driver and you have a small office cordless PBX for the > price of a USRP and PC, using entirely Open Source software. > > Yep, true, that's interesting from the political POV, but that's a rather expensive solution to get a SOHO cordless PBX... However, as a proof of concept it's worth the investment. And most likely cheaper than an "old school" enterprise PBX with the DECT features enabled and DECT base stations attached... > The DECT protocols are very well documented, and the handsets are very > cheap... > That's true. You even get SIP capable base stations over here in Europe for ~EUR 70-100 (USD 100-150) that allow you to assign different VoIP providers to different handsets, use IM on the handsets, ... but of course without source ;-). I wonder what other means to aid development are out there. I guess some kind of DECT monitor and/or base station with debugging capabilities would be really nice. If we do DECT in free software, we should be able to prove it's ETSI compliant ;-) Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] DECT anyone?
Hello, I'm currently investigating the possibilities to do DECT with GNU Radio. I currently have a USRP1 with BasicRX/TX. If possible, I'd like to avoid buying the RFX1800 because of budget reasons (I'm a student right now), so do you think it's feasible by "abusing" the RF part of a used DECT base station? I noticed that DECT is on the wishlist, and it sounds like a nice project for a master's thesis... is anyone already working on DECT? Alex signature.asc Description: PGP signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] HAM RADIO Friedrichshafen anyone?
Hello, I wonder if anyone is coming to Friedrichshafen (Germany) for Ham Radio 2006, June 23-25? http://www.hamradio-friedrichshafen.de/html/en/index.php Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Ham radio (FDH/Germany, Jun 24-26 2005) anyone?
Hello, I wonder if anyone is going to show up at Ham Radio this year... http://www.hamradio-friedrichshafen.de/html/en/ I haven't been there for years, and of course it would be nice to meet some other people interested in GNU Radio... Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
