Warning in usrp_benchmark_usb.py

Hi everyone,
in testing the USRP I came across several warnings. Can someone tell me
what they mean and if they are irrelevant?
Thanks in advance who will answer …

Federico Battaglia

@ubuntu:/usr/share/gnuradio/examples/usrp$ ./usrp_benchmark_usb.py
Testing 2MB/sec…
Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Tx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Rx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

gr_vmcircbuf_createfilemapping: createfilemapping is not available
usb_throughput = 2M
ntotal = 1000000
nright = 997766
runlength = 997766
delta = 2234
OK
Testing 4MB/sec…
Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Tx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Rx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

usb_throughput = 4M
ntotal = 2000000
nright = 1997113
runlength = 1997113
delta = 2887
OK
Testing 8MB/sec…
Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Tx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Rx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

usb_throughput = 8M
ntotal = 4000000
nright = 3998755
runlength = 3998074
delta = 1926
OK
Testing 16MB/sec…
Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Tx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Rx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

usb_throughput = 16M
ntotal = 8000000
nright = 7996694
runlength = 7996694
delta = 3306
OK
Testing 32MB/sec…
Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Tx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

Warning: Treating daughterboard with invalid EEPROM contents as if it
were a “Basic Rx.”
Warning: This is almost certainly wrong… Use appropriate
burn-*-eeprom utility.

usb_throughput = 32M
ntotal = 16000000
nright = 15993798
runlength = 15992882
delta = 7118
OK
Max USB/USRP throughput = 32MB/sec

On Aug 30, 2010, at 8:15 AM, Federico Battaglia wrote:

in testing the USRP I came across several warnings. Can someone tell me what they mean and if they are irrelevant?
[…]
@ubuntu:/usr/share/gnuradio/examples/usrp$ ./usrp_benchmark_usb.py
Testing 2MB/sec…
Warning: Treating daughterboard with invalid EEPROM contents as if it were a “Basic Tx.”
Warning: This is almost certainly wrong… Use appropriate burn-*-eeprom utility.

Warning: Treating daughterboard with invalid EEPROM contents as if it were a “Basic Rx.”
Warning: This is almost certainly wrong… Use appropriate burn-*-eeprom utility.

Those look relevant to me. Each RF daughterboard is supposed to have an
EEPROM (memory chip) whose contents tell the gnuradio software what kind
of board is installed. Your software is complaining that it couldn’t
identify the installed daughterboard(s), so their EEPROM(s) may need to
be reprogrammed.

There’s some discussion of the EEPROMs here that might be helpful:

http://gnuradio.org/redmine/wiki/gnuradio/UsrpFAQDBoards


Mark J. Blair, NF6X [email protected]
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.

On Mon, Aug 30, 2010 at 8:15 AM, Federico Battaglia
[email protected] wrote:

Hi everyone,
in testing the USRP I came across several warnings. Can someone tell me what
they mean and if they are irrelevant?
Thanks in advance who will answer …

That message usually means you either have an unrecognized
daughterboard installed or no daughterboard installed. It can happen
when you have a daughterboard just on side A but not B.

Jason

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