NCS 2.2 custom net child image

[Hiihtaja]

Hello !

I have used multicore sample as base and add to it own network image and b0n bootloader ( as child to network image).

And net_core_app_update.bin is not build.

Looks like it is known issue and might be fixed in ncs 2.2 release or some patch is available some where.

Similar problems : 

 NCS 2.0 custom child image + mcuboot build

 NCS 2.1.0 custom child image + mcuboot build 

 NRF5340 multicore image dfu package not have net core binary 

Could it be possible to have some workaround about it ?

In our case we have custom radio image and muiltiimage type of build is expected as natural environment where app and network corea image + 2 bootloaders are build in one shot.

Regards,

Eugene

[Hieu]

Hi Eugene,

Just want to let you know that I am talking with our internal engineers.

We have determined that simultaneous update of both the application core and the network core is possible in the sense that you can upload both the new image of application core and of network core back-to-back, and only have to reset once.
Other than that, uploading in a single command such as using the DFU zip package is not possible.

We also found that currently, after uploading the new network core image, you need to give the device one or two minutes so that it can correctly move the image from the shared RAM to the network core flash. Only after that is completed should you trigger the reset, which will set the new network core image as active.

Using slot 3 to upgrade network core (with the mcumgr argument -n 3) doesn't seem right. I will double check my understanding with my colleagues a bit further and return in a bit.

Regards,

Hieu

[Hiihtaja]

Hi Hieu !

Thank you !

Yes, please clarify direct  serial recovery in case of both cores.

Regards,

Eugene

[Hieu]

Hi Eugene,

Turns out my contact is tied up with some other obligations, while reaching a certain answer will take time. Our situation remains that it is likely a bug.

To recap, here is the how serial recovery can be done in the current NCS v2.2.0:

- To update the app core, use mcumgr upload with arguments "-e -n 1"
- To update the net core, use mcumgr upload with argments "-e -n 3"
- After net core image is uploaded, please wait 1-2 minutes for the image to be transferred from shared RAM to net core flash area
- It is possible to do both the above back-to-back, then reset only once, and have both cores updated
- It is not possible to use the build/zephyr/dfu_application.zip file to update both core at the same time

If you would like to be informed, I can keep this ticket open and update you every 1-2 week. Would you like that?

I'm sorry we could not reach a conclusion right away.

Best regards,

Hieu

[Hiihtaja]

Hi Hieu !

No problem to wait.

But how I can track progress of update of netcore image after transfering ?

Or I need just  to wait and after that initiate HW reset ?

What kind of partition enumeration in case of CONFIG_SINGLE_APPLICATION_SLOT=y ?

1 and 2 ?

Regards,

Eugene

[Hieu]

Hi Eugene,

Hiihtaja said:

But how I can track progress of update of netcore image after transfering ?

Or I need just  to wait and after that initiate HW reset ?

Unfortunately, there is no tracking interface at the moment, you will have to wait and then trigger reset.

On the other hand, I was informed that in future version, they intend to shift the transfer to happen after reset, not before.

Hiihtaja said:

What kind of partition enumeration in case of CONFIG_SINGLE_APPLICATION_SLOT=y ?

1 and 2 ?

CONFIG_SINGLE_APPLICATION_SLOT doesn't work with multi-image build at the moment. Did you get it to work somehow?

Best regards,

Hieu