-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
doc: update known issues for NCS v2.5.0 #12657
Conversation
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
This same template seem to be copied again. So I can check LwM2M related issues, but not Zephyr in general. |
@divipillai CIA-890 is resolved for this release. |
For Audio: Following issues has been fixed since last tag: OCT-2558 and OCT-2587 and should not be tagged with v2-5-0 |
b1e42d3
to
992ac1a
Compare
992ac1a
to
499fa69
Compare
499fa69
to
c0faf1e
Compare
My bad, I copied the old template. Update the description and commit message. Thanks! |
c0faf1e
to
555cdd7
Compare
Sorry, I missed the
|
One of them does not work here any more and the other is on holiday and not the right person, this should be assigned to the person that did the last zephyr upmerge, @de-nordic |
@divipillai: We have two new known issues, should those be added separately, or should I create PR against this? |
You can let me know here. I can add those in this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes requested
555cdd7
to
fa68acd
Compare
72755ae
to
5c61e9a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add another Known issue:
Mcuboot: If Fault Injection hardening (FIH)is enabled the bug in boot_image_check_hook() manifesting so multicore application can't be booted. nRF5340 mcuboot builds witch simultaneous multimage update enabled. Workaround are: disable FIH or patch #12846.
tracking: NCSDK-24203
@@ -1648,6 +1861,27 @@ OCX-189: When inputting -40 dBm to HCI_OPCODE_VS_SET_CONN_TX_PWR (0x3F6), the ac | |||
The TX power for a connection cannot be less than -20 dBm. | |||
Controller still output -20 dBm if the setting is -40 dBm. | |||
|
|||
.. rst-class:: v2-5-0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discovered last minute that OCX-188 has re-occurred, so we need to add v2-5-0 to the rst-class on this one.
We have also created a new OCX ticket (OCX-227), since OCX-188 was fixed, but then it broke again.
Is it possible to write it like this?:
OCX-184/OCX-227: If 0 dBm TX power is selected, the FEM/PA TX/RX pins do not toggle correctly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will add them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Please check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@divipillai Bah, I wrote my suggestion for OCX-184 instead of OCX-188, sorry
Meaning:
- Nothing regarding OCX-184 should be changed
- The text for OCX-188 should be: OCX-188/OCX-227: The controller reserves some pins (0.28 - 0.31), which may collide with FEM/PA features
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Please check.
5c61e9a
to
9c55d4e
Compare
@nvlsianpu : Could you check and approve the PR. |
c89240b
to
d506e3c
Compare
Added v2.5.0 tag to known issues. ---- - [ ] Asset Tracker v2 done by @simensrostad - [ ] Serial LTE Modem issue checked by @MarkusLassila - [ ] LTE Sensor Gateway issue checked by @lemrey (NCSDK-20026) - [ ] Low Power UART sample issue on nRF5340 DK by @nordic-krch and @anangl - [ ] Thingy:53 issue checked by @MarekPieta - [ ] Thread issues checked by @bpienk - [ ] Zigbee issues checked by @sebastiandraus - [ ] Matter issues checked by @kkasperczyk-no - [ ] HomeKit issues checked by @annwoj and @mariuszpos - [ ] nRF Desktop, CAF, nRF Machine Learning checked by @MarekPieta - [ ] nRF Audio (including Controller) checked by @rick1082 and @alexsven - [ ] CAF issues checked by @MarekPieta - [ ] NCS modem libraries and Networking libraries issues checked by @simensrostad - [ ] Sidewalk issues checked by @annwoj - [ ] BLE issue checked by @grochu - [ ] BT Mesh issue checked by @Balaklaka - [ ] Build system issue checked by @osaether - [ ] DFU and FOTA issues checked by @osaether - [ ] NFC issues checked by @grochu - [ ] SPM issues checked by @osaether - [ ] Crypto issues checked by @frkv and @joerchan - [ ] MPSL issues checked by @laxiLang - [ ] Radio driver issues checked by @ankuns - [ ] SD Controller issues checked by @laxiLang - [ ] TF-M done by @SebastianBoe - [ ] Radio test sample issue checked by @KAGA164 and @grochu - [ ] nRFxlib Modem library issues checked by @lemrey - [ ] Zephyr issues checked by @de-nordic - [ ] Zephyr LwM2M issues checked by @SeppoTakalo Signed-off-by: divya pillai <[email protected]> doc: doc review doc review Signed-off-by: divya pillai <[email protected]> doc: doc review doc review Signed-off-by: divya pillai <[email protected]>
d506e3c
to
0c00c06
Compare
Added v2.5.0 tag to known issues.