KRKNWK-19540: Update childimage build documentation for fem and wifi_coex

Add sysbuild build system information
Use ipc_radio child image as default configuration

Signed-off-by: Dawid Przybylo <[email protected]>

Author: dawidprzybylo

doc/nrf/app_dev/device_guides/fem/21540ek_dev_guide.rst

@@ -52,14 +52,20 @@ For example:
 .. parsed-literal::
    :class: highlight
 
-   west build -b nrf5340dk/nrf5340/cpuapp -- -DSHIELD=nrf21540ek_fwd -Dmultiprotocol_rpmsg_SHIELD=nrf21540ek
+   west build -b nrf5340dk/nrf5340/cpuapp -- -DSHIELD=nrf21540ek_fwd -Dipc_radio_SHIELD=nrf21540ek
 
-In this command, the *childImageName_* parameter has the ``multiprotocol_rpmsg_`` value and builds a multiprotocol application with support for 802.15.4 and Bluetooth.
-The *childImageName_* parameter can take the following values:
+In this command, the *childImageName_* parameter has the ``ipc_radio_`` value as default and builds the application with support for the combination of 802.15.4 and Bluetooth.
+The ``ipc_radio`` has been used since the build system migration to sysbuild.
+See :ref:`Migrating to sysbuild <child_parent_to_sysbuild_migration>` page.
+Setting the correct sysbuild option enables support for 802.15.4 and Bluetooth :ref:`ipc_radio`.
+
+``ipc_radio`` represents all applications with support for the combination of both 802.15.4 and Bluetooth.
+You can configure your application using the following sysbuild configurations:
+
+* ``SB_CONFIG_NETCORE_IPC_RADIO=y`` for applications having support for 802.15.4, but not for Bluetooth.
+* ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for application having support for Bluetooth, but not for 802.15.4.
+* ``SB_CONFIG_NETCORE_IPC_RADIO=y`` and ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
 
-*  ``multiprotocol_rpmsg_`` for multiprotocol applications with support for 802.15.4 and Bluetooth
-*  ``802154_rpmsg_`` for applications with support for 802.15.4, but without support for Bluetooth
-*  ``hci_ipc_`` for application with support for Bluetooth, but without support for 802.15.4
 
 .. note::
    On nRF53 devices, ``SPIM0`` and ``UARTE0`` are mutually exclusive AHB bus masters on the network core as described in the `Product Specification <nRF5340 Product Specification_>`_, Section 6.4.3.1, Table 22.

doc/nrf/app_dev/device_guides/fem/fem_nrf21540_gpio.rst

@@ -51,14 +51,18 @@ To use nRF21540 in GPIO mode, complete the following steps:
 
    The state of the remaining control pins should be set in other ways and according to `nRF21540 Product Specification`_.
 
-#. On nRF53 devices, you must also apply the same devicetree node mentioned in step 1 to the network core.
-   To do so, apply the overlay to the correct network core child image by creating an overlay file named :file:`child_image/*childImageName*.overlay` in your application directory, for example :file:`child_image/multiprotocol_rpmsg.overlay`.
+#. On nRF53 devices, you must also apply the same devicetree node mentioned in **Step 1** to the network core  using sysbuild.
+   To apply the overlay to the correct network core child image, create an overlay file named :file:`sysbuild/*childImageName*/boards/nrf5340dk_nrf5340_cpunet.overlay` in your application directory, for example :file:`sysbuild/ipc_radio/boards/nrf5340dk_nrf5340_cpunet.overlay`.
+   For more information, see the :ref:`Migrating to sysbuild <child_parent_to_sysbuild_migration>` page.
 
-   The ``*childImageName*`` string must be one of the following values:
+   The *childImageName* default value is set to ``ipc_radio``:
 
