USB-TO-GPIO datasheet(21/50 Pages) TI1

21 / 50 page

www.ti.com

Compliant Versioning

To implement this versioning scheme properly, a Windows™ application calls a Firmware Version

command that, along with some others, is reserved and must be present in each implementation of the

device. If the Family Code does not match the code that the application is looking for, it should not

assume anything about what protocols are supported. The Family Code should immediately attempt to

reprogram the firmware with its own version (binary image distributed with the application).

A Windows application that correlates Family Code and Major Version with the firmware implementation

should then, theoretically, only have to check that the Minor Version is greater than or equal to its target

Minor Version. A firmware programmer should be careful to never remove functionality from an

implementation with the same Family Code/Major Version, or an older Windows application may attempt

to make a malformed call to it when it attempts to communicate. In the case that such a drastic change is

made, it is recommend that the firmware developer change the Family Code byte.

Table 4-3. Initial Family Codes

FAMILY CODE (DECIMAL)

GROUP/TEAM

Reserved

01–16

Digital Power + POE

17–32

HPA Design Tools team

33–48

Battery Management

49–239

Unassigned

240–255

Open for custom implementations (user defined)

SLLU093 – August 2006

Firmware Versioning Scheme

Submit Documentation Feedback

USB-TO-GPIO Scheda tecnica(PDF) 21 Page - Texas Instruments