Zigbee OTA upgrade example uses the Zigbee OTA cluster recommendations concerning the firmware file name (that is used for the version control and prevention of the downgrade to the previous version if such an option enabled). According to mentioned recommendations, file version is the 32-bit binary-coded decimal (BCD), where the upper 2 bytes represent the application release and build, and lower 2 bytes correspond to the stack release (0x0101 in the OTA example).
For example, 0x10120101 means application release 1.0, build 12 with stack release 0.1 b01. So, as for the major, and minor version numbers in release representation, there is only one decimal digit. But what if we need greater version value? For example, how to deal with release 11.10?
Is it possible to omit the stack release and build info, and use the 2 BCD digits (1 byte) for the major value of release number, another 2 BCD digits (1 byte) for the minor value, and remained 4 BCD digits (2 bytes) for the build number? So, the release 11.10 build 35 would be represented as 0x11100035 (without the information about the stack release). We are using the DFU option that prevents firmware downgrade, would it work correctly in this case?
