Read network core app version from app core (nRF5340, v2.6.1) to confirm successful update

[responsible_duck]

Hello,

We tried using pcd_network_core_app_version() to read the network core version (presumably set by CONFIG_FW_INFO_FIRMWARE_VERSION in our hci_ipc.conf) from the app core. To do this, we set the following flags to the app core prj.conf:

CONFIG_PCD=y
CONFIG_PCD_APP=y
CONFIG_FW_INFO=y
CONFIG_PCD_READ_NETCORE_APP_VERSION=y

However, we got a build error: "/opt/nordic/ncs/v2.6.1/zephyr/subsys/dfu/boot/mcuboot.c:23:10: fatal error: zephyr/fw_info.h: No such file or directory" 

Went in mcuboot.c and updated the include to: #include <fw_info.h>. Now it builds. But it does not run. 

Is there an example out there of how to do this properly?

Thanks,

Ever

[Hung Bui]

Hi Ever, 

Have you managed to test multiple cores  update for nRF53 ? 
As far as I know the \nrf\modules\mcuboot\hooks nrf53_hooks.c is calling pcd_network_core_app_version() to compare netcore version with pcd_version_cmp_net(). This function is called in loader.c in MCUboot. 

You would need to define 

CONFIG_PCD_APP=y

CONFIG_NRF53_MULTI_IMAGE_UPDATE=y 

CONFIG_PCD_READ_NETCORE_APP_VERSION=y

I'm not so sure why defining <fw_info.h>, but could you try to check what in the loader.c ? 

[responsible_duck]

Hi Hung,

Please ignore the <fw_info.h> detail. This was an accidental include when browsing the source code of 2.6.1.

I updated the description above.

We specifically want to read the firmware net core from the app core. So we added these flags to the app core image prj.conf:

CONFIG_PCD=y
CONFIG_PCD_APP=y
CONFIG_FW_INFO=y
CONFIG_PCD_READ_NETCORE_APP_VERSION=y

Then we tried calling `pcd_network_core_app_version()` from the app core (inspired by the code in loader.c that you mentioned) but it doesn't seem to work. 

We are not supporting CONFIG_NRF53_MULTI_IMAGE_UPDATE=y we want to do non-simultaneous updates only so that we may revert images since this is not supported with simultaneous multi-image updates. 

[Hung Bui]

Hi Ever, 
Could you tell if you have managed to do DFU update for the netcore ? I would need to know if the bootloader on the netcore is working properly. 
The pcd_network_core_app_version() requires the communication between the application on the app core and the bootloader on the netcore. 

I would suggest to take a look at this sample from Amanda: RE: Downgrade protection works only for the app_core -image-and not for the net-core -image 

She managed to make the functions work. Please take a look that she actually need to add CONFIG_PCD_READ_NETCORE_APP_VERSION=y to the hci ipc b0n image: 
-Dhci_ipc_b0n_CONFIG_PCD_READ_NETCORE_APP_VERSION=y

[responsible_duck]

Hi thanks,

I saw the attached example as well as the discussion. Based on this I added the following:

mcuboot.conf:

CONFIG_BOOT_VERSION_CMP_USE_BUILD_NUMBER=y

CONFIG_MCUBOOT_DOWNGRADE_PREVENTION=y

CONFIG_FW_INFO=y

CONFIG_PCD_APP=y

CONFIG_PCD_READ_NETCORE_APP_VERSION=y

CONFIG_BOOT_SWAP_SAVE_ENCTLV=n

in netboot prj.conf:

CONFIG_PCD_READ_NETCORE_APP_VERSION=y

in hci_ipc.conf:

CONFIG_FW_INFO_FIRMWARE_VERSION=5

CONFIG_FW_INFO=y

in main app prj.conf:

CONFIG_PCD=y

CONFIG_PCD_APP=y

CONFIG_FW_INFO=y

CONFIG_PCD_READ_NETCORE_APP_VERSION=y

CONFIG_MCUBOOT_USE_ALL_AVAILABLE_RAM=y

 

It seems we are actually getting stuck in the same code area as the post you linked: "the program hangs  in the "do while" loop  of the function: network_core_pcd_cmdset in the file pcd.c". This happens when trying to begin the image install (moving from image 1 slot 1 to image 1 slot 0). Note that we are not doing simultaneous updates of both net and app core as we do not expect to update interface between them and we don't have a lot of space to hold both combined. One of our requirements is to be able to reverse images upon failure/fault.

 

[responsible_duck]

This is the output right before starting install process:

Images:
image=0 slot=0
version: 0.0.1
bootable: true
flags: active confirmed
hash: 1442099e438cd871d9fc389d9242ffb94f9deafec6565f4bbf1d7846725f1d67


image=1 slot=0
version: 0.0.0
bootable: true
flags: confirmed
hash: Unavailable


image=1 slot=1
version: 0.0.2
bootable: true
flags: pending
hash: 4c384da3fb8c8089d1a9722a042193d71fcf2106963c36a91a1b0a45253e5cda
Split status: N/A (0)