1. 23 Mar, 2018 1 commit
  2. 20 Mar, 2018 1 commit
    • Robert Schmidt's avatar
      free configmodule memory when shutting down · 318e4a34
      Robert Schmidt authored
      It is possible to restart the lte-softmodem via the FlexRAN controller. For
      this to work, the end_configmodule() method needs to be called when shutting
      the lte-softmodem down so that the configuration can be read again during a
      restart.
      318e4a34
  3. 08 Mar, 2018 5 commits
    • oai's avatar
      more NB-IoT integration · da50d68b
      oai authored
      da50d68b
    • oai's avatar
    • oai's avatar
    • Cedric Roux's avatar
      add a stop_rf function in the RU · 96380582
      Cedric Roux authored
      When the program exits it has to stop the streaming of the USRP.
      The function exit_fun is supposed to do that. When quitting with
      control+c (very common case) this function is not called. The
      code is very unclear there, so let's add a stop_rf in the RU,
      as there is already a start_rf.
      
      If we don't call trx_end_func, then at the next run the USRP
      device may be in an unstable state and behave improperly.
      
      If the program crashes then the USRP device may be in an
      unstable state. The only solution to this problem is to reset
      the USRP device.
      
      Maybe there is a way to clean the state of the device when we
      open it, before we start using it. Sort of a cleanup before
      use. That could be a better solution to "bad state after program
      crash".
      
      What has been tested:
      - monolithic eNB only
      96380582
    • Cedric Roux's avatar
      cleanup - remove unnecessary calls to get_cpu_freq_GHz · 5a61f994
      Cedric Roux authored
      The one in lte-enb.c disrupts the realtime. Using a B200mini with
      20MHz bandwidth leads to the UE unable to connect for it seesms like
      the UL and DL are not properly time synched because of this sleep
      of one second that happens after the USRP streaming has started.
      We see some random access attempts but the decoded preamble is
      wrong.
      
      This may be dependant on the setup. I had sporadic errors with
      a B210, where sometimes the UE could connect and sometimes not.
      5a61f994
  4. 22 Feb, 2018 1 commit
  5. 12 Feb, 2018 2 commits
  6. 09 Feb, 2018 3 commits
  7. 08 Feb, 2018 1 commit
  8. 05 Feb, 2018 1 commit
  9. 31 Jan, 2018 8 commits
  10. 28 Jan, 2018 1 commit
  11. 24 Jan, 2018 1 commit
  12. 21 Jan, 2018 1 commit
  13. 16 Jan, 2018 1 commit
  14. 15 Jan, 2018 3 commits
    • Mongazon's avatar
      Fix #582, RTAI, RTAI_ENABLED, ENABLE_RTAI_CLOCK, RTAI_ISNT_POSIX,... · cf0e9175
      Mongazon authored
      Fix #582, RTAI, RTAI_ENABLED, ENABLE_RTAI_CLOCK, RTAI_ISNT_POSIX, _RTAI_MATH_H, CELLULAR, TIMER_ONESHOT_MODE, EMOS, EMOS_CHANNEL, OAI_EMU, OPENAIR_EMU, PHY_ABSTRACTION, PHY_ABSTRACTION_UL removed
      cf0e9175
    • Cedric Roux's avatar
      Fix NFAPI integration · 922b5b59
      Cedric Roux authored
      This commit fixes issues introduced by the previous commit.
      
      Summary of work:
      - cleanup:
        - fix LOG_XX to be less verbose
        - fix cmake_targets/CMakeLists.txt
        - fix oaienv
        - remove dead code
      - bug fixes:
        - in openair1/SCHED/fapi_l1.c we had:
            eNB->pdcch_vars[subframe&1].num_dci           = number_dci;
          should be:
            eNB->pdcch_vars[subframe&1].num_dci           = 0;
          This bug let the PHY send more DCIs than what should have been
          sent because num_dci is incremented later on in the code.
          This fix may be a problem for fapi mode, to be checked.
        - add new T VCD traces
        - revert openair1/PHY/TOOLS/file_output.c to 'develop' version
        - remove thread_id in logRecord/logRecord_mt
        - revert (and adapt) configuration files
        - be careful when doing frame++, we need to % 1024
        - revert target_rx_power in openair2/LAYER2/MAC/eNB_scheduler_ulsch.c
      - NFAPI:
        - the open-nFAPI code has been included in the repository. See nfapi/README.
          Maybe we should "git clone" the Cisco repository instead. We have to be
          careful of availability though.
      
      What has been tested:
      - monolithic eNB FDD 5/10MHz with one UE, iperf UDP/TCP uplink/downlink
      
      Anything else may fail to work, especially the FAPI mode, which has not
      been tested at all.
      922b5b59
    • Cedric Roux's avatar
      import NFAPI work from David Price from Cisco (non-working commit, do not use it) · 7757b9e7
      Cedric Roux authored
      It has been chosen to not include the full history of commits
      from David. He included a binary version of wireshark, probably
      a modified one that understands NFAPI. Wireshark is released under
      the GPL license, we cannot include it in the repository. We could
      have done a next commit to remove this binary. But then it would
      still be present in the history of commits, which may not be allowed.
      And it would take space on disk. We could edit the history to remove
      wireshark entirely. But this operation is too complicated.
      
      There was also a pcap capture file, which has nothing to do in
      the history of commits and would take space on disk. There again,
      it's too difficult to edit the history to remove it.
      
      There was a file .gitignore that was also removed.
      
      The original history can be found on David's repository:
      https://gitlab.eurecom.fr/daveprice/openairinterface5g/
      The branch is: nfapi-ru-rau-split.
      
      A copy of that branch has been included in the internal OAI
      repository, for those who have access to it.
      The branch is the same. The last commit ID is
      91064382.
      
      You can compare the current commit with the commit 9106...
      to see what differs.
      
      The current commit has to be considered non-working.
      The commit following the current commit will fix problems with
      the work in the current commit.
      
      If you use git bisect, don't spend time analyzing the current
      commit.
      7757b9e7
  15. 11 Jan, 2018 1 commit
  16. 10 Jan, 2018 1 commit
  17. 09 Jan, 2018 1 commit
  18. 14 Dec, 2017 7 commits