On 2021-12-08 03:25, iw1...@gmail.com wrote:
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: 10000baseT/Full
Supported pause frame use: Symmetric Receive-only Supports
auto-negotiation: No Supported FEC modes: Not reported Advertised link
modes: 10000baseT/Full Advertised pause frame use: No Advertised
auto-negotiation: No Advertised FEC modes: Not reported Speed:
10000Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0
Transceiver: internal Auto-negotiation: off Supports Wake-on: g
Wake-on: g Current message level: 0x00000007 (7) drv probe link Link
detected: yes |
Since there are two 10GBit connections, I tried the programming using
one or the other, but result is the same. So, I do not think it is a
problem of cable or SFP+ adapter.
I checked with wireshark what is going on, and the result is that
there is an exchange of 72 UDP packets of short length (16 bytes) from
PC to USRP, each followed by a reply of 16 bytes, and the
communication terminates with a longer one from PC (272 bytes)
followed by 4 bytes reply from USRP. So, it seems not much data is
transferred and the real image transfer never starts.
The packets are not all the same, so something seems going on, but I
have the impression that the last one creates some problems. For the
first 72, the answer is quite immediate (20-30us), but the last reply
from USRP takes almost 1 second.
If needed, I can attach the wireshark extrack.
||So, has this device always done this, or it started doing it at some
point recently? How old is the device?
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
