Page History
The firmware requirements are derived from requests that come from the ASIC, detector and DAQ subsystems. The goal of defining them is to communicate among the design team and support teams which feature must be present and why and therefore establish a communication platform.
| Requirement number | Description | Metric of success | Status |
|---|---|---|---|
| ASIC | |||
| ASIC 1.0 | Generate wareforms to control ASIC data acquisition (i.e. R0, ACQ, GR, SRO, CLK, DigRST, etc) | Waveform generated by the FPGA matches ASIC specs | |
| ASIC 1.1 | Receive and decode data with stream auto tuning | Receive encoded data, with the firmware finding the best eye delay position automatically | |
| ASIC 1.2 | Data decode using 16b20b to retrieve SoF, Eof, and real data | Data decoded can be used to generate image packets | |
| ASIC 1.3 | Program each ASIC individually using SACI bus | ||
| ASIC 1.4 | Provide external DAC 20bit voltage source to check ASIC ADC performance. (This allows to fine tune Pipo delay) | ||
| ASIC 1.5 | Two trigger operation should be available. Run Triggers generates a frame but does not send data. Run Triggers followed but DAQ triggers generates a frame and sends data to DAQ. This two trigger operation allows for system level thermal stabilization | ||
| ASIC 1 | Allow ASIC power supplies to be turned on and off via registers | ||
| ASIC 1 | Monitor ASIC analog outputs (for the ASIC where this feature is available) and stream the data as a "pseudo" scope | ||
| DATA | |||
| DATA 1.0 | Data packet should be created with a 4 ASIC to one packet | FW demonstrate implemented 4 to 1 | |
| DATA 1.1 | Data packed should be added by a header containing acquisition number, ID | ||
| DATA 1.2 | Data descrambling, image should be reagentes in FW such that each 4 x 1 ASIC data shout is receiving with physical meaning (in software a single matrix reshape should be enough to display the 4x1 ASIC image correctly) | ||
| DAQ | |||
| DAQ 1.0 | Serial number of each carrier, digital board and analog board should be readout and available via register access | ||
| DAQ 1.1 | Timing module should be part of the FW, where trigger information and timestamps are received | ||
| DAQ 1.2 | Monitor environmental variables (temperature, humidity and selected voltage and currents based on board specific schematics) | ||
| DAQ 1.3 | Add to the data packed the trigger information. This should be implemented with surf module | ||
| DAQ 1.4 | |||
- Image header description
Add a table hear with new header description
...
Overview
Content Tools