[Discuss-gnuradio] GNU Radio overview podcast
Eric was kind enough to spend time with me to produce an overview podcast of GNU Radio, targetted at teh curious or newcomer.It's my first recorded podcast, so the audio quality is not what I would have hoped, but I believe it is usable. http://www.petrovic.org/blog/2006/10/18/gnu-radio-podcast/-- MarkAE6RT ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Suse10.1 walkthrough and a question concerning crosstalk
Matt, Coupling problem solved. Doh! -45 dBm is *way* too low; only the very low order A/D bits were toggling. When I put in something closer to +10 dBm I get a nice strong signal and the image on the other port of the same daughtercard is down about 60 dB. I can't measure the crosstalk from one daughtercard to the other. I guess that the tiny amount of crosstalk at -45 dBm was just enough to flip the LSB of the unconnected port often enough to give me a spectral line at a very low level. With more amplitude the A/Ds are acting more "linear" and I can now see the difference in levels more accurately. The upside is that I know a lot more about the code now than when I started. Best regards, Mark SullivanOn 9/24/06, Matt Ettus <[EMAIL PROTECTED]> wrote: Mark Sullivan wrote:> When I inject a signal at a -45 dBm level on the "RX-B" sma connector> on a Basic RX daughtercard, I see a copy of the signal on the "RX-A"> side when I use usrp_fft.py. The level is 10-20 dB below that of what > I see if I move the signal from "RX-B" to "RX-A," but this seems like> too much coupling. Using a 50 ohm termination on the unconnected sma> connector helps a little bit. I see no copy of the signal from either > input of the other Basic RX daughtercard. Any thoghts, anyone?>I don't know what's happening here, but I see about -80dB couplingbetween the channels.>> Here is a walkthough I put together for Suse10.1. I found a few> "gotchas" not described in the build instructions on the Wiki.Thanks! I put this on the wiki, but didn't "wikify" the formatting.Feel free to edit it. It is linked to from the Suse install page. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Suse10.1 walkthrough and a question concerning crosstalk
Pascal, Thanks for the tip, I'll add that to version 0.2. I can tell that you are much less "linux impaired" than I! Best regards, Mark SullivanOn 9/26/06, Pascal Charest <[EMAIL PROTECTED]> wrote: On 9/22/06, Mark Sullivan <[EMAIL PROTECTED] > wrote: (...) INSTALLING SDCC Log on to your account (not root). You need to install the SDCC package. Get the source tarball from Sourceforge at http://sourceforge.net/project/showfiles.php?group_id=599. (it will be called "sdcc-src-2.6.0.tar.gz" unless a newer version is available now) Do NOT load the Suse RPMs- the pair of RPMs depend upon each other, and the RPM command won't install either. Put the tarball in your home directory. Double-click on the icon for the tarball. A window will appear; click on "Extract." Click on "Extract" in the new window that appears. This will create a directory called "SDCC" in your home directory. Open up a terminal. (Click on "Applications" on the menu toolbar,scroll up to "System" in the menu that appears,scroll down to "Terminal" in the *next* menu that appears, then click on "Gnome Terminal" in yet another menu that appears) In the terminal window, type "cd SDCC" and hit Enter. Now type "./configure" and hit Enter. Now type "make" and hit Enter. now type "sudo make install" and hit Enter. When asked for the root password, enter it. type "cd .." and hit Enter. (...)Yeah, when trying a command like 'rpm -ivh sdcc-xxx.rpm', the system complains about dependencies with sdcc-common and when trying 'rpm -ivh sdcc-common-xxx.rpm', it complains about dependencies with sdcc... But, if you download both packages in the same directory and try 'rpm -ivh sdcc*.rpm', it works! Rpm will find cross-dependencies between package if they are installed at the same time. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Suse10.1 walkthrough and a question concerning crosstalk
Eric, As an additional experiment I hacked multi_file.py in the multi-antenna folder so that the multiplexor was set to channel 0 for all four "I" inputs; with a carrier injected into channel 1, I saw identical leakage. I then changed the mux setting to channel 1 for all "I" and saw the injected carrier. This isn't sounding like software. Best regards, Mark SullivanOn 9/22/06, Eric Blossom <[EMAIL PROTECTED]> wrote: On Fri, Sep 22, 2006 at 05:38:54PM -0400, Mark Sullivan wrote:> When I inject a signal at a -45 dBm level on the "RX-B" sma connector on a> Basic RX daughtercard, I see a copy of the signal on the "RX-A" side when I > use usrp_fft.py. The level is 10-20 dB below that of what I see if I move> the signal from "RX-B" to "RX-A," but this seems like too much coupling.> Using a 50 ohm termination on the unconnected sma connector helps a little > bit. I see no copy of the signal from either input of the other Basic RX> daughtercard. Any thoghts, anyone?>> Best regards,>> Mark SullivanHi Mark,There's a chance that the code that determines the rx digital mux setting isn't handling this case properly.Assuming that the Basic Rx is on the "A" side, please try this: $ usrp_fft.py -R a:0 -f and try moving the test signal from RX-A to RX-B and this: $ usrp-fft.py -R a:1 -f and move the test signal from RX-A to RX-BWhat happens?Thanks,Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Suse10.1 walkthrough and a question concerning crosstalk
When I inject a signal at a -45 dBm level on the "RX-B" sma connector on a Basic RX daughtercard, I see a copy of the signal on the "RX-A" side when I use usrp_fft.py. The level is 10-20 dB below that of what I see if I move the signal from "RX-B" to "RX-A," but this seems like too much coupling. Using a 50 ohm termination on the unconnected sma connector helps a little bit. I see no copy of the signal from either input of the other Basic RX daughtercard. Any thoghts, anyone? Best regards, Mark Sullivan Here is a walkthough I put together for Suse10.1. I found a few "gotchas" not described in the build instructions on the Wiki. Installing GnuRadio and the USRP on Suse 10.1 for the Linux-impaired. Version 0.1 22 September 2006 What you will need: PC with USB 2.0 and DVD drive, Suse 10.1 DVD, USRP, An internet connection, The better part of an afternoon. INSTALLING LINUX Boot from the DVD. Don't use the CD version; it is missing fftw3f.pc and the FFTW package will not install. Choose your language of choice and click on NEXT. Select "YES" to accept the license and click on NEXT. On the "System Analysis" screen select "New Installation" and click on NEXT. On the "Time Zone" screen set up your clock and click on NEXT. On the "Desktop" screen select "Gnome" and click on NEXT. On the "Installation Summary" screen click on "Software" (it should be displaying "Standard Software Gnome 2"). The "Software Selection" screen appears. Click on "Details" to customize your selection. Select "Package Groups" as the Filter; you should get a tree on the left of the screen. Click on the "development" branch; click on the "package" menu on the toolbar, scroll down to "All in this list," in the pull down menu, then select "Install." Under the "Development" tree, click on "KDE" sub-branch; click on the "package" menu on the toolbar, scroll down to "All in this list," in the pull down menu, then select "Do not install." Under the "Productivity" tree, click on "Scientific" sub-branch; click on the "package" menu on the toolbar, scroll down to "All in this list," in the pull down menu, then select "Install." Click on the "Libraries" tree; click on the "package" menu on the toolbar, scroll down to "All in this list," in the pull down menu, then select "Install." Click on "Accept." You will get a pop-up window with three warnings. Click on the circles next to "do not install flex-old" for the first two warnings and click on the circle next to "do not install gtkl-compat-devel" for the remaining warning. Click on the "OK, try again" button at the bottom of the pop up window. An Adobe license window appears; click on the "Accept" button. A flash player license window appears, click on the "Cancel" button. The "Installation Settings" window reappears after a long pause. Click on "Accept" at the lower right hand corner. A "Confirm" window appears; click "Install." A "Package Installation" screen appears. Click on the "Details" tab to watch the progress of the install. This would be a good time to take a break; installation will take about 1 hour to complete. The system will reboot and the Install screen re-appears. Enter your hostname and domain and click on Next. Enter your root password and click on Next. Write down your root password so you don't forget it! A "Network Configuration" screen appears. If you have DHCP set up, select that option and click on Next. A "Test Connection" window appears. Click on Next. Assuming all is well with the connection, click on Next again after the test is complete. An "Online Update" screen appears; select "Configure now" and click on Next. Wait for a while for the server to be selected. An "Online Update Configuration" window appears; click on "OK." Click on the circle next to "Run Update," then click on Next. A "Update Select" screen appears; click on "Accept" The YAST package will now be updated. You can update the rest of your system later. After "Total Progress" reaches 100%, click on Next. After a pause, the "Update Select" screen reappears. Click on Cancel. The "Authentication Method" screen appears. Click on the circle next to "Local." The "New Local User" screen appears. Enter your name, username, and password. The "Release Notes" screen appears. Click on Next. The "Hardware Configuration" screen appears. Click on Next. The "Installation Com
[Discuss-gnuradio] multi-antenna example
Hi all, I got my USRP up and running just fine after a fresh install of Suse 10.1 I'm working on a "walkthrough" that describes some of the problems I encountered; I'd be happy to add it to the Wiki if anybody is interested. After running the USB benchmark (32M, no problem) and seeing the FFT display work, just for fun I attached an antenna directly to my basic RX and keyed an FRS radio nearby. No problem seeing the 465 MHz FM signal pop up. Very cool. Now for the only problem I've encountered. I have two basic RX cards installed, and I'm injecting a single signal into the "RX-A" input of the A side card at a level of about 45 dBm or so. I run the multi-antenna capture to file code with maximum decimation (256) and software filtering turned off for a 50 millisecond collect. I then look at the spectrum of the resulting four files with MATLAB (sorry!). I see my carrier in both channels 0 and 1 (but not 3 or 4) at nearly the same level. I didn't see any error messages during the collect; is it possible that the software couldn't keep up with the data and got out of sync? I'm going to try writing some test code to pull in the data to memory before writing out to disk next. Any thoughts? Best regards, Mark Sullivan ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP - hotplug / udev / auto-loading of firmware
I also added to the rules fileSYSFS{idVendor}=="077d", SYSFS{idProduct}=="0410", MODE="0666"so I could access the Powermate without becoming root.
On 6/29/06, Lee Patton <[EMAIL PROTECTED]> wrote:
On Thu, 2006-06-29 at 07:44 +0100, Kalen Watermeyer wrote:> I ask because I run Ubuntu 6.06 (Dapper), which uses> udev, and will need to edit my device manager's rules> to identify my custom board, and am not sure if this
> is necessary. Oh, and the OS detects my FX2 micro when> I run lsusb (albeit unconfigured).>> Finally, if I do have to edit the rules (SYSFS,> VendorId etc), what exactly will I need to let my
> system know? (I have read udev docs briefly, but was a> little confused)You don't necessarily have to do this, but it is useful to run as anon-root user. See the following link for specific details:
http://lists.gnu.org/archive/html/discuss-gnuradio/2006-06/msg00213.html___
Discuss-gnuradio mailing listDiscuss-gnuradio@gnu.orghttp://lists.gnu.org/mailman/listinfo/discuss-gnuradio
-- MarkAE6RT
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Python docs
Good day.I'd like to know more about the Python doc problem.http://lists.gnu.org/archive/html/discuss-gnuradio/2005-01/msg00249.html
From what I can tell, generating python docs for gnuradio is an outstanding taskhttp://www.comsec.com/wiki?SuggestedProjectsI say this because I do not see xsltproc, for example, called anywhere during build, and I think if this problem were already solved, I probably would.
While I cannot yet volunteer to work on this problem, a bit of status on where it is would be helpful.Some things I believe and/or have executed:- Being new to swig and python and its uses in given situations, I'm still a bit disoriented wrto which gnuradio-core ("core") piece dovetails into what other piece.
I think it goes like this:In the beginning, there was C++. From that follows python interfaces into C++ via swig. From there we find utility python code in the core written by some human and not a code generating tool. And from there we find python application code here and there.
- True or false (and why so either way): the documentation task above must be solved before we can produce, presumably with epydoc, html docs for *any* core python code.- Having compiled the core with --enable-doxygen, I notice that there are xml files in the output, presumably the ones mentioned in the mailing list post.
- I notice some %feature("autodoc","1") instances in some .i swig files. It appears we are incrementally solving the problem that is the subject of the mailing list posting above. - I see many .i files that do not contain "autodoc"/"docstring" directives. Not sure why, or what the implications are. (Notice how
this can mean "I disagree with what I see" or "Someone tell me why I see what I see, because I just don't know". I mean the latter.).- assuming we get to swig_doc.i files mentioned in the post, would there be one swig_doc.i file for every other .i file in the core?
- a general backing question: a python module can have code that originates in high level python code (a .py file) as well as code that comes to us by way of a swig interface. gnuradio.gr
, e.g., has a flow_graph via 'native' python code as well as a file_sink that comes to us via swig. Presumably we lack input that can generate docs for that swig interface object.- if this problem were already solved, can I get an example of an html file that would exist as a result? Just the file name, not the contents.
Thank you.-- Mark
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Creating a CW receiver for 20m ham band
Good day.Does anyone have GNU Radio code I can inspect to learn how to decode and render to audio CW transmissions in, say, the US amateur bands?Thank you.-- Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Which LinuxOS to use?-->1.Unbuntu, Fedora, Mandrake, FreeBSD
I , too, am an Ubuntu 6.06 user. What were you attempting to fix by modifying gnuradio-core/aclocal.m4?MarkOn 6/26/06, Robert McGwier < [EMAIL PROTECTED]> wrote:Lamar:I installed Ubunto 5.X and GnuRadio just made and ran after I used apt (synaptic) to download any package GnuRadio could not find. With Ubunto6.0X I had to make a modification to aclocal.m4 (and I am sure thereare other ways to fix it) in gnuradio-core but otherwise, it just compiled and ran. It is easy to install and maintain and with theopening up to universe, multiverse, nongpl code as opposed to Debian onwhich it is based, I find I am not building out of necessity. I haveCHOSEN (for example) to build swig.1.2.latest for various reasons but Idid not need to.BobLamar Owen wrote:> On Monday 26 June 2006 11:42, Marcus Leech wrote:>>> FC6 is just around the corner--the TEST1 release is already available. >> Sigh. Yeah, I had sworn I wasn't going to get back on the Fedora roller coaster;> that's why I use CentOS of the servers. But the needs of the bleeding edge> have conspired to cause me to go with FC5 the needs being driven by > GNUradio in part, and Plone in part. But with YUM, it's relatively painless to "keep up". Depending upon your bandwidth, at least.> --AMSAT VP Engineering. Member: ARRL, AMSAT-DL, TAPR, Packrats,NJQRP/AMQRP, QRP ARCI, QCWA, FRC. ARRL SDR Wrk Grp ChairmanTime for a new motto, what should I choose?___ Discuss-gnuradio mailing listDiscuss-gnuradio@gnu.orghttp://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- MarkAE6RT ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Boost: regarding not found shared_ptr.hpp
I installed boost in nonstandard location $HOME/gr, and thereby produced the same build failure as this gentleman http://lists.gnu.org/archive/html/discuss-gnuradio/2005-06/msg00282.html In my Linux environment, I set CPPFLAGS=-I$HOME/gr/include/boost-1_33_1export CPPFLAGSand where $ ls $HOME/gr/include/boost-1_33_1boostThis constitutes a third fix for this failed build situation. The first two being 1) install boost in a standard location so the preprocessor can find stuff without being told, and 2) pass --with-boost-include-dir=$HOME/gr/include/boost-1_33_1 to configure hth somebody.-- Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Release, website, and other notes.
On 26Jun, Eric Blossom wrote: > On Fri, Jun 24, 2005 at 01:46:15PM -0400, Lamar Owen wrote: > > With all the changes and bugfixes that have percolated down CVS, do we > > think > > we might be getting close to a 2.6 release? > > Sounds like a good idea. I'll need to coordinate with Matt to ensure What is the most informative way to report what release version one is running when using CVS builds? Thanks. Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gnuradio core build fails on make check
Ges, when I encountered a similar imponderable I inserted import sys print sys.path in a judicious place, just to see what path obtained at that moment. While it will not solve your immediate problem directly, it might be interesting to see what is your python sys.path when the failure occurs. > File "./qa_add_and_friends.py", line 23, in ? > from gnuradio import gr, gr_unittest > ImportError: No module named gnuradio iow, e.g., in gr-build/gnuradio-core/src/python/gnuradio/gr/qa_add_and_friends.py import sys print sys.path from gnuradio import gr, gr_unittest ... Or the moral equivalent. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gnuradio-core make check fails
Ges, This background may help http://lists.gnu.org/archive/html/discuss-gnuradio/2005-06/msg00214.html If you have not already solved your problem, do this as root $ find / -name libpython\* and send me the output off-list. We'll see if we can give you a workaround. Mark On 28Jun, Ges wrote: > Hi, > > Please forgive me for consecutive multiple posts. > I missed this earlier... > > when i run ./configure in gnuradio-core, i saw the > following.. > > checking for Python library path... > /usr/lib/python2.3/config > checking python extra libraries... > checking Python headers and library usability... > configure: WARNING: no dev lib > checking for swig... /usr0/local/gr/bin/swig > checking for SWIG version... 1.3.25 > checking for socket in -lsocket... no > checking for the pthreads library -lpthreads... no > checking whether pthreads work without any flags... no > checking whether pthreads work with -Kthread... no > checking whether pthreads work with -kthread... no > checking for the pthreads library -llthread... no > checking whether pthreads work with -pthread... yes > checking for joinable pthread attribute... > PTHREAD_CREATE_JOINABLE > checking if more special flags are required for > pthreads... no > > It says "no dev lib" found for python headers and > library usability. > > I am not sure if this is the problem. > > I could find libpython.2.3.a but not libpython.so. I > saw some old posts regarding this! > I have installed python-devel rpm for 2.3.2. are any > other packages missing other than python and > python-devel > > > If anyone thinks its easier to get things running on a > different environment maybe Fedora Core 2 or Fedora > Core 3, I could try that. I am trying to use gnuradio > for my research work, so i owuld like to get it up n > running as quickly as possible. > > Thank you > > -Gesly George > > --- Ramakrishnan Muthukrishnan <[EMAIL PROTECTED]> > wrote: > > > On Tue, June 28, 2005 10:30 am, Ges said: > > > Hi, > > > I am a newbie trying to build gnuradio...i was > > > following the instructions at > > > > > http://www.kd7lmo.net/ground_gnuradio_baseline.html. > > > > > > Well, after installing all the required base > > software, > > > i checked out the latest code from CVS... > > > > > > but make check on gnuradio-core fails... > > > .. > > > .. > > > I went through but i couldnt find anything that > > would > > > fix this. > > > > > > I am trying this on RedHat 9 with Python 2.3.2 and > > > Swig 1.3.25. I have also tried Swig 1.3.24 and was > > > initially using Python 2.2,since I thought the > > errors > > > might have to do with Python and Swig. But I still > > get > > > the same errors listed above. > > > > Which version of gcc? > > > > g++ --version > > > > There are known issues with gcc-3.3. On Debian many > > people have found > > issues with gcc-3.3 but 3.4 seem to be fine. So may > > be you can try with > > gcc-3.4. > > > > -- > > Ramakrishnan > > > > > > > > > __ > Yahoo! Mail > Stay connected, organized, and protected. Take the tour: > http://tour.mail.yahoo.com/mailtour.html > > > > ___ > 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] Gentoo build from CVS: success and notes
info/fyi For the archives, some notes on building gnuradio from the current state of CVS in a Gentoo 2005.0 environment. I've now built gnuradio from CVS and successfully run some OTA files referenced below. Time to buy a USRP! Below, "Gentoo emerge" is Gentoo parlance for "install" a particular software package. - Gentoo 2005.0 stage2 build - causes most of the system to be built from the ground up via source compilation, which took a couple (read a few) days. Some of this time was spent thrashing around and chin-scratching, wondering "what just happened?" - http://www.gentoo.org/doc/en/gentoo-x86-quickinstall.xml (terse, but good) - or http://www.gentoo.org/doc/en/handbook/2005.0/handbook-x86.xml?style=printable&full=1 (verbose) - ensure ALSA and USB 2.0 support during kernel build - Gentoo emerge the update to gcc 3.4.4 immediately after the 'system' build (speculative) - http://gentoo-wiki.com/HOWTO_Migrate_to_GCC_3.4 - else recompile existing key packages that require libstdc++.so.5 (experience) - for i in `find / -type f`; do echo $i ; ldd $i 2>/dev/null | grep "not found"; done # gross, but tells - Gentoo emerge packages xorg-x11, libusb, tetex (Tex/LaTex), libusb, hotplug, coldplug, boost, urw-fonts-2.1-r2, alsa-headers(?) - Gentoo emerge other useful packages such as usbutils, pciutils, xmms, sox, alsa-utils, etc - For CVS builds of gnuradio - install base packages per http://www.kd7lmo.net/ground_gnuradio_baseline.html - but use swig 1.3.23, and not the later 1.3.25 - if swig1.3.25 python "ImportError: cannot import name buffer" results during gnuradio-core make checks - CVS checkout gnuradio code http://comsec.com/wiki?HowtoBuildFromCVS - place "$python_path" first in "for" list in all instances of file gnuradio-core/config/gr_python.m4 - else static libpython is found first and configure's test program fails to link - recall "no dev lib" warning re configure's python development lib check - make sure PKG_CONFIG_PATH is set and contains $HOME/gr/lib/pkgconfig/ # per http://www.kd7lmo.net/ground_gnuradio_baseline.html $BUILD/gr-build/gnuradio-core/ $BUILD/gr-build/usrp/ where $BUILD/gr-build results from the main gnuradio CVS checkout http://comsec.com/wiki?HowtoBuildFromCVS - replace PYTHONPATH="$swigbld:$swigbld/.libs:$swigsrc:$py" with PYTHONPATH="$PYTHONPATH:$swigbld:$swigbld/.libs:$swigsrc:$py" in file gr-build/gnuradio-core/src/python/gnuradio/gr/run_tests.in - ./for-all-dirs ../buildit 2>&1 | tee make.log # per http://comsec.com/wiki?HowtoBuildFromCVS - Test by running OTA samples here http://www.kd7lmo.net/ground_gnuradio_ota.html using python code here http://www.kd7lmo.net/ground_gnuradio_ota.html (Thanks, KD7LMO!) Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] PYTHONPATH issue regarding missing Numeric module during CVS builds
There was earlier some discussion surrounding why Numeric cannot be found during the build tests http://lists.gnu.org/archive/html/discuss-gnuradio/2005-04/msg00135.html The problem is manifested by a console message to the effect ImportError: No module named Numeric I encountered the same problem, and fixed by changing PYTHONPATH="$swigbld:$swigbld/.libs:$swigsrc:$py" to PYTHONPATH="$PYTHONPATH:$swigbld:$swigbld/.libs:$swigsrc:$py" in the file gr-build/gnuradio-core/src/python/gnuradio/gr/run_tests.in Prior to the "for-all-dirs" build process, PYTHONPATH must contain an element that points to the Numeric module. For example PYTHONPATH=/home/petrovic/gr/lib/python2.3/site-packages:/home/petrovic/gr/lib/python2.3/site-packages/Numeric:/usr/lib/python2.3/site-packages export PYTHONPATH per KL7LMO's Numeric installation instructions http://www.kd7lmo.net/ground_gnuradio_ota.html Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] SIGBUS in testing gr_vmcircbuf_mmap_shm_open_factory
fyi Offered as a data point for this platform, for contemporary users or those of posterity... Building from CVS for this platform Linux cq 2.6.11-gentoo-r11 #3 Sat Jun 18 20:11:08 PDT 2005 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux gcc v3.4.4 runs an equivalent test $ gdb .libs/lt-test_vmcircbuf $ run -v [...] Testing gr_vmcircbuf_mmap_shm_open_factory... [...] which results in [...] ... test_a_bunch_64x16KB[63] OK Program received signal SIGBUS, Bus error. [Switching to Thread 16384 (LWP 2655)] 0xb7f71c53 in test_a_bunch (factory=0x804a3a0, n=32, size=4194304, start_ptr=0xb5bc, verbose=true) at gr_vmcircbuf.cc:125 125 p[i] = counter + i; The other "factory" tests (gr_vmcircbuf_sysv_shm_factory, gr_vmcircbuf_mmap_tmpfile_factory) in the suite pass. Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] static libpython3.2.a issue while building gnuradio-core from CVS
On 21Jun, Eric Blossom wrote: > On Tue, Jun 21, 2005 at 07:08:06AM -0700, Mark S Petrovic wrote: > > I've deduced that there are things known about this issue, or a related > > issue, as I saw similar discussion here > > > > http://lists.gnu.org/archive/html/discuss-gnuradio/2005-05/msg00148.html > > > > However, I provide what I believe may be related detail and > > reproducibility that may be helpful. > > > > In the course of building (not running) gnuradio-core from CVS, I > > encounter an unresolved symbol issue related to a static libpython > > library in Python 2.3.5. > > Hi Mark, > > Thanks for the info. Happy to do so. > When I get a bit of spare time, I'm going to back out the dependency > on -no-undefined and libpython. It's currently breaking the AMD64 and > OS/X builds too. These particular options are only required when building > windows DLLs, and the autoconf code should be changed to only use them > on the windows related environment like Cygwin and MinGW. Until this dependency is backed out, does the failure of the test program, which generates only a configure warning, indicate that the code will otherwise not fully compile or the runtime gnuradio not function properly? iow, until you make the change, can one simply ignore the "no dev lib" warning re libpython during configure? Thanks. Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] static libpython3.2.a issue while building gnuradio-core from CVS
> > 2. Python 2.3.5 built from source with --enable-shared and linked with > > -export-dynamic produces the following libraries > > > > $ find /usr/lib -name libpython\* |xargs ls -l > > lrwxrwxrwx 1 root root 19 Jun 20 13:06 /usr/lib/libpython2.3.so -> > > libpython2.3.so.1.0 > > -r-xr-xr-x 1 root root 944568 Jun 20 13:06 /usr/lib/libpython2.3.so.1.0 > > -rw-r--r-- 1 root root 1479196 Jun 20 13:06 > > /usr/lib/python2.3/config/libpython2.3.a > > what outputs "ldd /usr/lib/libpython2.3.so.1.0" ? $ ldd /usr/lib/libpython2.3.so.1.0 linux-gate.so.1 => (0xe000) libpthread.so.0 => /lib/libpthread.so.0 (0xb7eb9000) libdl.so.2 => /lib/libdl.so.2 (0xb7eb4000) libutil.so.1 => /lib/libutil.so.1 (0xb7eb) libm.so.6 => /lib/libm.so.6 (0xb7e8a000) libc.so.6 => /lib/libc.so.6 (0xb7d58000) /lib/ld-linux.so.2 (0x8000) ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] static libpython3.2.a issue while building gnuradio-core from CVS
On 21Jun, Mark S Petrovic wrote: > As a result, the python dev lib test program as seen in > gnuradio-core/config.log > > gcc -o conftest -g -O2 -Wall -I/usr/include/python2.3 conftest.c > -L/usr/lib/python2.3/config -lpython2 > .3 -lpthread -ldl -lutil >&5 > > does not succeed in linking because libpython2.3.a has unresolved math > symbols. For example, from config.log I should have mentioned that the failure to link the test program causes configure to print to the console the message checking Python headers and library usability... configure: WARNING: no dev lib I also should have asked: what is the best way to deal with the static lib issue? Is Python on my system somehow built incompatibly with gnuradio build suite? Should the static library be removed (sounds like a bad idea)? Should gr_python.m4 be modified to find the .so first? Thanks. Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] static libpython3.2.a issue while building gnuradio-core from CVS
I've deduced that there are things known about this issue, or a related issue, as I saw similar discussion here http://lists.gnu.org/archive/html/discuss-gnuradio/2005-05/msg00148.html However, I provide what I believe may be related detail and reproducibility that may be helpful. In the course of building (not running) gnuradio-core from CVS, I encounter an unresolved symbol issue related to a static libpython library in Python 2.3.5. 1. My environment: Gentoo Linux 2005.0 Linux cq 2.6.11-gentoo-r11 #2 Thu Jun 16 17:29:09 PDT 2005 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux gcc v3.4.4 autoconfv2.59 automakev1.9.5 libtool v1.5.16 swigv1.3.25 python v2.3.5 pkg-config v0.15.0 2. Python 2.3.5 built from source with --enable-shared and linked with -export-dynamic produces the following libraries $ find /usr/lib -name libpython\* |xargs ls -l lrwxrwxrwx 1 root root 19 Jun 20 13:06 /usr/lib/libpython2.3.so -> libpython2.3.so.1.0 -r-xr-xr-x 1 root root 944568 Jun 20 13:06 /usr/lib/libpython2.3.so.1.0 -rw-r--r-- 1 root root 1479196 Jun 20 13:06 /usr/lib/python2.3/config/libpython2.3.a 3. via the invocation of "buildit" on gnuradio-core/, we get ./bootstrap && ./configure --enable-maintainer-mode which drives the execution of gr-build/gnuradio-core/config/gr_python.m4. gr_python.m4 has in its PYTHON_DEVEL macro (see in gr_python.m4 "# Check for Python headers usability") a loop that searches for libpython$PYTHON_VERSION.*. The loop list for i in "$python_path/lib/python$PYTHON_VERSION/" "$python_path/lib/python$PYTHON_VERSION/config/" "$python_pat h/lib/python/config/" "$python_path/lib/python/" "$python_path/" "$python_path/libs" is ordered in such a way that /usr/lib/python2.3/config/libpython2.3.a is found before /usr/lib/libpython2.3.so. As a result, the python dev lib test program as seen in gnuradio-core/config.log gcc -o conftest -g -O2 -Wall -I/usr/include/python2.3 conftest.c -L/usr/lib/python2.3/config -lpython2 .3 -lpthread -ldl -lutil >&5 does not succeed in linking because libpython2.3.a has unresolved math symbols. For example, from config.log /usr/lib/python2.3/config/libpython2.3.a(complexobject.o)(.text+0x2fe): In function `_Py_c_pow': : undefined reference to `hypot' where $ nm /usr/lib/python2.3/config/libpython2.3.a |grep hypot U hypot 4. From my narrow perspective, I can "fix" this problem by moving "$python_path/" to the front of the "for" loop in gr_python.m4, such that /usr/lib/libpython2.3.so is found before the static lib version /usr/lib/python2.3/config/libpython2.3.a. Doing so allows the test program to link to the .so version of the library, which results in a successful linking of the test program. Or, one can fix by linking the test program to libm, but that doesn't sound right. Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] fm_demod.py
Hi, I am executing the FM demodulator example provided in the gnuradio examples (gnuradio-examples-0.3) and have three questions. 1. Does the program require two input frequencies or one? 2. If I type ./fm_demod.py 97.5 94.5 does this mean that signal between 97.5MHz and 94.5MHz will be demodulated? Will this then demodulate 96.5MHz. 3. If I type ./fm_demod.py 104.7 does this mean that signal at 104.7 will be demodulated? Thanks for the advice, Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Using PCI DAS4020/12 with the example program provided
Hi, I have the PCI DAS4020/12 installed on my PC. I am attempting to run the FM demodulator example provided in the gnuradio examples (in gnuradio-examples-0.3). I have two questions. 1. What input frequency ranges is the program looking for? 2. When I run the program inputing 104 as the input freq, I get the following error: /dev/parport0: permission denied. Aborted. Is anyone using the PCI DAS4020/12 and able the run the FM demodulator example provided? I have installed the mc4020 module as well. Thanks for any help. Mark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
