- Jun 05, 2018
-
-
hongzhi wang authored
-
- Jun 04, 2018
-
-
hongzhi wang authored
-
- May 30, 2018
-
-
Hongzhi Wang authored
-
- Apr 25, 2018
- Apr 09, 2018
-
-
Florian Kaltenberger authored
-
- Apr 06, 2018
-
-
root authored
Conflicts: cmake_targets/build_oai openair1/PHY/LTE_TRANSPORT/prach.c openair1/SCHED/phy_procedures_lte_ue.c targets/ARCH/COMMON/common_lib.h targets/RT/USER/lte-softmodem.c
-
- Mar 08, 2018
-
-
oai authored
-
- Jan 19, 2018
-
-
Massive authored
-
- Jan 15, 2018
-
-
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.
-
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 9106438239e0bc626ff1fa1d97d911caadd0fbb9. 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.
-
- Jan 11, 2018
-
-
bruno mongazon authored
-
bruno mongazon authored
-
- Nov 14, 2017
-
-
bruno mongazon authored
-
- Nov 04, 2017
-
-
Raymond Knopp authored
-
- Oct 23, 2017
-
-
Wang Tsu-Han authored
added numerology paramter
-
Cedric Roux authored
-
- Oct 20, 2017
-
-
Raymond Knopp authored
-
- Oct 06, 2017
-
-
Cedric Roux authored
internal use, no documentation, no support.
-
- Sep 27, 2017
-
-
Cedric Roux authored
-
- Sep 21, 2017
-
-
Raymond Knopp authored
-
Raymond Knopp authored
-
- Aug 29, 2017
-
-
Cedric Roux authored
-
- Aug 23, 2017
-
-
Cedric Roux authored
How to use: 1 - compilation of softmodem: ./build_oai --eNB -t ETHERNET 2 - compilation of mobipass driver: cd cmake_targets/lte_build_oai/build make oai_mobipass ln -sf liboai_mobipass.so liboai_transpro.so 3 - configuration: edit the configuration file, set "node_timing" to "synch_to_mobipass_standalone" that is, have the line: node_timing = "synch_to_mobipass_standalone"; 4 - run: run as usual: sudo ./lte-softmodem -C <configuration file>
-
- Aug 22, 2017
-
-
Florian Kaltenberger authored
-
- Aug 18, 2017
-
-
Florian Kaltenberger authored
-
Florian Kaltenberger authored
-
Florian Kaltenberger authored
-
- Aug 14, 2017
-
-
Raymond Knopp authored
-
- Jun 23, 2017
-
-
Cedric Roux authored
-
Cedric Roux authored
Several problems are present. The first is that _write returns 0 instead of the number of samples. We solve it by returning nsamps. The second is that _read may return less samples at the beginning and we don't want to exit for that. We solve it also by returning nsamps. (We still need to log more in this, to be done in the next commit.) The third is that after initialization we don't send anything for a while, time for the softmodem to finish its init. This generates lots of "RX overrun". We solve it by disabling TX and RX modules after init and then in trx_brf_start we activate them again (and also call bladerf_sync_config, which seems to be mandatory, and bladerf_calibrate_dc, which may be avoided, perhaps). Maybe not the end of the story. Sometimes it works, UE connects, traffic is fine (tested only with 5MHz). Sometimes it does not, UE does not connect, or it connects but then traffic is bad, especially uplink. To be refined.
-
- Jun 04, 2017
-
-
Raymond Knopp authored
-
- May 22, 2017
-
-
Cedric Roux authored
-
- May 18, 2017
-
-
Cedric Roux authored
those popped up thanks to previous commit
-
- May 15, 2017
-
-
Cedric Roux authored
No need for this special case. Plus, it fails with the work from Nokia on compilation cleanup.
-
- Apr 25, 2017
-
-
Raymond Knopp authored
-
- Apr 18, 2017
-
-
Raymond Knopp authored
-
- Apr 17, 2017
-
-
Raymond Knopp authored
-
- Mar 27, 2017
-
-
Cedric Roux authored
We have a strange problem with the timestamp of the very first packets received from the LimeSDR that leads to a complete failure of the eNB. A simple workaround is to discard the first RX packet just after a "start" of the device. We also change the value of "tx_sample_advance" to a more reasonable value. The problem of timestamp was "solved" differently in the past and at the time we needed to put a much higher value. This may have to be refined at some point.
-
- Mar 24, 2017
-
-
Cedric Roux authored
-