Commit 502d432a authored by Paolo Baesso's avatar Paolo Baesso

Updated documentation to explain how to set DUT to AIDA-with-trigger mode

parent 63fc39cc
......@@ -192,7 +192,7 @@ Paolo Baesso - \monthname, \the\year
\include{ch_TLU_Preparation}
\include{ch_TLU_Hardware}
\include{ch_TLU_clock}
\include{DUT_signals}
\include{ch_DUT_signals}
\include{ch_TLU_triggerInputs}
\include{ch_Shutter}
\include{ch_EventBuffer}
......
......@@ -34,7 +34,8 @@ Figure~\ref{fig:eudet-trigger-busy-trignumber} shows the signal timing for this
\includegraphics[width=0.99\linewidth]{./Images/aida-tlu-eudet-trigger-busy_trignumber_01.pdf}
\caption{Trigger/Busy Interface Mode With Trigger Number }
\label{fig:eudet-trigger-busy-trignumber}
\end{figure}
\end{figure}\\
This mode of operations is enabled by setting the DUTMaskMode flag for the specific \gls{dut} to 0b00. See section~\ref{ch:configFile} for details.
\subsection{Synchronous (AIDA) Mode}
In synchronous mode (also known as AIDA mode) the \gls{tlu} sends a clock (by default 40MHz) to the \gls{dut}.\\
......@@ -46,7 +47,8 @@ Figure~\ref{fig:aida-handshake} shows the signal timing for this interface mode.
\includegraphics[width=0.99\linewidth]{./Images/aida-tlu-aida-interface_01.pdf}
\caption{Synchronous (AIDA) Interface Mode }
\label{fig:aida-handshake}
\end{figure}
\end{figure}\\
This mode of operations is enabled by setting the DUTMaskMode flag for the specific \gls{dut} to 0b11. See section~\ref{ch:configFile} for details.
\subsection{Synchronous Mode With Trigger Number}
This is a modification of the synchronous/AIDA mode.\\
......@@ -57,4 +59,5 @@ Figure~\ref{fig:aida-handshake-with-trigger} shows the signal timing for this in
\includegraphics[width=0.99\linewidth]{./Images/aida-tlu-aida-with-trigger-timing_01.pdf}
\caption{Synchronous (AIDA) Interface Mode With Trigger Number }
\label{fig:aida-handshake-with-trigger}
\end{figure}
\ No newline at end of file
\end{figure}\\
This mode of operations is enabled by setting the DUTMaskMode flag for the specific \gls{dut} to 0b01. See section~\ref{ch:configFile} for details.
\ No newline at end of file
......@@ -88,8 +88,14 @@ Not all parameters are needed; if one of the parameters is not present in the fi
A detailed explanation of how to determine the correct word is provided in section~\ref{ch:triggerLogic}.
\item[DUTMask] \verb|[unsigned int, 0x1]| This mask indicates which \gls{hdmi} inputs have an AIDA device connected. Each of the lowest four bits correspond to a connector (bit 0= DUT1, bit 1= DUT2, bit 2= DUT3, bit 3= DUT4). If the bit is set to 1 the \gls{tlu} expects a device connected and exchanging signals according to the mode selected (see DUTMaskMode).
\item[DUTMaskMode] \verb|[unsigned int, 0xFF]| Defines the mode of operation of the device connected to a specific \gls{hdmi} port.\\
Two bits are needed for each device, so bits 0,1 refer to \gls{hdmi}1, bits 2, 3 refer to \gls{hdmi}2, etc. Currently only the lower bit of each pair is needed to specify if the device is in AIDA mode (\texttt{bX1}) or EUDET mode (\texttt{bx0}).\\
Example: to configure device 1 and 2 as EUDET and the rest as AIDA, the parameters should be set to 11-11-x0-x0, i.e. 0xF0 (but 0xFA, 0xF2 and 0xF8 would also work the same).\\
Two bits are needed for each device, so bits 0,1 refer to \gls{hdmi}1, bits 2, 3 refer to \gls{hdmi}2, etc. The bits define whether the device is in AIDA or EUDET mode and if the trigger output is required, as described in section~\ref{sec:InterfaceModes}. The available options are:
\begin{description}
\item[0x00] EUDET mode.
\item[0x01] AIDA mode with trigger output.
\item[0x11] AIDA mode.
\item[0x10] reserved for future mode. Do not use.
\end{description}
Example: to configure device 0 and 1 as EUDET, 2 as AIDA and 3 as AIDA with trigger the parameters should be set to 01-11-00-00, i.e. 0x70.\\
See also section~\ref{ch:IPBus_DUT}.
\item[DUTMaskModeModifier] \verb|[unsigned int, 0xF]| This mask only affects EUDET mode. Each of the lower 4 bits correspond to a device. If the device is in EUDET mode, it can assert DUTClk to produce a global veto in the triggers. This behaviour occurs if the corresponding bit is set to 1. If the bit is set to 0, asserting the DUTClk from the device will not produce a global veto.
\item[DUTIgnoreBusy] \verb|[unsigned int, 0xF]| This mask tells the \gls{tlu} to ignore the BUSY signal from a specific device, either in AIDA or EUDET mode. If the device is in AIDA mode, this means that further triggers will be issued while the device is busy. If the device is in EUDET mode, this means that the \gls{tlu} will not pause while they are in the handshake phase. In turn, this means that the device will likely receive events where the trigger number does not increase sequentially by one.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment