Forum Discussion

thorax58's avatar
thorax58
Icon for New Contributor rankNew Contributor
4 years ago

FlexRAN reference # SCSY-36054 (SIB1 decoding issue)

Is it possible to get the conditions under which SCSY-36054 occurred (error decoding SIB1 when CellId={1,3,5}) in FlexRAN 20.11). I'm having a CRC failure when decoding SIB1 using FlexRAN 21.03 but...
AndrewG_Intel's avatar
AndrewG_Intel
Icon for Occasional Contributor rankOccasional Contributor
4 years ago

Hello thorax58

Thank you for posting on the Intel® communities.

In order to check this further and provide the proper information, could you please confirm the following details?


1- Are you referring to IIntel® FlexRAN reference architecture?

2- Are you developing or integrating 5G network devices?

3- Are you using other Intel® components in regards to this request? For instance, Processors or Wireless cards? Could you please provide the exact model of those components?

4- Could you please elaborate more regarding what you are trying the achieve and the issue that you are having?


Best regards,

Andrew G.

Intel Customer Support Technician


  • thorax58's avatar
    thorax58
    Icon for New Contributor rankNew Contributor
    4 years ago

    Hi Andrew. I'm referring to the Intel FlexRAN Reference Architecture, specifically the Release Notes for version 21.03.1 (639554-2.6.1-flexran-ref-solution-sw-release-note-v21.03.1.pdf). On page 126 there's a known issue in version 20.11 describing a SIB1 decoding error when using CellId={1,3,5} with reference # SCSY-36054.

    I would like to know more details about the conditions under which this error could occur. I did not see this error in 20.11 but am seeing something similar in 21.03, despite it being noted as fixed for 21.03.

    I am working on a 5g device using N3000 cards and am trying to do a UE attach. This works under 20.11 whereas I haven't got it to work under 21.03 yet.

    At this stage I'm just doing my own due diligence and would like to know more details about SCSY-36054 to see if it's relevant to my situation. If it's not, I will pursue the regular support channels.

    Thanks.