[USRP-users] Read-all USRP parameters

Joe crossen jmcrossen80 at gmail.com
Wed Jan 22 19:12:09 EST 2020


Hi all,

I know there is a manual for this -
http://files.ettus.com/manual/page_identification.html#id_naming
Though I'm still having difficulties.

Firstly, can the eeprom of the device be read/changed from the device
itself?
I have ssh'd into the USRP, and get the following when attempting to
read-all:

root at ettus-e3xx-sg3:/usr/lib/uhd/utils# ./usrp_burn_mb_eeprom --read-all
Creating USRP device from address:
[INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106400;
UHD_3.11.0.1-0-unknown
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 288000 bytes.
Actual sock buff size: 163840 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=288000
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 288000 bytes.
Actual sock buff size: 163840 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=288000
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 288000 bytes.
Actual sock buff size: 163840 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=288000
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 288000 bytes.
Actual sock buff size: 163840 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=288000
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 288000 bytes.
Actual sock buff size: 163840 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=288000
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 288000 bytes.
Actual sock buff size: 163840 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=288000
[INFO] [E300] Detecting internal GPS
[ERROR] [E300] An error occured making GPSDd interface: RuntimeError:
Failed to connect to gpsd: can't connect to host/port pair
[INFO] [E300] Initializing core control...
[INFO] [E300] Performing register loopback test...
[INFO] [E300] Register loopback test passed
Error: RuntimeError: Expected FPGA compatibility number 17.x, but got 16.0:
The FPGA build is not compatible with the host code build.
Please run:

 "/usr/lib/uhd/utils/uhd_images_downloader.py"

Failing this, I attempted the same from my host machine (with the USRP
device in usrp_e3x0_
network_mode).
/usr/local/lib/uhd/utils$ ./usrp_burn_mb_eeprom --args="serial=3174549"
--read-all
This resulted in a very similar output with the error:
Error: RuntimeError: Expected FPGA compatibility number 255.x, but got 16.0:

*Note: *my host machine is running UHD 3.14.1 and I suspect this doesn't
help the matter- I've attempted to roll this version back by downloading
older uhd binaries - https://files.ettus.com/binaries/uhd/
though was getting all of these dependency issues. I'm new to Linux and
this has been a head-f**k.

I'm not sure how to troubleshoot this.
Any advice would be great!
Thanks,
Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20200123/a58a9d55/attachment.html>


More information about the USRP-users mailing list