Hi,
I am using NRF5340DK and NCS2.1.0. I am able to have network core source code in my application using multicore (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_multi_image.html).
But I would like to have bin file of custom net core inside zephyr and dfu_package zip file. Please suggest a way to do it.
Hi,
Here are two samples I have made to do DFU for the nRF5340:
https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/nrf5340
Is this the kind of inspiration you are looking for?
Regards,
Sigurd Hellesvik
Thanks for the response.
My question may not be clear. When we build NRF5340, it gets NCS hci_rpmsg sample application as network core.
I would like to get rid of it and so I added multi image build in my application code base which add child image as my own network core applicaiton.
I am able to do it but custom network core application (which is inside application code directory) binary is not available in dfu_package.zip.
So my question is while adding child image, how we can specify binary name and path of child image. Also how we can add it inside zip.
Hi
ErDarshan said:1. Help us to get the issue/ticket link for this issue and plan to fix it.
We have an internal tracker for this issue, but I am not able to share much details from it.
However, it looks like zephyr will add a new way of building multiple images called sysbuild.
This might be the better way to do things, but I do not think we have any samples using it in the nRF Connect SDK yet.
ErDarshan said:2. Please elaborate more about your seconds option
"Sign the net core hex file manually using Imgtool and add it to dfu_application.zip manually."
dfu_application.zip is just an zip-file wil three things:
And the build system will use Imgtool to generate these signed binary from the built hex files.
In that case, I would try to sign with these parameters:
"Fork the nRF Connect SDK to add a netcore image in the same way as for example zephyr/samples/bluetooth/hci_rpmsg is added when CONFIG_BT is set."
The rpmsg samples are handeled uniquely in the build system. See if (CONFIG_NCS_INCLUDE_RPMSG_CHILD_IMAGE).
rpmsg samples are listed in RF5340 Protocols and use cases.
Use git to fork the nRF Connect SDK.
Then change one of these to do what you need the custom netcore application to do.
ErDarshan said:3. Please share the patch link which is provided in devzone.nordicsemi.com/.../ncs-2-0-custom-child-image-mcuboot-build. (Provided links shows diff from main branch and it is about 140 files!!!!) If you can provie patch for SDK 2.1.0, it will be more useful.
Ah, that link seems to have compared the forked repo with the current main 4 months ago. So understandably a lot of files have changed.
I will ask our developer who created the patch about this.
Regards,
Sigurd Hellesvik
Thanks. Waiting for your patch so I can apply it over NCSV2.1.0.
Hi,
I think this is the patch:
https://github.com/hakonfam/fw-nrfconnect-zephyr/commit/970c4323fba917b88361dd57c47dee2f5f2a009a
Does that work for you?
Regards,
Sigurd Hellesvik
Let me try. Have some queries related to patch,
1. Does this work for other project / boards as well where multicore image is not added or using hci_rpmsg sample code.
2. What is the reason that this patch is not merged?
3. What is the plan to merge this patch or solution for this?
Hi,
ErDarshan said:1. Does this work for other project / boards as well where multicore image is not added or using hci_rpmsg sample code.
This patch makes mcuboot build last.
It will force mcuboot to build last for all projects.
ErDarshan said:2. What is the reason that this patch is not merged?
This patch is a workaround of the issue.
Our developers will investigate to find a root issue here before making a real patch.
ErDarshan said:3. What is the plan to merge this patch or solution for this?
I do not know about our timeline for this.
If you want to know about our timeline for different things, you can ask the Nordic sales representative in your region.
Regards,
Sigurd Hellesvik
Hi,
ErDarshan said:1. Does this work for other project / boards as well where multicore image is not added or using hci_rpmsg sample code.
This patch makes mcuboot build last.
It will force mcuboot to build last for all projects.
ErDarshan said:2. What is the reason that this patch is not merged?
This patch is a workaround of the issue.
Our developers will investigate to find a root issue here before making a real patch.
ErDarshan said:3. What is the plan to merge this patch or solution for this?
I do not know about our timeline for this.
If you want to know about our timeline for different things, you can ask the Nordic sales representative in your region.
Regards,
Sigurd Hellesvik
Hi Thanks for the response.
Still for the first question, can you confirm if this workaround will not affect anyother project / board. Here project, I mean firmware without multicore image and board I mean other boards like NRF5240 or NRF5240 Dongle or NRF9160.
Hi,
Sigurd Hellesvik said:This patch makes mcuboot build last.
It will force mcuboot to build last for all projects.
If your project is dependent on child image build order, this might impact the build.
I guess that it should not cause any problems, but I can not know for certain.
Regards,
Sigurd Hellesvik
I've noticed that this is a problem in version 2.1.3 of the SDK as well. The patch works:
https://github.com/hakonfam/fw-nrfconnect-zephyr/commit/970c4323fba917b88361dd57c47dee2f5f2a009a
What are the plans for releasing this patch? Is it fixed in version 2.2.0?
Thanks,
Mike Norton
Hi Mike,
I will query our developers about this, and return when I find out more.
Regards,
Sigurd Hellesvik
The patch you link to will not be included.
It is a hotfix which you can add yourself in needed.
The same issue will be fixed in another way in a future release, related to https://github.com/tejlmand/fw-nrfconnect-zephyr-1/commit/7063995bae0288f01fdc6994a3afe038753eb117
Regards,
Sigurd Hellesvik
