E100 - No devices found for ----->

luislavena · June 23, 2011, 10:34am

Hi all,

we are new with E100.

we managed to use UHD:USRP_Source without further configuration and
display
it on QT_GUI_SINK.

we don’t manage with UHD:USRP_Sink without further configuration:

File “/usr/local/lib/python2.6/site-packages/gnuradio/uhd/uhd_swig.py”,
line 1854, in usrp_sink
return _uhd_swig.usrp_sink(*args, **kwargs)
RuntimeError: LookupError: KeyError: No devices found for ----->
Empty Device Address

How to configure the sink address???

Any help appreciated!
thanks!
Ralf

uhd_usrp_probe output:

linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.000.001-

Opening USRP-E on /dev/usrp_e0
Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga.bin… done = 1
Configuration complete.
re-Opening USRP-E on /dev/usrp_e0
USRP-E100 clock control: 6
r_counter: 1
a_counter: 0
b_counter: 12
prescaler: 8
vco_divider: 2
chan_divider: 15
vco_rate: 1920.000000MHz
chan_rate: 960.000000MHz
out_rate: 64.000000MHz

rwirdemann · June 23, 2011, 12:21pm

OK, first simple reason discovered.
UHD can only be used for one device - either UHD_usrp_sink or source.

How can UHD be used for both devices in parallel?

Thanks,
Ralf

rwirdemann · June 23, 2011, 1:12pm

On Thu, Jun 23, 2011 at 3:16 AM, Ralf W. [email protected] wrote:

OK, first simple reason discovered.
UHD can only be used for one device - either UHD_usrp_sink or source.

How can UHD be used for both devices in parallel?

You have to access both source and sink from the same process, but
then it is possible to use both at the same time.

Jason

rwirdemann · June 23, 2011, 3:33pm

OK, first simple reason discovered.
UHD can only be used for one device - either UHD_usrp_sink
or source.

How can UHD be used for both devices in parallel?

You have to access both source and sink from the same process, but
then it is possible to use both at the same time.

Jason

Hi Jason,
thanks but I am a little confused.
I would say it is in the same process since I have sink and source in
the same
GRC setup. The failure shows up when the generated python script
instantiates an
UHD devices the second time as far as I understand.
Is there any combined UHD_usrp_sink/source block for GRC or how is this
to
be done practically?

Thanks
Ralf

rwirdemann · June 23, 2011, 3:50pm

OK, first simple reason discovered.
UHD can only be used for one device - either UHD_usrp_sink
or source.

How can UHD be used for both devices in parallel?

You have to access both source and sink from the same process, but
then it is possible to use both at the same time.

Jason

Hi Jason,
thanks but I am a little confused.
I would say it is in the same process since I have sink and source in
the same
GRC setup. The failure shows up when the generated python script
instantiates an
UHD devices the second time as far as I understand.
Is there any combined UHD_usrp_sink/source block for GRC or how is this
to
be done practically?

Thanks
Ralf

rwirdemann · June 23, 2011, 6:25pm

On 06/23/2011 03:16 AM, Ralf W. wrote:

OK, first simple reason discovered.
UHD can only be used for one device - either UHD_usrp_sink or source.

How can UHD be used for both devices in parallel?

Sorry, Its a known bug related to opening twice. Its fixed on the next
branch. Solution w/ instructions:
http://comments.gmane.org/gmane.comp.hardware.usrp.e100/754

-Josh

rwirdemann · June 23, 2011, 7:07pm

On Thu, Jun 23, 2011 at 5:32 AM, Ralf W. [email protected] wrote:

OK, first simple reason discovered.

Hi Jason,
thanks but I am a little confused.
I would say it is in the same process since I have sink and source in the same
GRC setup. The failure shows up when the generated python script instantiates an
UHD devices the second time as far as I understand.
Is there any combined UHD_usrp_sink/source block for GRC or how is this to
be done practically?

Can you send the simplest .grc file which causes this issue?

Jason

