Trip-T Front End Board Documentation Home
Triggers
Note: This page refers to the Bootloader Firmware, a description of TFB
triggers for the User Firmware can be found
here
There are two ways of triggering the TFB:
- through the configuration bus, by writing to register 0;
- through the dedicated trigger input using the trigger structure
The configuration bus trigger vector mappings for method 1 when the
user firmware is booted are as follows.
- 0x1 = unallocated
- 0x2 = unallocated
- 0x4 = unallocated
- 0x8 = Start I2c Transaction
- 0x10 = unallocated
- 0x20 = Start Firmware Load
- 0x40 = Start Firmware Readback
- 0x80 = Trigger load HV trim DAC load.
- 0x100 = Trigger PROM TAP Reset
- 0x200 = Trigger Monitor Player Command Buffer Readback
- 0x400 = unallocated
- 0x800 = Issue I2C Timeout Reset
The trigger line has 12 independent triggers accessible through the
dedicated trigger input signal pair. At present there are no allocated
triggers from this interface. The table is included for completeness.
- 0x1 = unallocated
- 0x2 = unallocated
- 0x4 = unallocated
- 0x8 = unallocated
- 0x10 = unallocated
- 0x20 = unallocated
- 0x40 = unallocated
- 0x80 = unallocated
- 0x100 = unallocated
- 0x200 = unallocated
- 0x400 = unallocated
- 0x800 = unallocated