|
|
|
|
Display the firmware banner as follows:
|
|
| Project: Tfx
|
|
| Firmware: <Major Version>.<Minor Version><Patch Level> <Build Type>
|
|
| Build: <Build Number>
|
|
| Date: <Build Date> <Build Time>
|
|
| Control board: <Control Board Version>
|
|
| Driver boards: <Driver Board Top Version><Driver Board Bottom Version>
|
|
| Xilinx: <Xilinx Version>
|
|
| The firmware version is defined by the major version, the minor version and the patch level. The major version is displayed as a single numerical digit, the minor version is displayed as two numerical digits and the patch level is displayed as a single lowercase alphabetical digit. Note that if the patch level is zero, an 'a' is not displayed. For example:
|
|
|
- Firmware: 1.00e Release
- Firmware: 1.01 Beta
- Firmware: test build
|
|
| The build type will be one of the following:
|
|
|
- Engineering
- Alpha
- Beta
- Release
|
|
| A build type of "Release" is an official release and will have a corresponding ECO or DP. A build type of "Beta" is intended for limited field testing and should be replaced with an official release whenever possible. A build type of "Engineering" and "Alpha" should not be used in the field.
|
|
| The build number is incremented on a daily basis by an autobuild. The build number allows firmware developer's to determine the approximate point at which the firmware was built from development.
|
|
| The build date and build time determine the date and time of the firmware build.
|
|
| The control board version, driver board top version, driver board bottom version and Xilinx version determine various hardware versions.
|