Re: [Discuss-gnuradio] usb_control_msg error

[Eric Blossom]

On Thu, Mar 06, 2008 at 01:01:18PM +0200, Ahmet Hasim Gokceoglu wrote:
> Hi,
> 
> I have been trying to test my USRP with usrp_benchmark_usb.py for a couple
> of days but there is a problem that I still couldn't solve. Each time I run
> the program I get;
> 
> Testing 2MB/sec... usb_control_msg failed: error sending control message:
> Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usb_control_msg failed: error sending control message: Connection timed out
> usrp: failed to load fpga bitstream /opt/gnuradio/share/usrp/rev4
> /std_2rxhb_2tx.rbf
> Traceback (most recent call last):
>     File "./usrp_benchmark_usb.py", line 106, in ?
>        main ( )
>     File "./usro_benchmark_usb.py", line 96, in main
>         ok=run_test (rate, verbose)
>      File "./usrp_benchmark__usb.py", line 63, in run_test
>         usrp_tx=usrp.sink_s(0, tx_interp)
>       File "/opt/gnuradio/lib/python2.4/site-packages/gnuradio/usrp.py",
> line 230, in __init__
>           fpga_filename, firmware_filename)
>       File "/opt/gnuradio/lib/python2.4/site-packages/gnuradio/usrp1.py",
> line 940, in  sink_s
>            return _usrp1.sink_s(*args)
> RuntimeError: can't open usrp1
> 
> I have high speed usb connection and one other thing to note is that after I
> run the program the green LED that blinks with 2Hz stops blinking and
> remains ON. The TVRX and RFX2400 daughterboards are also mounted. I don't
> know whether any kind of setting for the daughterboards or motherboards are
> missing or wrong to give such kind of usb_control_msg error. Does anybody
> have any idea?

Sorry, no clue.  You're running under windows, right?
Bad USB cable?

Have you considered one of the free OS alternatives?
It's where virtually all of the development takes place.

Eric