|
| From: | 汤图杨 |
| Subject: | [Discuss-gnuradio] RE: Discuss-gnuradio Digest, Vol 78, Issue 23 |
| Date: | Sun, 24 May 2009 11:00:01 +0800 |
|
Hi : Few days ago i typed the following commands to install the BBN 80211 address@hidden bbn_80211]#./configure address@hidden bbn_80211]#./make address@hidden bbn_80211]#./make check address@hidden bbn_80211]#./make install and the info that the system showed did not seem to be abnormal . but when i used the following command to run a example : address@hidden bbn_80211]#./src/examples/bbn_80211b_tx.py Traceback (most recent call last): File "./src/examples/bbn_80211b_tx.py", line 28, in <module> from gnuradio import gr, gru, blks ImportError: cannot import name blks thanks Xiaoming > Date: Sat, 23 May 2009 12:00:35 -0400 > From: address@hidden > Subject: Discuss-gnuradio Digest, Vol 78, Issue 23 > To: address@hidden > > Send Discuss-gnuradio mailing list submissions to > address@hidden > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > or, via email, send a message with subject or body 'help' to > address@hidden > > You can reach the person managing the list at > address@hidden > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Discuss-gnuradio digest..." > > > Today's Topics: > > 1. build error on OS X 10.4: ld: multiple definitions of symbol > _posix_memalign (Alexander List) > 2. Bit Recovery on Oversampled Signal (Tom Lutz) > 3. Eugene Grayver is out of the office. (Eugene Grayver) > 4. Re: USRP Quartus project same version as GNURadio ? > (Sebastiaan Heunis) > 5. Re: USRP Quartus project same version as GNURadio ? (Mark Porter) > 6. Re: Using a USRP as a PID feeback controller (Aviv Keshet) > 7. Re: build error on OS X 10.4: ld: multiple definitions of > symbol _posix_memalign (Michael Dickens) > 8. Anyone on this list have a SheevaPlug (Marcus D. Leech) > 9. Re: Anyone on this list have a SheevaPlug (Philip Balister) > 10. Re: USRP Quartus project same version as GNURadio ? (Mark Porter) > 11. Re: USRP Quartus project same version as GNURadio ? (Eric Blossom) > 12. Re: USRP Quartus project same version as GNURadio ? (Eric Blossom) > 13. Re: Using a USRP as a PID feeback controller (Aviv Keshet) > 14. Re: Using a USRP as a PID feeback controller (Marcus D. Leech) > 15. Build tree versus Install Tree (Tom Lutz) > 16. New doxygen docs (Eric Blossom) > 17. Re: Build tree versus Install Tree (Eric Blossom) > 18. Re: Build tree versus Install Tree (Tom Lutz) > 19. Re: build error on OS X 10.4: ld: multiple definitions of > symbol _posix_memalign (Alexander List) > 20. 'optparser' folder location (Ahmed Majeed Khan) > 21. Re: 'optparser' folder location (Eric Blossom) > 22. Re: New doxygen docs (address@hidden) > 23. Ways to limit stored vector length with file_sink( ) (Yc Park) > 24. Re: Ways to limit stored vector length with file_sink( ) > (Sebastiaan Heunis) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 22 May 2009 18:02:02 +0200 > From: Alexander List <address@hidden> > Subject: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple > definitions of symbol _posix_memalign > To: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > 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-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-3.2/omnithread/.libs/libgromnithread.dylib > /Users/alex/Documents/work/nc-projects/gr/gnuradio-3.2/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[5]: *** [libgnuradio-core-qa.la] Error 1 > make[4]: *** [all-recursive] Error 1 > make[3]: *** [all-recursive] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > ---8<--- > > Any hints? > > Alex > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 249 bytes > Desc: not available > Url : http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20090522/ad251bcb/signature.bin > > ------------------------------ > > Message: 2 > Date: Fri, 22 May 2009 12:44:15 -0400 > From: Tom Lutz <address@hidden> > Subject: [Discuss-gnuradio] Bit Recovery on Oversampled Signal > To: address@hidden > Message-ID: > <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > I believe there was some discussion recently on this, and I'd like to > hear more about what everyone thinks... > > I need to recover bits from a binary data stream, and I'm wondering if > there is something better than the M&M loop to do so, as I have many > samples per symbol. > > I didn't see any existing blocks that would do this, but maybe one of > you knows an algorithm or white paper I can read and implement. > > > Thanks, > Tom > > > > > ------------------------------ > > Message: 3 > Date: Fri, 22 May 2009 10:00:25 -0700 > From: Eugene Grayver <address@hidden> > Subject: [Discuss-gnuradio] Eugene Grayver is out of the office. > To: address@hidden > Message-ID: > <address@hidden> > > Content-Type: text/plain; charset=US-ASCII > > > I will be out of the office starting 05/22/2009 and will not return until > 06/11/2009. > > I will be checking my e-mail periodically. > > > > > > ------------------------------ > > Message: 4 > Date: Fri, 22 May 2009 19:08:30 +0200 > From: Sebastiaan Heunis <address@hidden> > Subject: Re: [Discuss-gnuradio] USRP Quartus project same version as > GNURadio ? > To: Mark Porter <address@hidden> > Cc: Gnuradio <address@hidden> > Message-ID: > <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > Mark > > Have you made sure that the .rbf is in /usr/local/share/usrp/rev4? > Also, I think that when you issue ls -l when you are in the directory > containing the .rbf file, you should get: > > -rw-r--r-- usrp_std.rbf > > Sebastiaan > > > > > ------------------------------ > > Message: 5 > Date: Fri, 22 May 2009 13:28:27 -0400 > From: Mark Porter <address@hidden> > Subject: Re: [Discuss-gnuradio] USRP Quartus project same version as > GNURadio ? > To: Sebastiaan Heunis <address@hidden> > Cc: Gnuradio <address@hidden> > Message-ID: > <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > Thanks for the pointers. > > I had already put my RBF where the others are (/usr/share/usrp/rev4) and the > others (e.g. std_4rx_0tx.rbf) are working. > I fixed my file permissions, it is still not working, I was root anyway... > > Other hypotheses : Newer version of Quartus, gnuradio not built on Windows > machine (only using fpga files in /usrp/fpga/...), std.ihx from same version > as the one used to compile verilog. > > Thanks for your input > > Mark > > On Fri, May 22, 2009 at 1:08 PM, Sebastiaan Heunis <address@hidden>wrote: > > > Mark > > > > Have you made sure that the .rbf is in /usr/local/share/usrp/rev4? > > Also, I think that when you issue ls -l when you are in the directory > > containing the .rbf file, you should get: > > > > -rw-r--r-- usrp_std.rbf > > > > Sebastiaan > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20090522/2502bcad/attachment.html > > ------------------------------ > > Message: 6 > Date: Fri, 22 May 2009 13:28:19 -0400 > From: Aviv Keshet <address@hidden> > Subject: Re: [Discuss-gnuradio] Using a USRP as a PID feeback > controller > To: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > I've posted my verilog sources. Here is my modified top-level usrp module: > http://web.mit.edu/~akeshet/www/USRP_PID/usrp_std.v > > The PID feedback module is here: > http://web.mit.edu/~akeshet/www/USRP_PID/PIDfeedback.v > > One more accessory module for doing arithmetic is here: > http://web.mit.edu/~akeshet/www/USRP_PID/SignedRightShiftingTruncator.v > > > The USRP top level module is, of course, under the GPL. The other 2 source files > I release to the public domain. No warranties, expressed or implied, blah blah > blah. > > In testing, when connecting the control signal output directly into the > controller's measure input, I was able to achieve settling times of .5 to 1 us. > > Aviv > > > > > ------------------------------ > > Message: 7 > Date: Fri, 22 May 2009 13:40:18 -0400 > From: Michael Dickens <address@hidden> > Subject: Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple > definitions of symbol _posix_memalign > To: Alexander List <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > 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 > > =================================================================== > --- gnuradio-core/src/lib/Makefile.am (revision 11081) > +++ gnuradio-core/src/lib/Makefile.am (working copy) > @@ -59,6 +59,5 @@ > filter/libfilter-qa.la \ > general/libgeneral-qa.la \ > runtime/libruntime-qa.la \ > - missing/libmissing.la \ > libgnuradio-core.la \ > $(CPPUNIT_LIBS) > > > > > > ------------------------------ > > Message: 8 > Date: Fri, 22 May 2009 13:55:23 -0400 > From: "Marcus D. Leech" <address@hidden> > Subject: [Discuss-gnuradio] Anyone on this list have a SheevaPlug > To: GNURadio Discussion List <address@hidden> > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > I just saw on slashdot an announcement of a interesting device, > SheevaPlug, which is roughly the size of a large wall-wart, and > boasts a 1.2GHz ARM9 like CPU, 512M ram, with 512M flash, USB 2.0, > and a GbE port. > > Anyone on this list happen to have one? > > -- > Marcus Leech > Principal Investigator, Shirleys Bay Radio Astronomy Consortium > http://www.sbrac.org > > > > > > ------------------------------ > > Message: 9 > Date: Fri, 22 May 2009 14:12:13 -0400 > From: Philip Balister <address@hidden> > Subject: Re: [Discuss-gnuradio] Anyone on this list have a SheevaPlug > To: "address@hidden Org" <address@hidden> > Message-ID: <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > Marcus D. Leech wrote: > > I just saw on slashdot an announcement of a interesting device, > > SheevaPlug, which is roughly the size of a large wall-wart, and > > boasts a 1.2GHz ARM9 like CPU, 512M ram, with 512M flash, USB 2.0, > > and a GbE port. > > > > Anyone on this list happen to have one? > > No, but the ARM9 has no floating point support. Get a Beagle/Overo :) > It still might be interesting to run Gnuradio on, but it will take lots > of work to convert the floating point to the ARM9 "dsp" instructions. > > If you are still interested, I'm pretty sure Angstrom is running on it, > and I explain how to get gnuradio running. > > Philip > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: smime.p7s > Type: application/x-pkcs7-signature > Size: 3303 bytes > Desc: S/MIME Cryptographic Signature > Url : http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20090522/bf0ba802/smime.bin > > ------------------------------ > > Message: 10 > Date: Fri, 22 May 2009 14:30:19 -0400 > From: Mark Porter <address@hidden> > Subject: Re: [Discuss-gnuradio] USRP Quartus project same version as > GNURadio ? > To: Sebastiaan Heunis <address@hidden> > Cc: Gnuradio <address@hidden> > Message-ID: > <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > Issue fixed thanks. > > On Fri, May 22, 2009 at 1:28 PM, Mark Porter <address@hidden>wrote: > > > Thanks for the pointers. > > > > I had already put my RBF where the others are (/usr/share/usrp/rev4) and > > the others (e.g. std_4rx_0tx.rbf) are working. > > I fixed my file permissions, it is still not working, I was root anyway... > > > > Other hypotheses : Newer version of Quartus, gnuradio not built on Windows > > machine (only using fpga files in /usrp/fpga/...), std.ihx from same version > > as the one used to compile verilog. > > > > Thanks for your input > > > > Mark > > > > > > On Fri, May 22, 2009 at 1:08 PM, Sebastiaan Heunis <address@hidden>wrote: > > > >> Mark > >> > >> Have you made sure that the .rbf is in /usr/local/share/usrp/rev4? > >> Also, I think that when you issue ls -l when you are in the directory > >> containing the .rbf file, you should get: > >> > >> -rw-r--r-- usrp_std.rbf > >> > >> Sebastiaan > >> > > > > > > > > > > > -- > Mark > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20090522/5f24e79b/attachment.html > > ------------------------------ > > Message: 11 > Date: Fri, 22 May 2009 11:36:41 -0700 > From: Eric Blossom <address@hidden> > Subject: Re: [Discuss-gnuradio] USRP Quartus project same version as > GNURadio ? > To: Mark Porter <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > On Fri, May 22, 2009 at 11:34:49AM -0400, Mark Porter wrote: > > Hi, > > > > I'm trying to RUN my own RBF file with the Quartus project (usrp_std.qpf). > > The compilation goes through and I get usrp_std.rbf . However when I try to > > create a usrp source like so : > > > > self.fpga_filename = "usrp_std.rbf" > > self.u = usrp.source_c (decim_rate = self.usrp_decim, > > fpga_filename=self.fpga_filename, mux =0) > > > > I get an error > > > > File "/usr/lib/python2.6/site-packages/gnuradio/usrp/usrp_swig.py", line > > 1607 in source_c > > return _usrp_swig.source_c(*args, **kwargs) > > *RuntimeError: can't open usrp* > > > > *Using the precompiled rbf works flawlessly (e.g. std_4rx_0tx.rbf)* > > > > Does the Quartus project have to come from the exact same gnuradio version > > as the one running on the device (I have release 3.1.3 on Quartus and > > 3.1.3+svn10302 r6.1 on the device itself) ? > > > > Thanks > > Mark > > Mark, > > Can you please post the entire backtrace? If the library can't find > your code, it'll print something like, > > fprintf (stderr, "Can't find fpga bitstream: %s\n", proto_filename); > > Eric > > > > > ------------------------------ > > Message: 12 > Date: Fri, 22 May 2009 11:45:30 -0700 > From: Eric Blossom <address@hidden> > Subject: Re: [Discuss-gnuradio] USRP Quartus project same version as > GNURadio ? > To: Mark Porter <address@hidden> > Cc: Gnuradio <address@hidden> > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > On Fri, May 22, 2009 at 02:30:19PM -0400, Mark Porter wrote: > > Issue fixed thanks. > > So that the archive has the answer, what was the fix? > > Eric > > > > On Fri, May 22, 2009 at 1:28 PM, Mark Porter <address@hidden>wrote: > > > > > Thanks for the pointers. > > > > > > I had already put my RBF where the others are (/usr/share/usrp/rev4) and > > > the others (e.g. std_4rx_0tx.rbf) are working. > > > I fixed my file permissions, it is still not working, I was root anyway... > > > > > > Other hypotheses : Newer version of Quartus, gnuradio not built on Windows > > > machine (only using fpga files in /usrp/fpga/...), std.ihx from same version > > > as the one used to compile verilog. > > > > > > Thanks for your input > > > > > > Mark > > > > > > > > > On Fri, May 22, 2009 at 1:08 PM, Sebastiaan Heunis <address@hidden>wrote: > > > > > >> Mark > > >> > > >> Have you made sure that the .rbf is in /usr/local/share/usrp/rev4? > > >> Also, I think that when you issue ls -l when you are in the directory > > >> containing the .rbf file, you should get: > > >> > > >> -rw-r--r-- usrp_std.rbf > > >> > > >> Sebastiaan > > >> > > > > > ------------------------------ > > Message: 13 > Date: Fri, 22 May 2009 15:29:33 -0400 > From: Aviv Keshet <address@hidden> > Subject: Re: [Discuss-gnuradio] Using a USRP as a PID feeback > controller > To: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > It's been pointed out that I have committed the sin of using undefined jargon. > For the record, PID stands for Proportional Integral Derivative. > > PID is a ubiquitous type of feedback controller, mostly thanks to being > conceptually quite simple. The input is an error signal (or a measurement and > setpoint signal) of some process under control. The PID controller applies 3 > types of feedback: > > P - proportional, in which the control output is proportional to the error > signal. > I - integral, in which the control output is proportion to the time-integral of > the error signal. > D - derivative, in which the control output is proportional to the > time-derivative of the error signal. > > These three terms are added together to produce the control output. By the right > selection ("tuning") of the 3 gain values, stable feedback control of a wide > variety of processes is possible. > > > > > ------------------------------ > > Message: 14 > Date: Fri, 22 May 2009 15:37:31 -0400 > From: "Marcus D. Leech" <address@hidden> > Subject: Re: [Discuss-gnuradio] Using a USRP as a PID feeback > controller > To: Aviv Keshet <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > Aviv Keshet wrote: > > It's been pointed out that I have committed the sin of using undefined jargon. > > For the record, PID stands for Proportional Integral Derivative. > > > > PID is a ubiquitous type of feedback controller, mostly thanks to being > > conceptually quite simple. The input is an error signal (or a measurement and > > setpoint signal) of some process under control. The PID controller applies 3 > > types of feedback: > > > > P - proportional, in which the control output is proportional to the error > > signal. > > I - integral, in which the control output is proportion to the time-integral of > > the error signal. > > D - derivative, in which the control output is proportional to the > > time-derivative of the error signal. > > > > These three terms are added together to produce the control output. By the right > > selection ("tuning") of the 3 gain values, stable feedback control of a wide > > variety of processes is possible. > > > > > > > We'll be using a couple of PID control systems for our big dish. > > -- > Marcus Leech > Principal Investigator, Shirleys Bay Radio Astronomy Consortium > http://www.sbrac.org > > > > > > ------------------------------ > > Message: 15 > Date: Fri, 22 May 2009 17:36:16 -0400 > From: Tom Lutz <address@hidden> > Subject: [Discuss-gnuradio] Build tree versus Install Tree > To: address@hidden > Message-ID: > <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > Is there an easy way to test out my code modifications without doing > 'make install'? It takes so long... > > Thanks, > Tom > > > > > ------------------------------ > > Message: 16 > Date: Fri, 22 May 2009 14:55:12 -0700 > From: Eric Blossom <address@hidden> > Subject: [Discuss-gnuradio] New doxygen docs > To: Firas Abbas <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > On Thu, May 21, 2009 at 09:50:23PM -0700, Firas Abbas wrote: > > > > Hi, > > > > > On Thu, 5/21/09, Ankit Saf <address@hidden> wrote: > > > > > > I'll go a step further and ask if there is are more help files on available GNU radio blocks, and > > > about writing your own block? > > > > > > Thanks! > > > > There is a old and un-updated document that lists Gnuradio blocks at: > > > > http://www.scribd.com/doc/9688074/Simple-Gnuradio-User-Manual-v10 > > > > > > Best Regards, > > Firas > > I've uploaded current doxygen generated docs. Click on the C++ blocks link to > get a list of blocks. > > http://gnuradio.org/doc/doxygen/index.html > > > Also, the code in the trunk has been modified so that it now builds > documentation by default. If you want to turn it off, use --disable-docs > at configure time. > > Eric > > > > > ------------------------------ > > Message: 17 > Date: Fri, 22 May 2009 14:56:42 -0700 > From: Eric Blossom <address@hidden> > Subject: Re: [Discuss-gnuradio] Build tree versus Install Tree > To: Tom Lutz <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > On Fri, May 22, 2009 at 05:36:16PM -0400, Tom Lutz wrote: > > Is there an easy way to test out my code modifications without doing > > 'make install'? It takes so long... > > > > Thanks, > > Tom > > If you've got QA code that was done according to the existing > framework, "make check" will run it without it having to be installed. > > Eric > > > > > ------------------------------ > > Message: 18 > Date: Fri, 22 May 2009 18:09:51 -0400 > From: Tom Lutz <address@hidden> > Subject: Re: [Discuss-gnuradio] Build tree versus Install Tree > To: Eric Blossom <address@hidden>, Tom Lutz <address@hidden>, > address@hidden > Message-ID: > <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > It's more like this: I want to use a block that I wrote in grc without > going through make install. > > On Fri, May 22, 2009 at 5:56 PM, Eric Blossom <address@hidden> wrote: > > On Fri, May 22, 2009 at 05:36:16PM -0400, Tom Lutz wrote: > >> Is there an easy way to test out my code modifications without doing > >> 'make install'? It takes so long... > >> > >> Thanks, > >> Tom > > > > If you've got QA code that was done according to the existing > > framework, "make check" will run it without it having to be installed. > > > > Eric > > > > > > > ------------------------------ > > Message: 19 > Date: Sat, 23 May 2009 00:12:11 +0200 > From: Alexander List <address@hidden> > Subject: Re: [Discuss-gnuradio] build error on OS X 10.4: ld: multiple > definitions of symbol _posix_memalign > To: Michael Dickens <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > 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 > > > > > ------------------------------ > > Message: 20 > Date: Fri, 22 May 2009 18:17:55 -0400 > From: "Ahmed Majeed Khan" <address@hidden> > Subject: [Discuss-gnuradio] 'optparser' folder location > To: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > > > Hi all, > I am trying to modify benchmark_rx.py and benchmark_tx.py but could not find the location of the folder "optparser" or the file "OptionParser.py" in my pc. Can anyone please comment over their location? > > Furthermore if these are not present in my pc, how can I still be able to run benchmark_rx.py and benchmark_tx.py successfully as both of these examples import functions from OptionParser.py. Waiting reply and thanking you in anticipation. > > -Ahmed > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20090522/fc55de5e/attachment.html > > ------------------------------ > > Message: 21 > Date: Fri, 22 May 2009 16:11:10 -0700 > From: Eric Blossom <address@hidden> > Subject: Re: [Discuss-gnuradio] 'optparser' folder location > To: Ahmed Majeed Khan <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > On Fri, May 22, 2009 at 06:17:55PM -0400, Ahmed Majeed Khan wrote: > > > > > > Hi all, > > > > I am trying to modify benchmark_rx.py and benchmark_tx.py but could > > not find the location of the folder "optparser" or the file > > "OptionParser.py" in my pc. Can anyone please comment over their > > location? > > > > Furthermore if these are not present in my pc, how can I still be > > able to run benchmark_rx.py and benchmark_tx.py successfully as both > > of these examples import functions from OptionParser.py. Waiting > > reply and thanking you in anticipation. > > > -Ahmed > > http://www.lmgtfy.com/?q=python+optparse > > > > > > ------------------------------ > > Message: 22 > Date: Fri, 22 May 2009 21:59:20 -0700 (PDT) > From: address@hidden > Subject: [Discuss-gnuradio] Re: New doxygen docs > To: Eric Blossom <address@hidden> > Cc: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=iso-8859-1 > > > Hi, > > > On Sat, 5/23/09, Eric Blossom <address@hidden> wrote: > > > > I've uploaded current doxygen generated docs. Click on the C++ blocks link to > > get a list of blocks. > > > > http://gnuradio.org/doc/doxygen/index.html > > > > Eric > > > > * Nice work after long waiting!. Thank you for this great efforts. > > * I think including C++ source code in the documentation (not only the .h files ) is better because if someone cannot understand the current API documentation he can click in the same page on the (.cc) source code and see how it is being implemented. Currently, if he want to do so, he must search gnuradio folders to find the required implementation file and then open it to see what he needs. > > * In the current documentation, we see : > > >>[Please note that at this time, we haven't found an acceptable way to provide unified documentation for the C++ parts of the system and the parts written in Python (mostly hierarchical blocks). Until this gets worked out, please bear with us, or better yet, solve it for us!]<< > > This is a mysterious statement. What is the target acceptable way? Is there an example how should this being done?. If we know what is required, may be we can help to find the required tool, or may be we can write a custom gnuradio documentation software that solves this problem. > > > > Best Regards, > > Firas > > > > > > > > > ------------------------------ > > Message: 23 > Date: Sat, 23 May 2009 08:58:49 +0200 > From: Yc Park <address@hidden> > Subject: [Discuss-gnuradio] Ways to limit stored vector length with > file_sink( ) > To: address@hidden > Message-ID: <address@hidden> > Content-Type: text/plain; charset=utf-8 > > Hi, > > I'm trying to record a complex vector out of usrp2 into a file. > > Since I'm a newbie with python, I started to implement it on GRC with > the file_sink and usrp2_source, though I can understand the generated > .py file. > > But when I run it, the file_sink records data forever until I force it > stop. > This easily gets more than hundred of megabytes of data. > > I tried with longer vector length with stream to vector module, but > nothing different. > > > So, does anybody know how to record a complex data with any given length > and stop? > > I'd appreciate any recommendations on GRC or .py commands. > > Best regards, > ycpark. > -- > Posted via http://www.ruby-forum.com/. > > > > > ------------------------------ > > Message: 24 > Date: Sat, 23 May 2009 11:42:55 +0200 > From: Sebastiaan Heunis <address@hidden> > Subject: Re: [Discuss-gnuradio] Ways to limit stored vector length > with file_sink( ) > To: address@hidden > Message-ID: > <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > YC > > I only have Gnuradio with a USRP1, but I assume the procedure should > be similar. There are two blocks, head and skiphead that allow you to > play around with where you want to start recording samples and how > many you record. > > Sebastiaan > > > > > ------------------------------ > > _______________________________________________ > Discuss-gnuradio mailing list > address@hidden > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > End of Discuss-gnuradio Digest, Vol 78, Issue 23 > ************************************************ 使用新一代 Windows Live Messenger 轻松交流和共享！ 立刻下载！ |
| [Prev in Thread] | Current Thread | [Next in Thread] |