In SDK version 2.9.0, the OTA process fails to retrieve the correct firmware version

[SunHuang]

After completing the OTA update, I executed the "otasoftwareupdaterequestor read-event version-applied" command but was unable to read back the version.

I then tried the "basicinformation read software-version" command and found that the version had not been updated, although the firmware functionality had indeed been updated.

The correct firmware version can also be seen from the "provider". What could be causing this issue?

1524.ota.zip

[Amanda Hsieh]

Hi, 

Both issues are related. The event is generated only if after a reboot the current software version is the same as the version encoded in the header of the OTA image that was to be applied. It seems as if you only updated the version in the OTA image header but not in the firmware itself.

Do you use the VERSION file for the firmware versioning or the CONFIG_CHIP_SOFTWARE_VERSION Kconfig option?

[SunHuang]

Hi,

I "only" use VERSION to control the firmware version. When the device boots up, it prints out CHIP_DEVICE_CONFIG_DEVICE_SOFTWARE_VERSION to verify whether the firmware version has been correctly updated. However, CHIP_DEVICE_CONFIG_DEVICE_SOFTWARE_VERSION has already been updated. So, how should I resolve this issue?

[SunHuang]

Hi

I was notified of this issue by the laboratory during the CSA certification process. The testing environment used by the laboratory also comes from Nordic’s tools. Therefore, I believe it is necessary to use the official CSA environment.

Nonetheless, I still tested the link you provided. Below is the error that occurred during pairing.

[SunHuang]

Hi,

Is there any new progress on this issue? If there are any updates, please let me know.

[Amanda Hsieh]

Hi, 

Is the TC_SU_2_7 the one that fails? It seems to use this command:

https://github.com/nrfconnect/sdk-connectedhomeip/blob/4c46941ef17b7b755c96c57e4ba42306cc524e1c/src/app/tests/suites/certification/Test_TC_SU_2_7.yaml#L245

Could you enable CONFIG_BOOTLOADER_MCUBOOT to make the image get confirmed by this line?

-Amanda H.

[SunHuang]

Hi,

That's right.

Amanda Hsieh said:

Is the TC_SU_2_7 the one that fails? It seems to use this command:

I did not use the CONFIG_BOOTLOADER_MCUBOOT configuration, but I did use the SB_CONFIG_BOOTLOADER_MCUBOOT configuration.

Amanda Hsieh said:

Could you enable CONFIG_BOOTLOADER_MCUBOOT to make the image get confirmed by this line?

[Amanda Hsieh]

Since the team cannot reproduce the issue, could you add some logs / debug this path, where the event is generated:

https://github.com/nrfconnect/sdk-connectedhomeip/blob/v2.9.0/src/app/clusters/ota-requestor/ota-requestor-server.cpp#L239

and if the code does not reach the lines, look on previous calls:

https://github.com/nrfconnect/sdk-connectedhomeip/blob/v2.9.0/src/app/clusters/ota-requestor/DefaultOTARequestor.cpp#L586

https://github.com/nrfconnect/sdk-connectedhomeip/blob/v2.9.0/src/app/clusters/ota-requestor/DefaultOTARequestorDriver.cpp#L88