New Ethernet MAC for USRP2

I am in the process of replacing the old GigE MAC logic for the USRP2
with a much cleaner design. This is the first step in allowing for a
bunch of big improvements. I would greatly appreciate it if people with
USRP2s would try this new version. Instructions on how to get it are
here:

http://gnuradio.org/trac/wiki/NewEthMAC

Please report both success or problems with it.

Thanks,
Matt

On Wed, Sep 30, 2009 at 11:04 PM, Matt E. [email protected] wrote:

I am in the process of replacing the old GigE MAC logic for the USRP2 with a
much cleaner design. This is the first step in allowing for a bunch of big
improvements. I would greatly appreciate it if people with USRP2s would try
this new version. Instructions on how to get it are here:

http://gnuradio.org/trac/wiki/NewEthMAC

Please report both success or problems with it.

Is this a completely new re-write or reworking what was originally
from opencores?

Thanks,
Brian

Brian P. wrote:

Is this a completely new re-write or reworking what was originally
from opencores?

This is a complete removal of the entire GigE MAC from OpenCores. The
MDIO (actually from the OpenCores 10/100 core) remains, but that’s it.

While I was at it, I rewrote all the FIFOs, the buffer pool interface,
and a few other things in there as well. From the user’s point of view,
everything should function exactly the same and you shouldn’t be able to
tell the difference. If there is any different behavior please let me
know.

Matt

new_eth

If we’re retrieving the source from your git repository, should we be
building from the new_eth branch, or from master?
Doug

On Wed, Sep 30, 2009 at 11:04 PM, Matt E. [email protected] wrote:

Thanks,
Matt


Discuss-gnuradio mailing list
[email protected]nvalid
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Doug G.
[email protected]

Mind if I update the wiki with instructions on creating a tracking
branch? To make it easier for those of us who enjoy building the
images ourselves.

Also - I can report my build of the images went without a problem,
and communicating with one of my USRP2’s with the new firmware/fpga
works fine. I was able to run usrp2_rx_cfile.py with -d 4 and receive
1e9 samples without problems. Other tests will have to wait a while,
but looks good from here.
Doug

On Thu, Oct 1, 2009 at 12:12 PM, Matt E. [email protected] wrote:

Please report both success or problems with it.


Doug G.
[email protected]

Douglas G. wrote:

Mind if I update the wiki with instructions on creating a tracking
branch? To make it easier for those of us who enjoy building the
images ourselves.

That would be great.

Also - I can report my build of the images went without a problem,
and communicating with one of my USRP2’s with the new firmware/fpga
works fine. I was able to run usrp2_rx_cfile.py with -d 4 and receive
1e9 samples without problems. Other tests will have to wait a while,
but looks good from here.
Doug

Thanks for testing this, and for all your help.

Matt

Hi,

I flashed the attached firmware/fpga file, and the USRP2 doesn’t work.

[email protected]:~$ sudo usrp2_fft.py -e eth1
usrp2: channel 0 not receiving
usrp2::rx_samples() failed

And this is the first time for me using git.
After I use ‘git fetch’ to get the repository, what’s next to get the
following command working?

git branch --track new_eth origin/new_eth
git checkout new_eth

Hanwen

2009/10/1 Matt E. [email protected]

hanwen wrote:

following command working?

git branch --track new_eth origin/new_eth
git checkout new_eth

Johnathan has already put this work onto the master, so you should just
use “git checkout master” now.

Matt

So what does this update actually do? Does it add UDP onto the network
stack? What about VRT? I know VRT and UDP are being implemented
independently, but around the same time. How does this update fit in
with
adopting those two protocols?

Thanks
Devin

And this is the first time for me using git.
After I use ‘git fetch’ to get the repository, what’s next to get the
following command working?

For future reference, ‘git fetch’ simply pulls the list of changesets.
In order to apply them to your current branch, you need to use ‘git
merge’.

Alternatively, doing a ‘git pull’ does it all for you - this is
generally the easier route unless you want to hand-select/view the
changesets before applying them.

Cheers,
Ben

devin kelly wrote:

So what does this update actually do? Does it add UDP onto the network
stack? What about VRT? I know VRT and UDP are being implemented
independently, but around the same time. How does this update fit in
with adopting those two protocols?

This update only changed the ethernet mac, so no functionality is
changed. It will allow us to add UDP and VRT. I have UDP and VRT
nearly complete, but I need people to test this heavily before I can
finish UDP/VRT.

Matt

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs