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’m currently unable to reproduce the issue right now, it's consistently able to read back the version successfully. Its status should remain successful if it succeeds once, and if it fails, it should keep failing. Have you already encountered this behavior?

[Amanda Hsieh]

SunHuang said:

Have you already encountered this behavior?

No. 

Does the lab see the correct behavior?

[SunHuang]

Hi

Currently, my environment can read the version, but the lab environment cannot. This is very unreasonable, since both are using the same firmware.

[Amanda Hsieh]

That's strange. Please check all the tool versions between your environment and the lab's environment, such as the version of chiptool /ubuntu, etc. 

[SunHuang]

Hi,

We had considered this issue as well, which is why the lab provided me with an environment. So, when I first opened the discussion thread, I wasn’t able to access the FW version (from the lab environment), but later on, I was suddenly able to access it.

[Amanda Hsieh]

If you are using the same versions of all the tools in your and the lab environment, I have no idea what would cause the issue.