On 20/02/2023 22:27, Wade Fife wrote:
Hi Joe,
The error you're getting basically means it can't communicate with the
FPGA on the N320. It's sending a packet to the device, but it's not
getting the response packet it expects. So it could be a network
configuration issue, a cabling issue, maybe a firewall issue, or
something else that's messing up the packets.
Double check the cabling and make sure you have the ports connected
correctly. For example, connect the host computer port with IP
192.168.10.1 to the port on the device configured to 192.168.10.2 (the
first port), or port 192.168.20.1 connected to 192.168.20.2 (the
second port). Sometimes cables get swapped or port IP addresses get
misconfigured and that can cause issues like this.
When you specify the "addr" argument, you're telling the software
which port to use to do the initialization that's failing, so make
sure that's correct and matches the configuration and cabling.
Wade
On Mon, Feb 20, 2023 at 11:57 AM <jmalo...@umass.edu> wrote:
With the HG image, things seem to be working fine. I can
benchmark, and i can collect samples at not only the full
rate(25e6 MS/S), but at a higher rate than the XG image, which is
strange.
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
I'm going to guess, given what Wade said above (the error messages
weren't immediately obvious to me) that when you moved
to XG, your physical hardware wasn't compatible. The XG images are
for 10GiG ethernet, so the SFP+ adaptors on both
ends have to match, AND you have to have a 10GiGe compatible network
adaptor on your host, and it has to be
configured correctly.
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
