-
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
manifest: sdk-nrfxlib: Pull command status check #14326
Conversation
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
All integration tests: null Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
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. |
2bd1b9b
to
d12d4d1
Compare
98a1a9a
to
32a6e21
Compare
53061e5
to
04d2728
Compare
04d2728
to
149f47e
Compare
2f43369
to
a7546c8
Compare
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 27a6a3dee6dc4c850edcd06b6edecb4d14735d1c more detailssdk-nrf:
nrfxlib:
Github labels
List of changed files detected by CI (10)
Outputs:ToolchainVersion: 9583beca34 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
f781adf
to
be3f846
Compare
a3f98ea
to
d9b6495
Compare
d9b6495
to
e49c8a0
Compare
e49c8a0
to
5870178
Compare
5870178
to
44000af
Compare
@ajayparida the Matter failure is caused by the net_mgmt API returning error when requesting for low power mode: I believe the nrfxlib related change refines commands handling between host and RPU, so it looks like a regression to me. Is there any test in WiFi suite that checks the Does application code require alignments after your change? |
Hi, Yes, there is change in nrfxlib. Host passes the commands to rpu and will wait for command status event. In a way host will know, command has been indeed received by rpu and processed. On timeout, in case no event received it will return failure. This way it helps to know that command has been received by fw and processed. There is no separate test suite, we can use existing "shell" sample to set ps on/off("cmd_wifi_ps on/off"). It will invoke net_mgmt(NET_REQUEST_WIFI_PS...) with params.enabled=on/off as being done in your code. No, I don't think application code require alignment. As in case host driver doesn't receive status event, it will return failure . It will be same as currenetly expected at your application for failure of command. It will call "ChipLogError(DeviceLayer, "Set low power mode request failed");" I have also asked UMAC firmware team to check they are giving event status for the commad NRF_WIFI_UMAC_CMD_SET_POWER_SAVE". |
Pull command status check related changes for commands not expecting data from firmware only status event(phase 1 changes). Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
44000af
to
27a6a3d
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.
Due to upmerge issues, the nRF7002 testing on Matter over WiFI is disabled on integration, however we found regression on that PR (current state).
After disabling the nRF7002DK in Matter testing the Integration tests will be green, however it does not mean that the regression has been fixed. Please contact me if the issue will be fixed, I can verify it on desk and give result.
This pull request has been marked as stale because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 7 days. Note, that you can always re-open a closed pull request at any time. |
Pull command status check phase1 changes.