NRF5340 Multi-Image example configuration help

[anthony32086]

I am working on a project that is being ported from the nRF52840 to the nRF5340 and the once unified radio and app codebase needs to be split to the app CPU and network CPU.

The problem I am facing is I don't quite understand how to create a multi image project and the examples provided by nrf_connect dont seme to have a multi image example.

All I see are options when selecting the example for app cpu or net cpu which look to configure the device tree  for that CPU but I don't see any for multi image projects.

When reading the documentation for the radio_test example I see that the app CPU needs to be flashed with the empty_app_core project but I would like to include this project as a parent to the radio_test child project.

Is there any examples on how to do this?

[uhrm]

Hi All,

Thanks a lot for all of this.

As zaxkv mentioned, I am also beginner and confused about the available documentation. I am trying to do the same than what Anthony mentioned, this is, replace hci_rpmsg with a custom net core. So, I followed this thread and per Anthony's post above I added the external_child_image.cmake, updated Kconfig.nrf, and added the child image configurations in the application core's proj.conf.

I am using NCS v1.5.1 and SES v5.34a, but whenever I load the project, I still see hci_rpmsg created inside the build directory (even after full clean), so not sure if I am missing something in order for it not to be included in the project. Thoughts?

And the other issue I see is that I am too getting the pm_config.h compile error, even though PARTITION_MANAGER_ENABLED is now in Kconfig whenever CONFIG_BUILD_EXTERNAL_CHILD_IMAGE=y.

Any ideas?

Thanks again!

Peter U

[anthony32086]

as Zaxkv pointed out, I forgot to mention that

 include(cmake/external_child_image.cmake) 

needs to be added to ncs/nrf/CMakeList.txt so make sure you have that too.

hci_rpmsg is included here whenever you build with CONFIG_BT_RPMSG_NRF53=y which is set when you use CONFIG_BT=y

if you are getting pm_config.h missing it is because you are trying to build the child image from the context of your project and not the ncs root directory so header includes are missing.

The build sequence from what observe is as follows.

- generate Kconfig autoconf.h headers from all ncs Kconfigs and prj.conf
- build zephyr kernel
- build child images
- enter project directory <--- no child images can be built after here due to ncs root path context being lost
- build project app image
- merge child images into final image

Therefore all child images MUST be built before the project directory is entered, my above solution is a variable child image injection to allow the ncs context to build a child image specified by the app. since Kconfig files and prj.conf are parsed first, an external child image can be injected into the ncs build sequence prior to the app project being built.

Make sure you are building all child images before your app is built by checking the build logs. the following text should be present when building with west in the terminal output in the following sequence,

"=== child image <CHILD IMAGE NAME> - <CPU DOMAIN> begin ==="

*child image is built*

"=== child image <CHILD IMAGE NAME> - <CPU DOMAIN> end ==="

"libmetal version: <PROJECT_VERSION> <CMAKE_SOURCE_DIR>"

where CMAKE_SOURCE_DIR is the path to your app project.

[uhrm]

Similar to what Anthony suggested, I have this build sequence:

- Zephyr kernel

- mcuboot

- hci_rpmsg

- my_net_core image -> This is where the build stops

- Everything else

I have been playing around with the build order and still have the same issue with pm_config.h, not sure what else I have to do.

I am wondering if this is related to this other issue with mcuboot, which is still not solved yet: devzone.nordicsemi.com/.../nrf5340-mcuboot-build-pm_config-h-not-found

[anthony32086]

I do not use mcuboot so I do not know how it might affect the build sequence.

You could try removing mcuboot.. Also I have not tried including both hci_rpmsg and a custom net core image either. If you are trying to use Bluetooth + a custom netcore image that might be a source of problems.

You might want to open a separate issue so the developers at Nordic can provide better support.  

[uhrm]

Got it now, the net core we are using is basically a copy of the the hci_rpmsg, the only difference is that it is out of the SDK folder structure (I will call that net_core).

So what I did was to just remove hci_rpmsg from the parent image build since the net_core provides the same features as they are the same. To do this I added the line below to the parent config file:

CONFIG_HCI_RPMSG_BUILD_STRATEGY_SKIP_BUILD=y

With that, the build completes successfully and now I have our net_core as a child image.

Thanks a lot for all the information in this thread!