discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Unable to find USRP


From: Berndt Josef Wulf
Subject: Re: [Discuss-gnuradio] Unable to find USRP
Date: Sat, 14 May 2005 11:39:21 +0930
User-agent: KMail/1.7.2

On Saturday 14 May 2005 02:19, Eric Blossom wrote:
> On Fri, May 13, 2005 at 10:47:17PM +0930, Berndt Josef Wulf wrote:
> > G'day Folks,
> >
> > after updating to the current GnuRadio CVS source I'm getting the
> > following error message when attempting to run applications that inovle
> > the USRP:
> >
> >   File "./usrp_fft.py", line 49, in __init__
> >     self.u = usrp.source_c (0, options.decim, 1, options.mux, 0)
> >   File "/usr/pkg/lib/python2p3/site-packages/gnuradio/usrp.py", line 95,
> > in source_c
> >     return ((usrp0.source_c,
> > usrp1.source_c)[look_for_usrp(which)])(which, *args, **kwargs)
> >   File "/usr/pkg/lib/python2p3/site-packages/gnuradio/usrp.py", line 69,
> > in look_for_usrp
> >     raise RuntimeError, "Unable to find USRP #%d" % (which,)
> > RuntimeError: Unable to find USRP #0
> >
> > All was fine prior to the update.
> >
> > Any ideas?
> >
> > cheerio Berndt
>
> Not really.
>
> Obvious check #1:  Is the USRP plugged in and powered up?
>
> Did you update all CVS components and build them in the right order?
> I like using gr-build, because it keeps me from having to think too
> much about this kind of thing.  I just fire it off and walk away.
>
> Eric

The building process was:

1.) gnuradio-core
2.) usrp
3.) gr-usrp
4.) gr-wxgui
6.) gr-audio-oss
7.) gr-gsm-fr-vocoder

This worked previously. Has there been any changes in the device naming 
convention?

cheerio Berndt
-- 
Every man who says frankly and fully what he thinks is doing a public service.
[Leslie Stephen]




reply via email to

[Prev in Thread] Current Thread [Next in Thread]