openlte-discuss Mailing List for openLTE (Page 2)
An open source 3GPP LTE implementation.
Status: Alpha
Brought to you by:
bwojtowi
Menu
▾
▴
openlte-discuss — Technical discussion
You can subscribe to this list here.
| 2012 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(9) |
Jun
(4) |
Jul
(14) |
Aug
(1) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(17) |
Feb
(13) |
Mar
(23) |
Apr
(12) |
May
(8) |
Jun
(7) |
Jul
(22) |
Aug
(7) |
Sep
(16) |
Oct
(30) |
Nov
(14) |
Dec
(14) |
| 2014 |
Jan
(7) |
Feb
(6) |
Mar
(16) |
Apr
(4) |
May
(15) |
Jun
(28) |
Jul
(20) |
Aug
(6) |
Sep
(59) |
Oct
(57) |
Nov
(26) |
Dec
(86) |
| 2015 |
Jan
(67) |
Feb
(62) |
Mar
(21) |
Apr
(19) |
May
(8) |
Jun
(17) |
Jul
(5) |
Aug
(25) |
Sep
(13) |
Oct
(2) |
Nov
(8) |
Dec
(23) |
| 2016 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(13) |
Aug
(5) |
Sep
(7) |
Oct
(7) |
Nov
(12) |
Dec
(13) |
| 2017 |
Jan
(2) |
Feb
(7) |
Mar
(3) |
Apr
(4) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(16) |
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
(2) |
| 2018 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Ben W. <bwo...@gm...> - 2017-08-06 00:09:01
|
Hi Suyash, FFT_pad_size is determined by subtracting the number of used subcarriers for a particular bandwidth (72, 180, 300, 600, 900, or 1200 for 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, and 20MHz respectively) from the FFT size used for a particular bandwidth (128, 256, 512, 1024, 2048, or 2048 for 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, and 20MHz respectively). Thanks, Ben On Thu, Apr 6, 2017 at 2:24 AM, Suyash Prakash <suy...@gm...> wrote: > Hi, > > I was referring your code for my project. > Can you please tell me how to choose the value of FFT_pad_size for > different bandwidths. > > -- > Suyash Prakash > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > |
|
From: Ben W. <bwo...@gm...> - 2017-08-06 00:05:32
|
Hi Thirupathi,
Please ensure that /usr/local/lib/python2.7/dist-packages/ is present in
PYTHONPATH.
Thanks,
Ben
On Thu, Jun 29, 2017 at 11:40 PM, Katam, Thirupathi Reddy <
Thi...@an...> wrote:
> Hi,
>
>
>
> I am getting “ImportError: /usr/local/lib/libLTE_fdd_dl_fs.so: undefined
> symbol” error as below with both
>
> LTE_fdd_dl_file_gen.py and LTE_fdd_dl_file_scan.py
>
>
>
> Please help me to resolve this issue.
>
>
>
> :~/open-lte-anritsu/build$ *LTE_fdd_dl_file_scan.py* -d gr_complex
> LTE_fdd_dl_scan_file_gr_coplex.bin
>
> Traceback (most recent call last):
>
> File "/usr/local/bin/LTE_fdd_dl_file_scan.py", line 7, in <module>
>
> import LTE_fdd_dl_fs
>
> File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/__init__.py",
> line 44, in <module>
>
> from LTE_fdd_dl_fs import *
>
> File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_fdd_dl_fs.py",
> line 28, in <module>
>
> _LTE_fdd_dl_fs = swig_import_helper()
>
> File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_fdd_dl_fs.py",
> line 24, in swig_import_helper
>
> _mod = imp.load_module('_LTE_fdd_dl_fs', fp, pathname, description)
>
> ImportError: /usr/local/lib/libLTE_fdd_dl_fs.so: undefined symbol:
> _ZN2gr10sync_blockC2ERKSsN5boost10shared_ptrINS_12io_signatureEEES6_
>
> :~/open-lte-anritsu/build$
>
>
>
> :~/open-lte-anritsu/build$ *LTE_fdd_dl_file_gen.py* LTE_fdd_dl_gen.bin
>
> Traceback (most recent call last):
>
> File "/usr/local/bin/LTE_fdd_dl_file_gen.py", line 7, in <module>
>
> import LTE_fdd_dl_fg
>
> File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/__init__.py",
> line 44, in <module>
>
> from LTE_fdd_dl_fg import *
>
> File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_fdd_dl_fg.py",
> line 28, in <module>
>
> _LTE_fdd_dl_fg = swig_import_helper()
>
> File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_fdd_dl_fg.py",
> line 24, in swig_import_helper
>
> _mod = imp.load_module('_LTE_fdd_dl_fg', fp, pathname, description)
>
> ImportError: /usr/local/lib/libLTE_fdd_dl_fg.so: undefined symbol:
> _ZN2gr10sync_blockC2ERKSsN5boost10shared_ptrINS_12io_signatureEEES6_
>
> :~/open-lte-anritsu/build$
>
>
>
>
>
> Here is the complete log
>
>
>
> :~/open-lte-anritsu$ *mkdir build*
>
> :~/open-lte-anritsu$ cd build/
>
> :~/open-lte-anritsu/build$ *cmake ../*
>
> -- The CXX compiler identification is GNU 4.8.5
>
> -- The C compiler identification is GNU 4.8.5
>
> -- Check for working CXX compiler: /usr/bin/c++
>
> -- Check for working CXX compiler: /usr/bin/c++ -- works
>
> -- Detecting CXX compiler ABI info
>
> -- Detecting CXX compiler ABI info - done
>
> -- Detecting CXX compile features
>
> -- Detecting CXX compile features - done
>
> -- Check for working C compiler: /usr/bin/cc
>
> -- Check for working C compiler: /usr/bin/cc -- works
>
> -- Detecting C compiler ABI info
>
> -- Detecting C compiler ABI info - done
>
> -- Detecting C compile features
>
> -- Detecting C compile features - done
>
> -- Build type not specified: defaulting to release.
>
> -- Boost version: 1.58.0
>
> -- Found the following Boost libraries:
>
> -- system
>
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
>
> Checking for GNU Radio Module: RUNTIME
>
> -- Checking for module 'gnuradio-runtime'
>
> -- Found gnuradio-runtime, version 3.7.9
>
> * INCLUDES=/usr/include
>
> * LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/
> usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> -- Found GNURADIO_RUNTIME: /usr/lib/x86_64-linux-gnu/
> libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> GNURADIO_RUNTIME_FOUND = TRUE
>
> Checking for GNU Radio Module: BLOCKS
>
> -- Checking for module 'gnuradio-blocks'
>
> -- Found gnuradio-blocks, version 3.7.9
>
> * INCLUDES=/usr/include
>
> * LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/
> usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/
> libgnuradio-pmt.so
>
> -- Found GNURADIO_BLOCKS: /usr/lib/x86_64-linux-gnu/
> libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/
> libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> GNURADIO_BLOCKS_FOUND = TRUE
>
> Checking for GNU Radio Module: FILTER
>
> -- Checking for module 'gnuradio-filter'
>
> -- Found gnuradio-filter, version 3.7.9
>
> * INCLUDES=/usr/include
>
> * LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/
> usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/
> x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-
> linux-gnu/libgnuradio-pmt.so
>
> -- Found GNURADIO_FILTER: /usr/lib/x86_64-linux-gnu/
> libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/
> libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-
> runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> GNURADIO_FILTER_FOUND = TRUE
>
> Checking for GNU Radio Module: PMT
>
> -- Checking for module 'gnuradio-runtime'
>
> -- Found gnuradio-runtime, version 3.7.9
>
> * INCLUDES=/usr/include
>
> * LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/
> usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> -- Found GNURADIO_PMT: /usr/lib/x86_64-linux-gnu/
> libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>
> GNURADIO_PMT_FOUND = TRUE
>
> -- Checking for module 'fftw3f >= 3.0'
>
> -- Found fftw3f , version 3.3.4
>
> -- Found FFTW3F: /usr/lib/x86_64-linux-gnu/libfftw3f.so
>
> --
>
> -- Checking for module SWIG
>
> -- Found SWIG version 3.0.8.
>
> -- Found SWIG: /usr/bin/swig3.0
>
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
> version "2.7.12")
>
> -- Found PythonInterp: /usr/bin/python2 (found suitable version "2.7.12",
> minimum required is "2")
>
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
> suitable version "2.7.12", minimum required is "2")
>
> -- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE
>
> -- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE - Success
>
> --
>
> -- Checking for module SWIG
>
> -- Found SWIG version 3.0.8.
>
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
> version "2.7.12")
>
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
> suitable version "2.7.12", minimum required is "2")
>
> -- Configuring done
>
> -- Generating done
>
> -- Build files have been written to: /home/am004916/open-lte-anritsu/build
>
> :~/open-lte-anritsu/build$
>
> ~/open-lte-anritsu/build$ *make*
>
> Scanning dependencies of target lte
>
> [ 2%] Building CXX object liblte/CMakeFiles/lte.dir/src/
> liblte_common.cc.o
>
> [ 4%] Building CXX object liblte/CMakeFiles/lte.dir/src/
> liblte_interface.cc.o
>
> [ 6%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_phy.cc.o
>
> [ 8%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_mac.cc.o
>
> [ 10%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_rlc.cc.o
>
> [ 13%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_pdcp.cc.o
>
> [ 15%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_rrc.cc.o
>
> [ 17%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_mme.cc.o
>
> [ 19%] Linking CXX static library liblte.a
>
> [ 19%] Built target lte
>
> Scanning dependencies of target tools
>
> [ 21%] Building CXX object libtools/CMakeFiles/tools.dir/
> src/libtools_socket_wrap.cc.o
>
> [ 23%] Building CXX object libtools/CMakeFiles/tools.dir/
> src/libtools_scoped_lock.cc.o
>
> [ 26%] Linking CXX static library libtools.a
>
> [ 26%] Built target tools
>
> Scanning dependencies of target pygen_LTE_fdd_dl_file_gen_7b784
>
> [ 28%] Shebangin LTE_fdd_dl_file_gen.py
>
> [ 28%] Built target pygen_LTE_fdd_dl_file_gen_7b784
>
> Scanning dependencies of target _LTE_fdd_dl_fg_swig_tag
>
> [ 30%] Building CXX object LTE_fdd_dl_file_gen/CMakeFiles/_LTE_fdd_dl_fg_
> swig_tag.dir/_LTE_fdd_dl_fg_swig_tag.cpp.o
>
> [ 32%] Linking CXX executable _LTE_fdd_dl_fg_swig_tag
>
> [ 32%] Built target _LTE_fdd_dl_fg_swig_tag
>
> [ 34%] Generating LTE_fdd_dl_fg.tag
>
> Scanning dependencies of target LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
>
> [ 36%] Building CXX object LTE_fdd_dl_file_gen/
> CMakeFiles/LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f.dir/LTE_
> fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f.cpp.o
>
> [ 39%] Linking CXX executable LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
>
> Swig source
>
> [ 39%] Built target LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
>
> Scanning dependencies of target LTE_fdd_dl_fg
>
> [ 41%] Building CXX object LTE_fdd_dl_file_gen/
> CMakeFiles/LTE_fdd_dl_fg.dir/src/LTE_fdd_dl_fg_samp_buf.cc.o
>
> [ 43%] Linking CXX shared library libLTE_fdd_dl_fg.so
>
> [ 43%] Built target LTE_fdd_dl_fg
>
> Scanning dependencies of target pygen_LTE_fdd_dl_file_gen_1d61e
>
> [ 45%] Generating LTE_fdd_dl_fg.pyc
>
> [ 47%] Generating LTE_fdd_dl_fg.pyo
>
> [ 50%] Built target pygen_LTE_fdd_dl_file_gen_1d61e
>
> Scanning dependencies of target _LTE_fdd_dl_fg
>
> [ 52%] Building CXX object LTE_fdd_dl_file_gen/
> CMakeFiles/_LTE_fdd_dl_fg.dir/src/LTE_fdd_dl_fgPYTHON_wrap.cxx.o
>
> [ 54%] Linking CXX shared module _LTE_fdd_dl_fg.so
>
> [ 58%] Built target _LTE_fdd_dl_fg
>
> Scanning dependencies of target pygen_LTE_fdd_dl_file_gen_063e3
>
> [ 60%] Generating src/__init__.pyc
>
> [ 63%] Generating src/__init__.pyo
>
> [ 63%] Built target pygen_LTE_fdd_dl_file_gen_063e3
>
> Scanning dependencies of target _LTE_fdd_dl_fs_swig_tag
>
> [ 65%] Building CXX object LTE_fdd_dl_file_scan/CMakeFiles/_LTE_fdd_dl_fs_
> swig_tag.dir/_LTE_fdd_dl_fs_swig_tag.cpp.o
>
> [ 67%] Linking CXX executable _LTE_fdd_dl_fs_swig_tag
>
> [ 67%] Built target _LTE_fdd_dl_fs_swig_tag
>
> Scanning dependencies of target LTE_fdd_dl_fs
>
> [ 69%] Building CXX object LTE_fdd_dl_file_scan/
> CMakeFiles/LTE_fdd_dl_fs.dir/src/LTE_fdd_dl_fs_samp_buf.cc.o
>
> [ 71%] Linking CXX shared library libLTE_fdd_dl_fs.so
>
> [ 71%] Built target LTE_fdd_dl_fs
>
> [ 73%] Generating LTE_fdd_dl_fs.tag
>
> Scanning dependencies of target LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
>
> [ 76%] Building CXX object LTE_fdd_dl_file_scan/
> CMakeFiles/LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d.dir/
> LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d.cpp.o
>
> [ 78%] Linking CXX executable LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
>
> Swig source
>
> [ 78%] Built target LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
>
> Scanning dependencies of target pygen_LTE_fdd_dl_file_scan_2bb29
>
> [ 80%] Generating LTE_fdd_dl_fs.pyc
>
> [ 82%] Generating LTE_fdd_dl_fs.pyo
>
> [ 84%] Built target pygen_LTE_fdd_dl_file_scan_2bb29
>
> Scanning dependencies of target _LTE_fdd_dl_fs
>
> [ 86%] Building CXX object LTE_fdd_dl_file_scan/
> CMakeFiles/_LTE_fdd_dl_fs.dir/src/LTE_fdd_dl_fsPYTHON_wrap.cxx.o
>
> [ 89%] Linking CXX shared module _LTE_fdd_dl_fs.so
>
> [ 93%] Built target _LTE_fdd_dl_fs
>
> Scanning dependencies of target pygen_LTE_fdd_dl_file_scan_2e555
>
> [ 95%] Generating src/__init__.pyc
>
> [ 97%] Generating src/__init__.pyo
>
> [ 97%] Built target pygen_LTE_fdd_dl_file_scan_2e555
>
> Scanning dependencies of target pygen_LTE_fdd_dl_file_scan_e108d
>
> [100%] Shebangin LTE_fdd_dl_file_scan.py
>
> [100%] Built target pygen_LTE_fdd_dl_file_scan_e108d
>
> :~/open-lte-anritsu/build$
>
> :~/open-lte-anritsu/build$
>
> ~/open-lte-anritsu/build$ *sudo -H make install*
>
> [ 19%] Built target lte
>
> [ 26%] Built target tools
>
> [ 28%] Built target pygen_LTE_fdd_dl_file_gen_7b784
>
> [ 32%] Built target _LTE_fdd_dl_fg_swig_tag
>
> [ 39%] Built target LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
>
> [ 43%] Built target LTE_fdd_dl_fg
>
> [ 50%] Built target pygen_LTE_fdd_dl_file_gen_1d61e
>
> [ 58%] Built target _LTE_fdd_dl_fg
>
> [ 63%] Built target pygen_LTE_fdd_dl_file_gen_063e3
>
> [ 67%] Built target _LTE_fdd_dl_fs_swig_tag
>
> [ 71%] Built target LTE_fdd_dl_fs
>
> [ 78%] Built target LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
>
> [ 84%] Built target pygen_LTE_fdd_dl_file_scan_2bb29
>
> [ 93%] Built target _LTE_fdd_dl_fs
>
> [ 97%] Built target pygen_LTE_fdd_dl_file_scan_2e555
>
> [100%] Built target pygen_LTE_fdd_dl_file_scan_e108d
>
> Install the project...
>
> -- Install configuration: "Release"
>
> -- Installing: /usr/local/lib/libLTE_fdd_dl_fg.so
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/_LTE_
> fdd_dl_fg.so
>
> -- Set runtime path of "/usr/local/lib/python2.7/
> dist-packages/LTE_fdd_dl_fg/_LTE_fdd_dl_fg.so" to ""
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_
> fdd_dl_fg.py
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_
> fdd_dl_fg.pyc
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_
> fdd_dl_fg.pyo
>
> -- Up-to-date: /usr/local/include/LTE_fdd_dl_fg/swig/LTE_fdd_dl_fg.i
>
> -- Up-to-date: /usr/local/lib/python2.7/dist-
> packages/LTE_fdd_dl_fg/__init__.py
>
> -- Installing: /usr/local/lib/python2.7/dist-
> packages/LTE_fdd_dl_fg/__init__.pyc
>
> -- Installing: /usr/local/lib/python2.7/dist-
> packages/LTE_fdd_dl_fg/__init__.pyo
>
> -- Installing: /usr/local/bin/LTE_fdd_dl_file_gen.py
>
> -- Installing: /usr/local/lib/libLTE_fdd_dl_fs.so
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/_LTE_
> fdd_dl_fs.so
>
> -- Set runtime path of "/usr/local/lib/python2.7/
> dist-packages/LTE_fdd_dl_fs/_LTE_fdd_dl_fs.so" to ""
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_
> fdd_dl_fs.py
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_
> fdd_dl_fs.pyc
>
> -- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_
> fdd_dl_fs.pyo
>
> -- Up-to-date: /usr/local/include/LTE_fdd_dl_fs/swig/LTE_fdd_dl_fs.i
>
> -- Up-to-date: /usr/local/lib/python2.7/dist-
> packages/LTE_fdd_dl_fs/__init__.py
>
> -- Installing: /usr/local/lib/python2.7/dist-
> packages/LTE_fdd_dl_fs/__init__.pyc
>
> -- Installing: /usr/local/lib/python2.7/dist-
> packages/LTE_fdd_dl_fs/__init__.pyo
>
> -- Installing: /usr/local/bin/LTE_fdd_dl_file_scan.py
>
> :~/open-lte-anritsu/build$
>
>
>
>
>
>
>
> Best Regards
>
> Thirupathi Reddy
>
> Ext 1258
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Openlte-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openlte-discuss
>
>
|
|
From: Ben W. <bwo...@gm...> - 2017-08-05 23:51:35
|
Hi Denis, I have been using B200/B210 for most of my testing with various Ubuntu releases. Other SDRs will work, you can check out the support in LTE_fdd_dl_scan, LTE_file_recorder, and LTE_fdd_enodeb. Also, other OSs may work, but I don't have any experience with that. Thanks, Ben On Wed, Jul 19, 2017 at 10:50 PM, Denis <de...@mi...> wrote: > Hello, > > Which of the USRP boards best to use with current release of OpenLTE? > Can I use OpenBSD as a host system without code modifications? > > Thank you for answer in advance. > > Denis > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > |
|
From: Ben W. <bwo...@gm...> - 2017-08-03 02:32:58
|
All, Version 00.20.05 is available. This version added two codeword support, refactored PUCCH channel decoding for 1, 1A, and 1B, added SR configuration index mapping, added liblte_common unit tests, and properly handling FI fields for multiple AMD PDUs in the LTE library, added helper functions and interprocess message queue support to the tools library, added SR support, moved GW, MME, and PDCP away from the singleton pattern, added direct IPC to a UE for MAC and PHY, removed QOS and fixed UL scheduling in favor of SR and BSR based UL scheduling, and refactored the AMD reception buffer to handle more than one PDU per SN in LTE_fdd_enodeb, and fixed a typo in lte_pucch_demod.m. I plan on focusing on picking through the emails and forum posts in the coming weeks. Please keep providing any and all feedback. Thanks, Ben |
|
From: YAN G. <yan...@te...> - 2017-08-02 16:26:10
|
Well docker is not native on a Mac, you rely then on a hypervisor/VM engine to run a Linux kernel. Virtualbox has USB support but you need to alter the boot2docker VM to add the USB passthrough. Then it should work. Unsure about xhyve hypervisor for USB support, but then in both case this is likely to give bad result on the realtime processing of I/Q samples recovered on the USB... better carry a Intel NUC for SDR processing :-) -- Yan (mobile) > Le 2 août 2017 à 14:25, Tomcsányi, Domonkos <do...@to...> a écrit : > > I'm glad to see docker is working for you, I always had issues of USB devices, but again I tried it on a Mac. > > Cheers, > Domi > > ----- Original Message ----- >> From: "YAN GRUNENBERGER" <yan...@te...> >> To: "n bui" <n....@no...>, "Domonkos Tomcsányi" <do...@to...> >> Cc: "openlte-discuss" <ope...@li...> >> Sent: Wednesday, August 2, 2017 8:23:55 AM >> Subject: Re: [Openlte-discuss] installing openlte > >> Hi, >> >> Another approach is to use pybombs. Since one month they offer some >> baseline Docker image in the registry, so it makes the creation of a >> docker for OpenLTE quite trivial on any linux distro supporting Docker >> (I did this on an Ubuntu 16.04): >> >> Example of Dockerfile : >> FROM pybombs/pybombs-prefix >> RUN apt-get -qy update >> RUN pybombs install openlte >> RUN /pybombs/lib/uhd/utils/uhd_images_downloader.py >> ENTRYPOINT ["/bin/bash"] >> >> To build it : >> #docker build -t openlte --rm . >> Took like one hour on an i7. >> >> Then to run it (using a USRP B210 connected through USB in my case) : >> #docker run -it --privileged --rm -v /dev/bus/usb:/dev/bus/usb -- >> network=host openlte >> >> You will obtain a prompt, and you can instantiate the environment and >> then run OpenLTE : >> #source /pybombs/setup_env.sh >> #LTE_fdd_enodeb >> *** LTE FDD ENB *** >> Please connect to control port 30000 >> >> Then another terminal with telnet localhost 30000 should get you the >> CLI of OpenLTE to configure band, IMSI/Ki, start the radio etc. >> >> Of course, YMMV and it reminds me I did not try to connect a UE >> recently to OpenLTE :-) >> >> Hope this helps, >> >> Best, >> >>> Le mardi 01 août 2017 à 22:50 +0200, Tomcsányi Domonkos a écrit : >>> Hi, >>> >>> This has been discussed a long time ago on the mailing list, if you >>> just do a Google search for the file in question you'll find the >>> thread. >>> However I'd suggest to ditch PolarSSL and use this patch that changes >>> to the successor of PolarSSL - to mbedTLS. It requires some manual >>> changing for the current version if I remember correctly, but it is >>> easy to do so since it is just a few lines of code, and a cmake file. >>> https://sourceforge.net/p/openlte/mailman/message/35039389/ >>> >>> Good luck! >>> >>> Domi >>> >>>> 2017. aug. 1. dátummal, 19:49 időpontban Nicola Bui <n.bui@northeas >>>> tern.edu> írta: >>>> >>>> Dear all, >>>> >>>> I am trying to install openlte. I install polarssl 1.2 from the >>>> archive on the website, but make complains that the file compat- >>>> 1.2.h does not exist. Indeed the polar folder does not have the >>>> file. >>>> Does anyone knows how to install openlte on ubuntu 16.04? >>>> >>>> Thanks, >>>> Nicola Bui >>>> Senior Research Scientist >>>> College of Computer and Information Science >>>> 202 West Village H >>>> 360 Huntington Avenue >>>> Boston, MA 02115 >>>> ----------------------------------------------------------------- >>>> ------------- >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot________ >>>> _______________________________________ >>>> Openlte-discuss mailing list >>>> Ope...@li... >>>> https://lists.sourceforge.net/lists/listinfo/openlte-discuss >>> >>> ------------------------------------------------------------------- >>> ----------- >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Openlte-discuss mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/openlte-discuss >> >> ________________________________ >> >> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede >> contener información privilegiada o confidencial y es para uso exclusivo de la >> persona o entidad de destino. Si no es usted. el destinatario indicado, queda >> notificado de que la lectura, utilización, divulgación y/o copia sin >> autorización puede estar prohibida en virtud de la legislación vigente. Si ha >> recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente >> por esta misma vía y proceda a su destrucción. >> >> The information contained in this transmission is privileged and confidential >> information intended only for the use of the individual or entity named above. >> If the reader of this message is not the intended recipient, you are hereby >> notified that any dissemination, distribution or copying of this communication >> is strictly prohibited. If you have received this transmission in error, do not >> read it. Please immediately reply to the sender that you have received this >> communication in error and then delete it. >> >> Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode >> conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa >> ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica >> notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização >> pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem >> por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e >> proceda a sua destruição ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição |
|
From: Nicola B. <n....@no...> - 2017-08-02 13:12:22
|
Thanks, I'll try your suggestion. Best, Nicola Bui Senior Research Scientist College of Computer and Information Science 202 West Village H 360 Huntington Avenue Boston, MA 02115 On Tue, Aug 1, 2017 at 4:50 PM, Tomcsányi Domonkos <do...@to...> wrote: > Hi, > > This has been discussed a long time ago on the mailing list, if you just > do a Google search for the file in question you'll find the thread. > However I'd suggest to ditch PolarSSL and use this patch that changes to > the successor of PolarSSL - to mbedTLS. It requires some manual changing > for the current version if I remember correctly, but it is easy to do so > since it is just a few lines of code, and a cmake file. > https://sourceforge.net/p/openlte/mailman/message/35039389/ > > Good luck! > > Domi > > 2017. aug. 1. dátummal, 19:49 időpontban Nicola Bui < > n....@no...> írta: > > Dear all, > > I am trying to install openlte. I install polarssl 1.2 from the archive on > the website, but make complains that the file compat-1.2.h does not exist. > Indeed the polar folder does not have the file. > Does anyone knows how to install openlte on ubuntu 16.04? > > Thanks, > Nicola Bui > Senior Research Scientist > College of Computer and Information Science > 202 West Village H > 360 Huntington Avenue > Boston, MA 02115 > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ > _________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > > |
|
From: Tomcsányi, D. <do...@to...> - 2017-08-02 12:25:17
|
I'm glad to see docker is working for you, I always had issues of USB devices, but again I tried it on a Mac. Cheers, Domi ----- Original Message ----- > From: "YAN GRUNENBERGER" <yan...@te...> > To: "n bui" <n....@no...>, "Domonkos Tomcsányi" <do...@to...> > Cc: "openlte-discuss" <ope...@li...> > Sent: Wednesday, August 2, 2017 8:23:55 AM > Subject: Re: [Openlte-discuss] installing openlte > Hi, > > Another approach is to use pybombs. Since one month they offer some > baseline Docker image in the registry, so it makes the creation of a > docker for OpenLTE quite trivial on any linux distro supporting Docker > (I did this on an Ubuntu 16.04): > > Example of Dockerfile : > FROM pybombs/pybombs-prefix > RUN apt-get -qy update > RUN pybombs install openlte > RUN /pybombs/lib/uhd/utils/uhd_images_downloader.py > ENTRYPOINT ["/bin/bash"] > > To build it : > #docker build -t openlte --rm . > Took like one hour on an i7. > > Then to run it (using a USRP B210 connected through USB in my case) : > #docker run -it --privileged --rm -v /dev/bus/usb:/dev/bus/usb -- > network=host openlte > > You will obtain a prompt, and you can instantiate the environment and > then run OpenLTE : > #source /pybombs/setup_env.sh > #LTE_fdd_enodeb > *** LTE FDD ENB *** > Please connect to control port 30000 > > Then another terminal with telnet localhost 30000 should get you the > CLI of OpenLTE to configure band, IMSI/Ki, start the radio etc. > > Of course, YMMV and it reminds me I did not try to connect a UE > recently to OpenLTE :-) > > Hope this helps, > > Best, > > Le mardi 01 août 2017 à 22:50 +0200, Tomcsányi Domonkos a écrit : >> Hi, >> >> This has been discussed a long time ago on the mailing list, if you >> just do a Google search for the file in question you'll find the >> thread. >> However I'd suggest to ditch PolarSSL and use this patch that changes >> to the successor of PolarSSL - to mbedTLS. It requires some manual >> changing for the current version if I remember correctly, but it is >> easy to do so since it is just a few lines of code, and a cmake file. >> https://sourceforge.net/p/openlte/mailman/message/35039389/ >> >> Good luck! >> >> Domi >> >> > 2017. aug. 1. dátummal, 19:49 időpontban Nicola Bui <n.bui@northeas >> > tern.edu> írta: >> > >> > Dear all, >> > >> > I am trying to install openlte. I install polarssl 1.2 from the >> > archive on the website, but make complains that the file compat- >> > 1.2.h does not exist. Indeed the polar folder does not have the >> > file. >> > Does anyone knows how to install openlte on ubuntu 16.04? >> > >> > Thanks, >> > Nicola Bui >> > Senior Research Scientist >> > College of Computer and Information Science >> > 202 West Village H >> > 360 Huntington Avenue >> > Boston, MA 02115 >> > ----------------------------------------------------------------- >> > ------------- >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot________ >> > _______________________________________ >> > Openlte-discuss mailing list >> > Ope...@li... >> > https://lists.sourceforge.net/lists/listinfo/openlte-discuss >> >> ------------------------------------------------------------------- >> ----------- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Openlte-discuss mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > ________________________________ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede > contener información privilegiada o confidencial y es para uso exclusivo de la > persona o entidad de destino. Si no es usted. el destinatario indicado, queda > notificado de que la lectura, utilización, divulgación y/o copia sin > autorización puede estar prohibida en virtud de la legislación vigente. Si ha > recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente > por esta misma vía y proceda a su destrucción. > > The information contained in this transmission is privileged and confidential > information intended only for the use of the individual or entity named above. > If the reader of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this communication > is strictly prohibited. If you have received this transmission in error, do not > read it. Please immediately reply to the sender that you have received this > communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode > conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa > ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica > notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização > pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem > por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e > proceda a sua destruição |
|
From: YAN G. <yan...@te...> - 2017-08-02 06:57:39
|
Hi, Another approach is to use pybombs. Since one month they offer some baseline Docker image in the registry, so it makes the creation of a docker for OpenLTE quite trivial on any linux distro supporting Docker (I did this on an Ubuntu 16.04): Example of Dockerfile : FROM pybombs/pybombs-prefix RUN apt-get -qy update RUN pybombs install openlte RUN /pybombs/lib/uhd/utils/uhd_images_downloader.py ENTRYPOINT ["/bin/bash"] To build it : #docker build -t openlte --rm . Took like one hour on an i7. Then to run it (using a USRP B210 connected through USB in my case) : #docker run -it --privileged --rm -v /dev/bus/usb:/dev/bus/usb -- network=host openlte You will obtain a prompt, and you can instantiate the environment and then run OpenLTE : #source /pybombs/setup_env.sh #LTE_fdd_enodeb *** LTE FDD ENB *** Please connect to control port 30000 Then another terminal with telnet localhost 30000 should get you the CLI of OpenLTE to configure band, IMSI/Ki, start the radio etc. Of course, YMMV and it reminds me I did not try to connect a UE recently to OpenLTE :-) Hope this helps, Best, Le mardi 01 août 2017 à 22:50 +0200, Tomcsányi Domonkos a écrit : > Hi, > > This has been discussed a long time ago on the mailing list, if you > just do a Google search for the file in question you'll find the > thread. > However I'd suggest to ditch PolarSSL and use this patch that changes > to the successor of PolarSSL - to mbedTLS. It requires some manual > changing for the current version if I remember correctly, but it is > easy to do so since it is just a few lines of code, and a cmake file. > https://sourceforge.net/p/openlte/mailman/message/35039389/ > > Good luck! > > Domi > > > 2017. aug. 1. dátummal, 19:49 időpontban Nicola Bui <n.bui@northeas > > tern.edu> írta: > > > > Dear all, > > > > I am trying to install openlte. I install polarssl 1.2 from the > > archive on the website, but make complains that the file compat- > > 1.2.h does not exist. Indeed the polar folder does not have the > > file. > > Does anyone knows how to install openlte on ubuntu 16.04? > > > > Thanks, > > Nicola Bui > > Senior Research Scientist > > College of Computer and Information Science > > 202 West Village H > > 360 Huntington Avenue > > Boston, MA 02115 > > ----------------------------------------------------------------- > > ------------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot________ > > _______________________________________ > > Openlte-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > ------------------------------------------------------------------- > ----------- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição |
|
From: Tomcsányi D. <do...@to...> - 2017-08-01 21:08:24
|
Hi, This has been discussed a long time ago on the mailing list, if you just do a Google search for the file in question you'll find the thread. However I'd suggest to ditch PolarSSL and use this patch that changes to the successor of PolarSSL - to mbedTLS. It requires some manual changing for the current version if I remember correctly, but it is easy to do so since it is just a few lines of code, and a cmake file. https://sourceforge.net/p/openlte/mailman/message/35039389/ <https://sourceforge.net/p/openlte/mailman/message/35039389/> Good luck! Domi > 2017. aug. 1. dátummal, 19:49 időpontban Nicola Bui <n....@no...> írta: > > Dear all, > > I am trying to install openlte. I install polarssl 1.2 from the archive on the website, but make complains that the file compat-1.2.h does not exist. Indeed the polar folder does not have the file. > Does anyone knows how to install openlte on ubuntu 16.04? > > Thanks, > Nicola Bui > Senior Research Scientist > College of Computer and Information Science > 202 West Village H > 360 Huntington Avenue > Boston, MA 02115 > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss |
|
From: Nicola B. <n....@no...> - 2017-08-01 20:24:12
|
Dear all, I am trying to install openlte. I install polarssl 1.2 from the archive on the website, but make complains that the file compat-1.2.h does not exist. Indeed the polar folder does not have the file. Does anyone knows how to install openlte on ubuntu 16.04? Thanks, Nicola Bui Senior Research Scientist College of Computer and Information Science 202 West Village H 360 Huntington Avenue Boston, MA 02115 |
|
From: Denis <de...@mi...> - 2017-07-20 06:23:52
|
Hello, Which of the USRP boards best to use with current release of OpenLTE? Can I use OpenBSD as a host system without code modifications? Thank you for answer in advance. Denis |
|
From: Katam, T. R. <Thi...@an...> - 2017-06-30 06:52:46
|
Hi,
I am getting "ImportError: /usr/local/lib/libLTE_fdd_dl_fs.so: undefined symbol" error as below with both
LTE_fdd_dl_file_gen.py and LTE_fdd_dl_file_scan.py
Please help me to resolve this issue.
:~/open-lte-anritsu/build$ LTE_fdd_dl_file_scan.py -d gr_complex LTE_fdd_dl_scan_file_gr_coplex.bin
Traceback (most recent call last):
File "/usr/local/bin/LTE_fdd_dl_file_scan.py", line 7, in <module>
import LTE_fdd_dl_fs
File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/__init__.py", line 44, in <module>
from LTE_fdd_dl_fs import *
File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_fdd_dl_fs.py", line 28, in <module>
_LTE_fdd_dl_fs = swig_import_helper()
File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_fdd_dl_fs.py", line 24, in swig_import_helper
_mod = imp.load_module('_LTE_fdd_dl_fs', fp, pathname, description)
ImportError: /usr/local/lib/libLTE_fdd_dl_fs.so: undefined symbol: _ZN2gr10sync_blockC2ERKSsN5boost10shared_ptrINS_12io_signatureEEES6_
:~/open-lte-anritsu/build$
:~/open-lte-anritsu/build$ LTE_fdd_dl_file_gen.py LTE_fdd_dl_gen.bin
Traceback (most recent call last):
File "/usr/local/bin/LTE_fdd_dl_file_gen.py", line 7, in <module>
import LTE_fdd_dl_fg
File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/__init__.py", line 44, in <module>
from LTE_fdd_dl_fg import *
File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_fdd_dl_fg.py", line 28, in <module>
_LTE_fdd_dl_fg = swig_import_helper()
File "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_fdd_dl_fg.py", line 24, in swig_import_helper
_mod = imp.load_module('_LTE_fdd_dl_fg', fp, pathname, description)
ImportError: /usr/local/lib/libLTE_fdd_dl_fg.so: undefined symbol: _ZN2gr10sync_blockC2ERKSsN5boost10shared_ptrINS_12io_signatureEEES6_
:~/open-lte-anritsu/build$
Here is the complete log
:~/open-lte-anritsu$ mkdir build
:~/open-lte-anritsu$ cd build/
:~/open-lte-anritsu/build$ cmake ../
-- The CXX compiler identification is GNU 4.8.5
-- The C compiler identification is GNU 4.8.5
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Build type not specified: defaulting to release.
-- Boost version: 1.58.0
-- Found the following Boost libraries:
-- system
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
Checking for GNU Radio Module: RUNTIME
-- Checking for module 'gnuradio-runtime'
-- Found gnuradio-runtime, version 3.7.9
* INCLUDES=/usr/include
* LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
-- Found GNURADIO_RUNTIME: /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
GNURADIO_RUNTIME_FOUND = TRUE
Checking for GNU Radio Module: BLOCKS
-- Checking for module 'gnuradio-blocks'
-- Found gnuradio-blocks, version 3.7.9
* INCLUDES=/usr/include
* LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
-- Found GNURADIO_BLOCKS: /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
GNURADIO_BLOCKS_FOUND = TRUE
Checking for GNU Radio Module: FILTER
-- Checking for module 'gnuradio-filter'
-- Found gnuradio-filter, version 3.7.9
* INCLUDES=/usr/include
* LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
-- Found GNURADIO_FILTER: /usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
GNURADIO_FILTER_FOUND = TRUE
Checking for GNU Radio Module: PMT
-- Checking for module 'gnuradio-runtime'
-- Found gnuradio-runtime, version 3.7.9
* INCLUDES=/usr/include
* LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
-- Found GNURADIO_PMT: /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
GNURADIO_PMT_FOUND = TRUE
-- Checking for module 'fftw3f >= 3.0'
-- Found fftw3f , version 3.3.4
-- Found FFTW3F: /usr/lib/x86_64-linux-gnu/libfftw3f.so
--
-- Checking for module SWIG
-- Found SWIG version 3.0.8.
-- Found SWIG: /usr/bin/swig3.0
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.12")
-- Found PythonInterp: /usr/bin/python2 (found suitable version "2.7.12", minimum required is "2")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.12", minimum required is "2")
-- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE
-- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE - Success
--
-- Checking for module SWIG
-- Found SWIG version 3.0.8.
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.12")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.12", minimum required is "2")
-- Configuring done
-- Generating done
-- Build files have been written to: /home/am004916/open-lte-anritsu/build
:~/open-lte-anritsu/build$
~/open-lte-anritsu/build$ make
Scanning dependencies of target lte
[ 2%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_common.cc.o
[ 4%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_interface.cc.o
[ 6%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_phy.cc.o
[ 8%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_mac.cc.o
[ 10%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_rlc.cc.o
[ 13%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_pdcp.cc.o
[ 15%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_rrc.cc.o
[ 17%] Building CXX object liblte/CMakeFiles/lte.dir/src/liblte_mme.cc.o
[ 19%] Linking CXX static library liblte.a
[ 19%] Built target lte
Scanning dependencies of target tools
[ 21%] Building CXX object libtools/CMakeFiles/tools.dir/src/libtools_socket_wrap.cc.o
[ 23%] Building CXX object libtools/CMakeFiles/tools.dir/src/libtools_scoped_lock.cc.o
[ 26%] Linking CXX static library libtools.a
[ 26%] Built target tools
Scanning dependencies of target pygen_LTE_fdd_dl_file_gen_7b784
[ 28%] Shebangin LTE_fdd_dl_file_gen.py
[ 28%] Built target pygen_LTE_fdd_dl_file_gen_7b784
Scanning dependencies of target _LTE_fdd_dl_fg_swig_tag
[ 30%] Building CXX object LTE_fdd_dl_file_gen/CMakeFiles/_LTE_fdd_dl_fg_swig_tag.dir/_LTE_fdd_dl_fg_swig_tag.cpp.o
[ 32%] Linking CXX executable _LTE_fdd_dl_fg_swig_tag
[ 32%] Built target _LTE_fdd_dl_fg_swig_tag
[ 34%] Generating LTE_fdd_dl_fg.tag
Scanning dependencies of target LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
[ 36%] Building CXX object LTE_fdd_dl_file_gen/CMakeFiles/LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f.dir/LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f.cpp.o
[ 39%] Linking CXX executable LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
Swig source
[ 39%] Built target LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
Scanning dependencies of target LTE_fdd_dl_fg
[ 41%] Building CXX object LTE_fdd_dl_file_gen/CMakeFiles/LTE_fdd_dl_fg.dir/src/LTE_fdd_dl_fg_samp_buf.cc.o
[ 43%] Linking CXX shared library libLTE_fdd_dl_fg.so
[ 43%] Built target LTE_fdd_dl_fg
Scanning dependencies of target pygen_LTE_fdd_dl_file_gen_1d61e
[ 45%] Generating LTE_fdd_dl_fg.pyc
[ 47%] Generating LTE_fdd_dl_fg.pyo
[ 50%] Built target pygen_LTE_fdd_dl_file_gen_1d61e
Scanning dependencies of target _LTE_fdd_dl_fg
[ 52%] Building CXX object LTE_fdd_dl_file_gen/CMakeFiles/_LTE_fdd_dl_fg.dir/src/LTE_fdd_dl_fgPYTHON_wrap.cxx.o
[ 54%] Linking CXX shared module _LTE_fdd_dl_fg.so
[ 58%] Built target _LTE_fdd_dl_fg
Scanning dependencies of target pygen_LTE_fdd_dl_file_gen_063e3
[ 60%] Generating src/__init__.pyc
[ 63%] Generating src/__init__.pyo
[ 63%] Built target pygen_LTE_fdd_dl_file_gen_063e3
Scanning dependencies of target _LTE_fdd_dl_fs_swig_tag
[ 65%] Building CXX object LTE_fdd_dl_file_scan/CMakeFiles/_LTE_fdd_dl_fs_swig_tag.dir/_LTE_fdd_dl_fs_swig_tag.cpp.o
[ 67%] Linking CXX executable _LTE_fdd_dl_fs_swig_tag
[ 67%] Built target _LTE_fdd_dl_fs_swig_tag
Scanning dependencies of target LTE_fdd_dl_fs
[ 69%] Building CXX object LTE_fdd_dl_file_scan/CMakeFiles/LTE_fdd_dl_fs.dir/src/LTE_fdd_dl_fs_samp_buf.cc.o
[ 71%] Linking CXX shared library libLTE_fdd_dl_fs.so
[ 71%] Built target LTE_fdd_dl_fs
[ 73%] Generating LTE_fdd_dl_fs.tag
Scanning dependencies of target LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
[ 76%] Building CXX object LTE_fdd_dl_file_scan/CMakeFiles/LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d.dir/LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d.cpp.o
[ 78%] Linking CXX executable LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
Swig source
[ 78%] Built target LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
Scanning dependencies of target pygen_LTE_fdd_dl_file_scan_2bb29
[ 80%] Generating LTE_fdd_dl_fs.pyc
[ 82%] Generating LTE_fdd_dl_fs.pyo
[ 84%] Built target pygen_LTE_fdd_dl_file_scan_2bb29
Scanning dependencies of target _LTE_fdd_dl_fs
[ 86%] Building CXX object LTE_fdd_dl_file_scan/CMakeFiles/_LTE_fdd_dl_fs.dir/src/LTE_fdd_dl_fsPYTHON_wrap.cxx.o
[ 89%] Linking CXX shared module _LTE_fdd_dl_fs.so
[ 93%] Built target _LTE_fdd_dl_fs
Scanning dependencies of target pygen_LTE_fdd_dl_file_scan_2e555
[ 95%] Generating src/__init__.pyc
[ 97%] Generating src/__init__.pyo
[ 97%] Built target pygen_LTE_fdd_dl_file_scan_2e555
Scanning dependencies of target pygen_LTE_fdd_dl_file_scan_e108d
[100%] Shebangin LTE_fdd_dl_file_scan.py
[100%] Built target pygen_LTE_fdd_dl_file_scan_e108d
:~/open-lte-anritsu/build$
:~/open-lte-anritsu/build$
~/open-lte-anritsu/build$ sudo -H make install
[ 19%] Built target lte
[ 26%] Built target tools
[ 28%] Built target pygen_LTE_fdd_dl_file_gen_7b784
[ 32%] Built target _LTE_fdd_dl_fg_swig_tag
[ 39%] Built target LTE_fdd_dl_fg_LTE_fdd_dl_file_gen_e8b9f
[ 43%] Built target LTE_fdd_dl_fg
[ 50%] Built target pygen_LTE_fdd_dl_file_gen_1d61e
[ 58%] Built target _LTE_fdd_dl_fg
[ 63%] Built target pygen_LTE_fdd_dl_file_gen_063e3
[ 67%] Built target _LTE_fdd_dl_fs_swig_tag
[ 71%] Built target LTE_fdd_dl_fs
[ 78%] Built target LTE_fdd_dl_fs_LTE_fdd_dl_file_scan_ab40d
[ 84%] Built target pygen_LTE_fdd_dl_file_scan_2bb29
[ 93%] Built target _LTE_fdd_dl_fs
[ 97%] Built target pygen_LTE_fdd_dl_file_scan_2e555
[100%] Built target pygen_LTE_fdd_dl_file_scan_e108d
Install the project...
-- Install configuration: "Release"
-- Installing: /usr/local/lib/libLTE_fdd_dl_fg.so
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/_LTE_fdd_dl_fg.so
-- Set runtime path of "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/_LTE_fdd_dl_fg.so" to ""
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_fdd_dl_fg.py
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_fdd_dl_fg.pyc
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/LTE_fdd_dl_fg.pyo
-- Up-to-date: /usr/local/include/LTE_fdd_dl_fg/swig/LTE_fdd_dl_fg.i
-- Up-to-date: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/__init__.py
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/__init__.pyc
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fg/__init__.pyo
-- Installing: /usr/local/bin/LTE_fdd_dl_file_gen.py
-- Installing: /usr/local/lib/libLTE_fdd_dl_fs.so
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/_LTE_fdd_dl_fs.so
-- Set runtime path of "/usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/_LTE_fdd_dl_fs.so" to ""
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_fdd_dl_fs.py
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_fdd_dl_fs.pyc
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/LTE_fdd_dl_fs.pyo
-- Up-to-date: /usr/local/include/LTE_fdd_dl_fs/swig/LTE_fdd_dl_fs.i
-- Up-to-date: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/__init__.py
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/__init__.pyc
-- Installing: /usr/local/lib/python2.7/dist-packages/LTE_fdd_dl_fs/__init__.pyo
-- Installing: /usr/local/bin/LTE_fdd_dl_file_scan.py
:~/open-lte-anritsu/build$
Best Regards
Thirupathi Reddy
Ext 1258
|
|
From: altaf sk <alt...@gm...> - 2017-05-10 13:26:08
|
Hi Ben and other users I have used openlte several times want to make it more stable. Can you kindly share your thoughts on the openlte enodeB setup. USRPB210 + i7 laptop produces underruns (when UE connects and access data) To solve these under runs do you recommend any other stable setup. Hardware Side: (currently only B210 is supported by enodeB) -- for eg: using PCIe USRP boards, network series boards. -- is it hard to add support for these boards. Software Side: -- Are the PHY and other layers too computation intensive on an i7. Does any type of software optimization could help here. Interface: USB3 interface. Is it too slow for LTE operation. Huge IQ data Regards, Altaf |
|
From: Suyash P. <suy...@gm...> - 2017-04-06 09:24:38
|
Hi, I was referring your code for my project. Can you please tell me how to choose the value of FFT_pad_size for different bandwidths. -- Suyash Prakash |
|
From: David <da...@sl...> - 2017-04-05 14:14:22
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello, <br>
<br>
I read that openlte is capable of sending MAC messages (live) to
127.0.0.1 with GSMTAP header<br>
<a class="moz-txt-link-freetext" href="https://sourceforge.net/p/openlte/mailman/message/33252654/">https://sourceforge.net/p/openlte/mailman/message/33252654/</a><br>
<br>
I just cannot figure out how to activate this ...? like in OpenBTS,
one can simply activate the feature by doing<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
config Control.GSMTAP.GSM 1<br>
<br>
Thanks<br>
Regards<br>
<br>
<pre class="moz-signature" cols="72">--
David
PGP Fingerprint: A682 0841 3CAB E1C3 99BF 9D66 92F0 C5B7 0FBE 4A22 </pre>
</body>
</html>
|
|
From: David <da...@sl...> - 2017-04-04 23:53:12
|
Hello, It seems that enable_pcap does not work - the same problem was reported here: https://sourceforge.net/p/openlte/discussion/general/thread/cbf135f7/ /tmp/*.pcap has always 0 bytes but when enabling pcap in openLTE, the modification-date is changed (the file seems to be touched) but no data is written to it. Somebody having similar issues? Regards -- David PGP Fingerprint: A682 0841 3CAB E1C3 99BF 9D66 92F0 C5B7 0FBE 4A22 |
|
From: Kia R. <kro...@fi...> - 2017-04-03 18:53:49
|
Hi, I am testing a Galaxy S7 on band 42, but it seems as though there is no connectivity with the eNodeB. I have the IMSI, MNC,MCC, and ki from the SIM card. It appears to say that there is an error between the MAC and PHY. I have to test later today, so I can reply with a formal log. Has anyone been able to resolve this issue? -- *Kia* |
|
From: Ralph A. S. d. <ra...@sc...> - 2017-03-31 06:40:15
|
Ah, looks simple enough - I will give this a try, thanks a lot! Ralph. > -----Original Message----- > From: Shinjo Park [mailto:ps...@se...] > Sent: Thursday, March 30, 2017 3:45 PM > To: ope...@li... > Subject: Re: [Openlte-discuss] polarssl is gone... > > Hi, > > I wrote a patch to replace PolarSSL to mbed TLS [1] but not got any response > since then. At least you can compile with mbed TLS with this patch. Given that > srsUE allows both mbed TLS and PolarSSL, I think their approach is better btw. > > [1] https://sourceforge.net/p/openlte/mailman/message/35039389/ > > Shinjo > > 2017년 3월 30일 목요일 오후 3시 4분 16초 CEST에 Ralph A. Schmid, dk5ras > 님이 쓴 글: > > Hi, > > > > Newer Linux distributions do not offer polarssl any more. When > > googling around, I found a statement: > > > > "The library is now called libmbedtls-dev, following the renaming of > > polarssl to mbedtls. If you're not finding it in the default > > repositories, it might be in the universe or multiverse repositories." > > > > This seems correct so far, mbedtls was in the repo and could be > > installed, but openlte does not like it. For srsUE this worked, it is > > satisfied with this changed library and builds flawlessly. > > > > Should I really download and install some old version of polarssl, or > > can we expect a change in the openlte sources, reflecting this change? > > > > Thanks for the great job you're doing with openlte! > > > > Ralph. > > > > > > > > > > ---------------------------------------------------------------------- > > ------ > > -- Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Openlte-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > > -- > Shinjo Park <ps...@se...> Security in Telecommunications > <sec.t-labs.tu-berlin.de> TU Berlin / Telekom Innovation Laboratories Ernst- > Reuter-Platz 7, Sekr TEL 17 / D - 10587 Berlin, Germany > Phone: +49 30 8353 58272 > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most engaging > tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss |
|
From: Shinjo P. <ps...@se...> - 2017-03-30 14:08:26
|
Hi, I wrote a patch to replace PolarSSL to mbed TLS [1] but not got any response since then. At least you can compile with mbed TLS with this patch. Given that srsUE allows both mbed TLS and PolarSSL, I think their approach is better btw. [1] https://sourceforge.net/p/openlte/mailman/message/35039389/ Shinjo 2017년 3월 30일 목요일 오후 3시 4분 16초 CEST에 Ralph A. Schmid, dk5ras 님이 쓴 글: > Hi, > > Newer Linux distributions do not offer polarssl any more. When googling > around, I found a statement: > > "The library is now called libmbedtls-dev, following the renaming of > polarssl to mbedtls. If you're not finding it in the default repositories, > it might be in the universe or multiverse repositories." > > This seems correct so far, mbedtls was in the repo and could be installed, > but openlte does not like it. For srsUE this worked, it is satisfied with > this changed library and builds flawlessly. > > Should I really download and install some old version of polarssl, or can we > expect a change in the openlte sources, reflecting this change? > > Thanks for the great job you're doing with openlte! > > Ralph. > > > > > ---------------------------------------------------------------------------- > -- Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss -- Shinjo Park <ps...@se...> Security in Telecommunications <sec.t-labs.tu-berlin.de> TU Berlin / Telekom Innovation Laboratories Ernst-Reuter-Platz 7, Sekr TEL 17 / D - 10587 Berlin, Germany Phone: +49 30 8353 58272 |
|
From: Ralph A. S. d. <ra...@sc...> - 2017-03-30 13:04:25
|
Hi, Newer Linux distributions do not offer polarssl any more. When googling around, I found a statement: "The library is now called libmbedtls-dev, following the renaming of polarssl to mbedtls. If you're not finding it in the default repositories, it might be in the universe or multiverse repositories." This seems correct so far, mbedtls was in the repo and could be installed, but openlte does not like it. For srsUE this worked, it is satisfied with this changed library and builds flawlessly. Should I really download and install some old version of polarssl, or can we expect a change in the openlte sources, reflecting this change? Thanks for the great job you're doing with openlte! Ralph. |
|
From: mg <mg...@gm...> - 2017-02-15 14:41:58
|
I installed Ubuntu 14.04 and unfortunately getting the exact same error when starting the eNB as with Ubuntu 16.04. What is the correct way to start the eNB in terminal window #2, following terminal window#1 command $ LTE_fdd_enodeb ? On Tue, Feb 14, 2017 at 11:12 AM, mg <mg...@gm...> wrote: > The errors we are seeing is from OpenLTE, from LTE_fdd_enb_msgq.cc, in > void* LTE_fdd_enb_msgq::receive_thread(void *inputs), while waiting for a > message. > > Can someone give us some indication if this environment is OK for OpenLTE, > or can you please point us to or recommend the environment that should work. > > > Our environment is: > > Ubuntu 16.04 LTS , 64-bit, > i7 @ 2.2GHz x 8 > > > GNURadio > > $ gnuradio-config-info --version > v3.7.10.1-211-gb49da168 > > $ gnuradio-config-info --prefix > /usr/local > > $ gnuradio-config-info --enabled-components > python-support;testing-support;volk;doxygen;sphinx;gnuradio- > runtime;gr-ctrlport;gr-blocks;gnuradio-companion;gr-fec;gr-f > ft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-atsc;gr-audio;* alsa;* > oss;gr-channels;gr-noaa;gr-pager;gr-qtgui;gr-trellis;gr-uhd; > gr-utils;gr-video-sdl;gr-vocoder;gr-fcd;gr-wavelet;gr-wxgui;gr-zeromq > > > UHD driver > > linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_003.010.001.HEAD-0-gc705922a > > and also tried 3.11.0 and 3.9.6 > > > On Mon, Feb 13, 2017 at 5:33 PM, mg <mg...@gm...> wrote: > >> >> I did rebuild the gnuradio using /build-gnuradio to select UHD driver >> version 3.10.1.1 >> And it integrates OK with OpenLTE , because now >> LTE_fdd_enodeb returns version 3.10.1: >> >> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >> UHD_003.010.001.HEAD-0-gc705922a >> >> We are still unable to start eNB, same error: fail "cant start" >> and terminal 3 debug still shows, see listing in Term 2 below. >> >> Can someone please tell us if we are not setting up correctly , we might >> have missed or skipped a step. >> We are looking at a source code, in LTE_fdd_enb_msgq.cc , and we see the >> point of failure, but we would like to be able to see >> how this works first because we have no idea how is suppose to work >> overall. >> >> Is there a golden combination that we are not aware of that OpenLTE needs >> to work ? >> >> thanks >> mg >> >> >> Term 2 display: >> 02/13/2017 09:04:26.979640 info iface LTE_fdd_enb_interface.cc 787 *** >> LTE FDD ENB DEBUG INTERFACE *** >> 02/13/2017 09:05:28.243762 warning msgq LTE_fdd_enb_msgq.cc 234 >> pdcp_to_gw circular buffer empty on receive >> 02/13/2017 09:05:31.291939 warning msgq LTE_fdd_enb_msgq.cc 234 >> rlc_to_mac circular buffer empty on receive >> 02/13/2017 09:05:31.292225 warning msgq LTE_fdd_enb_msgq.cc 234 >> phy_to_mac circular buffer empty on receive >> 02/13/2017 09:05:31.292278 warning msgq LTE_fdd_enb_msgq.cc 234 >> mac_to_phy circular buffer empty on receive >> 02/13/2017 09:05:31.292329 warning msgq LTE_fdd_enb_msgq.cc 234 >> mac_to_timer circular buffer empty on receive >> 02/13/2017 09:05:31.292369 warning msgq LTE_fdd_enb_msgq.cc 234 >> rrc_to_pdcp circular buffer empty on receive >> 02/13/2017 09:05:31.292418 warning msgq LTE_fdd_enb_msgq.cc 234 >> rrc_to_mme circular buffer empty on receive >> 02/13/2017 09:05:31.292449 warning msgq LTE_fdd_enb_msgq.cc 234 >> mac_to_rlc circular buffer empty on receive >> 02/13/2017 09:05:31.292493 warning msgq LTE_fdd_enb_msgq.cc 234 >> pdcp_to_rlc circular buffer empty on receive >> 02/13/2017 09:05:31.292535 warning msgq LTE_fdd_enb_msgq.cc 234 >> gw_to_pdcp circular buffer empty on receive >> 02/13/2017 09:05:31.292566 warning msgq LTE_fdd_enb_msgq.cc 234 >> pdcp_to_rrc circular buffer empty on receive >> 02/13/2017 09:05:31.292596 warning msgq LTE_fdd_enb_msgq.cc 234 >> mme_to_rrc circular buffer empty on receive >> 02/13/2017 09:05:31.292629 warning msgq LTE_fdd_enb_msgq.cc 234 >> rlc_to_pdcp circular buffer empty on receive >> 02/13/2017 09:06:11.209530 warning msgq LTE_fdd_enb_msgq.cc 234 >> phy_to_mac circular buffer empty on receive >> 02/13/2017 09:06:11.209594 warning msgq LTE_fdd_enb_msgq.cc 234 >> rrc_to_pdcp circular buffer empty on receive >> 02/13/2017 09:06:11.209641 warning msgq LTE_fdd_enb_msgq.cc 234 >> rlc_to_mac circular buffer empty on receive >> 02/13/2017 09:06:11.209677 warning msgq LTE_fdd_enb_msgq.cc 234 >> mac_to_phy circular buffer empty on receive >> 02/13/2017 09:06:11.209755 warning msgq LTE_fdd_enb_msgq.cc 234 >> mac_to_timer circular buffer empty on receive >> 02/13/2017 09:06:11.209800 warning msgq LTE_fdd_enb_msgq.cc 234 >> rlc_to_pdcp circular buffer empty on receive >> 02/13/2017 09:06:11.209853 warning msgq LTE_fdd_enb_msgq.cc 234 >> pdcp_to_rlc circular buffer empty on receive >> 02/13/2017 09:06:11.209907 warning msgq LTE_fdd_enb_msgq.cc 234 >> mac_to_rlc circular buffer empty on receive >> 02/13/2017 09:06:11.209955 warning msgq LTE_fdd_enb_msgq.cc 234 >> gw_to_pdcp circular buffer empty on receive >> 02/13/2017 09:06:11.209987 warning msgq LTE_fdd_enb_msgq.cc 234 >> pdcp_to_rrc circular buffer empty on receive >> 02/13/2017 09:06:11.210027 warning msgq LTE_fdd_enb_msgq.cc 234 >> rrc_to_mme circular buffer empty on receive >> 02/13/2017 09:06:11.210061 warning msgq LTE_fdd_enb_msgq.cc 234 >> mme_to_rrc circular buffer empty on receive >> >> >> >> >> >> On Mon, Feb 13, 2017 at 2:26 PM, mg <mg...@gm...> wrote: >> >>> I installed the entire system following the OpenLTE recomandations, >>> per openlte_v00-20-04. >>> >>> However when I initiate command to start eNB, I am getting <fail "cant >>> start"> >>> and the following in debug terminal window >>> ". . . warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw circular buffer >>> empty on receive >>> . . .warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer >>> empty on receive >>> " and keeps on going >>> >>> I noticed that when I run the commands >>> uhd_find_devices & uhd_usrp_probe, >>> LTE_fdd_enodeb >>> >>> I am getting: >>> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >>> UHD_3.11.0.git-71-g2016126f >>> >>> Ettus recommended to go to UHD version 3.10.1.1. So I installed it and >>> now the commands >>> uhd_find_devices & uhd_usrp_probe return version 3.10.1.1: >>> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >>> UHD_003.010.001.HEAD-0-gc705922a >>> >>> however LTE_fdd_enodeb, still returns version 3.11.0: >>> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >>> UHD_3.11.0.git-71-g2016126f >>> >>> and still eNB <fail "cant start"> and the ongoing "...circular buffer >>> empty on receive ..." >>> >>> If you could just point me in the right direction or any recommendations >>> ? >>> >>> thanks >>> mg >>> >>> >>> >>> On Fri, Feb 10, 2017 at 2:00 PM, mg <mg...@gm...> wrote: >>> >>>> >>>> I am starting first step towards using OpenLTE. >>>> >>>> And according to the instructions in "Installing OpenLTE >>>> <https://sourceforge.net/p/openlte/wiki/Installing%20OpenLTE/>", Installing >>>> GNURadio with UHD:, >>>> getting ready to install and build the gnuradio, as the first step. >>>> >>>> I was wondering if I need to perform a separate step for the Ettus >>>> radio X300, to get the >>>> UHD driver code - https://github.com/EttusResearch/uhd - and build it >>>> ? >>>> >>>> Or the gnuradio build pulls in the required code and/or dependencies? >>>> >>>> Looking forward working with you and to contribute to this project >>>> >>>> Thanks >>>> >>>> >>>> >>>> >>>> >>>> >>> >> > |
|
From: ravi k. <rk1...@gm...> - 2017-02-14 19:13:48
|
Hi Members I am trying to install openlte Presently, my test phone can see network but not able to connect to the network. I am getting authentication errror error mme LTE_fdd_enb_mme.cc 712 Authentication failure cause=14, RNTI=67, RB=SRB1 In one of the posting its mention that cause=14 means the k value associated with user profile do not match with the k value in USIM. I know both are same, since I am using sysmocom-SJ1 USIM and I have both imsi and k value of the USIM. Any suggestion to fix this. Apart from that I am getting some error and warnings 02/14/2017 10:41:16.456641 error phy LTE_fdd_enb_phy.cc 667 PDSCH current_tti from MAC (10231) does not match PHY (1) 02/14/2017 10:41:16.457442 error phy LTE_fdd_enb_phy.cc 667 PDSCH current_tti from MAC (10232) does not match PHY (2) 02/14/2017 10:41:16.458501 error phy LTE_fdd_enb_phy.cc 667 PDSCH current_tti from MAC (10233) does not match PHY (3) 02/14/2017 10:41:16.477110 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive 02/14/2017 10:41:16.477169 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive 02/14/2017 10:41:24.755977 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/14/2017 10:41:24.756106 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/14/2017 10:41:25.443621 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/14/2017 10:41:25.443830 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/14/2017 10:41:25.443927 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/14/2017 10:41:26.217511 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive 02/14/2017 10:41:26.692909 info mac LTE_fdd_enb_mac.cc 371 MAC_dl_tti - PHY_dl_tti != 2 (-10238), skipping 0 subframes 02/14/2017 10:41:26.693644 info mac LTE_fdd_enb_mac.cc 371 MAC_dl_tti - PHY_dl_tti != 2 (-10239), skipping 0 subframes 02/14/2017 10:41:26.694713 info mac LTE_fdd_enb_mac.cc 371 MAC_dl_tti - PHY_dl_tti != 2 (0), skipping 0 subframes any suggestion on that Guys, please reply, I can see on forum some of the member are able to connect test phone to network. Please share info. ravi |
|
From: mg <mg...@gm...> - 2017-02-14 16:12:32
|
The errors we are seeing is from OpenLTE, from LTE_fdd_enb_msgq.cc, in void* LTE_fdd_enb_msgq::receive_thread(void *inputs), while waiting for a message. Can someone give us some indication if this environment is OK for OpenLTE, or can you please point us to or recommend the environment that should work. Our environment is: Ubuntu 16.04 LTS , 64-bit, i7 @ 2.2GHz x 8 GNURadio $ gnuradio-config-info --version v3.7.10.1-211-gb49da168 $ gnuradio-config-info --prefix /usr/local $ gnuradio-config-info --enabled-components python-support;testing-support;volk;doxygen;sphinx;gnuradio- runtime;gr-ctrlport;gr-blocks;gnuradio-companion;gr-fec;gr-f ft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-atsc;gr-audio;* alsa;* oss;gr-channels;gr-noaa;gr-pager;gr-qtgui;gr-trellis;gr-uhd; gr-utils;gr-video-sdl;gr-vocoder;gr-fcd;gr-wavelet;gr-wxgui;gr-zeromq UHD driver linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.HEAD-0-gc705922a and also tried 3.11.0 and 3.9.6 On Mon, Feb 13, 2017 at 5:33 PM, mg <mg...@gm...> wrote: > > I did rebuild the gnuradio using /build-gnuradio to select UHD driver > version 3.10.1.1 > And it integrates OK with OpenLTE , because now > LTE_fdd_enodeb returns version 3.10.1: > > linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_003.010.001.HEAD-0-gc705922a > > We are still unable to start eNB, same error: fail "cant start" > and terminal 3 debug still shows, see listing in Term 2 below. > > Can someone please tell us if we are not setting up correctly , we might > have missed or skipped a step. > We are looking at a source code, in LTE_fdd_enb_msgq.cc , and we see the > point of failure, but we would like to be able to see > how this works first because we have no idea how is suppose to work > overall. > > Is there a golden combination that we are not aware of that OpenLTE needs > to work ? > > thanks > mg > > > Term 2 display: > 02/13/2017 09:04:26.979640 info iface LTE_fdd_enb_interface.cc 787 *** LTE > FDD ENB DEBUG INTERFACE *** > 02/13/2017 09:05:28.243762 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw > circular buffer empty on receive > 02/13/2017 09:05:31.291939 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac > circular buffer empty on receive > 02/13/2017 09:05:31.292225 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac > circular buffer empty on receive > 02/13/2017 09:05:31.292278 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy > circular buffer empty on receive > 02/13/2017 09:05:31.292329 warning msgq LTE_fdd_enb_msgq.cc 234 > mac_to_timer circular buffer empty on receive > 02/13/2017 09:05:31.292369 warning msgq LTE_fdd_enb_msgq.cc 234 > rrc_to_pdcp circular buffer empty on receive > 02/13/2017 09:05:31.292418 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_mme > circular buffer empty on receive > 02/13/2017 09:05:31.292449 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_rlc > circular buffer empty on receive > 02/13/2017 09:05:31.292493 warning msgq LTE_fdd_enb_msgq.cc 234 > pdcp_to_rlc circular buffer empty on receive > 02/13/2017 09:05:31.292535 warning msgq LTE_fdd_enb_msgq.cc 234 gw_to_pdcp > circular buffer empty on receive > 02/13/2017 09:05:31.292566 warning msgq LTE_fdd_enb_msgq.cc 234 > pdcp_to_rrc circular buffer empty on receive > 02/13/2017 09:05:31.292596 warning msgq LTE_fdd_enb_msgq.cc 234 mme_to_rrc > circular buffer empty on receive > 02/13/2017 09:05:31.292629 warning msgq LTE_fdd_enb_msgq.cc 234 > rlc_to_pdcp circular buffer empty on receive > 02/13/2017 09:06:11.209530 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac > circular buffer empty on receive > 02/13/2017 09:06:11.209594 warning msgq LTE_fdd_enb_msgq.cc 234 > rrc_to_pdcp circular buffer empty on receive > 02/13/2017 09:06:11.209641 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac > circular buffer empty on receive > 02/13/2017 09:06:11.209677 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy > circular buffer empty on receive > 02/13/2017 09:06:11.209755 warning msgq LTE_fdd_enb_msgq.cc 234 > mac_to_timer circular buffer empty on receive > 02/13/2017 09:06:11.209800 warning msgq LTE_fdd_enb_msgq.cc 234 > rlc_to_pdcp circular buffer empty on receive > 02/13/2017 09:06:11.209853 warning msgq LTE_fdd_enb_msgq.cc 234 > pdcp_to_rlc circular buffer empty on receive > 02/13/2017 09:06:11.209907 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_rlc > circular buffer empty on receive > 02/13/2017 09:06:11.209955 warning msgq LTE_fdd_enb_msgq.cc 234 gw_to_pdcp > circular buffer empty on receive > 02/13/2017 09:06:11.209987 warning msgq LTE_fdd_enb_msgq.cc 234 > pdcp_to_rrc circular buffer empty on receive > 02/13/2017 09:06:11.210027 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_mme > circular buffer empty on receive > 02/13/2017 09:06:11.210061 warning msgq LTE_fdd_enb_msgq.cc 234 mme_to_rrc > circular buffer empty on receive > > > > > > On Mon, Feb 13, 2017 at 2:26 PM, mg <mg...@gm...> wrote: > >> I installed the entire system following the OpenLTE recomandations, >> per openlte_v00-20-04. >> >> However when I initiate command to start eNB, I am getting <fail "cant >> start"> >> and the following in debug terminal window >> ". . . warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw circular buffer >> empty on receive >> . . .warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer >> empty on receive >> " and keeps on going >> >> I noticed that when I run the commands >> uhd_find_devices & uhd_usrp_probe, >> LTE_fdd_enodeb >> >> I am getting: >> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >> UHD_3.11.0.git-71-g2016126f >> >> Ettus recommended to go to UHD version 3.10.1.1. So I installed it and >> now the commands >> uhd_find_devices & uhd_usrp_probe return version 3.10.1.1: >> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >> UHD_003.010.001.HEAD-0-gc705922a >> >> however LTE_fdd_enodeb, still returns version 3.11.0: >> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >> UHD_3.11.0.git-71-g2016126f >> >> and still eNB <fail "cant start"> and the ongoing "...circular buffer >> empty on receive ..." >> >> If you could just point me in the right direction or any recommendations >> ? >> >> thanks >> mg >> >> >> >> On Fri, Feb 10, 2017 at 2:00 PM, mg <mg...@gm...> wrote: >> >>> >>> I am starting first step towards using OpenLTE. >>> >>> And according to the instructions in "Installing OpenLTE >>> <https://sourceforge.net/p/openlte/wiki/Installing%20OpenLTE/>", Installing >>> GNURadio with UHD:, >>> getting ready to install and build the gnuradio, as the first step. >>> >>> I was wondering if I need to perform a separate step for the Ettus radio >>> X300, to get the >>> UHD driver code - https://github.com/EttusResearch/uhd - and build it >>> ? >>> >>> Or the gnuradio build pulls in the required code and/or dependencies? >>> >>> Looking forward working with you and to contribute to this project >>> >>> Thanks >>> >>> >>> >>> >>> >>> >> > |
|
From: mg <mg...@gm...> - 2017-02-13 22:33:10
|
I did rebuild the gnuradio using /build-gnuradio to select UHD driver version 3.10.1.1 And it integrates OK with OpenLTE , because now LTE_fdd_enodeb returns version 3.10.1: linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.HEAD-0-gc705922a We are still unable to start eNB, same error: fail "cant start" and terminal 3 debug still shows, see listing in Term 2 below. Can someone please tell us if we are not setting up correctly , we might have missed or skipped a step. We are looking at a source code, in LTE_fdd_enb_msgq.cc , and we see the point of failure, but we would like to be able to see how this works first because we have no idea how is suppose to work overall. Is there a golden combination that we are not aware of that OpenLTE needs to work ? thanks mg Term 2 display: 02/13/2017 09:04:26.979640 info iface LTE_fdd_enb_interface.cc 787 *** LTE FDD ENB DEBUG INTERFACE *** 02/13/2017 09:05:28.243762 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw circular buffer empty on receive 02/13/2017 09:05:31.291939 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer empty on receive 02/13/2017 09:05:31.292225 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive 02/13/2017 09:05:31.292278 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive 02/13/2017 09:05:31.292329 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/13/2017 09:05:31.292369 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_pdcp circular buffer empty on receive 02/13/2017 09:05:31.292418 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_mme circular buffer empty on receive 02/13/2017 09:05:31.292449 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_rlc circular buffer empty on receive 02/13/2017 09:05:31.292493 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rlc circular buffer empty on receive 02/13/2017 09:05:31.292535 warning msgq LTE_fdd_enb_msgq.cc 234 gw_to_pdcp circular buffer empty on receive 02/13/2017 09:05:31.292566 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rrc circular buffer empty on receive 02/13/2017 09:05:31.292596 warning msgq LTE_fdd_enb_msgq.cc 234 mme_to_rrc circular buffer empty on receive 02/13/2017 09:05:31.292629 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_pdcp circular buffer empty on receive 02/13/2017 09:06:11.209530 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive 02/13/2017 09:06:11.209594 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_pdcp circular buffer empty on receive 02/13/2017 09:06:11.209641 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer empty on receive 02/13/2017 09:06:11.209677 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive 02/13/2017 09:06:11.209755 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/13/2017 09:06:11.209800 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_pdcp circular buffer empty on receive 02/13/2017 09:06:11.209853 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rlc circular buffer empty on receive 02/13/2017 09:06:11.209907 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_rlc circular buffer empty on receive 02/13/2017 09:06:11.209955 warning msgq LTE_fdd_enb_msgq.cc 234 gw_to_pdcp circular buffer empty on receive 02/13/2017 09:06:11.209987 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rrc circular buffer empty on receive 02/13/2017 09:06:11.210027 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_mme circular buffer empty on receive 02/13/2017 09:06:11.210061 warning msgq LTE_fdd_enb_msgq.cc 234 mme_to_rrc circular buffer empty on receive On Mon, Feb 13, 2017 at 2:26 PM, mg <mg...@gm...> wrote: > I installed the entire system following the OpenLTE recomandations, > per openlte_v00-20-04. > > However when I initiate command to start eNB, I am getting <fail "cant > start"> > and the following in debug terminal window > ". . . warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw circular buffer > empty on receive > . . .warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer > empty on receive > " and keeps on going > > I noticed that when I run the commands > uhd_find_devices & uhd_usrp_probe, > LTE_fdd_enodeb > > I am getting: > linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_3.11.0.git-71-g2016126f > > Ettus recommended to go to UHD version 3.10.1.1. So I installed it and > now the commands > uhd_find_devices & uhd_usrp_probe return version 3.10.1.1: > linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_003.010.001.HEAD-0-gc705922a > > however LTE_fdd_enodeb, still returns version 3.11.0: > linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_3.11.0.git-71-g2016126f > > and still eNB <fail "cant start"> and the ongoing "...circular buffer > empty on receive ..." > > If you could just point me in the right direction or any recommendations ? > > thanks > mg > > > > On Fri, Feb 10, 2017 at 2:00 PM, mg <mg...@gm...> wrote: > >> >> I am starting first step towards using OpenLTE. >> >> And according to the instructions in "Installing OpenLTE >> <https://sourceforge.net/p/openlte/wiki/Installing%20OpenLTE/>", Installing >> GNURadio with UHD:, >> getting ready to install and build the gnuradio, as the first step. >> >> I was wondering if I need to perform a separate step for the Ettus radio >> X300, to get the >> UHD driver code - https://github.com/EttusResearch/uhd - and build it ? >> >> >> Or the gnuradio build pulls in the required code and/or dependencies? >> >> Looking forward working with you and to contribute to this project >> >> Thanks >> >> >> >> >> >> > |
|
From: mg <mg...@gm...> - 2017-02-13 19:26:51
|
I installed the entire system following the OpenLTE recomandations, per openlte_v00-20-04. However when I initiate command to start eNB, I am getting <fail "cant start"> and the following in debug terminal window ". . . warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw circular buffer empty on receive . . .warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer empty on receive " and keeps on going I noticed that when I run the commands uhd_find_devices & uhd_usrp_probe, LTE_fdd_enodeb I am getting: linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.git-71-g2016126f Ettus recommended to go to UHD version 3.10.1.1. So I installed it and now the commands uhd_find_devices & uhd_usrp_probe return version 3.10.1.1: linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.HEAD-0-gc705922a however LTE_fdd_enodeb, still returns version 3.11.0: linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.git-71-g2016126f and still eNB <fail "cant start"> and the ongoing "...circular buffer empty on receive ..." If you could just point me in the right direction or any recommendations ? thanks mg On Fri, Feb 10, 2017 at 2:00 PM, mg <mg...@gm...> wrote: > > I am starting first step towards using OpenLTE. > > And according to the instructions in "Installing OpenLTE > <https://sourceforge.net/p/openlte/wiki/Installing%20OpenLTE/>", Installing > GNURadio with UHD:, > getting ready to install and build the gnuradio, as the first step. > > I was wondering if I need to perform a separate step for the Ettus radio > X300, to get the > UHD driver code - https://github.com/EttusResearch/uhd - and build it ? > > Or the gnuradio build pulls in the required code and/or dependencies? > > Looking forward working with you and to contribute to this project > > Thanks > > > > > > |
31 messages has been excluded from this view by a project administrator.