rwirdemann · June 24, 2011, 2:43pm

-----Original Message-----

UHD can only be used for one device - either UHD_usrp_sink
Hi Jason,
Can you send the simplest .grc file which causes this issue?

Jason

Hi Jason,

Josh wrote to use the latest branch. This one is still building since
we don’t have any cross compile environment yet…

However, attached is a GRC setup which fails due to parallel use
of two UHD devices. Well, this is very simple.

Hope the parallel issue is fixed using the latest branch. If not, we
appreciate more support.

Regards,
Ralf

rwirdemann · June 23, 2011, 6:07pm

On 23/06/2011 8:32 AM, Ralf W. wrote:

Ralf

This should “Just Work™”. Make sure you have the latest UHD and Gnu
Radio. If it continues to not work, then there’s a problem
with the code, and Josh/Phil should look into it.

rwirdemann · June 27, 2011, 8:56pm

we don’t manage wih the E100 FPGA5 bitstream.
It is placed in the images directory and we use a new branch but we
don’t really think the FPGA5 is used.

What do you mean?

And we still have the same problem with parallel UHD devices (sink/source).

Another guy confirmed it was working for him just fine.

In any case, I think it will also work if you patch this onto the master
branch (very small change): diff --git a/host/lib/usrp/usrp_e100/usrp_e100_impl.cpp b/host/lib/usrp/usrp_e10 - Pastebin.com

Which branch shall we use? Can you pinpoint exactly?
Shall we use the Josh branch from http://gnuradio.org/cgit ?

For gnuradio? The master branch on gnuradio.org is fine.

Do you have images available? We still don’t have a cross-compile env. yet.
Hence compilation takes very long time…

Yes

http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/Experimental_Images

Another topic we recognized on E100 is that we suspect incomplete datastreams
when the Gumstix is overloaded performancewise. I will come back with details
on our transmitter setup which might cause overloads.
But - is it possible to overload the 720MHz Gumstix easily? What happens in
this case - samples are discarded?

On receive, the host backpressures the FPGA. See
http://www.ettus.com/uhd_docs/manual/html/general.html#overflow-underflow-notes

-Josh

rwirdemann · June 28, 2011, 4:08pm

Hi Josh,

today we managed to make UHD sink and source work in parallel on E100
using FPGA5.bin
by building UHD like this:

git clone git://code.ettus.com/ettus/uhd.git
cd uhd
git pull git://code.ettus.com/ettus/uhd.git next
cd host/
$ mkdir build
$ cd build
$ cmake -DCMAKE_CXX_FLAGS:STRING="-mcpu=cortex-a8 -mfpu=neon
-mfloat-abi=softfp -g" -DENABLE_USRP_E100=TRUE
-DENABLE_USRP_E_UTILS=TRUE -i
…/
$ make
$ make test
$ make install
$ ldconfig

Please bear in mind that we are absolute beginners to Gnuradio and E100.
We started one week ago.
Some more precise information really helps!!
However, your help is appreciated!

Thanks,
Ralf

Am 27.06.2011 18:50, schrieb Josh B.:

rwirdemann · June 27, 2011, 1:54pm

http://comments.gmane.org/gmane.comp.hardware.usrp.e100/754

-Josh

Hi Josh,

we don’t manage wih the E100 FPGA5 bitstream.
It is placed in the images directory and we use a new branch but we
don’t really think the FPGA5 is used.
And we still have the same problem with parallel UHD devices
(sink/source).

Which branch shall we use? Can you pinpoint exactly?
Shall we use the Josh branch from http://gnuradio.org/cgit ?

Do you have images available? We still don’t have a cross-compile env.
yet.
Hence compilation takes very long time…

Another topic we recognized on E100 is that we suspect incomplete
datastreams
when the Gumstix is overloaded performancewise. I will come back with
details
on our transmitter setup which might cause overloads.
But - is it possible to overload the 720MHz Gumstix easily? What happens
in
this case - samples are discarded?

Regards,
Ralf