Marcus After running sudo_images downloader" it seems that the images are "up
to date" as shown below.
mitll@mitll-virtual-machine:~$ sudo uhd_images_downloader
[INFO] Images destination: /usr/local/share/uhd/images
[INFO] Target usrp1_usrp1_fpga_default is up to date.
[INFO] Target b2xx_b210_fpga_default is up to date.
[INFO] Target b2xx_b205mini_fpga_default is up to date.
[INFO] Target e3xx_e320_fpga_default is up to date.
[INFO] Target usb_common_windrv_default is up to date.
[INFO] Target b2xx_common_fw_default is up to date.
[INFO] Target e3xx_e310_sg3_fpga_default is up to date.
[INFO] Target usrp2_n200_fpga_default is up to date.
[INFO] Target n230_n230_fpga_default is up to date.
[INFO] Target usrp1_b100_fpga_default is up to date.
[INFO] Target usrp1_b100_fw_default is up to date.
[INFO] Target n3xx_n320_fpga_default is up to date.
[INFO] Target n3xx_n310_fpga_default is up to date.
[INFO] Target n3xx_n300_fpga_default is up to date.
[INFO] Target usrp2_usrp2_fw_default is up to date.
[INFO] Target x3xx_x300_fpga_default is up to date.
[INFO] Target e3xx_e310_sg1_fpga_default is up to date.
[INFO] Target x3xx_x310_fpga_default is up to date.
[INFO] Target b2xx_b200mini_fpga_default is up to date.
[INFO] Target usrp2_n210_fw_default is up to date.
[INFO] Target usrp2_usrp2_fpga_default is up to date.
[INFO] Target octoclock_octoclock_fw_default is up to date.
[INFO] Target usrp2_n200_fw_default is up to date.
[INFO] Target usrp2_n210_fpga_default is up to date.
[INFO] Target b2xx_b200_fpga_default is up to date.
However, I re-flashed the device with " uhd_image_loader --args type=x300" ,
power cycled and after running uhd_usrp_probe get what's shown below. This
doesn't seem to be the new image. It's showing RFNoC blocks from a previous
image that was installed prior to my use and when I try to run a flowgraph I'm
getting the same error as mentioned in my previous message. Ideas??
mitll@mitll-virtual-machine:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800;
UHD_3.15.0.git-34-g3c8ed1b5
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
[INFO] [GPS] No GPSDO found
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D00000000000)
[INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1307 MB/s)
[INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1309 MB/s)
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001)
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001)
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000)
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000)
_____________________________________________________
/
| Device: X-Series Device
| _____________________________________________________
| /
| | Mboard: X310
| | revision: 11
| | revision_compat: 7
| | product: 30818
| | mac-addr0: 00:80:2f:18:33:28
| | mac-addr1: 00:80:2f:18:33:29
| | gateway: 192.168.10.1
| | ip-addr0: 192.168.10.3
| | subnet0: 255.255.255.0
| | ip-addr1: 192.168.20.2
| | subnet1: 255.255.255.0
| | ip-addr2: 192.168.30.2
| | subnet2: 255.255.255.0
| | ip-addr3: 192.168.40.2
| | subnet3: 255.255.255.0
| | serial: 3138B7C
| | FW Version: 6.0
| | FPGA Version: 36.0
| | FPGA git hash: 4bc2c6f
| | RFNoC capable: Yes
| |
| | Time sources: internal, external, gpsdo
| | Clock sources: internal, external, gpsdo
| | Sensors: ref_locked
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: TwinRX Rev C (0x0095)
| | | Serial: 3137E4E
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: TwinRX RX0
| | | | Antennas: RX1, RX2
| | | | Sensors: lo_locked
| | | | Freq range: 10.000 to 6000.000 MHz
| | | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | | Connection Type: II
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 1
| | | | Name: TwinRX RX1
| | | | Antennas: RX1, RX2
| | | | Sensors: lo_locked
| | | | Freq range: 10.000 to 6000.000 MHz
| | | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | | Connection Type: QQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ads62p48
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | _____________________________________________________
| | /
| | | RX Dboard: B
| | | ID: TwinRX Rev B (0x0093)
| | | Serial: 31411AC
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: TwinRX RX0
| | | | Antennas: RX1, RX2
| | | | Sensors: lo_locked
| | | | Freq range: 10.000 to 6000.000 MHz
| | | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | | Connection Type: II
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 1
| | | | Name: TwinRX RX1
| | | | Antennas: RX1, RX2
| | | | Sensors: lo_locked
| | | | Freq range: 10.000 to 6000.000 MHz
| | | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | | Connection Type: QQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: B
| | | | Name: ads62p48
| | | | Gain range digital: 0.0 to 6.0 step 0.5 dB
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: Unknown (0x0094)
| | | Serial: 3137E6C
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: Unknown (0x0094) - 0
| | | | Antennas:
| | | | Sensors:
| | | | Freq range: 0.000 to 0.000 MHz
| | | | Gain Elements: None
| | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9146
| | | | Gain Elements: None
| | _____________________________________________________
| | /
| | | TX Dboard: B
| | | ID: Unknown (0x0092)
| | | Serial: 31411CD
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: Unknown (0x0092) - 0
| | | | Antennas:
| | | | Sensors:
| | | | Freq range: 0.000 to 0.000 MHz
| | | | Gain Elements: None
| | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: B
| | | | Name: ad9146
| | | | Gain Elements: None
| | _____________________________________________________
| | /
| | | RFNoC blocks on this device:
| | |
| | | * DmaFIFO_0
| | | * Radio_0
| | | * Radio_1
| | | * DDC_0
| | | * DDC_1
| | | * DUC_0
| | | * DUC_1
On Tuesday, August 13, 2019, 11:41:52 PM EDT, Marcus D. Leech via
USRP-users <usrp-users@lists.ettus.com> wrote:
On 08/13/2019 11:33 PM, Tellrell White via USRP-users wrote:
Hello All
I seem to be receiving an a uhd error that is causing flowgraphs to stop when
trying to send and receive using the USRP X310. Now, I'm receiving the same
error shown below when running the "uhd_usrp_probe" command. Not quite sure
where this error is coming from but I see rfnoc in the last line of the
printout below which leads me to believe that rfnoc could have something to do
with the error. However, I'm not working with the rfnoc branch of uhd. I
believe someone else who was using the device before me may have been using
rfnoc. So, if this is indeed the issue, is there a way to rid the fpga of rfnoc
and use a regular, up to date image? o,
I'm working inside of a VM running Ubuntu 16.04 LTS. I'm using
UHD_3.15.0.git-34-g3c8ed1b5 as shown below, with GNU Radio 3.7.7.
mitll@mitll-virtual-machine:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800;
UHD_3.15.0.git-34-g3c8ed1b5
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Radio 1x clock: 200 MHz
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=24266666
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 24266666 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=24266666
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum
recommended size of 816000 and may result in dropped packets on some NICs
[ERROR] [UHD] Exception caught in safe-call.
in ctrl_iface_impl<_endianness>::~ctrl_iface_impl() [with uhd::endianness_t
_endianness = (uhd::endianness_t)0u]
at /home/mitll/uhd/host/lib/rfnoc/ctrl_iface.cpp:52
this->send_cmd_pkt(0, 0, true); -> EnvironmentError: IOError: Block ctrl
(CE_00_Port_30) no response packet - AssertionError: bool(buff)
in uint64_t ctrl_iface_impl<_endianness>::wait_for_ack(bool, double) [with
uhd::endianness_t _endianness = (uhd::endianness_t)0u; uint64_t = long unsigned
int]
at /home/mitll/uhd/host/lib/rfnoc/ctrl_iface.cpp:142 Error:
EnvironmentError: IOError: Block ctrl (CE_00_Port_30) no response packet -
AssertionError: bool(buff)
in uint64_t ctrl_iface_impl<_endianness>::wait_for_ack(bool, double) [with
uhd::endianness_t _endianness = (uhd::endianness_t)0u; uint64_t = long unsigned
int]
at /home/mitll/uhd/host/lib/rfnoc/ctrl_iface.cpp:142
Regards
Tellrell
Use:
uhd_image_loader --args type=x300
Assuming that you have already downloaded matching image files with:
sudo uhd_images_downloader
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
