Closed tblake84 closed 6 years ago
Just to double check. The problem also exists if you run srsENB from outside of the Docker container, right?
Sorry for the late response. Yes, it occurs outside the docker container as well. I have tried various versions of UHD (3.9.7, 3.9.10 and the latest 3.11.0.1) and all of them show the same error:
root@srslte:/opt/srslte# srsenb enb.conf
--- Software Radio Systems LTE eNodeB ---
Reading configuration file enb.conf...
[INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-ga1b5c4ae
Opening USRP with args: addr=10.10.210.147,master_clock_rate=30.72e6
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Determining maximum frame size...
[INFO] [X300] Maximum frame size: 1472 bytes.
[INFO] [X300] Setup basic communication...
[INFO] [X300] Loading values from EEPROM...
[INFO] [X300] Setup RF frontend clocking...
Error opening UHD: code 44
Error opening RF device
Failed to find device UHD with args addr=10.10.210.147
I have now tried this on two different hosts with three different versions of UHD both in and outside of a docker container and I am getting all the same result.
I am using Ubuntu 16.04 and installing UHD via PyBOMBS.
Another update:
I tried running some of the example binaries and receive the same exact error.
root@srslte:/opt/srslte/build/lib/examples# ./usrp_txrx -o test.tmp -a addr=10.10.210.147 -f 1940e6 -g 10 -G 10
Opening RF device...
[INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-ga1b5c4ae
Opening USRP with args: addr=10.10.210.147,master_clock_rate=30.72e6
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Determining maximum frame size...
[ERROR] [X300] receive_from: Message too long
[INFO] [X300] Setup basic communication...
[INFO] [X300] Loading values from EEPROM...
[INFO] [X300] Setup RF frontend clocking...
Error opening UHD: code 44
No compatible RF frontend found
Error opening rf
I have tried as many different USRPs as I have (N310, N210, and X300) and they all exhibit the same problem. I get no ENB log output and these radios work fine in our other applications.
Thanks for checking again. We are working on it.
Fixed in release 18.06
For People which use maybe still an old Version and get this error for the srsUE with "Error opening UHD: code 44": For me the problem was, that I had an old FPGA Image for the USRP. After downloading new images via uhd_images_downloader tool and uploading the new images to the USRP the problem was fixed.
Fixed in release 18.06 of what ? Also i tried installing latest USRP images but error still coming for me.
I'm using version 19.12.0 of srsLTE and getting the same error. My device is USRP-2901 and using UHD 3.14.1.1-release
Hi, I am running srsenb on 18.04 ubuntu machine, but when i try to run it, it gives the the following error: Could anyone please help me in this regard
Having the exact same issue. It used to run fine for me. After I make some small change in the code (just add more logging), and do an incremental build. The problem happens. Reboot the computer and USRP don't help. However, after deleting the build directory, recompiling and make install the srsLTE again (i.e., making a full new build) solve the issue for me.
Hi guys, The same problem happened to me. I did what "twei7" suggested, but did not work. Any idea what would be the problem? I deploy srs LTE on ubuntu 18.04 cloud image, do you think this may cause the problem?
I am having the same issue when I run
"osboxes@osboxes:~$ sudo srsenb [sudo] password for osboxes: --- Software Radio Systems LTE eNodeB ---
Reading configuration file /root/.config/srsran/enb.conf... WARNING: Could not verify cpu0 scaling governor
Built in Release mode using commit 89f16eed2 on branch master.
Opening 1 channels in RF device=default with args=default [zmq] Error: RF device args are required for ZMQ no-RF module /home/osboxes/srsRAN/lib/src/phy/rf/rf_imp.c.129: No compatible RF frontend found Error initializing radio."
Can anybody guide me on this?
I am running srsenb in a docker container for testing. Previous versions had other problems but this latest commit exhibits an inability to initiate the RF frontend.
Here is the relevant portion of the enb.conf
The USRP is responding just fine to other applications and uhd_usrp_probe: