Yet another uhd_find_devices does not find usrp2 and no ping from 192.168.10.2

Hi All,

uhd_find_devices returns No UHD Devices Found.

I do not get a ping back from 192.168.10.2 either.

Here is what I have:
-Ubuntu 10.04
-USRP2 with stock SD card and firmware, no daughterboards
-UHD+gnuradio installed yesterday using the Leech script from
http://www.sbrac.org/files/build-gnuradio
-Gigabit Ethernet
-PC IP set to: 192.168.10.1, netmask: 255.255.255.0
-Firewalls disabled (inactive)

Here is what happens:
When I power up the usrp2 (with ethernet connected)
-All 6 LEDs briefly flash followed by D & F lit.
-Ethernet green lights on.
-Ethernet orange light flashes every time it gets pinged.

So, I have all the good signs and everything should be set up correctly.
However uhd_find_devices returns No UHD Devices Found and I do not get a
ping back from 192.168.10.2 either.
I have also tried uhd_usrp_probe --args “addr=192.168.10.2” which
returns no
devices found as well.

Any ideas?

Thanks,
Jim

On 07/13/2011 05:18 PM, Jim S. wrote:

Hi All,

uhd_find_devices returns No UHD Devices Found.

I do not get a ping back from 192.168.10.2 either.

https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

The stock firmware on the USRP2 (which was released prior to the
invention of UHD), doesn’t
support UHD. You’ll have to burn the appropriate image into the USRP2
for it to support UHD.
The UHD “wire protocol” has undergone several revisions in the last
year as well, so it’s good to
have your USRP2 firmware match the host-side software. Further, the
stock USRP2 firmware
doesn’t have an IP stack at all–it used so-called “raw ethernet”
frames for communications, so it’s
not able to respond to pings, which use the ICMP ECHO (part of IP)
protocol.

You’ll find that the build-gnuradio script will have installed firmware
images in:

/usr/local/share/uhd/images

And you can use /usr/local/share/uhd/utils/usrp2_card_burner_gui.py to
place new firmware and FPGA
images onto your USRP2 SD card.


Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

Actually, I’m thinking that I might need to find another SD card reader.

Looks like I could use the --list option in the non-GUI version to
filter to
small size drives.

Right now I don’t even see the card in Disk Utility.

Thanks,
Jim

Thanks. That makes sense.

When I call usrp2_card_burner_gui.py it only finds one device
“/dev/sda2”
I’m pretty sure that that is where windows resides.

Is there any way to force the GUI to find the SD card?
Is there any way to confirm that what it finds is the SD card?

Thanks!
Jim

On 07/13/2011 05:51 PM, Jim S. wrote:

Thanks. That makes sense.

When I call usrp2_card_burner_gui.py it only finds one device “/dev/sda2”
I’m pretty sure that that is where windows resides.

Is there any way to force the GUI to find the SD card?
Is there any way to confirm that what it finds is the SD card?

Thanks!
Jim
Where it says Raw device: you can enter any device name you want

I always use ‘dmesg’ to confirm the device assignment, right after I
plug in the SD card.


Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

It’s working now. The fw upgrade fixed it. Thanks for the help!

Thanks for the dmesg tip as well.

Is there anything I can follow to get updates when there are new
firmware
releases?

Thanks,
Jim

On 07/13/2011 05:55 PM, Jim S. wrote:

Actually, I’m thinking that I might need to find another SD card reader.

Looks like I could use the --list option in the non-GUI version to
filter to small size drives.

Right now I don’t even see the card in Disk Utility.

Thanks,
Jim

If you’re using a Linux system, you can look at the output of “dmesg”
when you plug the SD card in
to determine which device it assigned.

I recently purchased a bunch of USB SD card readers at my local dollar
store for $2.00 apiece.
They work just fine. Sometimes cheap crap is golden :slight_smile:


Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

On 07/13/2011 09:11 PM, Jim S. wrote:

It’s working now. The fw upgrade fixed it. Thanks for the help!

Thanks for the dmesg tip as well.

Is there anything I can follow to get updates when there are new
firmware releases?

Thanks,
Jim

Josh usually posts to this list when there are UHD and firmware/FPGA
updates.

There’s also:

http://code.ettus.com/redmine/ettus/projects/uhd/wiki#Binary-downloads


Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

Cool- thanks for all your help.

Jim

To find which devices are present at the system, this command is also
helpful:

‘sudo fdisk -l’

If you run the command before and after you sett in the card, it is
usually easy to find out which device the card is.

Hi Josh,

Here are the partitions:

major minor #blocks name

8 0 625131864 sda
8 1 380204341 sda1
8 2 1 sda2
8 5 235879424 sda5
8 6 9046016 sda6

I have a 640GB drive dual booting windows and ubuntu.
Not sure what sda2 is. But this explains why it showed up on the gui.

The SD card was sdb and it showed up fine on the burner gui on the new
card
reader.

Thanks,
Jim