discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] USRP on NetBSD


From: Berndt Josef Wulf
Subject: Re: [Discuss-gnuradio] USRP on NetBSD
Date: Sat, 17 Dec 2005 00:14:58 +1030
User-agent: KMail/1.8.3

On Fri, 16 Dec 2005 06:05, Greg Troxel wrote:
> I have the following
>
>   NetBSD-current from within the last few weeks
>   GNU Radio 2.6 release (via NetBSD pkgsrc)
>   USRP rev 3 (brand new, arrived yesterday) with TVRX and Flex440
>   D-Link USB2 cardbus (NEC ehci)
>   IBM Thinkpad T30
>
> I can load firmware and see the USRP reattach.  When running the
> benchmark, with debugging turned on in libusb, I get the following.
> It seems there is a control message vendor write error for GET_CONFIG
> value 84 index 0.  This doesn't seem to provoke any gr-level error
> printfs.  Then, there's a python type error which indicates probably
> at best a missing error check.  I'm digging into this but new at most
> of the details so thought I'd send this out to see if it rang any
> bells.
>
> Current NetBSD allows muliple opens of the control endpoint.
>
> I saw a comment that when the firmware stalls one gets EPIPE, but it
> isn't clear if that's linux-specific behavior.
>
> The dial_tone demo fails opening audio output, not finding /dev/dsp,
> but I may just be able to symlink that to /dev/sound; there is a
> symlink like that in /emul/linux/dev/dsp but of course I'm running
> everything native.

I have a private hack enabling me to open the audio device for read and write 
using separate calls for sink and source from the same process. E.g. it runs 
the spectrum_inversion.py without problems. I can incorporate this patch in 
pkgsrc, but its a rather ugly hack.

> I'm going to be getting set up to run all this from CVS next.
>
> Testing 2MB/sec... usb_os_find_busses: Found /dev/usb0
> usb_control_msg: 64 9 27 288 0xbfbfce00 4 1000
[...]
> usb_control_msg: 64 9 28 288 0xbfbfce00 4 1000
> Traceback (most recent call last):
>   File "./benchmark_usb.py", line 106, in ?
>     main ()
>   File "./benchmark_usb.py", line 96, in main
>     ok = run_test (rate, verbose)
>   File "./benchmark_usb.py", line 64, in run_test
>     fg.connect (data_src, src_head, usrp_tx)
>   File
> "/usr/pkg/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py",
> line 115, in connect self._connect (points[i-1], points[i])
>   File
> "/usr/pkg/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py",
> line 120, in _connect self._connect_prim (s, d)
>   File
> "/usr/pkg/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py",
> line 126, in _connect_prim self._check_valid_dst_port (dst_endpoint)
>   File
> "/usr/pkg/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py",
> line 225, in _check_valid_dst_port self._check_port
> (dst_endpoint.block.input_signature(), dst_endpoint.port) File
> "/usr/pkg/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py",
> line 230, in _check_port if signature.max_streams () == -1: # infinite
> AttributeError: 'PySwigObject' object has no attribute 'max_streams'
> usb_control_msg: 64 9 3 288 0xbfbfd7c0 4 1000
> usb_control_msg: 64 9 11 288 0xbfbfd8d0 4 1000barossa: {5} 
cd /usr/pkg/share/examples/gnuradio/python/usrp/

I'm getting the usb_control_msg failed messages, but it doesn't seem to stop 
it from running the applications. I don't see the problem you're experiencing 
on a NetBSD-3.99.13. However, data bandwidth is limited to 4MB/sec.

barossa: {6} ./benchmark_usb.py
Testing 2MB/sec... usb_control_msg failed: error sending control message: 
Input/output error
usb_throughput = 2M
ntotal    = 1000000
nright    = 998661
runlength = 998661
delta     = 1339
OK
Testing 4MB/sec... usb_control_msg failed: error sending control message: 
Input/output error
usb_throughput = 4M
ntotal    = 2000000
nright    = 1999671
runlength = 1999671
delta     = 329
OK
Testing 8MB/sec... usb_control_msg failed: error sending control message: 
Input/output error
uUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuUuU
[...]

cheerio Berndt

Attachment: pgpmf8ugLwBn9.pgp
Description: PGP signature


reply via email to

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