[srslte-users] Reasons for CRC =KO in srsLTE
Justin Tallon
justin.tallon at softwareradiosystems.com
Thu Oct 25 09:24:25 UTC 2018
Hey Puneet!
How often is it happening? can you send logs?
____
Justin Tallon Ph.D.
Software Radio Systems (SRS)
http://www.softwareradiosystems.com
+353-86-067-0753 | justin.tallon at softwareradiosystems.com
On Thu, Oct 25, 2018 at 11:22 AM Puneet Sharma <puneet0711 at gmail.com> wrote:
> Hey Justin,
>
> Thanks for replying.
>
> What can I do to remove this error?
>
> Br
> Puneet Sharma
>
>
> On Thu, Oct 25, 2018, 11:18 AM Justin Tallon <
> justin.tallon at softwareradiosystems.com> wrote:
>
>> Hye Puneet!
>>
>> This indicates that there has been a CRC failure on this uplink block.
>>
>>
>> ____
>> Justin Tallon Ph.D.
>>
>> Software Radio Systems (SRS)
>> http://www.softwareradiosystems.com
>>
>> +353-86-067-0753 | justin.tallon at softwareradiosystems.com
>>
>>
>> On Thu, Oct 25, 2018 at 11:15 AM Puneet Sharma <puneet0711 at gmail.com>
>> wrote:
>>
>>> Hello Experts,
>>>
>>> Can anyone explain to me the reason for crc=KO? The logs are as follows
>>>
>>>
>>>
>>>
>>>
>>>
>>> *10:59:26.728160 [PHY1] [I] [01767] PUSCH: rnti=0x46, prb=(0,20),
>>> tbs=717, mcs=15, rv=0, snr=18.2 dB, n_iter=4, crc=KO, dec_time= 303
>>> us 0000: 3d 3a 1f 00 3f 00 00 00 00 00 00 00 00 00 00 00
>>> 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>> 10:59:26.728178 [MAC ] [W] [01767] SCHED: discarting TB 0 pid=7, tti=1767,
>>> maximum number of retx exceeded (1)10:59:26.729808 [PHY1] [I] [01769]
>>> PHICH: rnti=0x46, hi=0, I_lowest=0, n_dmrs=0, tti_tx_dl=177110:59:26.741858
>>> [PHY1] [I] [01781] PUCCH: rnti=0x46, corr=-0.00, n_pucch=0, n_prb=48, sr=no*
>>>
>>> Thanks in advance
>>>
>>> Regards
>>> Puneet Sharma
>>> _______________________________________________
>>> srslte-users mailing list
>>> srslte-users at lists.softwareradiosystems.com
>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20181025/eb5f106f/attachment.htm>
More information about the srsran-users
mailing list