Open AndrewOG255 opened 1 year ago
UPDATE:
RRC-ML1 config validate: Validation failed on CSI-RS params
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 config validate: BWP cfg validation
. . .
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 config validate: BWP ID 0 Current CORESET mask 0x1 sspace_mask 0x0000000000000003
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 config validate:After release for BWP ID 0, CORESET mask 0x1, sspace_mask 0x0000000000000003
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 SPS config validate: cc 0, bwp_id: 0, is_bwp_config_sps: 0, RRC OTA cs_rnti_enable: 0, sps_cfg_active_bmask: 0, sps_cfg_rel_bmask: 0, sps_cfg_addmod_bmask: 0
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 config validate:cc_id 0 bwp_id 0 BWP Cfg_mask 0x2|0x1- bwp_cmn_cfg 0x0|0x3, bwp_ded_cfg 0x3|0x0
NR5GML1 nr5g_ml1_rrc_intf.c ???
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 config validate: BWP pdsch ded cfg validation
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 config validate: ch_bw_used 0,ch_offset 0, carr_offset 0, bwp_start: 0, bwp_bw:52, bwp_end: 52, loc_and_bw 14025 for bwp_id 0
NR5GML1 nr5g_ml1_srch_api.c: ???
NR5GML1 nr5g_ml1_srch_csi_rs.c: ???
NR5GML1 nr5g_ml1_srch_csi_rs.c: ???
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 config validate: Validation failed on CSI-RS params
NR5GML1 nr5g_ml1_rrc_intf.c: RRC-ML1 cell group validate: Valid 0
NR5GRRC nr5g_rrc_llcdb.c: LLCDB: RRC API Validation failed: cphy_dedicated_cfg_req
NR5GRRC nr5g_rrc_utils.c: PROF_LOG: Did not find any entry time logged for this function call. Ignore func exit
NR5GRRC nr5g_rrc_llc.c: failed to construct lower layer cmds (validation failure). step1_step2_status(0x1)
. . .
NR5GRRC nr5g_rrc_llc.c: ???
NR5GRRC nr5g_rrc_llc.c: ??? a0="L0: RRC Setup Delay :";a1=3720477028(0xDDC1F964);a2=18254(0x474E);a3=950(0x3B6);
NR5GRRC nr5g_rrc_llc.c: ???
. . .
NR5GRRC nr5g_rrc_llc.c: LLCDB: cfg_reqi processing for proc (3) type (0) failed ! step1_step2_status (1)
NR5GRRC nr5g_rrc_llcdb.c: LLCDB: Revert L2 config in OC_ptr from backup
NR5GRRC nr5g_rrc_llcdb.c: ???
NR5GRRC nr5g_rrc_llcdb.c: LLCDB: NR5G_RRC_CFG_CONN_REL/NR5G_RRC_CFG_ABORT_ML1. Init all cfg_masks, addmod_masks and active_masks
Full UE's log between RRCSetup and RRCSetupComplete: Samsung Galaxy s23+ CSI-RS problem.txt
Hey @AndrewOG255, We are on this issue and will provide a patch shortly. Is it possible for you to switch to the new srsRAN Project? Also, may I ask how you get those logs from the phone?
Thanks
Hi @andrepuschmann,
... configuration files: enb.conf.txt rr.conf.txt sib.conf.txt rb.conf.txt
- our company is interested to purchase srsRAN commercial license and use paid technical support and stack modifications to get the necessary things done if this possible ... how to contact you better?
Hi @AndrewOG255 , I can help with this. Please reach out to info(at)srs.io
Hi @andrepuschmann,
- Thanks for fixing this problem so we can move on
- Yes, we would like to switch to srsRAN Project but for now we have one big impediment here: we need full documentation for all the options of config files for new srsRAN. The "documentation" may look like a commented example of some option that can be used.
- You can get same logs with QXDM5 tool if you know how to configure the logging details level. But we use the other 3rd party tool that is not sold publicly. It just has a bit more convenient GUI but same logs and functionality.
Just a reminder that the configuration file reference documentation for srsRAN Project is already available: https://docs.srsran.com/projects/project/en/latest/user_manuals/source/config_ref.html
@ismagom I will test it soon. Does it have CSI-RS problem fixed?
@ismagom I will test it soon. Does it have CSI-RS problem fixed?
@AndrewOG255 it should, but would be great if you could test it.
I have encountered the same problem. Has this problem been resolved on srsRAN_4G?
@pricalinat There are currently no plans to backport the fixes we made to the srsrRAN_4G repo. We are kindly requesting all 5G-SA users to move to the new repository if possible.
@pricalinat There are currently no plans to backport the fixes we made to the srsrRAN_4G repo. We are kindly requesting all 5G-SA users to move to the new repository if possible.
Thank you for your reply. If you were asked to recommend a suitable COTS UE, which one would you recommend? Because OnePlus 10 Pro is in the recommended list in the document, but this problem still occurs after we buy it. We need a mobile phone that can be adapted to your project.
We'll publish a list of tested phones shortly. But I can assure you that the OnePlus 10 Pro is working with the new code base.
We'll publish a list of tested phones shortly. But I can assure you that the OnePlus 10 Pro is working with the new code base.
Thank you for your response, but during the testing process, I found that my Oneplus 10 Pro cannot even find the network for the new project. In addition, I saw that you are using the Moto 30 Pro on Twitter. Is this phone now compatible? If so, I would consider buying it. Thanks again.
The Moto Edge 30 Pro uses the exact same baseband as the Oneplus 10 Pro. Also the OnePlus 10 Pro has been reported to be working just fine. So the issue you're having with your setup is different.
Hi @andrepuschmann, I have tested srsRAN_Project stack:
@AndrewOG255 I can't find a related issue in the new repo. Please consider to open one. For your tests, could you try to set the pci
in cell_cfg
back to 1
. We've found a regression that shows worse performance with some phone when the PCI is changed. This issue will be fixed in the next release (will come shortly) but it is still present in the current public repo.
Issue Description
Hi all, help needed! I have been trying to complete COTS UE registration procedure (at least until the keys verification step) but I got stuck somewhere between "11 | UE <- NW | Msg4 (PDSCH / CR+RRC Setup) " and "14 | UE -> NW | (PUSCH) RRCSetupComplete+NAS:RegistrationRequest | " according to "SA Initial Attach Sequence" https://www.sharetechnote.com/html/5G/5G_CallProcess_InitialAttach.html
Does any body know what can be a reason? Thanks in advance!
1 | UE <- NW | SSB (PSS,SSS,MIB) | 2 | UE <- NW | PDCCH / CORESET 0 / DCI 1_0 | 3 | UE <- NW | SIB1 | 4 | UE <- NW | PDCCH / DCI 1_0 | 5 | UE <- NW | Other SIBs | 6 | UE -> NW | Msg1 (PRACH/Preamble) | 7 | UE <- NW | (PDCCH / DCI 1_0, RA_RNTI) | 8 | UE <- NW | Msg2 (PDSCH / Random Access Response) | 9 | UE -> NW | Msg3 (RRC Setup Request) | 10 | UE <- NW | (PDCCH / DCI 1_0, T_C_RNTI) | 11 | UE <- NW | Msg4 (PDSCH / CR+RRC Setup) | 12 | UE <- NW | (PDCCH / DCI 0_0 or 0_1, C_RNTI) | 13 | UE -> NW | PUCCH or PUSCH / UCI (HARQ ACK/NACK) | 14 | UE -> NW | (PUSCH) RRCSetupComplete+NAS:RegistrationRequest | . . .
My COTS UE is Samsung Galaxy S23+ with debugging software similar to QXDM so I can see what happens on different levels and subsystems inside the phone. So I can see how far I'm in "SA Initial Attach Sequence"
After some attempts of RRCSetup->RRCSetupComplete I see the following errors in enb.log
I see the following diag messages on the UE side:
[Nr5g][0xB88A]NR5G MAC RACH Attempt [Nr5g][0xB821]NR5G RRC OTA Packet ( rrcSetup ) (step 11) [Nr5g][0xB885]NR5G MAC DCI Info (probably step 12) [Nr5g][0xB89B]NR5G MAC UCI Information (probably step 13)
In enb.log I see:
enb.log.zip