nrf5340kd CPUNET For Custom Child Image

[dev_j]

Hello,

In ncs, I am working with \nrf\samples\ipc\ipc_service. I want MCUboot to build \nrf\samples\ipc\ipc_service\remote to run on nrf5340 CPUNET. When I CONFIG_BOARD_ENABLE_CPUNET=y, I see the child image empty_net_core - CPUNET instead of the ipc_service\remote. When I remove CONFIG_BOARD_ENABLE_CPUNET, I the project builds and produces merged_remote.hex, zephyr.hex and zephyr.bin in build\remote\zephyr, but when I flash them to the CPUNET, I get "ERROR: The file specified is not a valid hex file, has data outside valid areas
ERROR: or does not have data in valid areas." How can I have remote\ built to run on CPUNET, and produce remote_core_app_to_update.bin, remote_core_app_update.bin in \ipc_service\build\zephyr?

Thank you

[Kazi Afroza Sultana]

Hello,

The ipc_service sample builds both APP and NET core images by default (without sysbuild or CONFIG_BOARD_ENABLE_CPUNET).

After building the program using this command from the remote folder west build -b nrf5340dk_nrf5340_cpunet ,

Can you try to run the zephyr.hex file from build folder of your remote folder using nrfutil from the build directory?

nrfutil device program --firmware zephyr.hex --options chip_erase_mode=ERASE_ALL --core Network