-
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
Don't select zcbor #15776
base: main
Are you sure you want to change the base?
Don't select zcbor #15776
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
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
What's the rationale for this change? All applications based on nRF RPC will have to explicitly enable ZCBOR while this seems like an implementation detail that should be enabled automatically. Edit: ok, I found a description in sdk-nrfxlib PR but still some pitfall examples would be appreciated :) |
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. |
I general no option with prompt should ever use
We can use the same mechanism that I did for SSF where we check for the presence of the devicetree nodes required for the module to be enabled, and then extend the definition of ZCBOR so that it will be
It is currently not possible to add |
When an option depends on another option being set, its definition should use 'depends on' - not 'select'. Using 'select' introduces a two way dependency which makes it impossible to express proper kconfig dependencies in some cases. See 'select pitfalls' chapter in zephyr documentation for details. Enable ZCBOR by default if required IPC nodes are present. Ref: NCSDK-27818 Signed-off-by: Håkon Amundsen <[email protected]>
All interaction with SSF has to be done with canonical encoded ZCBOR. Ref: NCSDK-27818 Signed-off-by: Håkon Amundsen <[email protected]>
Is this for NCS 2.7.0?
…________________________________
From: Jonathan Nilsen ***@***.***>
Sent: Thursday, June 6, 2024 4:48:07 AM
To: nrfconnect/sdk-nrf ***@***.***>
Cc: Skeggs, Pete ***@***.***>; Review requested ***@***.***>
Subject: Re: [nrfconnect/sdk-nrf] Don't select zcbor (PR #15776)
@jonathannilsen approved this pull request.
—
Reply to this email directly, view it on GitHub<#15776 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAC423EXEVF3DPKCOJQUUDDZGBD7PAVCNFSM6AAAAABI4IIBPSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCMBRG4ZDIMRUGE>.
You are receiving this because your review was requested.Message ID: ***@***.***>
|
@@ -5,8 +5,8 @@ | |||
|
|||
menuconfig NRF_CLOUD_COAP | |||
bool "nRF Cloud COAP" | |||
depends on ZCBOR |
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.
in the nrf_cloud_multi_service
sample please add CONFIG_ZCBOR=y
to the .conf files that set CONFIG_NRF_CLOUD_COAP=y
.
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.
Is there some condition in Kconfig or DTS that can let us know that NRF_CLOAD_COAP is enabled? For instance we can add some kconfig fragment so that ZCBOR will have default y
if one of those conditions are met.
if NRF_CLOUD_COAP
config ZCBOR
default y
endif
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.
Maybe so, but personally I'd rather not have ZCBOR intelligently enable itself based on the presence of a downstream dependent library.
I'd rather just have users of NRF_CLOUD_COAP
enable ZCBOR now that it is no longer automatically selected by the library
@@ -90,8 +90,8 @@ endif # NRF_CLOUD_REST | |||
|
|||
menuconfig NRF_CLOUD_FOTA_FULL_MODEM_UPDATE | |||
bool "Enable full modem FOTA updates" | |||
depends on ZCBOR |
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.
in the nrf_cloud_multi_service
, asset_tracker_v2
, and nrf_cloud_rest_fota
samples, please add CONFIG_ZCBOR=y
to the .conf files that set CONFIG_NRF_CLOUD_FOTA_FULL_MODEM_UPDATE=y
.
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.
Related to my comment above, is there some condition we can check that is common for all of these?
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.
NRF_CLOUD_FOTA_FULL_MODEM_UPDATE
and NRF_CLOUD_COAP
would be enabled by the application, so I don't know know of any such condition.
No, we did a simpler approach for 2.7.0 (#15790) but we should get this fixed properly once 2.7.0 is out. |
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 enable ZCBOR in all configuration that use nRF RPC, especially for Bluetooth serialization
No description provided.