srsRAN/n310 | Error: failed receiving packet.

[houshangaziziaccelleran]

Hello

I have following UHD version on my server:

ad@bm-super11-intel:~/houshang$ uhd_config_info --version
UHD 4.7.0.0-0ubuntu1~jammy1
ad@bm-super11-intel:~/houshang$ ssh [[email protected]](mailto:[email protected])

And the following UHD version on my n310:

root@ni-n3xx-32000F1:~# uhd_config_info --version
UHD 4.7.0.0-0-ga5ed1872
root@ni-n3xx-32000F1:~#

They are the same and my n310 is updated with the following file:

ad@bm-super11-intel:~/houshang$ md5sum /usr/share/uhd/images/usrp_n310_fpga_HG.bit
532b338d6861268c05a4fd9837ca80e5  /usr/share/uhd/images/usrp_n310_fpga_HG.bit
ad@bm-super11-intel:~/houshang$

I am running srsRAN gNB on my server (Commit 9d5dd742a).

Here are the error messages I get:

==== gNB started ===
Type <h> to view help
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 2805; Underflow: 2238; Overflow: 0;
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 0; Underflow: 5; Overflow: 0;
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 0; Underflow: 4; Overflow: 0;
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 0; Underflow: 4; Overflow: 0;
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 0; Underflow: 4; Overflow: 0;
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.

And obviously it is not working with this amount of errors.

Can anyone help me with this please?

Thanks
Houshang

[kishorfarm]

Hello.

I have the same exact problem. I'm running srsRAN gnb with a N310 and UHD 4.7.0.0-0 version.

Did you manage to solve this? @houshangaziziaccelleran

Thank you and regards.

Below I copy the log:

root@optiplex-7040:~# gnb -c /home/enb/config/srsran/gnb_rf_n310_fdd_srsUE.yml

--== srsRAN gNB (commit e5d5b44b9) ==--

Lower PHY in quad executor mode.
Cell pci=1, bw=20 MHz, 1T1R, dl_arfcn=524000 (n7), dl_freq=2620.0 MHz, dl_ssb_arfcn=523970, ul_freq=2500.0 MHz

Available radio types: uhd.
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
[INFO] [LOGGING] Fastpath logging disabled at runtime.
Making USRP object with args 'type=n3xx,master_clock_rate=122.88e6,send_frame_size=8000,recv_frame_size=8000'
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=3269EB8,name=ni-n3xx-3269EB8,fpga=HG,claimed=False,addr=192.168.10.2,master_clock_rate=122.88e6,send_frame_size=8000,recv_frame_size=8000
[INFO] [MPM.main] Launching USRP/MPM, version: 4.7.0.0-ga5ed1872
[INFO] [MPM.main] Spawning RPC process...
[INFO] [MPM.PeriphManager] Device serial number: 3269EB8
[INFO] [MPM.PeriphManager] Initialized 2 daughterboard(s).
[INFO] [MPM.PeriphManager] init() called with device args `clock_source=internal,time_source=internal'.
[INFO] [MPM.RPCServer] RPC server ready!
[INFO] [MPM.RPCServer] Spawning watchdog task...
[INFO] [MPM.PeriphManager] init() called with device args `fpga=HG,master_clock_rate=122.88e6,mgmt_addr=192.168.10.2,name=ni-n3xx-3269EB8,product=n310,recv_frame_size=8000,send_frame_size=8000,clock_source=internal,time_source=internal'.
[INFO] [MPM.Magnesium-0] Re-initializing daughter board. This may take some time.
[INFO] [MPM.Magnesium-1] Re-initializing daughter board. This may take some time.
[WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping.
N2: Connection to AMF on 10.53.1.2:38412 completed
==== gNB started ===
Type <h> to view help
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 896; Underflow: 141; Overflow: 5;
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 7; Underflow: 0; Overflow: 0;
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
Late: 7; Underflow: 0; Overflow: 0;

Also, this is the srsRAN gnb YAML config file (it's the original srsRAN example config file modified to use a N310 instead of a B210):

# This example configuration outlines how to configure the srsRAN Project gNB to create a single FDD cell
# transmitting in band 3, with 20 MHz bandwidth and 15 kHz sub-carrier-spacing. A USRP B200 is configured
# as the RF frontend using split 8, with a Leo Bodnar GPSDO as an external reference clock.

# This particular configuration is intended to be used with srsUE. Note the `pdcch` parameters set in the
# `cell_cfg` section. These are set to match the capabilities of srsUE.

cu_cp:
  amf:
    addr: 10.53.1.2
    port: 38412
    bind_addr: 10.53.1.1
    supported_tracking_areas:
      - tac: 7
        plmn_list:
          - plmn: "00101"
            tai_slice_support_list:
              - sst: 1

ru_sdr:
  device_driver: uhd
  device_args: type=n3xx
  clock: gpsdo
  srate: 122.88
  tx_gain: 55
  rx_gain: 40

# DL EARFCN  Band  Mode  DL (MHz) 
# 368500     n3    FDD   1842.5   
# 524000     n7    FDD   2620         

# UL EARFCN  Band  Mode  UL (MHz)
# 349500     n3    FDD   1747.5
# 500000     n7    FDD   2500

cell_cfg:
  dl_arfcn: 524000
  band: 7
  channel_bandwidth_MHz: 20
  common_scs: 15
  plmn: "00101"
  tac: 7
  pdcch:
    dedicated:
      ss2_type: common
      dci_format_0_1_and_1_1: false
    common:
      ss0_index: 0
      coreset0_index: 12
  prach:
    prach_config_index: 1
  pdsch:
    mcs_table: qam64
  pusch:
    mcs_table: qam64

log:
  filename: /tmp/gnb.log
  all_level: info

pcap:
  mac_enable: false
  mac_filename: /tmp/gnb_mac.pcap
  ngap_enable: false
  ngap_filename: /tmp/gnb_ngap.pcap

[gabrielzb19]

Hi @kishorfarm @houshangaziziaccelleran I've got the same error with USRP x410, were you able to solve this tiemout error?

[kishorfarm]

Hi gabrielzb19.

I'm afraid the problem is not yet solved. I've tried different things with no success. Now I'm upgrading the SFP+ 1 Gb adapter to a SFP+ 10 Gb to see if the problem is a bottleneck in the Ethernet connection between the N310 and the PC with srsRAN. Will tell you if I have news. Regards.

[kishorfarm]

Well, finally I solved the problem. We moved from using a 1 Gb Ethernet adapter on SFP+ 0 to using a 10 Gb Ethernet adapter on SFP+ 1. The 1 Gb connection was not enough for srsRAN Project, it was needed to upgrade to 10 Gb.

[gabrielzb19]

@kishorfarm Great news, for me it also worked, but now I'm facing some issues when deploying the UE (my setup consists of two USRP one for gNB and another one for UE), I used the one suggested in SRSRAN documentation but I do not know how to adapt it to my USRPs (x410), can you share your UE .conf file please? It would be really helpful for me.

[kishorfarm]

Hi gabrielzb19. So far I'm only using COTS UEs (Motorola G55). I want to connect one srsue (using a B210) to the gnb (N310) but I've not tried yet.

[gabrielzb19]

Hi kishorfarm,
Just one more question, are you able to ping from one USRP to another by using the IP's assigned to their SFP interfaces ?
For instance:
USRP 1: 192.168.20.1
USRP 2: 192.168.100.2
Because I think my UE does not ''find'' the gNB because USRPs are not in the same network.