Merge remote-tracking branch 'origin/fix-prach-diff-mu' into integration_2026_w12 (!3935)
[FHI72] Fix long PRACH format The problem was that xran_is_prach_slot() compared if the current slot is the scheduled one. However, this becomes irrelevant if long PRACH format used. Successfully tested end-to-end the PRACH index 7 with TDD DDDDDDDSUU and Benetel v2.0.5.
This commit is contained in:
@@ -61,8 +61,8 @@ We tested the category A radio units listed below.
|
||||
|-----------------|---------------------------------------------|
|
||||
|VVDN LPRU |03-v3.0.5 |
|
||||
|LiteON RU |01.00.08/02.00.03/02.00.10 |
|
||||
|Benetel 650 |RAN650-1v1.0.4-dda1bf5|RAN650-1v1.2.2-2fa04bc|
|
||||
|Benetel 550 |RAN550-1v1.0.4-605a25a|RAN550-1v1.2.2-2fa04bc|
|
||||
|Benetel 650 |RAN650-1v1.0.4-dda1bf5/RAN650-1v1.2.2-2fa04bc/RAN650-1v1.4.2-NM-c48047d|
|
||||
|Benetel 550 |RAN550-1v1.0.4-605a25a/RAN550-1v1.2.2-2fa04bc/RAN550-1v1.4.1-M-25fa970/RAN550-1v2.0.5-M-92a9d2c|
|
||||
|Foxconn RPQN |v3.1.15q.551_rc10 |
|
||||
|
||||
Tested libxran releases:
|
||||
@@ -563,6 +563,15 @@ flexran_prach_workaround=disabled
|
||||
dl_tuning_special_slot=0x13b6
|
||||
```
|
||||
|
||||
In addition, PRACH format 0 is also verified with FW v2.0.5. An example gNB config file can be found at [`gnb.sa.band77.273prb.fhi72.2x2-benetel550-long-prach.conf`](../targets/PROJECTS/GENERIC-NR-5GC/CONF/gnb.sa.band77.273prb.fhi72.2x2-benetel550-long-prach.conf). On the RU side, the following parameters shall be modified:
|
||||
```bash
|
||||
mimo_mode=1_3
|
||||
prach_format=long
|
||||
prach_freq_offset_dynamic=false
|
||||
lf_prach_compression_enable=true
|
||||
lf_prach_slot_id=0
|
||||
```
|
||||
|
||||
#### LITEON
|
||||
|
||||
##### RU configuration
|
||||
|
||||
Reference in New Issue
Block a user