Skip to content
Snippets Groups Projects
  1. Apr 16, 2018
    • Bi-Ruei, Chiu's avatar
      Compare version number using MAKE_VERSION macro to provide better SW configuration: · 5c23af77
      Bi-Ruei, Chiu authored
      1. Previous SW configuration for different RRC version relies on whether macro Rel10,
         Rel14 defined or not by checking #ifdef Rel14 or #if defined(Rel10) || defined(R14).
         Whenever there is a newer RRC version, e.g. Rel15, it will be very a tedious and
         error-prone job to add defined(Rel15) in every place.
      
      2. Some RRC messages are defined in release 13 instead of release 14, NB-IoT
         feature is one of such example. Our code shall reflect this fact instead of using
         an afterward version number in software configuration.
      
      3. Some RRC messages or some fields of certain RRC messages are added in the middle
         a release, e.g. SystemInformationBlockType1_v1310_IEs_t defined in RRC 13.1.0
         and RRC 9.2.0 made some changes to SIB12 and SIB13 so we have sib12_v920 and
         sib13_v920 fields in SIB12 and SIB13's struct.
         We need a finer grain of control when using ASN1 from different RRC version.
      
      4. S1AP also has this problem that it use UPDATE_RELEASE_9 and UPDATE_RELEASE_10 to
         differentiate between various S1AP version.
      
      This commit propose using MAKE_VERSION(x,y,z) to designate the version number and
      modify current conditional compilation accordingly.
      
      Note: 2018/04/16, Modified based on Cedric's comment.
      5c23af77
    • Cedric Roux's avatar
      79eb6eb4
  2. Apr 11, 2018
    • Cedric Roux's avatar
      integration fix: various fixes · e29d500d
      Cedric Roux authored
      - fix compilation of dlsim/ulsim/oaisim by defining some needed
        global variables
      - fix compilation of oaisim: compile coding and params_libconfig
      - fix running of if4p5 with low CPU count (oaisim was not working
        on the machine 'haswell' because of this)
      e29d500d
    • WANG Tsu-Han's avatar
      fixs for 5-7 core · 68fdd19c
      WANG Tsu-Han authored
      68fdd19c
  3. Apr 10, 2018
  4. Apr 06, 2018
  5. Apr 05, 2018
  6. Mar 23, 2018
  7. Mar 20, 2018
  8. Mar 16, 2018
  9. Mar 14, 2018
  10. Mar 08, 2018
    • 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
  11. Mar 06, 2018
  12. Mar 05, 2018
  13. Feb 23, 2018
  14. Feb 22, 2018
  15. Feb 21, 2018
  16. Feb 20, 2018
  17. Feb 19, 2018
  18. Feb 18, 2018
  19. Feb 16, 2018
  20. Feb 14, 2018
  21. Feb 12, 2018
  22. Feb 09, 2018
Loading