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

[dev_j]

Thank you Kazi Afroza Sultana , I was able to build the IPC sample, but I am trying to produce remote_core_app_to_sign.bin or net_core_app_to_sign.bin and remote_core_app_update.bin/net_core_app_update.bin. I used the remote/zephyr/zephyr.bin and it did not work. I need a binary file to update the network core firmware. Thank you again.

[dev_j]

I wanted to clarify that I need help producing an updatable binary via DFU from the child image module (remote). The dfu_application.zip folder only has app_update.bin. When I manually sign the build/remote/zephyr/zephyr.bin with the same key, this does not work to update the firmware. Please help. Using ncs2.6.1 and can't upgrade for now.