[srsran-users] Srsue with USRP N310 for MIMO 2x2 in SRSRAN version
家祺 张
eric990621 at outlook.com
Thu Apr 28 10:43:05 UTC 2022
Hello all,
I’m trying to use srsue with a USRP N310 to listening to a commercial LTE cell in MIMO 2x2. But I met the same questions as this link<https://lists.srsran.com/pipermail/srsran-users/2021-June/004351.html> discussed about.
I tried the advices the link gave, but as you know srsLTE has evolved to srsRan. I think some details may have changed and the configuration way in ue.conf is a little bit different.
The log below is what I got when I try:
nof_antennas = 2
device_name = uhd
device_args = type=x300,clock=external,sampling_rate=1.92e6
srate = 1.92e6
eric at eric-G3-3590:~$ sudo srsue
Couldn't open , trying /home/eric/.config/srsran/ue.conf
Reading configuration file /home/eric/.config/srsran/ue.conf...
WARNING: cpu0 scaling governor is not set to performance mode. Realtime processing could be compromised. Consider setting it to performance mode before running the application.
Built in Release mode using commit 5275f3336 on branch master.
Opening 2 channels in RF device=uhd with args=type=n3xx,clock=external,sampling_rate=1.92e6
Available RF device list: UHD zmq
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_4.1.0.HEAD-0-g25d617ca
[INFO] [LOGGING] Fastpath logging disabled at runtime.
Opening USRP channels=2, args: type=n3xx,master_clock_rate=122.88e6
[INFO] [UHD RF] RF UHD Generic instance constructed
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.10.2,type=n3xx,product=n310,serial=31BFEAB,fpga=HG,claimed=False,addr=192.168.10.2,master_clock_rate=122.88e6
[WARNING] [MPM.RPCServer] A timeout event occured!
[INFO] [MPM.PeriphManager] init() called with device args `fpga=HG,master_clock_rate=122.88e6,mgmt_addr=192.168.10.2,product=n310,clock_source=internal,time_source=internal'.
[WARNING] [UDP] The recv buffer could not be resized sufficiently.
Target sock buff size: 2500000 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.rmem_max=2500000
[WARNING] [UDP] The send buffer could not be resized sufficiently.
Target sock buff size: 2500000 bytes.
Actual sock buff size: 212992 bytes.
See the transport application notes on buffer resizing.
Please run: sudo sysctl -w net.core.wmem_max=2500000
[WARNING] [UDP] The current recv_buff_size of 212992 is less than the minimum recommended size of 816000 and may result in dropped packets on some NICs
[WARNING] [UDP] The current send_buff_size of 212992 is less than the minimum recommended size of 307200 and may result in dropped packets on some NICs
[WARNING] [RFNOC::GRAPH] One or more blocks timed out during flush!
[INFO] [MPM.Magnesium-0] Re-initializing daughter board. This may take some time.
[ERROR] [RPC] At least one PLL did not lock! Check the logs for details.
/home/eric/srsRAN/lib/src/phy/rf/rf_uhd_imp.cc:930: uhd_init failed, freeing...
[ERROR] [UHD RF] RuntimeError: Error during RPC call to `set_sync_source'. Error message: At least one PLL did not lock! Check the logs for details.
[ERROR] [MPM.RPCServer] Uncaught exception in method set_sync_source: At least one PLL did not lock! Check the logs for details.
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/usrp_mpm/rpc_server.py", line 186, in new_claimed_function
return function(*args)
File "/usr/lib/python3.7/site-packages/usrp_mpm/periph_manager/n3xx.py", line 705, in set_sync_source
skip_rfic=args.get('skip_rfic', None)
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/magnesium.py", line 400, in update_ref_clock_freq
self._reinit(self.master_clock_rate)
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/magnesium.py", line 359, in _reinit
self.init(args)
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/magnesium.py", line 295, in init
args, self._init_args, fast_reinit)
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/mg_init.py", line 615, in init
args
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/mg_init.py", line 547, in _full_init
self.PHASE_DAC_SPI_ADDR,
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/mg_init.py", line 181, in _init_lmk
self.log
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/lmk_mg.py", line 52, in __init__
self.config()
File "/usr/lib/python3.7/site-packages/usrp_mpm/dboard_manager/lmk_mg.py", line 218, in config
raise RuntimeError("At least one PLL did not lock! Check the logs for details.")
RuntimeError: At least one PLL did not lock! Check the logs for details.
Error initializing radio.
I have searched the error reason ’ RuntimeError: At least one PLL did not lock! Check the logs for details.’ From this link<https://github.com/EttusResearch/uhd/issues/449>, I I think the problem is with the UHD. But according to the discussion at this link, UHD 4.1 should be ok, but I'm still having this problem. Could it still be the UHD? My ubuntu version is 18.04 LTS and UHD is 4.1.0.HEAD-0-g25d617ca. Could you please give me a hand ? There's really nothing more I can do about this kind of problem, thank you very much for your kindness in taking a little time to focus on it..
Thanks sincerely,
Eric
从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20220428/d5a7335c/attachment-0001.htm>
More information about the srsran-users
mailing list