discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] USRP2 VRT support


From: Tim Pearce
Subject: Re: [Discuss-gnuradio] USRP2 VRT support
Date: Mon, 28 Dec 2009 23:30:32 +0000

Josh,

Thanks for the help, I'd checked out the wrong version!

I haven't used git before/didn't realise it was a branch so I just ran "git clone http://gnuradio.org/git/jblum.git" and compiled

In case anyone else gets stuck with the same issue - after running this command changing branches seemed to sort everything out for me:

(from jblum/)
git checkout origin/usrp2_vrt
git checkout -b usrp2_vrt

I need to go and read up on the new non-cvs style systems :)

Cheers,

Tim

git clone http://gnuradio.org/git/jblum.git usrp2_vrt

On Mon, Dec 28, 2009 at 10:21 PM, Josh Blum <address@hidden> wrote:
Tim Pearce wrote:
Josh,

The USRP2 doesn't respond when loaded with the firmware at:
http://www.ettus.com/usrp2_vrt

I've just run find_usrps -e eth1 with wireshark running and can only see the
outgoing packet:

1    0.000000    Toshiba_b4:52:54    Broadcast    0xbeef    Ethernet II

Given the transport type is the old (I think) 0xbeef I guess this is wrong,
I'm just about to recheckout the source code and compile again, but "vrt" is
a directory present in where I compiled gnuradio from - I've just double
checked by:


The vrt directory was there prior to this work. A good way to verify that you pulled in the right branch would be to check
usrp2/firmware/include/usrp2_eth_packet.h and see that it has the following defines:

#define U2_DATA_ETHERTYPE               0xBEEF  // used in our data frames
#define U2_CTRL_ETHERTYPE               0xBEF0  // used in our control frames

Thats where the firmware and host code gets the ethernet transport type from.

-Josh


reply via email to

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