Hi, I installed Labview UHD driver for USRP N210 on Windows 7. I burned the firmware and FPGA images provided from NI website. USRP is working perfectly with Labview on windows 7.
I tried using the same driver and images to use with Matlab 2010b. It did not work. Shouldn't the same UHD driver and images work with Matlab also? If it should, how? Does anyone know about it? Help will be much appreciated. Thanks, Khalid. On Sat, Feb 12, 2011 at 8:00 PM, <[email protected]> wrote: > Send Discuss-gnuradio mailing list submissions to > [email protected] > > 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 > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Discuss-gnuradio digest..." > > > Today's Topics: > > 1. Re: USRP1, FPGA and ADC clock (Matt Ettus) > 2. Re: GNU Radio Conference (Tom Rondeau) > 3. Re: channel coding questions (Achilleas Anastasopoulos) > 4. make errors in gnu radio 3.3.0 (Chomal, Sunil) > 5. Re: make errors in gnu radio 3.3.0 (Don Ward) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 11 Feb 2011 10:13:27 -0800 > From: Matt Ettus <[email protected]> > Subject: Re: [Discuss-gnuradio] USRP1, FPGA and ADC clock > To: Przemyslaw Dmochowski <[email protected]> > Cc: "[email protected]" <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > The FPGA and ADC are run off of the same clock, directly from the main > oscillator. They need to be the same frequency. Why would you want to > use different clocks? > > Matt > > > On 02/10/2011 05:15 AM, Przemyslaw Dmochowski wrote: > > Hi, > > > > I was wonder how the RX and TX data from/to ADC is read by Altera FPGA. > > > > I see from the schematics that FPGA and ADC take the clock from the same > > > > output of AD9513. > > > > From Ad9862 I read that the ADC data is latched using CLKOUT1, but this > > output is not connected > > > > to FPGA, so at which moment is the data from ADC sampled by FPGA, with > > which clock? > > > > And the same question about latching the DAC data in AD9862 send from > FPGA. > > > > I looked at the clock and it looks distorted and I wanted > > > > to separate the ADC and FPGA clocks. > > > > Is it possible to drive the FPGA and ADC from different clock sources? > Are > > > > different frequencies for FPGA and ADC allowed? > > > > Do the clocks have to be synchronized? If not how much phase shift > between > > > > ADC clock and FPGA clock is allowed? > > > > Thanks, > > > > Przemek > > > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > [email protected] > > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > ------------------------------ > > Message: 2 > Date: Fri, 11 Feb 2011 14:16:27 -0500 > From: Tom Rondeau <[email protected]> > Subject: Re: [Discuss-gnuradio] GNU Radio Conference > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > On Fri, Feb 4, 2011 at 9:44 AM, Martin Braun <[email protected]> wrote: > > Hi Tom, hi list, > > > > What's the status on the dates? At our lab, conference viѕits etc. for > > 2011 are currently being planned, so I thought I'd ping this thread. > > I guess it's unlikely someone will cross the atlantic "just" for a > week-end > > of GNU Radio (I'm not saying "wouldn't like to"), so if the dates aren't > > fixed yet, I would like to mention that putting said conference close to > > some other conference (say, something COMSOC or similar) might increase > > the chances of getting Europeans to participate. > > For example, PIMRC 2011 is in Toronto (practically 'round the corner :) > > from 5-8 September. > > > > Bye, > > MB > > Thanks Martin, I'll keep that in mind. I will try to work out soon > what the dates will be. And, yes, Toronto is pretty easy to get to, > and I wouldn't be surprised if a number of flights to/from Europe to > Toronto have a stop in PHL. > > Tom > > > > > On Fri, Jan 21, 2011 at 11:19:04AM -0500, Tom Rondeau wrote: > >> I want to have a separate thread for discussing the GNU Radio > >> conference details. Here is what we have so far: > >> > >> When: Sometime in September, 2011 > >> Where: Philadelphia, PA, USA – probably on the University of > Pennsylvania campus > >> How long: 2.5 – 3 days > >> > >> The first thing I would like to do is nail down the exact dates. There > >> are two ways we can go with this, and I'm polling the community here > >> to try to figure it out. We can either hold the conference during the > >> week or over a weekend. The weekend would look like (probably): Friday > >> afternoon, all day Saturday and Sunday. If we held it during the week, > >> I was thinking something like: all day Wednesday and Thursday and > >> Friday morning. > >> > >> There are certain people who will find either time better than the > >> other depending on your work/life situations. So we want to make sure > >> that this happens during the most convenient time for the most amount > >> of people. Once we figure this out, I will work on securing a location > >> to host the event. A show of hands for how many people think they can > >> attend would also help me determine what size we need to account for. > >> > >> Thanks, > >> Tom > > > > -- > > Karlsruhe Institute of Technology (KIT) > > Communications Engineering Lab (CEL) > > > > Dipl.-Ing. Martin Braun > > Research Associate > > > > Kaiserstraße 12 > > Building 05.01 > > 76131 Karlsruhe > > > > Phone: +49 721 608-43790 > > Fax: +49 721 608-46071 > > www.cel.kit.edu > > > > KIT -- University of the State of Baden-Württemberg and > > National Laboratory of the Helmholtz Association > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > [email protected] > > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > > > ------------------------------ > > Message: 3 > Date: Fri, 11 Feb 2011 14:59:15 -0500 > From: Achilleas Anastasopoulos <[email protected]> > Subject: Re: [Discuss-gnuradio] channel coding questions > To: gnuradio mailing list <[email protected]>, [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Ben, > > > I have a simple example of turbo coding/decoding (i think it is a sccc) > in the examples section of gr-trellis. It is SLOW! > I don't think there is any particular reason other than you are > essentially have to run 2 siso blocks per iteration, ie, roughly > 4 VA's per iteration (recall forward/backward pass)... > The comment i made about buffering is from my experience: > You can always get a better performance if you combine the functionality > of multiple gnuradio blocks into one gnuradio block... > > > Regarding suboptimal receivers, I don't have any intention of writing > code for them, but if anyone is willing to work seriously on that i can > help (maybe an undergrad student project for the summer...) > Similarly, for a turbo decoding hierarchical block: it is trivial to put > together siso blocks and do it (the code is essentially there: see the > python code in the examples). I can think of an sccc and a pccc block > whereby you define the 2 constituent FSMs (or even more), an interleaver > structure, and the number of iterations; that's all there is to it. > > Regarding integration with the "constellations" class i think it is a > wonderful idea. When I was writing gr-trellis I thought of > constellations as arbitrary one-dimensional look-up tables with n-dim > entries. Repackaging the "metrics" code to use constellations would be > great. > YES, I believe that the "constellations" class has to be general enough > to include n-dimensional constellations. What if you want to implement > 4-FSK, or even arbitrary CPM (I am currently working on that). > Also, there are trellis-codes that output 2 QPSK (or 2 8PSK) symbols at > every step and having these constellations as 1 2D complex constellation > makes integration with gr-trellis very easy... > > Achilleas > > > > ------------------------------ > > Message: 4 > Date: Sat, 12 Feb 2011 17:41:48 +0530 > From: "Chomal, Sunil" <[email protected]> > Subject: [Discuss-gnuradio] make errors in gnu radio 3.3.0 > To: "'[email protected]'" <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Hi, > I am trying to build the gnu radio (release 3.3.0) for the first time on my > windows pc. > I am following the steps as in > http://gnuradio.org/redmine/wiki/gnuradio/CygwinInstallMain > I have installed cygwin and the relevant packages as mention in the above > link. > I have also installed the boost package(boost_1_45_0) > > The link 'Hints,tips,known problems in windows' doesn't seems to address > the issue . > > I have seen somebody had posted a similar problem some time back. But I > could not follow exactly what is the solution. > > I have installed boost in the directory \usr\src\boost_1_45_0 > I tried setting the the environment variable LD_LIBRARY_PATH to this i.e > export LD_LIBRARY_PATH=/usr/src/boost_1_45_0/libs > > But this didn't work.... > > Anybody can help ??? > > > libtool: link: rm -fr .libs/libgruel.dll.a > libtool: link: g++ -shared -nostdlib > /usr/lib/gcc/i686-pc-cygwin/4.3.4/crtbegin. > o .libs/realtime.o .libs/sys_pri.o .libs/thread.o > .libs/thread_body_wrapper.o . > libs/thread_group.o -Wl,--whole-archive pmt/.libs/libpmt.a > msg/.libs/libmsg.a - > Wl,--no-whole-archive -L/usr/lib -lboost_thread-gcc-mt-1_33_1 > -L/usr/lib/gcc/i6 > 86-pc-cygwin/4.3.4 -L/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../.. > /usr/lib/gcc/i68 > 6-pc-cygwin/4.3.4/libstdc++.dll.a -lgcc_s -lgcc_s -lcygwin -luser32 > -lkernel32 - > ladvapi32 -lshell32 -lgcc_s -lgcc_s > /usr/lib/gcc/i686-pc-cygwin/4.3.4/crtend.o > -O2 -o .libs/cyggruel-3-3-0-0.dll -Wl,--enable-auto-image-base -Xlinker > --out- > implib -Xlinker .libs/libgruel.dll.a > Creating library file: .libs/libgruel.dll.a > .libs/thread_group.o: In function `_ZN5boost12shared_mutex4lockEv': > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:129: undefined > referenc > e to `boost::this_thread::disable_interruption::disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:137: undefined > referenc > e to `boost::this_thread::disable_interruption::~disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:137: undefined > referenc > e to `boost::this_thread::disable_interruption::~disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:129: undefined > referenc > e to `boost::this_thread::disable_interruption::disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:137: undefined > referenc > e to `boost::this_thread::disable_interruption::~disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:137: undefined > referenc > e to `boost::this_thread::disable_interruption::~disable_interruption()' > .libs/thread_group.o: In function `thread<boost::function0<void> >': > /usr/local/include/boost/thread/detail/thread.hpp:204: undefined reference > to `b > oost::thread::start_thread()' > .libs/thread_group.o: In function `_ZN5boost12shared_mutex11lock_sharedEv': > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:59: undefined > reference > to `boost::this_thread::disable_interruption::disable_interruption()' > .libs/thread_group.o: In function `shared_lock': > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:66: undefined > reference > to `boost::this_thread::disable_interruption::~disable_interruption()' > .libs/thread_group.o: In function `_ZN5boost12shared_mutex11lock_sharedEv': > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:66: undefined > reference > to `boost::this_thread::disable_interruption::~disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:59: undefined > reference > to `boost::this_thread::disable_interruption::disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:66: undefined > reference > to `boost::this_thread::disable_interruption::~disable_interruption()' > > .libs/thread_group.o:/home/a0876473/gnuradio-3.3.0/gruel/src/lib/thread_group.cc > :89: undefined reference to `boost::thread::interrupt()' > .libs/thread_group.o: In function `_ZN5boost12shared_mutex11lock_sharedEv': > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:66: undefined > reference > to `boost::this_thread::disable_interruption::~disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:59: undefined > reference > to `boost::this_thread::disable_interruption::disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:66: undefined > reference > to `boost::this_thread::disable_interruption::~disable_interruption()' > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:66: undefined > reference > to `boost::this_thread::disable_interruption::~disable_interruption()' > .libs/thread_group.o: In function `~thread_data': > /usr/local/include/boost/thread/detail/thread.hpp:42: undefined reference > to `bo > ost::detail::thread_data_base::~thread_data_base()' > /usr/local/include/boost/thread/detail/thread.hpp:42: undefined reference > to `bo > $ > /usr/local/include/boost/thread/detail/thread.hpp:42: undefined reference > to `bo > ost::detail::thread_data_base::~thread_data_base()' > /usr/local/include/boost/thread/detail/thread.hpp:42: undefined reference > to `bo > ost::detail::thread_data_base::~thread_data_base()' > .libs/thread_group.o: In function `interruption_checker': > /usr/local/include/boost/thread/pthread/thread_data.hpp:97: undefined > reference > to `boost::detail::get_current_thread_data()' > > .libs/thread_group.o:/usr/local/include/boost/thread/pthread/condition_variable. > hpp:55: undefined reference to `boost::this_thread::interruption_point()' > .libs/thread_group.o: In function `thread_data_base': > /usr/local/include/boost/thread/pthread/thread_data.hpp:67: undefined > reference > to `vtable for boost::detail::thread_data_base' > .libs/thread_group.o: In function `thread_data': > /usr/local/include/boost/thread/detail/thread.hpp:54: undefined reference > to `bo > ost::detail::thread_data_base::~thread_data_base()' > > .libs/thread_group.o:thread_group.cc:(.rdata$_ZTIN5boost6detail11thread_dataINS_ > 9function0IvEEEE[typeinfo for > boost::detail::thread_data<boost::function0<void> > >]+0x8): undefined reference to `typeinfo for > boost::detail::thread_data_base' > collect2: ld returned 1 exit status > make[5]: *** [libgruel.la] Error 1 > make[5]: Leaving directory `/home/a0876473/gnuradio-3.3.0/gruel/src/lib' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory `/home/a0876473/gnuradio-3.3.0/gruel/src/lib' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/home/a0876473/gnuradio-3.3.0/gruel/src' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/home/a0876473/gnuradio-3.3.0/gruel' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/a0876473/gnuradio-3.3.0' > make: *** [all] Error 2 > > Regards > Sunil > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20110212/264734dd/attachment.html > > ------------------------------ > > Message: 5 > Date: Sat, 12 Feb 2011 08:40:14 -0500 > From: "Don Ward" <[email protected]> > Subject: Re: [Discuss-gnuradio] make errors in gnu radio 3.3.0 > To: "Chomal, Sunil" <[email protected]>, <[email protected]> > Message-ID: <7845470E6FFE4D239558EE3A9841B668@amber> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > Chomal, Sunil wrote: > > > I am trying to build the gnu radio (release 3.3.0) for the first time on > > my windows pc. > > I am following the steps as in > > http://gnuradio.org/redmine/wiki/gnuradio/CygwinInstallMain > > I have installed cygwin and the relevant packages as mention in the above > > link. > [...] > > > > I have installed boost in the directory \usr\src\boost_1_45_0 > > I tried setting the the environment variable LD_LIBRARY_PATH to this i.e > > export LD_LIBRARY_PATH=/usr/src/boost_1_45_0/libs > > You shouldn't need this. > > [...] > > > > libtool: link: rm -fr .libs/libgruel.dll.a > > libtool: link: g++ -shared -nostdlib > > /usr/lib/gcc/i686-pc-cygwin/4.3.4/crtbegin. > > o .libs/realtime.o .libs/sys_pri.o .libs/thread.o > > .libs/thread_body_wrapper.o . > > libs/thread_group.o -Wl,--whole-archive pmt/.libs/libpmt.a > > msg/.libs/libmsg.a - > > Wl,--no-whole-archive -L/usr/lib -lboost_thread-gcc-mt-1_33_1 > -L/usr/lib/gcc/i6 > > The line above is looking for boost_thread-gcc-mt-1_33_1. > Apparently ./configure is finding boost 1.33.1 instead of 1.45.0. > Do you have the Cygwin boost 1.33.1 package installed? If so, try > removing it. Then rerun ./configure and look at the output to see > what version of boost is found. > > > 86-pc-cygwin/4.3.4 -L/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../.. > > /usr/lib/gcc/i68 > > 6-pc-cygwin/4.3.4/libstdc++.dll.a -lgcc_s -lgcc_s -lcygwin -luser32 > -lkernel32 > > - > > ladvapi32 -lshell32 -lgcc_s -lgcc_s > > /usr/lib/gcc/i686-pc-cygwin/4.3.4/crtend.o > > -O2 -o > > .libs/cyggruel-3-3-0-0.dll -Wl,--enable-auto-image-base -Xlinker --out- > > implib -Xlinker .libs/libgruel.dll.a > > Creating library file: .libs/libgruel.dll.a > > .libs/thread_group.o: In function `_ZN5boost12shared_mutex4lockEv': > > /usr/local/include/boost/thread/pthread/shared_mutex.hpp:129: undefined > > referenc > > e to > > `boost::this_thread::disable_interruption::disable_interruption()' > [...] > > -- Don W. > > > > > ------------------------------ > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > End of Discuss-gnuradio Digest, Vol 99, Issue 12 > ************************************************ >
_______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
