You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `multiprotocol_rpmsg` sample for the nrf5340 is removed.
The functionality is taken over by the `ipc_radio` application.
Signed-off-by: Andrzej Kuros <[email protected]>
||||| for Bluetooth, ``SB_CONFIG_NETCORE_IPC_RADIO_BT_RPC`` enables nRF RPC serialization for Bluetooth, or |
@@ -34,7 +32,7 @@ The default for Thingy:53 is the :ref:`nrf5340_empty_net_core` sample applicatio
34
32
The default for other nRF53 devices is having no image added to the build.
35
33
36
34
When configuring an application, such as :zephyr:code-sample:`ble_peripheral_hr`, you must configure it with a supported network core image to ensure proper functionality.
37
-
For basic Bluetooth samples, you can use :zephyr:code-sample:`bluetooth_hci_ipc`, :ref:`multiprotocol-rpmsg-sample`, or :ref:`ipc_radio` (one of the :ref:`companion components <companion_components>`).
35
+
For basic Bluetooth samples, you can use :zephyr:code-sample:`bluetooth_hci_ipc`, or :ref:`ipc_radio` (one of the :ref:`companion components <companion_components>`).
38
36
Use one of the following command patterns to build a sample with the :zephyr:code-sample:`bluetooth_hci_ipc` network image selected (with the relevant *board_target*, path to your application *app_dir*, and path to Zephyr's shared sysbuild directory *<path_to_zephyr>/share/sysbuild*):
Copy file name to clipboardExpand all lines: doc/nrf/app_dev/device_guides/nrf53/building_nrf53.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ To program the nRF5340 DK from the command line, use either west (which uses nrf
98
98
* :file:`rpc_host`
99
99
* :file:`hci_rpsmg`
100
100
* :file:`802154_rpmsg`
101
-
* :file:`multiprotocol_rpmsg`
101
+
* :file:`ipc_radio`
102
102
103
103
#. Navigate to the build folder of the application sample and run the following command to erase the flash memory of the application core and program the application sample:
Copy file name to clipboardExpand all lines: doc/nrf/app_dev/device_guides/nrf53/features_nrf53.rst
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -215,7 +215,7 @@ Multiprotocol support for the nRF5340 DK
215
215
216
216
* - Network core
217
217
- Application core
218
-
* - :ref:`multiprotocol-rpmsg-sample`
218
+
* - :ref:`ipc_radio`
219
219
- | :ref:`Thread samples <openthread_samples>`
220
220
|:ref:`Zigbee samples <zigbee_samples>`
221
221
@@ -227,10 +227,8 @@ When using Thread or Zigbee in parallel with Bluetooth LE, run the low-level rad
227
227
228
228
Bluetooth LE and IEEE 802.15.4 multiprotocol architecture in multicore SoC
229
229
230
-
For the network core, the |NCS| provides the :ref:`multiprotocol-rpmsg-sample` sample.
231
-
It is a combination of the :zephyr:code-sample:`bluetooth_hci_ipc` sample (for Bluetooth LE) and the :zephyr:code-sample:`nrf_ieee802154_rpmsg` sample (for IEEE 802.15.4).
232
-
This means that it enables both the Bluetooth LE Controller and the nRF IEEE 802.15.4 radio driver and simultaneously exposes the functionality of both stacks to the application core using the `RPMsg Messaging Protocol`_.
233
-
Separate RPMsg endpoints are used to obtain independent inter-core connections for each stack.
230
+
For the network core, the |NCS| provides the :ref:`ipc_radio`.
231
+
The :ref:`ipc_radio` enables both the Bluetooth LE Controller and the nRF IEEE 802.15.4 radio driver and simultaneously exposes the functionality of both stacks to the application.
234
232
235
233
For the application core, the |NCS| provides a series of samples for the :ref:`Thread <ug_thread>` and :ref:`Zigbee <ug_zigbee>` protocols.
Copy file name to clipboardExpand all lines: doc/nrf/protocols/matter/getting_started/transmission_power.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,7 +158,7 @@ You can do this by either editing the :file:`prj.conf` file or building the samp
158
158
The parameter name varies depending on the devices you are building for.
159
159
For example:
160
160
161
-
* If you want to build for Thread devices for the ``nrf5340dk/nrf5340/cpuapp`` board target with a Bluetooth LE TX power equal to 3 dBm, add ``-Dmultiprotocol_rpmsg_CONFIG_BT_CTLR_TX_PWR_PLUS_3=y`` as the CMake argument.
161
+
* If you want to build for Thread devices for the ``nrf5340dk/nrf5340/cpuapp`` board target with a Bluetooth LE TX power equal to 3 dBm, add ``-Dipc_radio_CONFIG_BT_CTLR_TX_PWR_PLUS_3=y`` as the CMake argument.
162
162
* If you want to build for Wi-Fi® devices for the ``nrf7002dk/nrf5340/cpuapp`` board target with a Bluetooth LE TX power equal to 3 dBm, add ``-Dhci_ipc_CONFIG_BT_CTLR_TX_PWR_PLUS_3=y`` as the CMake argument.
163
163
164
164
See `nRF Connect for VS Code extension pack <How to work with build configurations_>`_ documentation for more information.
@@ -174,7 +174,7 @@ You can do this by either editing the :file:`prj.conf` file or building the samp
174
174
175
175
.. code-block:: console
176
176
177
-
west build -b nrf5340dk/nrf5340/cpuapp -- -Dmultiprotocol_rpmsg_CONFIG_BT_CTLR_TX_PWR_PLUS_3=y
177
+
west build -b nrf5340dk/nrf5340/cpuapp -- -Dipc_radio_CONFIG_BT_CTLR_TX_PWR_PLUS_3=y
178
178
179
179
* If you want to build for Wi-Fi® devices for the ``nrf7002dk/nrf5340/cpuapp`` board target with a Bluetooth LE TX power equal to 3 dBm, run the following command:
0 commit comments