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

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

SunHuang — Thu, 03 Jul 2025 01:47:23 GMT

ATL replied that this issue can be put on hold for now. They're fine with using an alternative command to retrieve the version. Thank you for your assistance!

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

Amanda Hsieh — Tue, 15 Apr 2025 15:56:37 GMT

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.

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

SunHuang — Tue, 15 Apr 2025 09:07:13 GMT

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.

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

Amanda Hsieh — Fri, 11 Apr 2025 21:39:50 GMT

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.

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

SunHuang — Fri, 11 Apr 2025 08:58:50 GMT

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

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

Amanda Hsieh — Tue, 01 Apr 2025 13:30:36 GMT

[quote user="SunHuang"]Have you already encountered this behavior?[/quote]

No.

Does the lab see the correct behavior?

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

SunHuang — Tue, 01 Apr 2025 00:34:10 GMT

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?

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

JONATHAN LL — Fri, 21 Mar 2025 08:01:10 GMT

Are there any more logs that you can provide here to us like Amanda mentioned?

Also I am checking if what you observe is something we have see.

Regards,
Jonathan

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

SunHuang — Tue, 18 Mar 2025 08:48:11 GMT

Hi,

I don’t know how to explain this. However, I have tested it several times, and the result shows that the version can be read. But the lab still responds that the version cannot be read. Could there be an instability factor in this command?

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

Amanda Hsieh — Wed, 12 Mar 2025 14:20:42 GMT

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

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

SunHuang — Mon, 10 Mar 2025 09:15:32 GMT

Hi,

That's right.

[quote userid="77782" url="~/f/nordic-q-a/118679/in-sdk-version-2-9-0-the-ota-process-fails-to-retrieve-the-correct-firmware-version/526377"]Is the TC_SU_2_7 the one that fails? It seems to use this command:[/quote]

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

[quote userid="77782" url="~/f/nordic-q-a/118679/in-sdk-version-2-9-0-the-ota-process-fails-to-retrieve-the-correct-firmware-version/526377"]Could you enable CONFIG_BOOTLOADER_MCUBOOT to make the image get confirmed by this line?[/quote]

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

Amanda Hsieh — Fri, 07 Mar 2025 14:41:37 GMT

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.

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

SunHuang — Thu, 06 Mar 2025 02:20:13 GMT

Hi,

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

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

SunHuang — Thu, 27 Feb 2025 01:21:25 GMT

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.

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

Amanda Hsieh — Tue, 25 Feb 2025 14:16:10 GMT

Please use this version https://github.com/nrfconnect/sdk-connectedhomeip/releases/tag/v2.9.0 for the chiptool.

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

SunHuang — Tue, 25 Feb 2025 08:14:10 GMT

Hi,

1.The NCS version I use is 2.9.0

2.The chiptool is using CSA environment

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

Amanda Hsieh — Mon, 24 Feb 2025 15:41:04 GMT

Which version of NCS and chip tool are you using?

Do you use the corresponding version of NCS and chip tool?

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

SunHuang — Mon, 24 Feb 2025 06:38:09 GMT

Hi,

Please ignore oftwareVersion: 34144256, as this is the experimental result from my test on the development version using a sample code(matter lock). Since you requested the VERSION file currently in use, I have provided my project's VERSION file.

In any case, neither of them can retrieve the correct version using "otasoftwareupdaterequestor read-event version-applied". However, my own project is able to read the correct version using "basicinformation read software-version" after executing the OTA update.

So please focus on the issue where "otasoftwareupdaterequestor read-event version-applied" fails to retrieve the version.

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

Amanda Hsieh — Fri, 21 Feb 2025 15:23:32 GMT

Getting the version-applied event can indeed be investigated as there can be multiple reasons why it's not delivered, but I would like to first understand how is this possible that

after DFU "basicinformation read software-version" shows the old version, but you see a new functionality
if you program the new firmware directly "basicinformation read software-version" shows the new version

Are you sure the behavior is like this? As if you didn't modify the code for accessing the software version, the software version is just a constant in the firmware so the same value should be returned no matter if the new firmware was flashed directly or installed as an upgrade.

Also, the initial logs show that chip-tool received version SoftwareVersion: 34144256 (0x2090000, that is 2.9.0.0) yet the VERSION files they provided contain 0.0.1.0 and 1.0.1.0 versions, respectively. Does it mean that originally you didn't update the VERSION file?

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

SunHuang — Thu, 20 Feb 2025 08:37:06 GMT

If I directly flash the firmware, I can get the correct version. In the end, I found that "occasionally" the version can still be read through read-event version-applied. This instability could cause issues for us when obtaining Matter certification.

[quote userid="77782" url="~/f/nordic-q-a/118679/in-sdk-version-2-9-0-the-ota-process-fails-to-retrieve-the-correct-firmware-version/523607"]Could you program the new firmware to see if you can get the correct version?[/quote]

devzone.nordicsemi.com/.../ver.zip

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

Amanda Hsieh — Tue, 18 Feb 2025 22:39:50 GMT

[quote user="SunHuang"]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. [/quote]

It seems the DFU works fine as expected. In such a case, the basic information cluster should return the "wrong" version if you don't update. Could you program the new firmware to see if you can get the correct version? Also, could you share your VERSION file, in the old and new firmware versions?

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

SunHuang — Sat, 08 Feb 2025 00:07:58 GMT

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?

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

Amanda Hsieh — Fri, 07 Feb 2025 14:05:02 GMT

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?

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

Amanda Hsieh — Thu, 06 Feb 2025 16:17:47 GMT

Hi,

I am working on your case and will update it when I collect enough information.

Regards,
Amanda H.