In the past when I collected data from the x410 without DPDK, it would work just fine to use solely 1 network port.
I tried using the management address now, but I still get errors, but it is slightly different. Notably there is not a “no chdr_connection available” error. `./benchmark_rate --rx_rate 491.52e6 --rx_channels 0 --tx_rate 491.52e6 --tx_channels 0 --args "addr=192.168.10.2,mgmt_addr=192.168.1.254,use_dpdk=1"` `[INFO] [UHD] linux; GNU C++ version 9.4.0; Boost_107100; DPDK_19.11; UHD_4.5.0.main-2-ga7657c80` `[WARNING] [PREFS] Loaded config from /root/.uhd. This location is considered deprecated, consider moving your config file to /root/.config instead.` `EAL: Detected 32 lcore(s)` `EAL: Detected 1 NUMA nodes` `EAL: Multi-process socket /var/run/dpdk/rte/mp_socket` `EAL: Selected IOVA mode 'PA'` `EAL: No available hugepages reported in hugepages-1048576kB` `EAL: Probing VFIO support...` `EAL: VFIO support initialized` `EAL: PCI device 0000:06:00.0 on NUMA socket -1` `EAL: probe driver: 15b3:1017 net_mlx5` `EAL: PCI device 0000:06:00.1 on NUMA socket -1` `EAL: probe driver: 15b3:1017 net_mlx5` `[ERROR] [DPDK] Could not find route to destination address 192.168.10.2` `[ERROR] [X300] X300 Network discovery error RuntimeError: DPDK: Could not find route to destination address 192.168.10.2` `[00:00:00.000209] Creating the usrp device with: addr=192.168.10.2,mgmt_addr=192.168.1.254,use_dpdk=1...` `[ERROR] [DPDK] Could not find route to destination address 192.168.10.2` `[ERROR] [X300] X300 Network discovery error RuntimeError: DPDK: Could not find route to destination address 192.168.10.2` `Error: LookupError: KeyError: No devices found for ----->` `Device Address:` ` addr: 192.168.10.2` ` mgmt_addr: 192.168.1.254` ` use_dpdk: 1`
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