-   *  ``multiprotocol_rpmsg`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
-   *  ``802154_rpmsg`` for applications having support for 802.15.4, but not for Bluetooth.
-   *  ``hci_ipc`` for application having support for Bluetooth, but not for 802.15.4.
+   ``ipc_radio`` represents all applications with support for the combination of both 802.15.4 and Bluetooth.
+   You can configure your application using the following sysbuild configurations:
+
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` for applications having support for 802.15.4, but not for Bluetooth.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for application having support for Bluetooth, but not for 802.15.4.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` and ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.SB_CONFIG_NETCORE_IPC_RADIO=y`` and ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
 
    .. note::
        This step is not needed when testing with :ref:`direct_test_mode` and :ref:`radio_test` on the nRF53 Series devices.

doc/nrf/app_dev/device_guides/fem/fem_simple_gpio.rst

@@ -50,15 +50,19 @@ To use the Simple GPIO implementation of FEM with SKY66112-11, complete the foll
 
    The state of the other control pins should be set according to the SKY66112-11 documentation.
    See the official `SKY66112-11 page`_ for more information.
-#. On nRF53 devices, you must also apply the same devicetree node to the network core.
 
-   Create a devicetree overlay file with the same information as you used in Steps 1 to 3.
-   To apply the overlay to the correct network core child image, create the file in the :file:`child image` directory of your application directory, and name it :file:`*childImageName*.overlay`, for example :file:`child_image/multiprotocol_rpmsg.overlay`.
-   The ``*childImageName*`` string must be one of the following values:
+#. On nRF53 devices, you must also apply the same devicetree node mentioned in **Step 1** to the network core using sysbuild.
+   To apply the overlay to the correct network core child image, create an overlay file named :file:`sysbuild/*childImageName*/boards/nrf5340dk_nrf5340_cpunet.overlay` in your application directory, for example :file:`sysbuild/ipc_radio/boards/nrf5340dk_nrf5340_cpunet.overlay`.
+   For more information, see the :ref:`Migrating to sysbuild <child_parent_to_sysbuild_migration>` page.
 
-   *  ``multiprotocol_rpmsg`` for multiprotocol applications with support for 802.15.4 and Bluetooth.
-   *  ``802154_rpmsg`` for applications with support for 802.15.4, but without support for Bluetooth.
-   *  ``hci_ipc`` for applications with support for Bluetooth, but without support for 802.15.4.
+   The *childImageName* default value is set to ``ipc_radio``:
+
+   ``ipc_radio`` represents all applications with support for the combination of both 802.15.4 and Bluetooth.
+   You can configure your application using the following sysbuild configurations:
+
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` for applications having support for 802.15.4, but not for Bluetooth.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for application having support for Bluetooth, but not for 802.15.4.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` and ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
 
    .. note::
        This step is not needed when testing with the :ref:`direct_test_mode` or :ref:`radio_test` samples on nRF53 Series devices.

doc/nrf/app_dev/device_guides/wifi_coex.rst

@@ -128,14 +128,17 @@ To enable Wi-Fi coexistence on the nRF70 Series device, complete the following s
    The first element ``&gpio0`` indicates the GPIO port (``port 0`` has been selected in the example shown).
    The second element is the pin number on that port.
 
-#. On the nRF5340, apply the same devicetree node mentioned in Step 1 to the network core.
-   Apply the overlay to the correct network-core child image by creating an overlay file named :file:`child_image/*childImageName*.overlay` in your application directory, for example :file:`child_image/multiprotocol_rpmsg.overlay`.
+#. On the nRF5340, you must also apply the same devicetree node mentioned in step 1 to the network core using sysbuild build system. For more information, see the :ref:`Migrating to sysbuild <child_parent_to_sysbuild_migration>` page.
+   To do so, apply the overlay to the correct network core child image by creating an overlay file named :file:`sysbuild/*childImageName*/boards/nrf5340dk_nrf5340_cpunet.overlay.overlay` in your application directory, for example :file:`sysbuild/ipc_radio/boards/nrf5340dk_nrf5340_cpunet.overlay`.
 
-   The ``*childImageName*`` string must assume one of the following values:
+   The ``*childImageName*`` default value is set to ``ipc_radio`` :ref:`ipc_radio`.
 
-   *  ``multiprotocol_rpmsg`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
-   *  ``802154_rpmsg`` for applications having support for 802.15.4, but not for Bluetooth.
-   *  ``hci_ipc`` for application having support for Bluetooth, but not for 802.15.4.
+   ``ipc_radio`` represents all applications with support for the combination of both 802.15.4 and Bluetooth.
+   You can configure your application using the following sysbuild configurations:
+
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` for applications having support for 802.15.4, but not for Bluetooth.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for application having support for Bluetooth, but not for 802.15.4.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` and ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
 
 #. Enable the following Kconfig options:
 
@@ -206,14 +209,18 @@ To enable the generic three-wire coexistence, do the following:
    The first element ``&gpio0`` indicates the GPIO port (``port 0`` has been selected in the example shown).
    The second element is the pin number on that port.
 
-#. On the nRF5340, apply the same devicetree node mentioned in Step 1 to the network core.
-   Apply the overlay to the correct network-core child image by creating an overlay file named :file:`child_image/*childImageName*.overlay` in your application directory, for example :file:`child_image/multiprotocol_rpmsg.overlay`.
+#. On nRF53 devices, you must also apply the same devicetree node mentioned in **Step 1** to the network core using sysbuild.
+   To apply the overlay to the correct network core child image, create an overlay file named :file:`sysbuild/*childImageName*/boards/nrf5340dk_nrf5340_cpunet.overlay` in your application directory, for example :file:`sysbuild/ipc_radio/boards/nrf5340dk_nrf5340_cpunet.overlay`.
+   For more information, see the :ref:`Migrating to sysbuild <child_parent_to_sysbuild_migration>` page.
+
+   The *childImageName* default value is set to ``ipc_radio``:
 
-   The ``*childImageName*`` string must assume one of the following values:
+   ``ipc_radio`` represents all applications with support for the combination of both 802.15.4 and Bluetooth.
+   You can configure your application using the following sysbuild configurations:
 
-   * ``multiprotocol_rpmsg`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
-   * ``802154_rpmsg`` for applications having support for 802.15.4, but not for Bluetooth.
-   * ``hci_ipc`` for application having support for Bluetooth, but not for 802.15.4.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` for applications having support for 802.15.4, but not for Bluetooth.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for application having support for Bluetooth, but not for 802.15.4.
+   * ``SB_CONFIG_NETCORE_IPC_RADIO=y`` and ``SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y`` for multiprotocol applications having support for both 802.15.4 and Bluetooth.
 
 #. Enable the following Kconfig options: