Re: [Discuss-gnuradio] usb_claim_interface Invalid argument error

[Eric Blossom]

On Mon, Oct 31, 2005 at 09:12:51PM -0500, EDWARD HALL wrote:
>
> I've had a usrp version 2 running successfully for several months
> but that changed abruptly a couple of days ago and I can't get it
> operating again.  I'm running from version 2.5 tarballs and Debian
> Sarge on an i386 system.

What changed?  New kernel by any chance?

> After stopping and restarting an application I get the the following
> message that looks like the application cannot open the usb
> interface to usrp:
> 
>     self.src = usrp.source_c (0, self.usrp_decim, 1, 0xf0f0f0f2, 0)
>   File "/usr/local/lib/python2.3/site-packages/gnuradio/usrp.py", line 65, 
> in source_c
>     return ((usrp0.source_c, usrp1.source_c)[look_for_usrp(which)])(which, 
> *args, **kwargs)
>   File "/usr/local/lib/python2.3/site-packages/gnuradio/usrp1.py", line 
> 1168, in source_c
>     return _usrp1.source_c(*args)
> RuntimeError: std::runtime_error
> 
> 
> Running usrper load_standard_bits gives this output:
> 
> debian:/home/ward/usrp-0.8/host/apps# usrper load_standard_bits
> usrper: found unconfigured usrp; needs firmware.
> usrp_open_interface: usb_claim_interface: failed conf 0
> could not set config 1: Invalid argument
> open_nth_cmd_interface: open_cmd_interface failed
> usrper: failed

> Why would I start getting the "Invalid argument" between application
> runs?  Any help regarding what to look for would be appreciated.
>
> Thanks,
> Ward

Hi Ward,

I'm not sure, but this may be related to a problem that Jeff Long
reported a couple of days ago.  He was seeing usb_set_configuration
fail from within usrp_open_interface.  The problem was triggered by
some change in the kernel devio.c code.  Not sure which kernel version
he was running.  The work-around is to ignore an -EBUSY return from
usb_set_configuration in usrp_prims.cc.  I'll be checking that into CVS
later tonight.

Eric