Last update for today… Installed latest UHD from ETTUS repository, downloaded
new images and tried the loader without success (the USRP probe shows the
incompatibility of the FPGA image with new UHD version):
```
abusso@ttclabsdr:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost
Thanks Rob.
About versions, indeed I mean 2.7 (I think this was the old one) and now is
3.8. The UHD version is the default one that comes with Ubuntu 18 LTS.
```
abusso@ttclabsdr:~$ uhd_usrp_probe --version
linux; GNU C++ version 7.3.0; Boost_106501; UHD_003.010.003.000-0-unknown
```
I can upg
We received the board at end of June 2020 and not used that much due to Covid
restriction in accessing the lab.
I think it was working with “old” GNU-Radio (version 2), but in May 2021 we
updated everything to GNU-Radio 3 (including Linux distribution, etc.). At that
point, I had problem since
I did some more experiments, but without results…
Just to answer your last, the USRP is connected directly to the NIC (no
switches).
```
abusso@ttclabsdr:~$ sudo ethtool enp4s0f0
Settings for enp4s0f0:
Supported ports: [ FIBRE ]
Supported link modes: 1baseT/Full
Sup
The NIC is an Intel X710 Dual Port 10Gb Direct Attach, SFP+,PCIe. MTU is now
9000. I tried now with 1500, but still same error. I still have to check with
new image, if any.
```
abusso@ttclabsdr:~$ ifconfig
eno1: flags=4163 mtu 1500
inet 10.181.165.152 netmask 255.255.252.0 broadcast
I can try re-programming with new images (if not already done) starting from
Vivado. Is this what you mean?
I tried a flood ping. With up to 6000 bytes packet all is fine. With 7000 I
start loosing a bit. With 8000 it loose 50%. I’m not sure if this is normal
with such long packets.
```
abusso
This is what I obtain from the two commands. In the image loader command, if I
do not specify the image it takes automatically the XG, which is the same I
used to program the FPGA with Vivado (2x10G).
```
abusso@ttclabsdr:~$ uhd_usrp_probe
```
```
linux; GNU C++ version 7.3.0; Boost_106501; UHD
That is what I did (with the help of a colleague). It all went fine till almost
the end. I managed to get the x310 working (e.g. answering to the
uhd_usrp_probe command) after programming with Vivado.
But when I try the uhd_image_loader command at the end, I get the error above
(exactly in the
Hello all,
Did you manage to solve this and how?
I had similar problem, even without modifying the image. After an update of UHD
drivers I loaded the new image using the image loader and something went wrong
(so I could not use the x310 anymore). I get the same error as reported in the
first p
