1. 17 Oct, 2018 1 commit
  2. 14 Aug, 2018 1 commit
  3. 30 Jul, 2018 2 commits
  4. 29 Jun, 2018 2 commits
  5. 03 Jun, 2018 1 commit
  6. 02 Jun, 2018 1 commit
  7. 28 May, 2018 1 commit
  8. 15 May, 2018 1 commit
  9. 29 Apr, 2018 1 commit
  10. 22 Apr, 2018 1 commit
  11. 09 Apr, 2018 1 commit
  12. 13 Mar, 2018 1 commit
  13. 08 Mar, 2018 1 commit
  14. 27 Feb, 2018 1 commit
    • Cedric Roux's avatar
      hotfix: clear DCI padding bits · c9f89db8
      Cedric Roux authored
      The problem is the following (as reported by an user):
      
        "one UE is attached to OAI system. UE is near the antenna. Try to detach
        the UE and attach again. Repeat this procedure for 5-6 times. OAI system
        does not work and any the UE can not attach to this system. I use TEMS
        software and I can see MIB signaling on this UE but UE can not decode SIB1
        and SIB2."
      
      What happens is that the DCI for SIB1 and SIB2 is not cleared before
      use. That is the bits in the 'padding' field keep the values that were
      set before. If the structure has been used to transmit other DCIs
      (eg. for UEs) in the past, it may be reused with some of those bits set
      to 1. When receiving this DCI, the UE won't accept it because it
      gets some bits at 1 where it expects them to be 0.
      
      The short-term/quick solution is to clear the 'padding' field.
      A better solution would be to rewrite this part of the code,
      which is way too complicated for what it does. But this takes
      too much time.
      
      In dci.h the field 'dummy' of some structures was renamed to 'padding'.
      The fields 'padding32' and 'padding64' were also renamed to 'padding'
      for consistency.
      
      Some structures (DCI2B_1_5MHz_TDD, DCI2B_10MHz_FDD, DCI2D_1_5MHz_FDD,
      DCI2D_5MHz_FDD, DCI2D_10MHz_FDD) had a 'padding' field at the end, which
      was renamed to 'padding0'. I don't know if this field should be here at all.
      To me this field looks very suspicious. When we test DCIs 2B and 2D we
      should be careful.
      
      (cherry picked from commit c5ca2bd8)
      c9f89db8
  15. 22 Feb, 2018 1 commit
    • Cedric Roux's avatar
      integration: cleanup · 8ca5fb4e
      Cedric Roux authored
      - remove spaces at the end of lines
      - remove useless dead code
        use: git show -p <this commit> -w
        to see it clearly
      8ca5fb4e
  16. 20 Feb, 2018 1 commit
  17. 19 Feb, 2018 1 commit
  18. 17 Feb, 2018 1 commit
  19. 16 Feb, 2018 1 commit
  20. 14 Feb, 2018 1 commit
    • Cedric Roux's avatar
      fixup previous bad merge (UE disconnection did not work properly anymore) · 91332d39
      Cedric Roux authored
      Doing airplane mode off to connect a cots UE followed by airplane mode on
      to disconnect it gives very bad results (bad disconnection with lots of
      UL failures followed by lots of logs in the eNB). It used to work properly
      after the work done by Xu Bo.
      
      It turns out that in 2018.w04 things were still working okay. But
      in 2018.w05 no.
      
      So I ran:
      
          git diff 2018.w04 2018.w05
      
      And I checked all the modifications that I thought were relevant
      (everything related to the UE, oaisim, if4 and fapi has not been checked).
      
      This commits takes back the version of 2018.w04.
      
      The modifications in openair2/RRC/LITE/rrc_eNB.c are necessary, I think.
      
      The other modifications may not be necessary or even wrong. To be checked
      at some point.
      91332d39
  21. 13 Feb, 2018 1 commit
  22. 12 Feb, 2018 1 commit
  23. 08 Feb, 2018 2 commits
  24. 07 Feb, 2018 1 commit
  25. 05 Feb, 2018 1 commit
  26. 23 Jan, 2018 1 commit
  27. 22 Jan, 2018 2 commits
  28. 15 Jan, 2018 2 commits
    • 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
  29. 10 Jan, 2018 1 commit
  30. 08 Jan, 2018 1 commit
  31. 03 Jan, 2018 1 commit
    • Cedric Roux's avatar
      hotfix: clear DCI padding bits · c5ca2bd8
      Cedric Roux authored
      The problem is the following (as reported by an user):
      
        "one UE is attached to OAI system. UE is near the antenna. Try to detach
        the UE and attach again. Repeat this procedure for 5-6 times. OAI system
        does not work and any the UE can not attach to this system. I use TEMS
        software and I can see MIB signaling on this UE but UE can not decode SIB1
        and SIB2."
      
      What happens is that the DCI for SIB1 and SIB2 is not cleared before
      use. That is the bits in the 'padding' field keep the values that were
      set before. If the structure has been used to transmit other DCIs
      (eg. for UEs) in the past, it may be reused with some of those bits set
      to 1. When receiving this DCI, the UE won't accept it because it
      gets some bits at 1 where it expects them to be 0.
      
      The short-term/quick solution is to clear the 'padding' field.
      A better solution would be to rewrite this part of the code,
      which is way too complicated for what it does. But this takes
      too much time.
      
      In dci.h the field 'dummy' of some structures was renamed to 'padding'.
      The fields 'padding32' and 'padding64' were also renamed to 'padding'
      for consistency.
      
      Some structures (DCI2B_1_5MHz_TDD, DCI2B_10MHz_FDD, DCI2D_1_5MHz_FDD,
      DCI2D_5MHz_FDD, DCI2D_10MHz_FDD) had a 'padding' field at the end, which
      was renamed to 'padding0'. I don't know if this field should be here at all.
      To me this field looks very suspicious. When we test DCIs 2B and 2D we
      should be careful.
      c5ca2bd8
  32. 27 Dec, 2017 1 commit
  33. 07 Dec, 2017 1 commit
  34. 23 Nov, 2017 1 commit
  35. 23 Oct, 2017 1 commit