Custom cpunet application

[jbreal]

In all the bluetooth samples for the nrf5340, whenever the configuration is set to the cpuapp board, a child image automagically built from the "hci_ipc" sample. What do I need to do in order to customize the network cpu application? For example, if I want to use MPSL to switch between a custom radio protocol and bluetooth, I would need to modify the hci_ipc child image. What exactly cause the hci_ipc project to be included, and how can I change that to say.. hci_ipc_custom?

[dejans]

Hi,

There is general information about Multiprotocol Service Layer (MPSL) available in the documentation. NCS supports coexistence of short-range radio and other radios. Depending on the used RF technology of other radio, different options can be chosen. For changing devicetree and overlay file you can refer to enabling generic three-way coexistence. Overlay file hci_ipc.overlay can be added to the network core child image configuration. If network core child image is built automatically, relevant configs can be changed using child_image\hci_ipc.conf file, as shown in configuration of the child image. Bluetooth HCI driver is included using CONFIG_BT_HCI_IPC configuration option.
When building for nrf5340, there are several other pages which might be relevant for your use case that can be found in the documentation - protocols and use cases (controller and host split), default build configuration and configuration of the child image.

Best regards,
Dejan