discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] UHD Announcement - April 23rd 2010


From: Josh Blum
Subject: Re: [Discuss-gnuradio] UHD Announcement - April 23rd 2010
Date: Mon, 26 Apr 2010 12:43:35 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100217 Shredder/3.0.3pre

That does look a bit suspicious. I have two suggestions:

  1) if its a firewall issue, make sure that the linux firewall is off
2) if its a timeout issue edit the udp_simple.cpp and change milliseconds(100) to something larger, say 1000

-Josh

On 04/26/2010 12:13 PM, Douglas Geiger wrote:
On Fri, Apr 23, 2010 at 7:31 PM, Josh Blum<address@hidden>  wrote:
XCVR2450 and RFX series boards are now supported in the UHD.

Here is the link to the wiki and manual that I have been working on:
http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki

The microblaze firmware has changed since the previous announcement.
Download the most recent builds here:
http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/files

Feedback and testing is appreciated!

Thank you,
-Josh


Josh,
  Trying it out on one of my USRP2's here, with an RFX2400. The build
went well: libuhd, firmware and fpga images all built fine. And
building the gr-uhd branch of gnuradio had no problems either,
although I haven't gotten to the point of being able to use it yet:  I
seem to be having trouble with the USRP2 registering as being found.
For example, if I run uhd_find_devices, I get:

$ uhd_find_devices
No UHD Devices Found

Opening up wireshark, I can see that the host and USRP2 are
communicating over UDP (with the correct IP addresses, it seems to me
at least):

43    14:56:36.672264    192.168.10.1    192.168.10.255    UDP    Source port: 
40243  Destination port: 49152
44    14:56:36.672336    192.168.10.2    192.168.10.1    UDP    Source port: 
49152  Destination port: 40243

Host has the IP address 192.168.10.1 on the interface connected to the
USRP2, and the USRP2 appears to have the default 192.168.10.2. I can
send the contents of the UDP packets if you'd like to see them.
Taking a quick look at the usrp2::find function, it looks like it's
supposed to be waiting in a while loop until a timeout occurs, is it
possible the timeout is happening before the response came from the
USRP2? Or have I perhaps made some simple mistake?
  Thanks,
   Doug





reply via email to

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