Forum: GNU Radio Help initial problems with the USRP2

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
92ca9751a50257dff2db28ec4a3e4952?d=identicon&s=25 Ane Andersen (Guest)
on 2009-04-07 15:43
(Received via mailing list)
Hi
Hope somebody will help me get a little futher with my USRP2. I have no
previous experience with USPRS, ubuntu or python.
I am running Ubuntu 8.10 and latest version of gnuradio.

I tried find_usprs and got a response MACaddress and HW_rev 0x0301 from
the
box.

Then I tried running usrp2_fft.py and usrp2_rx_cfile.py with RFX1200
mounted
and also without  any card mounted.
With the RFX1200 mounted I in both cases get the following response

Usage: "filname" [Options]

Options:
-h -help
-m
etc.
Trying different options I still get the same response
If I remove the daugtherboard. The system responses with Runtimerror:
Unable
to retrive daughterboard info

Is there anybody out there that can help me?

Br
Ane
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2009-04-07 18:31
(Received via mailing list)
On Tue, Apr 07, 2009 at 03:41:18PM +0200, Ane Andersen wrote:
> With the RFX1200 mounted I in both cases get the following response
>
> Usage: "filname" [Options]
>
> Options:
> -h -help
> -m
> etc.
> Trying different options I still get the same response
> If I remove the daugtherboard.



> The system responses with Runtimerror: Unable to retrive daughterboard info
>
> Is there anybody out there that can help me?

Download and install the latest FPGA and firmware images onto the SD
Card.

  http://gnuradio.org/releases/usrp2-bin/trunk

