Firmware Versions

Last Updated on : 2024-11-20 08:51:50download

This topic describes different firmware versions that support multiple protocols, such as Wi-Fi, Zigbee, Bluetooth mesh, Bluetooth Low Energy (Bluetooth LE), and Narrowband Internet of Things (NB-IoT). The following tables list the acronyms and full names of the firmware versions. This allows you to learn more about firmware uploads and updates.

Wi-Fi firmware versions

Version format: hv.sv.bv (00.00.00 to 99.99.99)

Acronym	Full name	Description
hv	Hardware version	The version is updated in the case of hardware revisions or main component changes after hardware mass production. The version number `hv` is incremented by `1` for each update. The version is updated after the major program is changed, such as software rebuilding. The version number `hv` is incremented by `1` for each update. The version is updated after the value of `sv` is iterated to `99`. The version number `hv` is incremented by `1` for each update. The value of `hv` starts from `1`.
sv	Software version	The version is updated after software function requirements are modified. For example, functions are added, modified, or deleted. The version number `sv` is incremented by `1` for each update. The value of `sv` starts from `0`.
bv	Bug fix version	The version is updated after each software optimization or bug fix, such as iterative tests. The version number `bv` is incremented by `1` for each update. After a version is built, the version number `bv` plus `1` is used as an over-the-air (OTA) update test version. The value of `bv` starts from `0`.

Note:

After the version number hv is incremented by 1 for each update, the values of sv and bv start from 0. After the version number sv is incremented by 1 for each update, the value of bv starts from 0.

The value of each version field ranges from 0 to 99. The leading zero 0 for each field is omitted. For example, 01.00.00 is simplified into 1.0.0.

The version beta.n indicates an iteration record number that only applies to internal development. For the same version, n is increased by 1 for each build.

The preceding rules apply to the firmware versions of IP cameras (IPCs) and smart gateways.

Examples:

1.0.0: the initial firmware version.
1.0.2: Compared with 1.0.0, only bug fixes and unit testing are implemented for this version.
1.1.2: Compared with 1.0.2, more software functions are added and integration testing is implemented for this version.
2.0.4: Compared with 1.1.2, the hardware version or major software version is updated and system testing is implemented for this version.

Zigbee firmware versions

Version format: fv.sv.tv (0.0.0 to 3.3.15)

Acronym	Full name	Description
fv	First version	The first 2-bit version field. Valid values: `1` to `3`. Each time the value of `sv` reaches the maximum number of bits, the value of `fv` is incremented by `1`. The value of `fv` starts from `1`.
sv	Second version	The second 2-bit version field. Each time the value of `tv` reaches the maximum number of bits, the value of `sv` is incremented by `1`. Valid values: `0` to `3`. The value of `sv` starts from `0`.
tv	Third version	The third 4-bit version field. Valid values: `0` to `15`. The value of `tv` is incremented by `1` for each test. The value of `tv` starts from `0`.

Note:

Each Zigbee firmware version is an 8-bit Zigbee Cluster Library (ZCL) version and is defined in the application version attribute of the basic cluster. To make full use of version bits, the firmware version is incremented by 1 for each test.

The value of fv starts from 1 that is the initial version.

The value of sv or tv is incremented by 1 for each update. The value starts from 0.

Examples:

1.0.0: the initial firmware version.
1.0.3: Compared with 1.0.0, three tests have been implemented for this version.
1.1.0: Compared with 1.0.3, 13 tests have been implemented for this version.

Bluetooth mesh firmware versions

Version format: bv.sv (0.0 to 9.9)

Acronym	Full name	Description
bv	Big version	The major version. The value of `bv` is incremented by `1` for each new function. Valid values: `0` to `9`. The value of `bv` starts from `0`.
sv	Small version	The minor version. The value of `sv` is incremented by `1` for each software optimization or bug fix. Valid values: `0` to `9`. The value of `sv` starts from `0`.

Note:

After the version number bv is incremented by 1 for each update, the value of sv starts from 0.

The value of bv starts from 0 that is the initial version.

Examples:

0.3: the version that follows the initial version after four tests have been implemented.
1.7: the eighth minor version of the second major version.

Bluetooth LE firmware versions

Version format: bv.sv (0.0 to 99.99)

Acronym	Full name	Description
bv	Big version	The major version. The value of `bv` is incremented by `1` for each new function. Valid values: `0` to `99`. The value of `bv` starts from `0`.
sv	Small version	The minor version. The value of `sv` is incremented by `1` for each software optimization or bug fix. Valid values: `0` to `99`. The value of `sv` starts from `0`.

Note:

After the version number bv is incremented by 1 for each update, the value of sv starts from 0.

The value of bv starts from 0 that is the initial version.

Bluetooth LE supports the versioning method of Wi-Fi firmware in the hv.sv.bv format. This versioning method applies when you configure the Bluetooth LE SDK.

Examples:

0.3: the version that follows the initial version after four tests have been implemented.
10.27: the 28th minor version of the 11th major version.

NB-IoT firmware versions

Version format: mv.sv.bv (00.00.00 to 99.99.99)

Acronym	Full name	Description
mv	Major version	The version is updated after a major system modification or after a specific number of partial modifications. This applies when the size of a differential package is too large and does not support forward compatibility. The version number `mv` is incremented by `1` for each update. The version is updated in the case of major program changes, such as software rebuilding. The version number `mv` is incremented by `1` for each update. The version is updated when the value of `sv` is iterated to `99`. The version number `mv` is incremented by `1` for each update. The value of `mv` starts from `1`.
sv	Sub-version	The version is updated after software function requirements are modified. For example, functions are added, modified, or deleted. The version number `sv` is incremented by `1` for each update. The value of `sv` starts from `0`.
bv	Bug fix version	The version is updated after each software optimization or bug fix, such as iterative tests. The version number `bv` is incremented by `1` for each update. After a version is built, the version number `bv` plus `1` is used as an OTA update test version. The value of `bv` starts from `0`.

Note:

After the version number mv is incremented by 1 for each update, the values of sv and bv start from 0. After the version number sv is incremented by 1 for each update, the value of bv starts from 0.

The value of each version field ranges from 0 to 99. The leading zero 0 for each field is omitted. For example, 01.00.00 is simplified into 1.0.0.

Examples:

1.0.0: the initial firmware version.
1.0.4: Compared with 1.0.0, only bug fixes and integration testing are implemented for this version.
1.1.2: Compared with 1.0.4, more software functions are added and integration testing is implemented for this version.
2.0.4: Compared with 1.1.2, major system updates and system testing are implemented for this version.