[srslte-users] LimeSDR USB crash when enb

Federico Quattrin fede.quattrin at gmail.com
Wed Jun 5 13:09:51 UTC 2019


Hi all,
I'm trying to build a enb with a limeSDR, I installed SoapySDR, LimeSuite
and LimeUtil. I'm working with the srsLTE version 18.02. when I built it I
did without UHD, bladeRF and without GUI. And I did run the command "sudo
srslte_install_configs.sh service".
I set the log file to be in debug mode but is it empty. Please attached
find you the enb.conf file. I don't know what the problem could be, maybe
some library from Soapy is missing? In the console I receive this message:


Built in Release mode using 18.12.0.

---  Software Radio Systems LTE eNodeB  ---

Reading configuration file /etc/srslte/enb.conf...
[INFO] [UHD] linux; GNU C++ version 8.3.0; Boost_106700;
UHD_3.14.0.0-0-unknown
Soapy has found device #0: addr=1d50:6108, driver=lime, label=LimeSDR-USB
[USB 3.0] 90706024F2337, media=USB 3.0, module=FX3, name=LimeSDR-USB,
serial=00090706024F2337,
[INFO] Make connection: 'LimeSDR-USB [USB 3.0] 90706024F2337'
[INFO] Reference clock 30.72 MHz
[INFO] Device name: LimeSDR-USB
[INFO] Reference: 30.72 MHz
[INFO] LMS7002M calibration values caching Disable
[INFO] RX LPF configured
Set Rx bandwidth to 2.50 MHz
[INFO] Filter calibrated. Filter order-4th, filter bandwidth set to 5
MHz.Real pole 1st order filter set to 2.5 MHz. Preemphasis filter not active
[INFO] TX LPF configured
Set Tx bandwidth to 5.00 MHz
Setting up RX stream
srsLTE crashed... backtrace saved in './srsLTE.backtrace.crash'...
---  exiting  ---
libusb: warning [libusb_exit] application left some devices open


Thanks in advance!
Greetings,
Federico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190605/0da51e3f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: enb.log
Type: text/x-log
Size: 39 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190605/0da51e3f/attachment.bin>


More information about the srsran-users mailing list