|
DRS4 Forum
|
DRS4 Discussion Forum |
Not logged in |
 |
|
Tue May 19 14:14:45 2015, Ilja Bekman, DRS4 firmware UCF constraints
|
Fri May 22 14:25:45 2015, Stefan Ritt, DRS4 firmware UCF constraints
|
Tue May 26 11:27:27 2015, Felix Bachmair, DRS4 firmware UCF constraints
|
Fri Jun 5 12:07:38 2015, Stefan Ritt, DRS4 firmware UCF constraints
|
Fri Jun 5 13:15:35 2015, Felix Bachmair, DRS4 firmware UCF constraints
|
Fri Jun 5 13:29:55 2015, Stefan Ritt, DRS4 firmware UCF constraints
|
Fri Jun 5 13:32:03 2015, Stefan Ritt, DRS4 firmware UCF constraints
|
|
Message ID: 429
Entry time: Fri Jun 5 13:29:55 2015
In reply to: 428
Reply to this: 430
|
Author: |
Stefan Ritt |
Subject: |
DRS4 firmware UCF constraints |
|
|
Do the following:
Use the TRG OUT of the evaluation board as a "busy". Only if this signal goes low (meaning that the readout of the board is complete and the board has been restarted), then re-enable triggers in your trigger logic.
/Stefan
> Hi Stefan,
> No we only use one evaluation board. We use the evaluation board as a part of our beam test setup. It includes a telescope based on the current PSI46V2.1 CMS Pixel chip and a trigger logic board for triggering the telescope and the evaluation board. This includes a
> handshake between every device and the tlu
> e.g. the tlu expects an answer for each trigger.
> If the trigger comes within this first 200 mus it seems that not every trigger is accepted.
> In this moment our readout would 'die' since the tlu is waiting for the handshake. |