Eric
92ca9751a50257dff2db28ec4a3e4952?d=identicon&s=25 Ane Andersen (Guest)
on 2009-04-08 15:53
(Received via mailing list)
>
> Hi Eric
I just tried flashing the SD ram as instructed on the web. It didn't
change
much. Now when I run the two scripts I randomly get either "segment
fault"
or some lines of traceback print with a runtimeerror "Unable to retrieve
daughterboard info. I also tried  another USRP2 with newest FW. It
responded
the same way. This however had the DBSRX mounted (unfortunately not
modified
for USRP2 since we didn't know until yesterday). I

Maybe you could help me if I write exactly what I do
with RFX1200 mounted
If I write: sudo ./usrp2_fft.py -f1300e6
I get this response:

Traceback (most recemt call last);
File "./usrp2_fft.py, line 274 in <module>
      main()
File"./usrp2_fft.py, line 270, in main
      app=stdgui2.stdapp(app_top_block, "USPR2 FFT", nstatus=1)
File "/usr/local/lib/python2.5/site-packages/gnuradio/wxgui/stdgui2.py",
line 36 in __init__
  wx.App.__init__(self, redirect=False)
File "/usr/lib/python2.5/sit-packages/wx-2.8-gtk2-unicode/wx/_core.py",
line
7912, in __init__
  self._BootstrapApp()
 File "/usr/lib/python2.5/sit-packages/wx-2.8-gtk2-unicode/wx/_core.py",
line 7487, in
_BootstrapApp
return _core_.PyApp__BootstrapApp(*args, **kwargs)
 File
"/usr/lib/python2.5/sit-packages/wx-2.8-gtk2-unicode/wx/stdgui2.py",
line 39 , in OnInit
  frame=stdframe (self.top_block_maker, self.title, self._nstatus)
File
"/usr/lib/python2.5/sit-packages/wx-2.8-gtk2-unicode/wx/stdgui2.py",
line 60 in __init__
 self.panel=stdpanel (self, self, top_block_maker)
 File
"/usr/lib/python2.5/sit-packages/wx-2.8-gtk2-unicode/wx/stdgui2.py",
line 81 in __init__
 self.top_block=top_block_maker(frame, self, vbox, sys.argv)
File  "./usrp2_fft.py", line 70 in __init__
  self.u=usrp2.source_32fc(options.interface, options.mac_addr)
File "/usr/local/lib/python2.5/site_packages/gnuradio/usrp2.py", line
585,
in source_32fc
 return _usrp2.source_32(*args, **kwargs)
RuntimeError: Unable to retrieve daughterboard info
"Unable to retrieve daughterboard info " any more but segment fault.

Br
Ane
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2009-04-08 18:33
(Received via mailing list)
On Wed, Apr 08, 2009 at 03:43:26PM +0200, Ane Andersen wrote:
> >
> > Hi Eric
> I just tried flashing the SD ram as instructed on the web. It didn't change
> much. Now when I run the two scripts I randomly get either "segment fault"
> or some lines of traceback print with a runtimeerror "Unable to retrieve
> daughterboard info. I also tried  another USRP2 with newest FW. It responded
> the same way. This however had the DBSRX mounted (unfortunately not modified
> for USRP2 since we didn't know until yesterday). I

I suspect that you're not using the latest code in the trunk. Please
update, build and install that.  That will fix the segfault.

The fact that you're still getting the "Unable to retrieve
daughterboard info" message makes me think that you didn't
successfully update the firmware on the SD Card with the latest
firmware binary.

Eric
92ca9751a50257dff2db28ec4a3e4952?d=identicon&s=25 Ane Andersen (Guest)
on 2009-04-15 17:14
(Received via mailing list)
Hi Eric
...Okey now I have another problem. I downloaded rev 10851 of the
gnuradio
from the trunk and now I get two errors when I try to make.

I configured ld.so.conf as describe in your wiki. But I still have make
errors

Br
Ane

2009/4/8 Eric Blossom <eb@comsec.com>
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2009-04-15 22:13
(Received via mailing list)
On Wed, Apr 15, 2009 at 04:59:15PM +0200, Ane Andersen wrote:
> Hi Eric
> ...Okey now I have another problem. I downloaded rev 10851 of the gnuradio
> from the trunk and now I get two errors when I try to make.
>
> I configured ld.so.conf as describe in your wiki. But I still have make
> errors
>
> Br
> Ane

Ane,

You haven't shown us what the two errors are.  Putting it mildly, that
makes it impossible to help you.

Please read and follow the suggestions in

  http://gnuradio.org/trac/wiki/ReportingErrors

Eric
92ca9751a50257dff2db28ec4a3e4952?d=identicon&s=25 Ane Andersen (Guest)
on 2009-04-16 10:49
(Received via mailing list)
...Sorry. I forgot  a thing or two ;-) This is the makelog. Hopefully
you
can help me now.


make  all-recursive
make[1]: Entering directory `/home/tui104/boost_temp/gnuradio'
Making all in config
make[2]: Entering directory `/home/tui104/boost_temp/gnuradio/config'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/tui104/boost_temp/gnuradio/config'
Making all in gruel
make[2]: Entering directory `/home/tui104/boost_temp/gnuradio/gruel'
Making all in src
make[3]: Entering directory `/home/tui104/boost_temp/gnuradio/gruel/src'
Making all in include
make[4]: Entering directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include'
Making all in gruel
make[5]: Entering directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include/gruel'
make  all-am
make[6]: Entering directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include/gruel'
make[6]: Nothing to be done for `all-am'.
make[6]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include/gruel'
make[5]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include/gruel'
make[5]: Entering directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include'
make[4]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gruel/src/include'
Making all in lib
make[4]: Entering directory
`/home/tui104/boost_temp/gnuradio/gruel/src/lib'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gruel/src/lib'
make[4]: Entering directory `/home/tui104/boost_temp/gnuradio/gruel/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/home/tui104/boost_temp/gnuradio/gruel/src'
make[3]: Leaving directory `/home/tui104/boost_temp/gnuradio/gruel/src'
make[3]: Entering directory `/home/tui104/boost_temp/gnuradio/gruel'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/tui104/boost_temp/gnuradio/gruel'
make[2]: Leaving directory `/home/tui104/boost_temp/gnuradio/gruel'
Making all in omnithread
make[2]: Entering directory
`/home/tui104/boost_temp/gnuradio/omnithread'
Making all in gnuradio
make[3]: Entering directory
`/home/tui104/boost_temp/gnuradio/omnithread/gnuradio'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/home/tui104/boost_temp/gnuradio/omnithread/gnuradio'
make[3]: Entering directory
`/home/tui104/boost_temp/gnuradio/omnithread'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/tui104/boost_temp/gnuradio/omnithread'
make[2]: Leaving directory `/home/tui104/boost_temp/gnuradio/omnithread'
Making all in gnuradio-core
make[2]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core'
Making all in src
make[3]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src'
Making all in gen_interpolator_taps
make[4]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/gen_interpolator_taps'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/gen_interpolator_taps'
Making all in lib
make[4]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib'
Making all in missing
make[5]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/missing'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/missing'
Making all in runtime
make[5]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/runtime'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/runtime'
Making all in filter
make[5]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/filter'
make  all-am
make[6]: Entering directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/filter'
make[6]: *** No rule to make target
`gr_secondorder_section_iir_filter_ff.lo', needed by `libfilter.la'.
Stop.
make[6]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/filter'
make[5]: *** [all] Error 2
make[5]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib/filter'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src/lib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/tui104/boost_temp/gnuradio/gnuradio-core'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/tui104/boost_temp/gnuradio'
make: *** [all] Error 2


2009/4/15 Eric Blossom <eb@comsec.com>
92ca9751a50257dff2db28ec4a3e4952?d=identicon&s=25 Ane Andersen (Guest)
on 2009-04-16 14:43
(Received via mailing list)
By the way I tried  to do a make distclean. This didn't change the
result of
the making and I didn't find anyother surgestions to solve the problem
in
the old mails:-(

2009/4/15 Eric Blossom <eb@comsec.com>
A576b201df57014077494da786319110?d=identicon&s=25 Tom Rondeau (Guest)
on 2009-04-16 15:17
(Received via mailing list)
Ane Andersen wrote:
> By the way I tried  to do a make distclean. This didn't change the
> result of the making and I didn't find anyother surgestions to solve
> the problem in the old mails:-(

Update to the newest revision of the trunk. This was a bug in that
particular version you checked out.

Tom
92ca9751a50257dff2db28ec4a3e4952?d=identicon&s=25 Ane Andersen (Guest)
on 2009-04-21 06:05
(Received via mailing list)
Hi Tom
Well yes Murphy's law is still in use. Actually I was wondering why I
was
recommended to check out the latest version in the trunc in the first
place.
Doesn't the stable releases work with USRP2?

When I checkout the 10851 trunc I uninstalled the gnuradio and made a
distclean just to be on the safe side. Should I do all this again or can
I
simply write

svn co http://....gnuradio?
./bootstrap
./configure
make
as usual?

Ane



2009/4/18 Tom Rondeau <trondeau1122@gmail.com>
A576b201df57014077494da786319110?d=identicon&s=25 Tom Rondeau (Guest)
on 2009-04-21 07:27
(Received via mailing list)
Ane Andersen wrote:
> ./bootstrap
> ./configure
> make
> as usual?
>
> Ane
>

Ok, one more time. Trunk revision 10851 has a bug in it. We are now up
to revision 10883 which does not have a bug in it. Update to the latest
trunk and do the full make process from bootstrap to make install.

If you want to use a stable release, yes, you can do that. If you want
to run the trunk, just don't use rev 10851.

Tom
D0072e69d706bb3ca211d33a1b536e2c?d=identicon&s=25 Johnathan Corgan (Guest)
on 2009-04-21 10:06
(Received via mailing list)
On Mon, Apr 20, 2009 at 5:23 AM, Tom Rondeau <trondeau1122@gmail.com>
wrote:

> Ok, one more time. Trunk revision 10851 has a bug in it. We are now up to
> revision 10883 which does not have a bug in it. Update to the latest trunk
> and do the full make process from bootstrap to make install.
>
> If you want to use a stable release, yes, you can do that. If you want to
> run the trunk, just don't use rev 10851.

The USRP2 is not supported in the 3.1.x stable release, only in the
trunk or the new 3.2 release candidate (I'm sure you knew that, just
clarifying for the original poster.)

Johnathan
This topic is locked and can not be replied to.