Bootloader

Each YOS device is equipped with a bootloader that allows easy but rich means of maintaining and flashing of the installed firmware, usually through our SRM service. Please contact siilXcon for more information about bootloader capabilities.

Product metadata

Information printed on the product tag is also saved in the processor of the product. Information is the same, but the format is a little bit different. This information saved in a processor are called product metadata. Metadata are: Basename, HWID, SWID and s/n. YOS provides a set of non-volatile descriptors for device identification. These include:

• Basename defining the logical (business) product name
• HWID defining the hardware vesion
• SWID defining the firmware version
• UUID/SN defining the unique devide identifier

Oprionally, a set of calibration vectors is provided for the application level:

• Utility calibration vector for factory calibration of the device
• User calibration vector for user-level calibration (such as vehicle model, VIN code, etc.)

info

Metadata (besides SWID) are held in a dedicated, non-volatile storage that is persistent throughout firmware flashing.

Basename

Name of the given product, could be created in cooperation with the customer. Base name defines, which firmwares could be loaded into the product. Examples: SL-serpent, SX-serpent, AX-felix.

HWID

Hardware ID. It is defined by product type, version and revison of PCB and assembly code. Assembly code is also part of the MPN. Example of HWID follows:

ESC3-AM1d 06dxh0610-805

| ESC3-AM | 1 | d | 06dxh0610 | 805 | | -------------- | ------------ | -------------------- | ---------------- | ---------------- | ---------------- | | Product family | Product type | Binary compatibility | Product revision | Assembly variant | Internal HW conf |

• Product family : Group of products, they have common functionalities, operating system YOS and some other parts of firmware.
• Product type : One product has its own specifications (could be modified by following parts of HWID) and typical usage.
• Binary compatibility : Reflects big changes in the product. Each product with different binary compatibility requires its own firmware release.
• Product revision : Reflects small changes in the product, new firmware release is not required, but often new PCB revision is also followed by new firmware release.
• Assembly variant : Product main features regarding parts placement on PCB are reflected here.
• Internal HW conf : Additional configuration of hardware regarding PCB is reflected here.
• Assembly code : This item consists of assembly variant and internal HW conf. Refer to corresponding device manual for more detailed information about assembly code, assembly variant and internal HW conf.

SWID

ID of firmware. Defined by application of product (block APPLICATION in the figure 3.1), release date and version. Example of SWID follows:

BLDC_copter_generic 20.8.2016 2.4.1

BLDC	copter	generic	20.8.2016	2.4.1
Utility	Product application	Modification	Release date	Release version

• Utility : Reflects primary purpose of the product, in case of motor controllers, abbreviation of motor driver algorithm is used.
• Product application : Application of the product, has typical features and settings.
• Modification : The application could have several modifications of firmware.
• Release date : The release date of firmware. Once the firmware is released, it is not changed.
• Release version : The release version is used for firmware marking independent on the date.

UUID

s/n is unique 96-bit identifier of each product. The 96-bit number is converted to ASCII string using a special algorithm. It is connected with the certain piece of the microprocessor in the product. If the microprocessor is replaced for some reason, s/n is changed automatically. Term UUID war formerly used instead of s/n.