this can happen during user removal
2022-02-13T00:47:49.195816 [RRC ] [I] Activity timer for rnti=0x50 expired after 80 ms
2022-02-13T00:47:49.195818 [GTPU ] [I] Removing user - rnti=0x50 not found.
2022-02-13T00:47:49.195818 [STCK ] [I] Bearers: No EPS bearer registered for rnti=0x50
2022-02-13T00:47:49.195827 [RRC ] [I] Removed user rnti=0x50
2022-02-13T00:47:49.199697 [PHY ] [E] [ 7234] Error setting grant for rnti=0x0, cc=0
2022-02-13T00:47:49.199698 [PHY0 ] [I] [ 7233] Failed setting UL grants. Some grant's RNTI does not exist.
2022-02-13T00:47:49.209172 [MAC ] [I] [ 7242] User rnti=0x4f removed from MAC/PHY
2022-02-13T00:47:49.223248 [MAC ] [I] [ 7256] User rnti=0x50 removed from MAC/PHY
Make PCAP handlers deregister from this list when they are destructed. This avoid the signal handler calling destructed objects under very rare circumstances.
fix MAC PDU packing issue for UL-CCCH that uses
only 6 B SDU. If the SDU fits inside 6 B, the LCID
for Msg3 should be set to be CCCH48 instead of CCCH64.
* Add CFR module to the phy lib
* Add dynamic threshold with PAPR estimation
* Add a CFR unit test, CFR module improvements and refactoring.
Swap the gain normalization before the CFR.
* Add CFR config interface to srsenb
* Add CFR support to pdsch_enodeb
* Add DL PAPR measurement to eNB.
Co-authored-by: Cristian Balint <cristian.balint@gmail.com>
* Add test coverage to srsran_vec_gen_clip_env
* in SA the entire PHY config is applied immediately
* for NSA (in some scenarios) parts of the config are applied after the RA complete
This fixes#3842
Previously tests were failing on some machines, because
receiver was unable to receive the last few samples from file.
Reason: the transmitter did not close the file properly, so
the last samples were (sometimes) not yet flushed to disk.
This commits extends the file-based RF device as follows:
* open device via device string
* add tx to file
* add multi-channel support (multiple files)
* add rf_file_test.c to for testing
It comes with the following changes:
* Add RF frontend API function "srslte_rf_open_file()"
* Open file-based RF via explicit call of custom
"rf_file_open_file()", instead of "srslte_rf_open_multi()"
function pointer as for regular devices.
* Introduce device name "file"
* Introduce new SRSLTE_ERROR_RX_EOF error code
* ZMQ: make update_rates() static to resolve conflicts