Hello,
We're about to start a new project with the nrf5340 as our SoC.
When reading the docs for the nrf5340 (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html#protocols-and-use-cases)
it says:
When using Bluetooth
Low Energy on the nRF5340, you have two options:
* Split the Bluetooth LE Controller and the host part of the Bluetooth LE stack and run them on different cores.
* Run the full Bluetooth LE stack on the network core (currently supported for development only).
We're just starting up the project and it is indeed a BLE project.
The current line of thinking was to use the net MCU to manage all the BLE and have the app MCU to handle drivers and data management. Between the two mcus we were going to implement some endpoints with the RPmsg service.To future clarify: the net mcu should manage all ble and the appcpu should be oblivious to the fact that it is communicating over BLE.
is this a poor decision in your view?
The main reason we would opt for this split is due to better testing of the main app. The net mcu should just manage the BLE, connection establishment etc. not any particular logic inherent to the app.We've seen that there is code which makes it possible to FOTA both app and net MCU. Is this possible if we do the split described above or is it just when using the net MCU as a BLE controller?
If it is best to keep the net MCU as a controller instead of what I've just described, why is that? What is the benefits?
Hope I've asked the correct questions here, thanks in advance!
Best regards,
