[srslte-users] Need help build error when make on srsLTE with LimeSDR
Andre Puschmann
andre.puschmann at softwareradiosystems.com
Fri Nov 9 16:45:34 UTC 2018
Now type "bt"+Enter and then "p e"+Enter and send the output
On 9/11/18 17:42, Sandi Suhendro wrote:
> Dear Andre,
> yes it crash, but the crash happen until I turn on the data in my phone.
>
> Here is the GDB trace :
>
> (gdb) run
> Starting program: /usr/local/bin/srsenb
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7fffee667700 (LWP 7892)]
> [New Thread 0x7fffede66700 (LWP 7893)]
>
> Built in Release mode using commit 1c015aab on branch master.
>
> --- Software Radio Systems LTE eNodeB ---
>
> Reading configuration file /home/duo/.srs/enb.conf...
> Error: could not create log file, no messages will be logged!
> [New Thread 0x7fffed665700 (LWP 7894)]
> Failed to open file "/tmp/enb.pcap" for writing
> linux; GNU C++ version 5.4.0 20160609; Boost_105800;
> UHD_003.010.002.HEAD-0-gbd6e21dc
>
> [New Thread 0x7fffe867b700 (LWP 7895)]
> [New Thread 0x7fffe7e7a700 (LWP 7896)]
> [Thread 0x7fffe7e7a700 (LWP 7896) exited]
> [New Thread 0x7fffe7679700 (LWP 7897)]
> [New Thread 0x7fffe6e78700 (LWP 7898)]
> [New Thread 0x7fffe6677700 (LWP 7899)]
> [New Thread 0x7fffe5e76700 (LWP 7900)]
> [New Thread 0x7fffe5675700 (LWP 7901)]
> [Thread 0x7fffe867b700 (LWP 7895) exited]
> [Thread 0x7fffe5e76700 (LWP 7900) exited]
> [New Thread 0x7fffe5e76700 (LWP 7902)]
> [Thread 0x7fffe5e76700 (LWP 7902) exited]
> [New Thread 0x7fffe5e76700 (LWP 7903)]
> [Thread 0x7fffe5e76700 (LWP 7903) exited]
> Soapy has found device #0: addr=1d50:6108, driver=lime,
> label=LimeSDR-USB [USB 3.0] 9061C02C73125, media=USB 3.0, module=FX3,
> name=LimeSDR-USB, serial=0009061C02C73125,
> [Thread 0x7fffe7679700 (LWP 7897) exited]
> [INFO] Make connection: 'LimeSDR-USB [USB 3.0] 9061C02C73125'
> [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
> Setting up TX stream
> Available device sensors:
> - clock_locked
> - lms7_temp
> Available sensors for RX channel 0:
> - lo_locked
> [INFO] Tx calibration finished
> [INFO] Rx calibration finished
> [New Thread 0x7fffe7679700 (LWP 7904)]
> [Thread 0x7fffe7679700 (LWP 7904) exited]
> State of gain elements for Rx channel 0 (AGC not supported):
> - TIA: 9.00 dB
> - LNA: 30.00 dB
> - PGA: -4.00 dB
> State of gain elements for Tx channel 0 (AGC not supported):
> - TIA: 9.00 dB
> - LNA: 30.00 dB
> - PGA: -4.00 dB
> Rx antenna set to LNAH
> Tx antenna set to BAND1
> [New Thread 0x7fffe7679700 (LWP 7905)]
>
> Warning burst preamble is not calibrated for device lime. Set a value
> manually
>
> Setting frequency: DL=1845.0 Mhz, UL=1750.0 MHz
> Tuned Tx to 1845.00 MHz
> Tuned Rx to 1750.00 MHz
> [New Thread 0x7fffe5e76700 (LWP 7906)]
> Warning: Failed to create thread with real-time priority. Creating it
> with normal priority: Cannot allocate memory
> [New Thread 0x7fffe7e7a700 (LWP 7907)]
> [Thread 0x7fffe5e76700 (LWP 7906) exited]
> [New Thread 0x7fffe867b700 (LWP 7908)]
> Warning: Failed to create thread with real-time priority. Creating it
> with normal priority: Cannot allocate memory
> [New Thread 0x7fffca502700 (LWP 7909)]
> [Thread 0x7fffe867b700 (LWP 7908) exited]
> [New Thread 0x7fffc9d01700 (LWP 7910)]
> Warning: Failed to create thread with real-time priority. Creating it
> with normal priority: Cannot allocate memory
> [New Thread 0x7fffc9500700 (LWP 7911)]
> [Thread 0x7fffc9d01700 (LWP 7910) exited]
> [New Thread 0x7fffc8cff700 (LWP 7912)]
> Warning: Failed to create thread with real-time priority. Creating it
> with normal priority: Cannot allocate memory
> [New Thread 0x7fffc84fe700 (LWP 7913)]
> [Thread 0x7fffc8cff700 (LWP 7912) exited]
> [New Thread 0x7fffc7cfd700 (LWP 7914)]
> [New Thread 0x7fffc74fc700 (LWP 7915)]
> [New Thread 0x7fffc6cfb700 (LWP 7916)]
> [New Thread 0x7fffc64fa700 (LWP 7917)]
> [New Thread 0x7fffc5cf9700 (LWP 7918)]
> [New Thread 0x7fffc54f8700 (LWP 7919)]
> Set master clock rate to 15.36 MHz
> Setting Sampling frequency 3.84 MHz
> [INFO] RX LPF configured
> Set Rx bandwidth to 2.88 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 manual TX/RX offset to 72 samples
>
> ==== eNodeB started ===
> Type <t> to view trace
> [INFO] Tx calibration finished
> [INFO] Rx calibration finished
> [New Thread 0x7fffc4cf7700 (LWP 7920)]
> [New Thread 0x7fffb7fff700 (LWP 7921)]
> [WARNING] L
> RACH: tti=6381, preamble=29, offset=3, temp_crnti=0x46
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> [WARNING] L
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> User 0x46 connected
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
> [WARNING] L
> Error: Can't write to empty file handle
> Error: Can't write to empty file handle
>
> Thread 26 "srsenb" received signal SIGBUS, Bus error.
> [Switching to Thread 0x7fffc6cfb700 (LWP 7916)]
> 0x00000000004b7c7e in
> srsenb::rrc::ue::send_connection_reconf_new_bearer(LIBLTE_S1AP_E_RABTOBESETUPLISTBEARERSUREQ_STRUCT*)
> ()
> (gdb)
>
> the enb.log same as attached.
>
>
> On Fri, Nov 9, 2018 at 11:34 PM Andre Puschmann
> <andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>> wrote:
>
> Hey,
>
> what do you mean by "stop by it self"? Does it crash? If so, send the
> backtrace file that is generated. You can also try to run the eNB in gdb
> with "gdb --args srsenb".
>
> Thanks
> Andre
>
> On 9/11/18 17:24, Sandi Suhendro wrote:
> > Hi Andre,
> > I set it to enable but its empty on tmp, thats why I create from
> wireshark.
> > also, I cannot close enb cause it stop by it self when turn on the
> data.
> >
> > here we go again the file attached.
> >
> > best,
> > Sandi
> >
> > On Fri, Nov 9, 2018 at 11:15 PM Andre Puschmann
> > <andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>> wrote:
> >
> > Hey,
> >
> > the enb.log is corrupted at the end (i.e. not all is written
> to the
> > file). Can you rerun and close the eNB properly so it will
> write the
> > entire logs? Also, please capture eNB PCAP by either turning
> PCAP on in
> > the config for appending --pcap.enable=true on the command line.
> >
> > Thanks
> > Andre
> >
> >
> > On 9/11/18 16:56, Sandi Suhendro wrote:
> > > Dear Andre,
> > > here is the pcap and enb.log attached.
> > >
> > > the connection is drop when I turn on the data.
> > > and here is the srsenb log on the terminal :
> > >
> > > <<<<<<<<<<<<
> > > --- Software Radio Systems LTE eNodeB ---
> > >
> > > Reading configuration file /home/duo/.srs/enb.conf...
> > > linux; GNU C++ version 5.4.0 20160609; Boost_105800;
> > > UHD_003.010.002.HEAD-0-gbd6e21dc
> > >
> > > Soapy has found device #0: addr=1d50:6108, driver=lime,
> > > label=LimeSDR-USB [USB 3.0] 9061C02C73125, media=USB 3.0,
> module=FX3,
> > > name=LimeSDR-USB, serial=0009061C02C73125,
> > > [INFO] Make connection: 'LimeSDR-USB [USB 3.0] 9061C02C73125'
> > > [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
> > > Setting up TX stream
> > > Available device sensors:
> > > - clock_locked
> > > - lms7_temp
> > > Available sensors for RX channel 0:
> > > - lo_locked
> > > [INFO] Tx calibration finished
> > > [INFO] Rx calibration finished
> > > State of gain elements for Rx channel 0 (AGC not supported):
> > > - TIA: 9.00 dB
> > > - LNA: 30.00 dB
> > > - PGA: -4.00 dB
> > > State of gain elements for Tx channel 0 (AGC not supported):
> > > - TIA: 9.00 dB
> > > - LNA: 30.00 dB
> > > - PGA: -4.00 dB
> > > Rx antenna set to LNAH
> > > Tx antenna set to BAND1
> > >
> > > Warning burst preamble is not calibrated for device lime.
> Set a value
> > > manually
> > >
> > > Setting frequency: DL=1845.0 Mhz, UL=1750.0 MHz
> > > Tuned Tx to 1845.00 MHz
> > > Tuned Rx to 1750.00 MHz
> > > Set master clock rate to 15.36 MHz
> > > Setting Sampling frequency 3.84 MHz
> > > [INFO] RX LPF configured
> > > Set Rx bandwidth to 2.88 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 manual TX/RX offset to 72 samples
> > >
> > > ==== eNodeB started ===
> > > Type <t> to view trace
> > > [INFO] Tx calibration finished
> > > [INFO] Rx calibration finished
> > > [WARNING] L
> > > RACH: tti=9281, preamble=45, offset=3, temp_crnti=0x46
> > > Unhandled feature in RRC function:
> > > liblte_rrc_unpack_rrc_connection_setup_complete_msg
> > >
> > > User 0x46 connected
> > > Bus error *(this happen when tuen on the data)*
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >
> > > I think the problem related this message : Unhandled feature
> in RRC
> > > function: liblte_rrc_unpack_rrc_connection_setup_complete_msg
> > >
> > > looking forward to hearing advise from you! :-)
> > >
> > > Many Thanks.
> > >
> > > regards,
> > > Sandi / DUO
> > >
> > > On Fri, Nov 9, 2018 at 3:57 PM Andre Puschmann
> > > <andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>> wrote:
> > >
> > > Hey,
> > >
> > > can you provide a eNB log with loglevel info along with the
> > > correpsonding S1 pcap, please? From the last PCAP you sent
> > everything
> > > looked fine at first glance.
> > >
> > > Thanks
> > > Andre
> > >
> > >
> > > On 8/11/18 10:23, ALEJANDRO BLANCO PIZARRO wrote:
> > > > Hi Sandi,
> > > >
> > > > Hi I am not an expert on LimeSRD and srsLTE, because I
> > always use
> > > USRP.
> > > > But, when the UE cannot attach correctly it is probably a
> > > > misconfiguration in the EPC, what EPC are you using?
> If you
> > can attach
> > > > the log of the EPC it will be great.
> > > >
> > > > BTW, 25MHz is pnb=25, not 15. If I were you, I would
> > configure the
> > > basic
> > > > set up, change the value of pnb to 6.
> > > >
> > > > Best,
> > > > Alejandro
> > > >
> > > > El jue., 8 nov. 2018 a las 5:08, Sandi Suhendro
> > (<djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>>) escribió:
> > > >
> > > > Hi Alejandro,
> > > > Change to 5mhz set on pnb=15
> > > >
> > > > Same result. :(
> > > > Always hangup after turn on data.
> > > >
> > > > Regards,
> > > > Sandi
> > > >
> > > > On Wed, Nov 7, 2018, 23:36 ALEJANDRO BLANCO PIZARRO
> > > > <100283180 at alumnos.uc3m.es
> <mailto:100283180 at alumnos.uc3m.es>
> > <mailto:100283180 at alumnos.uc3m.es
> <mailto:100283180 at alumnos.uc3m.es>>
> <mailto:100283180 at alumnos.uc3m.es <mailto:100283180 at alumnos.uc3m.es>
> > <mailto:100283180 at alumnos.uc3m.es
> <mailto:100283180 at alumnos.uc3m.es>>>
> > > <mailto:100283180 at alumnos.uc3m.es
> <mailto:100283180 at alumnos.uc3m.es>
> > <mailto:100283180 at alumnos.uc3m.es
> <mailto:100283180 at alumnos.uc3m.es>>
> > > <mailto:100283180 at alumnos.uc3m.es
> <mailto:100283180 at alumnos.uc3m.es>
> > <mailto:100283180 at alumnos.uc3m.es
> <mailto:100283180 at alumnos.uc3m.es>>>> wrote:
> > > >
> > > > Have you tried to decrement the bandwidth? It
> could be
> > > that with
> > > > your bandwidth, you have bottleneck. Try 5 MHz.
> > > >
> > > > Best,
> > > > Alejandro
> > > >
> > > > El mié., 7 nov. 2018 16:53, Sandi Suhendro
> > > <djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > > <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com> <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com>>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>> escribió:
> > > >
> > > > Dear Ignas, Andre,
> > > > the phone is attached but it produce an error
> > when turn on
> > > > the cellular data on my phone: (VIVO XShot)
> > > >
> > > > here is the log : (pcap attached)
> > > >
> > > > ==== eNodeB started ===
> > > > Type <t> to view trace
> > > > [INFO] Tx calibration finished
> > > > [INFO] Rx calibration finished
> > > > [WARNING] L
> > > > [WARNING] L
> > > > RACH: tti=10221, preamble=23, offset=1,
> > temp_crnti=0x46
> > > > RACH: tti=1, preamble=23, offset=1,
> temp_crnti=0x47
> > > > Disconnecting rnti=0x46.
> > > > Disconnecting rnti=0x47.
> > > > RACH: tti=381, preamble=44, offset=1,
> > temp_crnti=0x48
> > > > Disconnecting rnti=0x48.
> > > > RACH: tti=2891, preamble=22, offset=1,
> > temp_crnti=0x49
> > > > Unhandled feature in RRC function:
> > > >
> liblte_rrc_unpack_rrc_connection_setup_complete_msg
> > > >
> > > > Disconnecting rnti=0x49.
> > > > RACH: tti=4671, preamble=9, offset=1,
> > temp_crnti=0x4a
> > > > Unhandled feature in RRC function:
> > > >
> liblte_rrc_unpack_rrc_connection_setup_complete_msg
> > > >
> > > > User 0x4a connected
> > > > Bus error
> > > > >>>>>>>>>>>>>>>>.
> > > >
> > > > hope you can give me advise what is wrong?
> Thanks in
> > > advance.
> > > >
> > > > regards,
> > > > DUO / Sandi
> > > >
> > > >
> > > >
> > > > On Tue, Nov 6, 2018 at 8:43 PM Sandi Suhendro
> > > > <djks74 at gmail.com
> <mailto:djks74 at gmail.com> <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com>>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>> wrote:
> > > >
> > > > Dear Ignas,
> > > > Thanks to let me know to update. Now it
> > works and
> > > i saw
> > > > my 4g network now. :)
> > > >
> > > > Just strange not all phone see the
> network. Will
> > > try to
> > > > attach now. :)
> > > >
> > > > Thanks and warm regards,
> > > > Sandi
> > > >
> > > > On Tue, Nov 6, 2018, 19:56 Ignas
> Jarusevicius
> > > > <i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>
> > <mailto:i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>>
> > > <mailto:i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>
> > <mailto:i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>>>
> > > > <mailto:i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>
> > <mailto:i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>>
> > > <mailto:i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>
> > <mailto:i.jarusevicius at limemicro.com
> <mailto:i.jarusevicius at limemicro.com>>>> wrote:
> > > >
> > > > Hi Sandri,
> > > >
> > > > I have noticed that you are using old
> > libLimeSuite
> > > > version as recent versions show
> > 'module=FX3' for
> > > > LimeSDR-USB. So try updating
> LimeSuite.
> > > > Also, I was I able to get srsenb
> working
> > with
> > > > LimeSDR boards few months ago. I have
> > attached one
> > > > of my enb.conf that used to work (not
> > sure if it
> > > > still works with current srsLTE
> version).
> > > >
> > > > -Ignas
> > > >
> > > > On 2018-11-05 16:02, Sandi
> Suhendro wrote:
> > > >> Hi Andre,
> > > >> ok finally working to Lime direct via
> > Soapy, just
> > > >> edit the makelist text and remove
> the UHD.
> > > >>
> > > >> here I got more error, what
> should I do?
> > > >>
> > > >> <<<<<<<<<<
> > > >> --- Software Radio Systems LTE
> eNodeB ---
> > > >>
> > > >> Reading configuration file
> > > /home/duo/.srs/enb.conf...
> > > >> Soapy has found device #0:
> addr=1d50:6108,
> > > >> driver=lime, label=LimeSDR-USB
> [USB 3.0]
> > > >> 9061C02C73125, media=USB 3.0,
> > module=STREAM,
> > > >> name=LimeSDR-USB,
> serial=0009061C02C73125,
> > > >> [INFO] Make connection: 'LimeSDR-USB
> > [USB 3.0]
> > > >> 9061C02C73125'
> > > >> [INFO] Device name: LimeSDR-USB
> > > >> [INFO] Reference: 30.72 MHz
> > > >> [INFO] Init LMS7002M(0)
> > > >> [INFO] Ver=7, Rev=1, Mask=1
> > > >> [INFO] LMS7002M calibration values
> > caching Enable
> > > >> Set Rx bandwidth to 2.50 MHz
> > > >> [ERROR] setBandwidth(Tx, 0, 1.44 MHz)
> > Failed - Tx
> > > >> lpf(1.44 MHz) out of range 5-40
> MHz and
> > > 50-130 MHz
> > > >> setBandwidth fail: Tx lpf(1.44
> MHz) out
> > of range
> > > >> 5-40 MHz and 50-130 MHz
> > > >> Setting up RX stream
> > > >> Setting up TX stream
> > > >> Available device sensors:
> > > >> - clock_locked
> > > >> - lms7_temp
> > > >> Available sensors for RX channel 0:
> > > >> - lo_locked
> > > >> State of gain elements for Rx
> channel 0
> > (AGC not
> > > >> supported):
> > > >> - LNA: 30.00 dB
> > > >> - TIA: 0.00 dB
> > > >> - PGA: 5.00 dB
> > > >> State of gain elements for Tx
> channel 0
> > (AGC not
> > > >> supported):
> > > >> - LNA: nan dB
> > > >> - TIA: nan dB
> > > >> - PGA: nan dB
> > > >> Rx antenna set to LNAL
> > > >> Tx antenna set to BAND1
> > > >>
> > > >> Warning burst preamble is not
> > calibrated for
> > > >> device lime. Set a value manually
> > > >>
> > > >> Setting frequency: DL=1845.0 Mhz,
> > UL=1750.0 MHz
> > > >> Tuned Tx to 1845.00 MHz
> > > >> Tuned Rx to 1750.00 MHz
> > > >> Set master clock rate to 11.52 MHz
> > > >> Setting Sampling frequency 11.52 MHz
> > > >> setSampleRate Rx fail:
> > SoapyLMS7::setSampleRate()
> > > >> -- rate too high
> > > >> setSampleRate Tx fail:
> > SoapyLMS7::setSampleRate()
> > > >> -- rate too high
> > > >>
> > > >> Warning TX/RX time offset for
> sampling rate
> > > -1 KHz
> > > >> not calibrated. Using
> interpolated value
> > > >>
> > > >>
> > > >> ==== eNodeB started ===
> > > >> Type <t> to view trace
> > > >>
> > > >> >>>>>>>>>>>>>>
> > > >>
> > > >> Please advise! Thanks. :-)
> > > >>
> > > >> regards,
> > > >> Sandi / DUO
> > > >>
> > > >>
> > > >> On Mon, Nov 5, 2018 at 8:07 PM Sandi
> > Suhendro
> > > >> <djks74 at gmail.com
> <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>> wrote:
> > > >>
> > > >> I did try remove the soapyUHD and
> > delete the
> > > >> libuhd and libuhdsupport from
> > usr/local/lib,
> > > >> but when re install the
> srs-LTE, it
> > gives me
> > > >> error it need UHD.
> > > >> do you know it may cause I
> miss it
> > how to
> > > >> build srsLTE direct to soapySDR?
> > > >>
> > > >> anyway, it has output signal on
> > earfcn 1600,
> > > >> but dont see the network with
> UHD.
> > > >>
> > > >> maybe better using soapySDR
> instead
> > UHD, but
> > > >> the installation asking UHD.
> > > >>
> > > >> please advise.
> > > >>
> > > >> regards,
> > > >> Sandi
> > > >>
> > > >> On Mon, Nov 5, 2018 at 3:11
> AM Andre
> > > Puschmann
> > > >>
> > <andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>>>
> > > >> wrote:
> > > >>
> > > >> Hey,
> > > >>
> > > >> seems like you are trying to
> > run the Lime
> > > >> through UHD, i.e. using the
> > > >> uhd-soapy wrapper. I am not
> > sure if it is
> > > >> working well but maybe it
> > > >> does. Does it output a
> signal?
> > > >>
> > > >> We do have a Soapy driver
> which
> > also
> > > works
> > > >> with the Lime so maybe try
> > > >> using that instead. Probably
> > the easiest
> > > >> is to uninstall the uhd-soapy
> > > >> wrapper. The problem here is
> > that the
> > > >> srsLTE's RF driver
> library stops
> > > >> looking for other devices as
> > soon as a
> > > >> supported device is found
> and the
> > > >> UHD driver is the first
> to query.
> > > >>
> > > >>
> > > >> Hope that helps.
> > > >>
> > > >> Cheers
> > > >> Andre
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On 4/11/18 15:07, Sandi
> > Suhendro wrote:
> > > >> > Dear Andre,
> > > >> > Do you know what I miss?
> > > >> > I have this following
> error :
> > > >> > <<<<<<<<<
> > > >> > sudo srsenb
> > > >> > linux; GNU C++ version
> 5.4.0
> > 20160609;
> > > >> Boost_105800;
> > > >> >
> UHD_003.010.002.HEAD-0-gbd6e21dc
> > > >> >
> > > >> >
> > > >> > Built in Release mode using
> > commit
> > > >> 1c015aab on branch master.
> > > >> >
> > > >> > --- Software Radio
> Systems LTE
> > > eNodeB ---
> > > >> >
> > > >> > Reading configuration file
> > > >> /home/duo/.srs/enb.conf...
> > > >> > Opening USRP with args:
> > > >> > -- Make connection:
> > 'LimeSDR-USB [USB
> > > >> 3.0] 9061C02C73125'
> > > >> > -- Device name: LimeSDR-USB
> > > >> > -- Reference: 30.72 MHz
> > > >> > -- Init LMS7002M(0)
> > > >> > -- Ver=7, Rev=1, Mask=1
> > > >> > -- LMS7002M calibration
> > values caching
> > > >> Enable
> > > >> > Setting frequency:
> DL=1845.0 Mhz,
> > > >> UL=1750.0 MHz
> > > >> > Setting Sampling frequency
> > 11.52 MHz
> > > >> >
> > > >> > Warning TX/RX time
> offset has
> > not been
> > > >> calibrated for device
> > > >> > uhd_unknown. Set a
> value manually
> > > >> >
> > > >> >
> > > >> > ==== eNodeB started ===
> > > >> > Type <t> to view trace
> > > >> > Error timed out while
> > receiving samples
> > > >> from UHD.
> > > >> > Error timed out while
> > receiving samples
> > > >> from UHD.
> > > >> > Error timed out while
> > receiving samples
> > > >> from UHD.
> > > >> >>>>>>>>>>>>
> > > >> >
> > > >> > And in the log of
> nextepc is :
> > > >> > [11/04 20:48:59.179] eNB-S1
> > > >> accepted[127.0.1.1]:55722 in
> > s1_path
> > > module
> > > >> > [11/04 20:48:59.180] eNB-S1
> > > >> accepted[127.0.1.1] in
> > master_sm module
> > > >> >
> > > >> >
> > > >> > Please advise! Thanks in
> > advance. :-)
> > > >> >
> > > >> > regards,
> > > >> > Sandi / DUO
> > > >> >
> > > >> >
> > > >> > On Fri, Nov 2, 2018 at 3:51
> > PM Andre
> > > >> Puschmann
> > > >> >
> > > >>
> > > <andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>>
> > > >> >
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>>>>
> > > >> wrote:
> > > >> >
> > > >> > Sandi,
> > > >> >
> > > >> > glad to hear you got it
> > > working. Let
> > > >> us know how it goes.
> > > >> >
> > > >> > Cheers
> > > >> > Andre
> > > >> >
> > > >> > On 2/11/18 8:54, Sandi
> > Suhendro
> > > wrote:
> > > >> > > Dear Andre,
> > > >> > > sorry for this simple
> > matter. try
> > > >> to remove all and re
> install and it
> > > >> > > works now. Thanks.
> > > >> > >
> > > >> > > regards,
> > > >> > > Sandi / DUO
> > > >> > >
> > > >> > > On Thu, Nov 1,
> 2018 at
> > 10:33 PM
> > > >> Sandi Suhendro
> > <djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > >> <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>
> > > >> >
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > >> <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>>
> > > >> > >
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > >> <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>
> > > >> <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>
> > > >> <mailto:djks74 at gmail.com
> <mailto:djks74 at gmail.com>
> > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>
> > > <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>
> <mailto:djks74 at gmail.com <mailto:djks74 at gmail.com>>>>>>> wrote:
> > > >> > >
> > > >> > > Dear Andre,
> > > >> > > Thanks for
> response.
> > > >> > >
> > > >> > > Im using ubuntu
> > 16.04 and
> > > >> build soapySDR from git.
> > > >> > > as I remember Im
> > using ppa at
> > > >> first but I also install
> again
> > > >> > from git.
> > > >> > > what should I do?
> > remove all
> > > >> soapy from apt and make
> uninstall
> > > >> > from
> > > >> > > git too then re
> > install?
> > > >> > >
> > > >> > > please advise.
> > > >> > >
> > > >> > > regards,
> > > >> > > Sandi / DUO
> > > >> > >
> > > >> > > On Thu, Nov
> 1, 2018 at
> > > 9:33 PM
> > > >> Andre Puschmann
> > > >> > >
> > > >>
> > > <andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>>
> > > >> >
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>>>
> > > >> > >
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>>
> > > >> >
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>
> > > >>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>
> > > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>
> > <mailto:andre.puschmann at softwareradiosystems.com
> <mailto:andre.puschmann at softwareradiosystems.com>>>>>>>
> > > >> wrote:
> > > >> > >
> > > >> > > Likely to
> be a
> > > mismatch of
> > > >> headers. What system are
> you on and
> > > >> > > where do
> > > >> > > you get the
> > soapy dev
> > > >> package from? git, ppa?
> > > >> > >
> > > >> > >
> > > >> > > On 31/10/18
> > 12:43, Sandi
> > > >> Suhendro wrote:
> > > >> > > > Dear list,
> > > >> > > > hope
> someone can
> > > give me
> > > >> advise what is wrong?
> > > >> > > > Im runing
> > fine with
> > > >> osmocom or openbts-umts.
> (2g/3g)
> > > >> > > > but....
> > > >> > > > Im facing
> > SoapySDR
> > > range
> > > >> error when build srsLTE :
> > > >> > > >
> > > >> > > > [ 40%]
> Linking C
> > > >> executable pdsch_test
> > > >> > > > [ 40%]
> Built
> > target
> > > >> pdsch_test
> > > >> > > > [ 40%]
> Building C
> > > object
> > > >> > > >
> > > >>
> > > lib/src/phy/rf/CMakeFiles/srslte_rf_utils.dir/rf_utils.c.o
> > > >> > > > [ 40%]
> > Linking C static
> > > >> library libsrslte_rf_utils.a
> > > >> > > > [ 40%]
> Built
> > target
> > > >> srslte_rf_utils
> > > >> > > > [ 41%]
> Building C
> > > object
> > > >> > >
> > > >>
> > > lib/src/phy/rf/CMakeFiles/srslte_rf.dir/rf_imp.c.o
> > > >> > > > [ 41%]
> Building C
> > > object
> > > >> > > >
> > > >>
> > > lib/src/phy/rf/CMakeFiles/srslte_rf.dir/rf_uhd_imp.c.o
> > > >> > > > [ 41%]
> > Building CXX
> > > object
> > > >> > > >
> > > >>
> > > lib/src/phy/rf/CMakeFiles/srslte_rf.dir/uhd_c_api.cpp.o
> > > >> > > > [ 41%]
> Building C
> > > object
> > > >> > > >
> > > >>
> > > lib/src/phy/rf/CMakeFiles/srslte_rf.dir/rf_soapy_imp.c.o
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> /usr/include/SoapySDR/Types.h:25:3:
> > > error:
> > > >> conflicting
> > > >> > types for
> > > >> > > >
> ‘SoapySDRRange’
> > > >> > > > }
> SoapySDRRange;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > /usr/local/include/SoapySDR/Types.h:25:3:
> > > >> note: previous
> > > >> > >
> declaration of
> > > >> > > >
> > ‘SoapySDRRange’ was
> > > here
> > > >> > > > }
> SoapySDRRange;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> /usr/include/SoapySDR/Types.h:33:3:
> > > error:
> > > >> conflicting
> > > >> > types for
> > > >> > > >
> ‘SoapySDRKwargs’
> > > >> > > > }
> > SoapySDRKwargs;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > /usr/local/include/SoapySDR/Types.h:33:3:
> > > >> note: previous
> > > >> > >
> declaration of
> > > >> > > >
> ‘SoapySDRKwargs’
> > > was here
> > > >> > > > }
> > SoapySDRKwargs;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:39:30:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > > ‘SoapySDRKwargs_fromString’
> > > >> > > >
> SOAPY_SDR_API
> > > >> SoapySDRKwargs
> > > >> >
> > SoapySDRKwargs_fromString(const
> > > >> > > char
> *markup);
> > > >> > > >
> > > >>
> ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:39:30:
> > > >> note: previous
> > > >> > >
> declaration of
> > > >> > > >
> > > >>
> ‘SoapySDRKwargs_fromString’ was
> > here
> > > >> > > >
> SOAPY_SDR_API
> > > >> SoapySDRKwargs
> > > >> >
> > SoapySDRKwargs_fromString(const
> > > >> > > char
> *markup);
> > > >> > > >
> > > >>
> ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:45:21:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > > ‘SoapySDRKwargs_toString’
> > > >> > > >
> > SOAPY_SDR_API char
> > > >>
> *SoapySDRKwargs_toString(const
> > > >> > >
> SoapySDRKwargs
> > *args);
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:45:21:
> > > >> note: previous
> > > >> > >
> declaration of
> > > >> > > >
> > > >> ‘SoapySDRKwargs_toString’
> was here
> > > >> > > >
> > SOAPY_SDR_API char
> > > >>
> *SoapySDRKwargs_toString(const
> > > >> > >
> SoapySDRKwargs
> > *args);
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> /usr/include/SoapySDR/Types.h:50:5:
> > > error:
> > > >> redeclaration of
> > > >> > > enumerator
> > > >> > > >
> > > ‘SOAPY_SDR_ARG_INFO_BOOL’
> > > >> > > >
> > > >> SOAPY_SDR_ARG_INFO_BOOL,
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > /usr/local/include/SoapySDR/Types.h:50:5:
> > > >> note: previous
> > > >> > > definition of
> > > >> > > >
> > > >> ‘SOAPY_SDR_ARG_INFO_BOOL’
> was here
> > > >> > > >
> > > >> SOAPY_SDR_ARG_INFO_BOOL,
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> /usr/include/SoapySDR/Types.h:51:5:
> > > error:
> > > >> redeclaration of
> > > >> > > enumerator
> > > >> > > >
> > > ‘SOAPY_SDR_ARG_INFO_INT’
> > > >> > > >
> > > SOAPY_SDR_ARG_INFO_INT,
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > /usr/local/include/SoapySDR/Types.h:51:5:
> > > >> note: previous
> > > >> > > definition of
> > > >> > > >
> > > ‘SOAPY_SDR_ARG_INFO_INT’
> > > >> was here
> > > >> > > >
> > > SOAPY_SDR_ARG_INFO_INT,
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> /usr/include/SoapySDR/Types.h:52:5:
> > > error:
> > > >> redeclaration of
> > > >> > > enumerator
> > > >> > > >
> > > ‘SOAPY_SDR_ARG_INFO_FLOAT’
> > > >> > > >
> > > >> SOAPY_SDR_ARG_INFO_FLOAT,
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > /usr/local/include/SoapySDR/Types.h:52:5:
> > > >> note: previous
> > > >> > > definition of
> > > >> > > >
> > > >>
> ‘SOAPY_SDR_ARG_INFO_FLOAT’ was here
> > > >> > > >
> > > >> SOAPY_SDR_ARG_INFO_FLOAT,
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> /usr/include/SoapySDR/Types.h:53:5:
> > > error:
> > > >> redeclaration of
> > > >> > > enumerator
> > > >> > > >
> > > ‘SOAPY_SDR_ARG_INFO_STRING’
> > > >> > > >
> > > >> SOAPY_SDR_ARG_INFO_STRING
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > /usr/local/include/SoapySDR/Types.h:53:5:
> > > >> note: previous
> > > >> > > definition of
> > > >> > > >
> > > >>
> ‘SOAPY_SDR_ARG_INFO_STRING’ was
> > here
> > > >> > > >
> > > >> SOAPY_SDR_ARG_INFO_STRING
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> /usr/include/SoapySDR/Types.h:54:3:
> > > error:
> > > >> conflicting
> > > >> > types for
> > > >> > > >
> > ‘SoapySDRArgInfoType’
> > > >> > > > }
> > SoapySDRArgInfoType;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > /usr/local/include/SoapySDR/Types.h:54:3:
> > > >> note: previous
> > > >> > >
> declaration of
> > > >> > > >
> > ‘SoapySDRArgInfoType’
> > > >> was here
> > > >> > > > }
> > SoapySDRArgInfoType;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:103:3:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> ‘SoapySDRArgInfo’
> > > >> > > > }
> > SoapySDRArgInfo;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:103:3:
> > > >> note: previous
> > > >> > >
> declaration of
> > > >> > > >
> ‘SoapySDRArgInfo’
> > > was here
> > > >> > > > }
> > SoapySDRArgInfo;
> > > >> > > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:114:20:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > ‘SoapySDRKwargs_set’
> > > >> > > >
> > SOAPY_SDR_API void
> > > >>
> > SoapySDRKwargs_set(SoapySDRKwargs *args,
> > > >> > > const char
> > > >> > > > *key, co
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:120:19: note:
> > > >> previous
> > > >> > > declaration
> > > >> > > > of
> > ‘SoapySDRKwargs_set’
> > > >> was here
> > > >> > > >
> > SOAPY_SDR_API int
> > > >>
> > SoapySDRKwargs_set(SoapySDRKwargs *args,
> > > >> > > const char
> > > >> > > > *key, con
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:120:27:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > ‘SoapySDRKwargs_get’
> > > >> > > >
> > SOAPY_SDR_API const
> > > >> char
> > *SoapySDRKwargs_get(SoapySDRKwargs
> > > >> > > *args,
> > > >> > > > const
> char *
> > > >> > > >
> > > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:126:27: note:
> > > >> previous
> > > >> > > declaration
> > > >> > > > of
> > ‘SoapySDRKwargs_get’
> > > >> was here
> > > >> > > >
> > SOAPY_SDR_API const
> > > >> char
> *SoapySDRKwargs_get(const
> > > >> > SoapySDRKwargs
> > > >> > > > *args,
> const
> > > >> > > >
> > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:126:20:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > ‘SoapySDRKwargs_clear’
> > > >> > > >
> > SOAPY_SDR_API void
> > > >>
> SoapySDRKwargs_clear(SoapySDRKwargs
> > > >> > *args);
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:132:20: note:
> > > >> previous
> > > >> > > declaration
> > > >> > > > of
> > > >> ‘SoapySDRKwargs_clear’
> was here
> > > >> > > >
> > SOAPY_SDR_API void
> > > >>
> SoapySDRKwargs_clear(SoapySDRKwargs
> > > >> > *args);
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:132:20:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > > ‘SoapySDRKwargsList_clear’
> > > >> > > >
> > SOAPY_SDR_API void
> > > >>
> > SoapySDRKwargsList_clear(SoapySDRKwargs
> > > >> > > *args, const
> > > >> > > > size_t
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:138:20: note:
> > > >> previous
> > > >> > > declaration
> > > >> > > > of
> > > >>
> ‘SoapySDRKwargsList_clear’ was here
> > > >> > > >
> > SOAPY_SDR_API void
> > > >>
> > SoapySDRKwargsList_clear(SoapySDRKwargs
> > > >> > > *args, const
> > > >> > > > size_t
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:138:20:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > ‘SoapySDRArgInfo_clear’
> > > >> > > >
> > SOAPY_SDR_API void
> > > >> >
> > > >>
> > > SoapySDRArgInfo_clear(SoapySDRArgInfo *info);
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:144:20: note:
> > > >> previous
> > > >> > > declaration
> > > >> > > > of
> > > >> ‘SoapySDRArgInfo_clear’
> was here
> > > >> > > >
> > SOAPY_SDR_API void
> > > >> >
> > > >>
> > > SoapySDRArgInfo_clear(SoapySDRArgInfo *info);
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:41:0:
> > > >> > > >
> > > >>
> > /usr/include/SoapySDR/Types.h:144:20:
> > > >> error: conflicting
> > > >> > types for
> > > >> > > >
> > > ‘SoapySDRArgInfoList_clear’
> > > >> > > >
> > SOAPY_SDR_API void
> > > >> >
> > > >>
> > > SoapySDRArgInfoList_clear(SoapySDRArgInfo
> > > >> > > *info,
> > > >> > > > const size_
> > > >> > > >
> > ^
> > > >> > > > In file
> > included from
> > > >> >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:18:0,
> > > >> > > >
> > from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Types.h:150:20: note:
> > > >> previous
> > > >> > > declaration
> > > >> > > > of
> > > >>
> ‘SoapySDRArgInfoList_clear’ was
> > here
> > > >> > > >
> > SOAPY_SDR_API void
> > > >> >
> > > >>
> > > SoapySDRArgInfoList_clear(SoapySDRArgInfo
> > > >> > > *info,
> > > >> > > > const size_
> > > >> > > >
> > ^
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:
> > > >> In function
> > > >> > > >
> > ‘rf_soapy_open_multi’:
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:296:38:
> > > >> > error:
> > > >> > > >
> > initialization from
> > > >> incompatible pointer type
> > > >> > > >
> > > >>
> > [-Werror=incompatible-pointer-types]
> > > >> > > > const
> > SoapySDRKwargs
> > > >> *soapy_args =
> > > >> > >
> > > SoapySDRDevice_enumerate(NULL,
> > > >> > > > &length);
> > > >> > > >
> > > >>
> > ^
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:316:45:
> > > >> > error:
> > > >> > > passing
> > > >> > > >
> argument 1 of
> > > >> ‘SoapySDRDevice_make’ from
> > incompatible
> > > >> > pointer type
> > > >> > > >
> > > >>
> > [-Werror=incompatible-pointer-types]
> > > >> > > >
> SoapySDRDevice
> > > *sdr =
> > > >> >
> > > SoapySDRDevice_make(&(soapy_args[0]));
> > > >> > > >
> > > >>
> > > ^
> > > >> > > > In file
> > included from
> > > >> > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:37:0:
> > > >> > > >
> > > >>
> > > /usr/local/include/SoapySDR/Device.h:78:31: note:
> > > >> > expected ‘const
> > > >> > > >
> > SoapySDRKwargs * {aka
> > > >> const struct <anonymous>
> *}’ but
> > > >> > > argument
> is of
> > > >> > > > type ‘const
> > > >> SoapySDRKwargs * {aka
> const struct
> > > >> > <anonymous> *}’
> > > >> > > >
> SOAPY_SDR_API
> > > >> SoapySDRDevice
> > *SoapySDRDevice_make(const
> > > >> > >
> SoapySDRKwargs
> > > >> > > > *args);
> > > >> > > >
> > > >>
> ^
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:380:28:
> > > >> > error:
> > > >> > > invalid
> > > >> > > > initializer
> > > >> > > >
> SoapySDRRange
> > > tx_range =
> > > >> > >
> > > >>
> > > SoapySDRDevice_getGainRange(handler->device,
> > > >> > > > SOAPY_S
> > > >> > >�� >
> > > >> ^
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:381:28:
> > > >> > error:
> > > >> > > invalid
> > > >> > > > initializer
> > > >> > > >
> SoapySDRRange
> > > rx_range =
> > > >> > >
> > > >>
> > > SoapySDRDevice_getGainRange(handler->device,
> > > >> > > > SOAPY_S
> > > >> > > >
> > > >> ^
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:
> > > >> In function
> > > >> > > >
> > > ‘rf_soapy_set_rx_srate’:
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:581:29:
> > > >> > error:
> > > >> > > >
> > initialization from
> > > >> incompatible pointer type
> > > >> > > >
> > > >>
> > [-Werror=incompatible-pointer-types]
> > > >> > > >
> SoapySDRRange
> > > *bw_range =
> > > >> > > >
> > > >>
> > > SoapySDRDevice_getBandwidthRange(handler->device,
> > > >> S
> > > >> > > >
> > > >>
> ^
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:
> > > >> In function
> > > >> > > >
> > > ‘rf_soapy_set_tx_srate’:
> > > >> > > >
> > > >>
> > > /home/duo/srsLTE/lib/src/phy/rf/rf_soapy_imp.c:617:29:
> > > >> > error:
> > > >> > > >
> > initialization from
> > > >> incompatible pointer type
> > > >> > > >
> > > >>
> > [-Werror=incompatible-pointer-types]
> > > >> > > >
> SoapySDRRange
> > > *bw_range =
> > > >> > > >
> > > >>
> > > SoapySDRDevice_getBandwidthRange(handler->device,
> > > >> S
> > > >> > > >
> > > >>
> ^
> > > >> > > > cc1: some
> > warnings
> > > being
> > > >> treated as errors
> > > >> > > >
> > > >>
> > > lib/src/phy/rf/CMakeFiles/srslte_rf.dir/build.make:134:
> > > >> > recipe for
> > > >> > > > target
> > > >> > >
> > > >>
> > > 'lib/src/phy/rf/CMakeFiles/srslte_rf.dir/rf_soapy_imp.c.o'
> > > >> > failed
> > > >> > > >
> make[2]: ***
> > > >> > >
> > > >>
> > > [lib/src/phy/rf/CMakeFiles/srslte_rf.dir/rf_soapy_imp.c.o]
> > > >> > > > Error 1
> > > >> > > >
> > > >> CMakeFiles/Makefile2:2905:
> > recipe for
> > > target
> > > >> > > >
> > > >>
> > > 'lib/src/phy/rf/CMakeFiles/srslte_rf.dir/all'
> > > >> failed
> > > >> > > >
> make[1]: ***
> > > >> >
> > > >>
> > > [lib/src/phy/rf/CMakeFiles/srslte_rf.dir/all]
> > > >> Error 2
> > > >> > > >
> Makefile:160:
> > > recipe for
> > > >> target 'all' failed
> > > >> > > > make: ***
> > [all] Error 2
> > > >> > > >
> > > >> > > >
> > > >> > > > Please
> > advise! Thanks
> > > >> > > > --
> > > >> > > > Best
> Regards,
> > > >> > > > DUO
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >>
> > > _______________________________________________
> > > >> > > >
> srslte-users
> > > mailing list
> > > >> > > >
> > > >>
> > > srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>>
> > > >> >
> > > >>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > >>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>>>
> > > >> > >
> > > >>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > >>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>>
> > > >> >
> > > >>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > >>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>>>>
> > > >> > > >
> > > >> >
> > > >>
> > >
> >
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Best Regards,
> > > >> > > Sandi
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Best Regards,
> > > >> > > Sandi
> > > >> > >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Andre Puschmann
> > > >> >
> > > >> > Software Radio
> Systems (SRS)
> > > >> >
> > http://www.softwareradiosystems.com
> > > >> >
> > > >> > PGP/GnuPG key: 6C42AB31
> > > >> > fingerprint: 137A AE49
> > 785B A445
> > > >> 257C 8AD7 D877 A498 6C42 AB31
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Best Regards,
> > > >> > Sandi
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >> Andre Puschmann
> > > >>
> > > >> Software Radio Systems (SRS)
> > > >>
> http://www.softwareradiosystems.com
> > > >>
> > > >> PGP/GnuPG key: 6C42AB31
> > > >> fingerprint: 137A AE49 785B
> > A445 257C
> > > 8AD7
> > > >> D877 A498 6C42 AB31
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Best Regards,
> > > >> Sandi
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Best Regards,
> > > >> Sandi
> > > >>
> > > >>
> > > >>
> > _______________________________________________
> > > >> srslte-users mailing list
> > > >>
> > srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>>
> > > >>
> > >
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> > > >
> > _______________________________________________
> > > > srslte-users mailing list
> > > >
> > srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > >
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>>
> > > >
> > >
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards,
> > > > Sandi
> > > >
> > > >
> _______________________________________________
> > > > srslte-users mailing list
> > > >
> srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > >
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>>
> > > >
> > >
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> > > >
> > > >
> > > > _______________________________________________
> > > > srslte-users mailing list
> > > > srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>>
> > > >
> > http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> > > >
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > Sandi
> > >
> > >
> > > _______________________________________________
> > > srslte-users mailing list
> > > srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>
> > <mailto:srslte-users at lists.softwareradiosystems.com
> <mailto:srslte-users at lists.softwareradiosystems.com>>
> > >
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> > >
> >
> >
> > --
> > Andre Puschmann
> >
> > Software Radio Systems (SRS)
> > http://www.softwareradiosystems.com
> >
> > PGP/GnuPG key: 6C42AB31
> > fingerprint: 137A AE49 785B A445 257C 8AD7 D877 A498 6C42 AB31
> >
> >
> >
> > --
> > Best Regards,
> > Sandi
> >
>
>
> --
> Andre Puschmann
>
> Software Radio Systems (SRS)
> http://www.softwareradiosystems.com
>
> PGP/GnuPG key: 6C42AB31
> fingerprint: 137A AE49 785B A445 257C 8AD7 D877 A498 6C42 AB31
>
>
>
> --
> Best Regards,
> Sandi
>
--
Andre Puschmann
Software Radio Systems (SRS)
http://www.softwareradiosystems.com
PGP/GnuPG key: 6C42AB31
fingerprint: 137A AE49 785B A445 257C 8AD7 D877 A498 6C42 AB31
More information about the srsran-users
mailing list