1. 17 Oct, 2018 1 commit
  2. 16 Oct, 2018 1 commit
  3. 12 Oct, 2018 1 commit
  4. 30 Sep, 2018 2 commits
  5. 28 Sep, 2018 4 commits
  6. 27 Sep, 2018 1 commit
  7. 20 Sep, 2018 2 commits
  8. 19 Sep, 2018 1 commit
  9. 14 Sep, 2018 2 commits
    • Cedric Roux's avatar
      basic simulator: support TDD mode · 824f62d8
      Cedric Roux authored
      For whatever reason we need N_TA_offset to be 0 for the basic simulator
      to function properly.
      
      This is more a hack than a proper solution. More analysis is needed
      to understand what happens and what should be really done.
      824f62d8
    • Cedric Roux's avatar
      basic simulator: handle discontinuities in output · ab7515e2
      Cedric Roux authored
      In TDD mode the eNB does not output data all the time,
      only in downlink and special subframes.
      
      The basic simulator needs a continuous stream of samples.
      
      So let's fill the blank with silence.
      ab7515e2
  10. 13 Sep, 2018 2 commits
  11. 12 Sep, 2018 2 commits
  12. 11 Sep, 2018 1 commit
  13. 06 Sep, 2018 1 commit
  14. 05 Sep, 2018 5 commits
  15. 04 Sep, 2018 1 commit
  16. 03 Sep, 2018 7 commits
  17. 31 Aug, 2018 2 commits
  18. 30 Aug, 2018 1 commit
  19. 29 Aug, 2018 1 commit
  20. 27 Aug, 2018 2 commits
    • Cedric Roux's avatar
      bugfix: fix threading in the UE · a48c3658
      Cedric Roux authored
      Various problems were found with the basic simulator.
      
      Variables used by various threads for synchronization need to
      be initialized properly. That is before the various threads
      start using them.
      
      This goes for:
      - UE->is_synchronized
      - UE->proc.instance_cnt_synch
      - UE->proc.instance_cnt_rxtx
      
      The function "UE->rfdevice.trx_start_func" was called in
      "UE_thread_synch" but should be called in "UE_thread" because
      "UE_thread" is the one that calls "UE->rfdevice.trx_read_func"
      and there is no guaranty that the call to "UE->rfdevice.trx_start_func"
      is done before as it has to (it's in another thread).
      
      And finally "pthread_cond_signal(&proc->cond_rxtx)" was called twice,
      which may not be a problem but was certainly not intended. Plus
      removing one call simplifies the code by removing some "if" logic,
      which is a good thing per se.
      
      This commit was not tested with a real UE and may thus introduce some
      issues. Hopefully not!
      a48c3658
    • Cedric Roux's avatar
      basic simulator: bugfix: wait for synch ready at the right time · 97ddf5ea
      Cedric Roux authored
      Before this commit we were checking for UE->is_synchronized == 0
      then we were waiting for a potentially active synch routine to
      finish and then we were starting the synch routine again but the
      synch routine that was running may have set UE->is_synchronized
      to 1. This was leading to various problems, most notably the following
      message repeated over and over in the UE log and the UE unable to
      connect properly:
      
          [RRC]  [UE 0] Frame 377: OUT OF SYNC FROM eNB 0 (T310 active 0 : T310 0, N310 345, N311 0)
      
      So let's wait for a potentially active synch routine to finish
      before anything else.
      97ddf5ea