From: Michael Wiebusch Date: Thu, 24 Apr 2014 09:35:10 +0000 (+0200) Subject: update X-Git-Url: https://jspc29.x-matter.uni-frankfurt.de/git/?a=commitdiff_plain;h=f7dd510fca679ca942c34c1c326ccab291cb5c64;p=mvd_docu.git update --- diff --git a/electronics/CB_Debug_CheatSheet.pdf b/electronics/CB_Debug_CheatSheet.pdf new file mode 100644 index 0000000..65c1806 Binary files /dev/null and b/electronics/CB_Debug_CheatSheet.pdf differ diff --git a/electronics/CB_Debug_CheatSheet.svg b/electronics/CB_Debug_CheatSheet.svg new file mode 100644 index 0000000..84d6cfb --- /dev/null +++ b/electronics/CB_Debug_CheatSheet.svg @@ -0,0 +1,36360 @@ + + + + + + + + + + image/svg+xml + + + + + + + + + + + GNDA + VDDA + VDDA + VDDA + GNDA + VDDA_CHIP + GNDA + GNDD + VDDD + VDDD + VDDD + GNDD + VDDD_CHIP + GNDD + GNDD + CLKD_P + CLKD_N + MKD_P + MKD_N + D0_P + D0_N + D1_P + D1_N + GNDD + GNDD + GNDA + Vclp + GNDA + RESET + START + GNDD + CLKL_P + CLKL_N + GNDD + TDO + TDI + TMS + GNDD + GND_CHIP + VDISCRIREF2D + VDISCRIREF2C + VDISCRIREF2B + VDISCRIREF2A + VDISCRIREF1D + VDISCRIREF1C + VDISCRIREF1B + VDISCRIREF1A + TEMP + GNDD + TCK + + diff --git a/mvdsensorcontrol/.daqsetup.tex.kate-swp b/mvdsensorcontrol/.daqsetup.tex.kate-swp new file mode 100644 index 0000000..ec33129 Binary files /dev/null and b/mvdsensorcontrol/.daqsetup.tex.kate-swp differ diff --git a/mvdsensorcontrol/TRB3.png b/mvdsensorcontrol/TRB3.png new file mode 100644 index 0000000..e1ce728 Binary files /dev/null and b/mvdsensorcontrol/TRB3.png differ diff --git a/mvdsensorcontrol/daqscripts.tex b/mvdsensorcontrol/daqscripts.tex index 8325d2c..d5d55f6 100644 --- a/mvdsensorcontrol/daqscripts.tex +++ b/mvdsensorcontrol/daqscripts.tex @@ -34,7 +34,7 @@ daq\_evtbuild with timeout and shm name \subsection{start.pl} \begin{description} -\item[is called by] manual with argument systemName +\item[is called by] manual with argument systemName (not file, no path) \item[does] \begin{itemize} \item @@ -56,7 +56,7 @@ Run the necessary steps to configure and start MAPS sensors. (see also section \hyperref[sec:startup.pl]{startup.pl}) \begin{description} \item[is called by] -run.pl or manual with argument setupFile +run.pl or manual with argument /path/to/setupFile \item[does] \begin{itemize} \item diff --git a/mvdsensorcontrol/daqsetup.tex b/mvdsensorcontrol/daqsetup.tex index 8132e92..8fa8435 100644 --- a/mvdsensorcontrol/daqsetup.tex +++ b/mvdsensorcontrol/daqsetup.tex @@ -92,11 +92,59 @@ and thus on the efficiency of the sensor. \subsection{TRB3 FPGA board} -The +\begin{figure}[H] +\centering +\includegraphics[width=.6\textwidth]{TRB3.png} +\caption{Photo of a TRB3 board with optical link attached} +\label{fig:TRB3} +\end{figure} + + +The TRB3 board is the third iteration of the FPGA based multi purpose data acquisition +platform that was developed for the HADES experiment. It is also used in several other high energy +physics experiments due to its versatility. + +It is equiped with five Lattice ECP3-150EA FPGAs, i.e. one central and four peripheral FPGAs. +The board possesses eight SFP ports that are able to accomodate optical or electrical ethernet adaptors. +Next to each peripheral FPGA a high pin density extension connector is located, that can be equiped +with specialized adaptor or interface boards. This way a wide range of data acquisition applications +is possible. The FPGAs have an internal flash storage for its design configuration. +When the FPGA is powered or reset, it retrieves and loads the configuration from this flash. + +The TRB3 hardware platform and the associated software framework are developed and maintained +by the TRB collaboration. +In this set-up, the TRB3 is used as a network controlled data readout board for the MIMOSA26 MAPS. + +\subsection{FPGA design entities (draft!)} +The FPGA design is internally divided into individual modules, the so called entities. +An entitity can be pictured as a (virtual) black box with a multitude of binary data inputs +and outputs. Entities can contain virtually every kind of digital circuitry, such as +combinatorial logic, memory, arithmetic processing elements, etc. +The design for the TRB3 peripheral FPGAs consists of +three main entities: The readout controller (ROC), the JTAG controller and the converter board +controller (CbController). Each of the three has its distinct functionality. +\subsubsection{Readout controller} +The readout controller captures the synchronous serial data stream coming from the sensor. +By means of the front-end electronics and dedicated FPGA pins the readout controller receives +the following (differential) signals from the sensor: +\begin{description} +\item[CLKD] +The serial sensor data output clock, a square wave with a frequency of \SI{80}{\mega\hertz}. +\item[MKD] +This signal marks the beginning of a sensor readout frame. At the beginning of a frame, the MKD +signal is held high for four CLKD cycles and low otherwise. (If the sensor is not programmed, MKD +is constantly high) +\item[D0] +Serial data output for the first half of the sensor data. +\item[D1] +Serial data output for the second half of the sensor data. + +\end{description} +\subsection{JTAG controller} + +\subsection{Converter board controller} -[what is where] -to explain \begin{itemize} \item hub @@ -113,7 +161,18 @@ roc CbController \end{itemize} \item -tjah +\end{itemize} + +\subsection{Converter board v2013} +The converter board is the key component +??-> what to write +\begin{itemize} +\item +Key component of the front-end electronics +\item +Regulated power supplies (linear, switchable), voltage and consumption can be measured +\item +blah \end{itemize} diff --git a/mvdsensorcontrol/jtag.tex b/mvdsensorcontrol/jtag.tex index 950a4c0..ad28ada 100644 --- a/mvdsensorcontrol/jtag.tex +++ b/mvdsensorcontrol/jtag.tex @@ -210,7 +210,7 @@ changeConfigVal.pl -c config.xml [-v] \subsubsection{startup.pl} \label{sec:startup.pl} The script runs the necessary steps to configure and start the MAPS sensors. From a given -\hyperref[sec:setupFile]{setup configuration file} the script extracts: +\hyperref[sec:setupFile]{setup configuration file} (with full path!) the script extracts: \begin{itemize} \item The topology of the setup, i.e. how many controllers (and their addresses), how many chains, how many @@ -224,7 +224,7 @@ the sensors. (!!) It does not (yet) set the sensor enable, JTAG enable, and power switches on the Converter Board to the correct settings! This has to be done manually! (!!) \begin{verbatim} -startup.pl setupFile +startup.pl /path/to/setupFile Options: -h, --help brief help message