-
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
samples: applications: Use ipc_radio as default radio firmware. #15435
Conversation
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
9688e7a
to
2985a57
Compare
samples/matter/lock/sysbuild/ipc_radio/boards/nrf7002dk_nrf5340_cpuapp nrf7001.conf
Outdated
Show resolved
Hide resolved
2985a57
to
441ecc9
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.
Thanks!
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.
Thank you! 👍
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. |
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.
Approving the Fast Pair part
samples/openthread/cli/README.rst
Outdated
@@ -105,7 +105,7 @@ The following snippets are available: | |||
Not compatible with the ``tcat`` snippet. | |||
|
|||
.. note:: | |||
When building with the ``multiprotocol`` snippet for the ``nrf5340dk/nrf5340/cpuapp`` build target, the :kconfig:option:`SB_CONFIG_NETCORE_MULTIPROTOCOL_RPMSG` Kconfig option has to be set to ``y``. | |||
When building with the ``multiprotocol`` snippet for the ``nrf5340dk/nrf5340/cpuapp`` board target, set the :makevar:`FILE_SUFFIX` CMake variable to ``ble``. |
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.
When building with the ``multiprotocol`` snippet for the ``nrf5340dk/nrf5340/cpuapp`` board target, set the :makevar:`FILE_SUFFIX` CMake variable to ``ble``. | |
When building with the ``multiprotocol`` snippet for the ``nrf5340dk/nrf5340/cpuapp`` board target, set the :makevar:`FILE_SUFFIX` CMake option to ``ble``. | |
See :ref:`app_build_file_suffixes` and :ref:`cmake_options` for more information. |
@@ -129,7 +129,7 @@ The following snippets are available: | |||
* ``multiprotocol_ble`` - Enables the Multiprotocol Bluetooth LE extension. | |||
|
|||
.. note:: | |||
When building with ``multiprotocol_ble`` snippet, for the ``nrf5340dk/nrf5340/cpuapp`` build target, additional :kconfig:option:`SB_CONFIG_NETCORE_MULTIPROTOCOL_RPMSG` option has to be set. | |||
When building with the ``multiprotocol_ble`` snippet for the ``nrf5340dk/nrf5340/cpuapp`` board target, set the additional :makevar:`FILE_SUFFIX` CMake variable to ``ble``. |
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.
When building with the ``multiprotocol_ble`` snippet for the ``nrf5340dk/nrf5340/cpuapp`` board target, set the additional :makevar:`FILE_SUFFIX` CMake variable to ``ble``. | |
When building with the ``multiprotocol_ble`` snippet for the ``nrf5340dk/nrf5340/cpuapp`` board target, set the additional :makevar:`FILE_SUFFIX` CMake option to ``ble``. | |
See :ref:`app_build_file_suffixes` and :ref:`cmake_options` for more information. |
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.
certification.rst
for Thread protocol should be modified as well in two places:
https://github.com/nrfconnect/sdk-nrf/blob/main/doc/nrf/protocols/thread/certification.rst?plain=1#L70
82d1054
to
ee0f1bf
Compare
ee0f1bf
to
f0c8a48
Compare
f0c8a48
to
54b9d87
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.
I don't like the current approach. Earlier we had an abstraction of having NRF_DEFAULT_BLUETOOTH
option - sample was declaring that it wants to have Bluetooth. Now we have samples that enables NRF_DEFAULT_IPC_RADIO
also for targets with one core which looks odd. Maybe we could just change defaults in choice NETCORE
in sysbuild/Kconfig.netcore
so that NETCORE
would default to NETCORE_IPC_RADIO
if NRF_DEFAULT_BLUETOOTH
is enabled and we could introduce the NRF_DEFAULT_HCI_IPC
option that would default the NETCORE
to NETCORE_HCI_IPC
(NRF_DEFAULT_HCI_IPC
would be doing what NRF_DEAFULT_BLUETOOTH
is doing now).
The current approach has merit, because it explicitly states which application is used. |
Enabling |
54b9d87
to
65f50c0
Compare
None of the network core images specified in sdk-nrf/sysbuild/Kconfig.netcore Line 66 in e5e367d
|
65f50c0
to
7213c2e
Compare
Use ipc_radio as default radio firmware over: -hci_ipc -multiprotocol_rpmsg -802154_rpmsg Jira: NCSDK-27179 Co-authored-by: Kamil Gawor <[email protected]> Signed-off-by: Dominik Chat <[email protected]>
The |
7213c2e
to
ed37217
Compare
Use ipc_radio as default radio firmware.
test_audio: PR-259
test_chip: PR-760
test_thread: PR-1172