| Package | Version | Source | Binary | Docs |
|---|---|---|---|---|
| GNAT | V1-0-15 | src | bin | gnat, xbrd |
| GTEM | V1-2-0 | src | bin | doc |
| GAEM | V1-1-0 | src | bin | doc |
| GGLT | V1-2-1 | src | bin | doc |
| EVUT | V1-1-8 | src | bin | doc |
| CTST | V0-0-15 | src | bin | none |
Table 21. Package Versions
This release combines several new features, including:
get/set Parity functions -- see Section 4.3
External triggering for GAEM -- see Section C.2.3
Driver Patch Level -- see Section 10.1.1
New event data format -- see Section 10.1.2
The DriverInfo structure was updated to include a patch level field. This allows for differentiating between library versions that only have very minor differences.
Currently the GTEM library uses the patch level to distinguish between three versions of the library that have very minor changes for particular sub-system needs. The patch levels for GTEM are:
0 – Baseline GTEM, libgtem.o.
1 – Custom GTEM for NRL to test GCRC designs, libgtem_nrl.o
2 – Custom GTEM for TKR to test GTRC designs, libgtem_tkrV5.o
The format of the event data buffer returned to the event handler callback routine has changed somewhat in this release. The event format follows that outlined in LAT cPCI Communication Board, sect. 5.1.
The event format consists of a single 32-bit LAT Event descriptor word, followed by zero or more event contributions. The event format for a single tower contribution is shown below.
32 16 0 +========================+=====================+ | 16 bits error/status | 16 bit event length | +========================+=====================+ | 16 bits Cell Header | 16 bit contrib len | +========================+=====================+ | | | | / Bulk Event Data / | | | | +========================+=====================+ |
The 16 bit error/status word is encoded as follows:
0x8 – LATp cell truncated
0x10 – LATp cell header parity error
0x20 – LATp cell data parity error