-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect number of RE in tdd while decoding pdsch #566
Comments
Hello all,
Hope it helps. Best regards. |
Thanks for reporting this issue and proposing a solution. We try to reproduce on our side. |
Hey, thanks for the update. Do you mind sending a proper diff or patch for that, or even formatting it correctly here would be enough. Thanks |
yes, here is the diff. I also updated comment above |
Thanks for that. We've cherry-picked it and test now. The fix should be included in the next release. Have you tested srsUE by any chance with the TDD cell you have? |
Hello, 18:43:06.519600 [PHY0] [I] [ 2005] SYNC: MIB Decoded: Mode=TDD, PCI=11, PRB=50, Ports=4, CFO=0.8 KHz 18:43:07.095571 [PHY0] [I] [ 7079] Setting PHICH mi value auto. sf_idx=8, mi=1, idx=0 I can provide a full log if required. Hope it helps. |
Thanks for trying this out. The missing RAR could have many causes. Maybe also the Tx power is too low and you too far away from the cell. Hard to say without full logs, etc. Anyway, thanks again for flagging the issue. |
Dear All,
currently I use srsLTE with b200mini device and try to track random access response messages and contention resolution messages for several crnti on real enodeB, but on tdd I frequently got error
ERROR("Error expecting %d symbols but got %d\n", cfg->grant.nof_re, n) from pdsch.c, most of the time on the special subframes 1 and 6. Maybe I'm missing something.
In order to reproduce the error with minimum example I used pdsch_ue for two rnti: p-rnti and c-rnti on same enodeB where I got the error. Crnti correspond to the actually connected to the enodeB phone. The only changes I made in the srsLTE code for this example were in rf_uhd_impl.c to separately set the time source and clock source to external. I used commands
sudo pdsch_ue -a "serial=SEm0001" -f 2325e6 -g 50 -r fffe -G 2 -T 7
sudo pdsch_ue -a "serial=SEm0001" -f 2325e6 -g 50 -r 5f4c -G 2 -T 7
Please find the attached logs.
MIB message was
Tdd special config (sf_config = 2, ss_config = 7) was configured according to sib1 message:
50 50 17 0d 30 09 10 44 1f 15 81 a7 19 02 08 20 45 02 c4 ef 20 00
Driver version is 3.13.0. Version of srsLTE is 20.04.2.
pdsch_ue_logs.tar.gz
Best regards
The text was updated successfully, but these errors were encountered: