|
|
|
|
Display satellite version information. This monitor command displays all version information for each satellite board in the system. Both the 'expected' and 'detected' versions are displayed for all 'installed' boards that are successfully configured during system initialization.
|
|
| A satellite board is 'installed' if the nonvolatile parameter flag associated with that satellite is set ( see the monitor command sat (install|uninstall) [<satellite>] ). The firmware expects to detect installed satellites during initialization by successfully downloading a specific program image.
|
|
| To be considered usable satellites must report the expected 'type' and 'version' values. The expected values are hardcoded into tables in each firmware release. These tables indicate the expected satellite type and version.
|
|
|
- Board type: A unique value assigned to each satellite board type. A specific board type is expected to be located at a specific satellite port address. If any detected satellite on a specific port contains an unexpected board type the satellite subsystem initialization fails. This keeps the system from running if boards are swapped or connected incorrectly.
|
|
|
- Board version: This is the hardware revision number of the board ( not its Xilinx configuration version ). Any given release of firmware will support all satellite hardware revisions listed in the satellite configuration table. The firmware is capable of performing different initializations and altering it run time logic depending upon the detected satellite hardware version.
|
|
|
- Major Xilinx configuration version: The firmware expects the satellite's major configuration version number to match exactly the version in the table associated with the hardware version. By convention, each major version requires associated firmware support.
|
|
|
- Minor Xilinx configuration version: The firmware expects the satellite's minor Xilinx version to be greater than or equal to the hardcoded requirement.
|
|
| Below is a theoretical example of the output from this monitor command as it could appear in a development scenario where not all boards are installed, present, detected or verified:
|
|
| Expected-Detected Satellite Versions
Id Type HwVer Configuration
-------------------------------------
[0] NPE 02-02 00-00 02.00-02.00 (accepted)
[1] ACT 01-01 00-00 01.00-01.00 (accepted)
[2] PBP 04- 00- 01.00- (Satellite not installed)
[3] IBS 03- 00- 01.00- (Satellite not installed)
[4] DBP 06- 00- 01.00- (Satellite not installed)
[5] WLC 05-05 00-00 00.00-00.03 (accepted)
[6] RFE 07-07 00-00 01.00-01.00 (accepted)
[7] LVDU 08-08 02-02 03.00-03.00 (accepted)
[8] LVDL 09-09 01-01 03.00-03.00 (accepted)
[9] PBP2 10-10 00-00 00.00-00.00 (accepted) |
|
| The number in square brackets at the beginning of each line indicates the satellite port address. This is followed by the satellite mnemonic name.
|
|
| Both expected and reported versions are shown ( separated by a hyphen ) for the board type, board version ( HwVer ) and FPGA configuration. In cases where the satellite is uninstalled the detected version numbers are left blank.
|
|
| The last field indicates if the satellite was accepted or if not, the error encountered while trying to configure the satellite at initialization.
|
|
| Note that in a fully functioning production head ( i.e. a head that is not being used in a lab development scenario ), it is expected that all satellites will be accepted.
|
Thermal 1.0 / 1.7x equivalents:
|
|
|
- The monitor command sat ver does not have an equivalent.
|
|
| Thermal 2 equivalents:
|
|
|
- The monitor command sat ver does not have an equivalent.
|
COMMAND: sat status
|
|
|
COMMAND: sat (install|uninstall) [<satellite>]
|
|
|
COMMAND: sat uninstall all
|
|
|
PARAMETER: sat devsinstalled
|
The satellite boards that are displayed will depend on the version of Head controller board that is in the head.
|