Hi Joe, Perhaps you need a different "mgmt_addr" and "addr"? I seem to recall that it was necessary to have a management address that was the typical RJ45 and then a data streaming address that went to the high speed IO. My memory is for the N series USRPs - I have no experiment with the X410. Rob
On Wed, Dec 20, 2023 at 1:42 PM <jmalo...@umass.edu> wrote: > Hello, > > I am currently attempting to benchmark the x410 with the Mellanox > ConnectX-5 PCi Card over QSFP with the CG_400 image currently loaded on the > x410. I am currently using a 13th gen intel i9-13900KS on the host machine. > I currently have a QSFP cable connected between the Mellanox card and the > x410 > > I am following these instructions… > https://kb.ettus.com/Getting_Started_with_DPDK_and_UHD > > However, when I get to the benchmark_rate, I get the following output > > ./benchmark_rate --rx_rate 491.52e6 --rx_channels 0 --tx_rate 491.52e6 > --tx_channels 0 --args "addr=192.168.10.2,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.000215] Creating the usrp device with: > addr=192.168.10.2,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 > > [INFO] [MPMD] Initializing 1 device(s) in parallel with args: > mgmt_addr=192.168.10.2,type=x4xx,product=x410,serial=328AACC,name=ni-x4xx-328AACC,fpga=CG_400,claimed=False,addr=192.168.10.2,use_dpdk=1 > > [ERROR] [DPDK] Could not find route to destination address 192.168.10.2 > > [WARNING] [MPMD::XPORT::UDP] Error during MTU discovery on address > 192.168.10.2: RuntimeError: DPDK: Could not find route to destination > address 192.168.10.2 > > [ERROR] [MPMD::MB_IFACE] No CHDR connection available! > > [INFO] [MPM.PeriphManager] init() called with device args > `fpga=CG_400,mgmt_addr=192.168.10.2,name=ni-x4xx-328AACC,product=x410,use_dpdk=1,clock_source=internal,time_source=internal,initializing=True'. > > Error: RuntimeError: No CHDR connection available! > > I am having a difficult time parsing these errors at the moment. Should I > move my config file? Does the “x300 network” refer to an ettus device(I > have no x3xx connected) or something else? Any suggestions is greatly > appreciated. > > Thanks, > > Joe > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com >
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
