Subversion Repositories svnkaklik

Rev

Rev 1151 | Rev 1159 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log

Rev Author Line No. Line
1133 hlavac 1
\chap Trial version of the receiver, design and implementation
1073 kaklik 2
 
1149 hlavac 3
The whole design of the radioastronomic receiver digitization unit is meant to be used in a wide range of applications and tasks related to digitization of a signal. A good illustrating problem for its use is the signal digitization from multiple antenna arrays.
1083 kaklik 4
 
1132 kaklik 5
\midinsert
6
\clabel[expected-block-schematic]{Expected system block schematic}
7
\picw=\pdfpagewidth \setbox0=\hbox{\inspic ./img/Coherent_UHF_SDR_receiver.png }
8
\par\nobreak \vskip\wd0 \vskip-\ht0
9
\centerline {\kern\ht0 \pdfsave\pdfrotate{90}\rlap{\box0}\pdfrestore}
1151 hlavac 10
\caption/f Expected realization of signal digitalisation unit.
1132 kaklik 11
\endinsert
12
 
1073 kaklik 13
\sec Required parameters
14
 
1149 hlavac 15
We require the following technical parameters in order to overcome the existing digitization units solutions. Primarily, we need a wide a dynamical range and a high third-order intercept point (IP3\glos{IP3}{Third-order intercept point}). The receiver must accept signals with the wide dynamics because a typical radioastronomical signal is a weak signal covered by a strong man-made noise or other undesired noises as lighting, Sun emissions, etc.
1073 kaklik 16
 
1149 hlavac 17
\medskip
18
\noindent
19
The summary of other additional required parameters:
20
%
1083 kaklik 21
\begitems
1149 hlavac 22
  * Dynamic range better than 80 dB, see section \ref[dynamic-range-theory] for the explanation.
23
  * Phase stability between channels.
24
  * Low noise (all types).
25
  * Sampling jitter better than 100 metres.
26
  * Support for any number of receivers in the range of 1 to 8.
1083 kaklik 27
\enditems
28
 
1149 hlavac 29
\noindent
30
We analyze several of the parameters more in detail in the sequel.
1125 kaklik 31
 
1098 kaklik 32
\sec Sampling frequency
1133 hlavac 33
 
1150 hlavac 34
The sampling frequency has not been a limiting factor in the trial version. Generally, the sampling frequency is mostly limited by the sampling frequencies of the analog-to-digital conversion chips available on the market and by the interface bandwidth. The combination of required parameters -- dynamic range needing 16 bits  at least and a minimum sampling frequency of 1 Mega-Samples Per Second (MSPS\glos{MSPS}{Mega-Samples Per Second}) -- leads to the need of the high-end ADC chips. However, they do not support such low sampling frequencies at all. Their minimum sampling frequency is 5$\ $MSPS.
1083 kaklik 35
 
1151 hlavac 36
We calculated the minimal data bandwidth data rate for eight receivers, 2~bytes per sample and 5$\ $MSPS as $8 \cdot 2 \cdot 5\cdot 10^6 = 80\ $MB/sec. Such a data rate is at the limit of the actual writing speed of a classical hard disk drive (HDD\glos{HDD}{Hard disk drive}) and it is almost a double the real bandwidth of USB~2.0\glos{USB 2.0}{Universal Serial Bus version 2.0} interface. As a result of these facts, we must use a faster interface. Such a faster interface is especially needed in cases in which we require faster sampling rates than ADC's minimal 5$\ $MSPS sample rate.
1135 kaklik 37
The most perspective interface for use in our type of application is USB 3.0 or PCI Express interface. However, USB 3.0 is a relatively new technology without good development tools currently available. We have used PCI Express \glos{PCI Express}{Peripheral Component Interconnect Express}  interface as the simplest and the most reliable solution.
1133 hlavac 38
 
1075 kaklik 39
\sec System scalability
1073 kaklik 40
 
1151 hlavac 41
Special parameters of ADC modules are required to secure scalability of analog channels. Ideally, there should be a separate output for each analog channel in ADC module. ADC module must also have separate outputs for frames and data output clocks. These parameters allow the operation at relatively low digital data rates. As a result, the digital signal can be conducted even via long wires. The modular architecture enables the separation from a central logical unit which supports optimization of a number of analog channels.
1073 kaklik 42
 
1151 hlavac 43
Clock and data signals will be handled distinctively in our modular scalable design. Selected ADC chips are guaranteed to have the defined clock skew between the sampling and the data output clocks. This allows taking data and frame clocks from the first ADC module only. The rest of the data and frame clocks from other ADC modules can be measured for diagnostic purposes (failure detection, jitter measurement, etc.), but these redundant signals are not used for data sampling. If more robustness is required in the final application then Data Clock Output (DCO\glos{DCO}{Data Clock Output}) and FR signals may be collected from other modules and routed through a voting logic which  corrects possible signal defects.
1075 kaklik 44
 
1151 hlavac 45
This system concept allows for scalability, which is limited technically by a number of differential signals on the host side and its computational power.  There is another advantage of the scalable data acquisition system -- an economic one. Observatories or end users can make a choice how much money are they willing to spent on the radioastronomy receiver system. This freedom of choice is especially useful for scientific sites without previous experience in radioastronomy observations.
1075 kaklik 46
 
1134 fluktuacia 47
\secc Differential signalling
1075 kaklik 48
 
1151 hlavac 49
The above mentioned concept of the scalable design requires a relatively long circuit traces between ADC and the digital unit which captures the data and performs the computations. The long distance between the digital processing unit and the analog-to-digital conversion unit has the advantage in noise retention typically produced by digital circuits. Those digital circuits, such as FPGA\glos{FPGA}{Field-programmable gate array}, Ethernet or other flip-flops blocks and circuit traces, which work usually at high frequencies and emit the wide-band noise with relatively low power. In such cases, any increase in a distance between the noise source and the analog signal source increases S/N significantly. However, at the same time, a long distance introcuces problems with the digital signal transmission between ADC and the computational unit. However, this obstacle should be resolved more easily in a free-space than on board routing. The high-quality differential signalling shielded cables should be used, such as massively produced and cheap SATA\glos{SATA}{Serial ATA}\glos{ATA}{AT Attachment} cables. This technology has two advantages over PCB\glos{PCB}{printed circuit board} signal routing. First, it can use twisted pair of wires for leak inductance suppression in signal path. Second, the twisted pair may additionally be shielded by uninterrupted metal foil.
1075 kaklik 50
 
1076 kaklik 51
\secc Phase matching
52
 
1154 hlavac 53
The system phase stability is a mandatory condition for multi-antennas radioastronomy projects. It allows a precise, high resolution imaging of objects, increases signal to noise ratios in several observation methods and enables using of advanced algorithms for signal processing.
1076 kaklik 54
 
1154 hlavac 55
The high phase stability is achieved in our scalable design through centralized frequency generation and distribution with multi-output Low Voltage Emitter-coupled logic (LVPECL\glos{LVPECL}{Low Voltage Emitter-coupled logic}) hubs (CLKHUB02A), which have equiphased outputs for multiple devices. LVPECL logic is used on every system critical clock signal distribution hub. LVPECL logic has the advantage over the Low-voltage differential signaling (LVDS\glos{LVDS}{Low-voltage differential signaling}) in the signal integrity robustness. LVPECL uses higher logical levels and higher signalling currents. The power consumption of LVPECL logic is nearly constant over the operating frequency range due to the use of bipolar transistors. This arrangement minimizes voltage glitches which are typical for CMOS\glos{CMOS}{Complementary metal–oxide–semiconductor} logic. One drawback of its parameters is a high power consumption of LVPECL logic, which reaches tens of milliamperes per device easily.
1076 kaklik 56
 
1154 hlavac 57
This design ensures that all system devices have access to the defined phase and the known frequency.
1076 kaklik 58
 
1073 kaklik 59
\sec System description
60
 
1154 hlavac 61
This section deals with the description of the trial version based on Xilinx ML605 development board, see Figure~\ref[ML605-development-board]. The board had been used in a previous project and has not been used since. However, the FPGA parameters are more than sufficient of what we need for fast data acquisition system.
1073 kaklik 62
 
1133 hlavac 63
\secc Frequency synthesis
1075 kaklik 64
 
1154 hlavac 65
We have used a centralized topology as a basis for frequency synthesis. One precise high-frequency and low-jitter digital oscillator has been used \cite[MLAB-GPSDO]. The other working frequencies have been derived from it by the division of its signal. This central oscillator has a software defined GPS\glos{GPS}{Global Positioning System}  disciplined control loop for frequency stabilization.\fnote{SDGPSDO design has been developed in parallel to this diploma project as a related project, but it is not explicitly required by the thesis itself and thus it is described in a separate document.}
66
We have used new methods of software frequency monitoring and compensation in order to meet modern requirements on the radioastronomy equipment, which needs the precise frequency and phase stability over a wide baseline scales for effective radioastronomy imaging.
1133 hlavac 67
 
1154 hlavac 68
The GPSDO device consists of Si570 chip with LVPECL output. The phase jitter of the GPS disciplined oscillator (GPSDO\glos{GPSDO}{GPS disciplined oscillator}) is determined mainly by Si570 phase noise. Parameters of the Si570 are summarized in Table~\ref[LO-noise] (source \cite[si570-chip] ).
1112 kaklik 69
 
1154 hlavac 70
GPSDO design, which is included in the data acquisition system, has a special feature -- it generates time marks for a precise time-stamping of the received signal. Time-stamps are created by disabling the local oscillator outputs, connected to SDRX01B receivers, for 100 $\mu$s.  As the result, a rectangular click in the ADC input signal is created, which appears as a horizontal line in the spectrogram.
71
Time-stamps should be seen in the image in Figure~\ref[meteor-reflection] (above and below the meteor reflection).
1112 kaklik 72
 
1154 hlavac 73
Time-stamping should be improved in future by digitization of GPS signal received by the antenna on the observational station. Following that, the GPS signal can be directly sampled by a dedicated receiver and one separate ADC module. The datafile consists of samples from channels of radio-astronomy receivers along with the GPS signal containing the precise time information.
1126 kaklik 74
 
75
 
1134 fluktuacia 76
\midinsert \clabel[LO-noise]{Phase noise of the local oscillator}
1113 kaklik 77
\ctable{lcc}{
1114 kaklik 78
	&	 \multispan2 \hfil Phase Noise [dBc/Hz] \hfil 		\cr
79
Offset Frequency	&	$F_{out}$ 156.25 MHz	& $F_{out}$ 622.08 MHz \cr
1113 kaklik 80
100 [Hz]	&	–105	&	–97 \cr
81
1 [kHz]	&	–122	&	–107 \cr
82
10 [kHz]	&	–128	&	–116 \cr
83
100 [kHz]	&	–135	&	–121 \cr
84
1 [MHz]	&	–144	&	–134 \cr
85
10 [MHz]	&	–147	&	–146 \cr
86
100 [MHz]	&	n/a	&	–148 \cr
87
}
1154 hlavac 88
\caption/t The phase noise of the used Silicon Laboratories Si570 chip. Offset frequency is measured from carrier frequency. Values shown in the table are given for two different carrier frequencies.
1113 kaklik 89
\endinsert
1112 kaklik 90
 
1134 fluktuacia 91
Every ADC module will be directly connected to CLKHUB02A module which takes sampling clock signal delivered by FPGA from the main local oscillator.  This signal should use high quality differential signalling cable -- we should use SATA cable for this purpose. FPGA may slightly affect the clock signal quality by adding a noise, but it has a negligible effect on the application where developed system will be used.
1112 kaklik 92
 
1098 kaklik 93
 
1145 kaklik 94
\label[signal-cables] \secc Signal cable connectors
1073 kaklik 95
 
1154 hlavac 96
Several widely used and commercially easily accessible differential connectors were considered to be used in our design.
1126 kaklik 97
 
1073 kaklik 98
\begitems
1077 kaklik 99
* HDMI % [[http://en.wikipedia.org/wiki/Hdmi|HDMI]]</del>
100
* SATA  		%{http://en.wikipedia.org/wiki/Serial_attached_SCSI#Connectors|SAS]]/[[http://en.wikipedia.org/wiki/Serial_ATA|SATA]]
101
* DisplayPort 		%[[http://en.wikipedia.org/wiki/Display_port|DisplayPort]]</del>
102
* SAS/miniSAS
1073 kaklik 103
\enditems
104
 
1154 hlavac 105
Finally, MiniSAS connector was chosen as the best option to be used in connecting multiple ADC modules together. A transition between SATA and miniSAS is achieved by SAS to SATA adapter cable, which is commonly used in servers to connect SAS controller to multiple SATA hard disc in RAID systems and thus is commercially easily available. It is compatible with existing SATA cabling systems and aggregates multiple SATA cables to a single connector. It also has SPI configuration lines which can be seen in Figure~\ref[img-miniSAS-cable] as the standard pinheader connector.
106
The main drawback of miniSAS PCB connectors lies in the fact, that they are manufactured in SMT versions only. SMT design may eventually decrease the durability of the connector even if the outer metal housing of the connector is designed to be mounted using a standard through-hole mounting method.
1073 kaklik 107
 
1085 kaklik 108
\midinsert
1086 kaklik 109
\clabel[img-miniSAS-cable]{Used miniSAS cable}
1118 kaklik 110
\picw=5cm \cinspic ./img/miniSAS_SATA_cable.jpg
111
\caption/f An example of miniSAS cable similar to used.
1085 kaklik 112
\endinsert
113
 
1086 kaklik 114
\secc Signal integrity requirements
1126 kaklik 115
 
1105 kaklik 116
\label[diff-signaling]
1085 kaklik 117
 
1154 hlavac 118
We use ADC devices that have DATA clock frequency eight times higher than sampling frequency in a single line output mode, implying a 40 MHz output bit rate. This implies a $ 1/4 \cdot 10^7 = 25\ $ns time length of data bit, which is equivalent to 7.5~m light path in a free space. If the copper PCB with FR4 substrate layer or the coaxial/twinax cable is used, we could obtain the velocity factor of 0.66 in the worst case. Consequently, the light path for the same bit rate $t_s$ will be 4.95~m. Although we do not have any cables in the system with comparable lengths, the worst data bit skew described by data sheets of the used components is $0.3 \cdot t_s$, which is 1.485~m. Therefore the length matching is not critical in our current design operating on the lowest sampling speed. The length matching may become critical in future versions with higher sampling rates, where the cable length must be matched. However SATA cabling technology is already prepared for that case and matched SATA cables are a standard merchandise.
1086 kaklik 119
 
1093 fluktuacia 120
\secc ADC modules design
1073 kaklik 121
 
1124 kaklik 122
\midinsert
1126 kaklik 123
\clabel[adcdual-preview]{Preview of designed ADCdual PCB}
1132 kaklik 124
\picw=10cm \cinspic ./img/ADCdual01A_Top_Big.JPG
125
\picw=10cm \cinspic ./img/ADCdual01A_Bottom_Big.JPG
1134 fluktuacia 126
\caption/f Realised PCB of ADCdual01A modules. Differential pairs routings are clearly visible.
1124 kaklik 127
\endinsert
1083 kaklik 128
 
129
\secc ADC selection
130
 
1134 fluktuacia 131
There exist several standard ADC signalling formats currently used in communication with FPGA.
1083 kaklik 132
 
133
\begitems
134
  * DDR LVDS
135
  * JEDEC 204B
136
  * JESD204A
137
  * Paralel LVDS
138
  * Serdes
139
  * serial LVDS
140
\enditems
141
 
1154 hlavac 142
As a result of our need to use the smallest number of cables possible, the choice fell on the serial LVDS format. A small number of differential pairs is an important parameter determining the construction complexity and reliability\cite[serial-lvds]. No many currently existing ADC devices have this kind of digital interface. An ultrasound AFE device chips seem to be ideal for this purpose -- the chip has integrated both front-end amplifiers and filters. It has a drawback though. It is incapable of handling the differential input signal and has a relatively low dynamic range (as it consists only of 12bit ADC) and has many single ended ADC channels. Consequently, the scaling is possible only by a factor of 4 receivers (making 8 analog single ended channels).
1083 kaklik 143
 
1154 hlavac 144
If we add a requirement of a separate output for every analog channel and a 16bit depth, we find that there are only a few 2-Channel simultaneous sampling ADCs currently existing which meet these criteria. We have summarized those ADCs in Table~\ref[ADC-types].
1083 kaklik 145
 
1133 hlavac 146
\midinsert
1154 hlavac 147
\typosize[9/11] \def\t
148
abiteml{ }\let\tabitemr=\tabiteml
1126 kaklik 149
\clabel[ADC-types]{Available ADC types}
1116 kaklik 150
\ctable{lccccccc}{
1086 kaklik 151
\hfil ADC Type & LTC2271 & LTC2190 & LTC2191 & LTC2192 & LTC2193 & LTC2194 & LTC2195 \cr
1126 kaklik 152
SNR [dB] & 84.1 & 77 & 77 & 77 & 76.8 & 76.8 & 76.8  \cr
153
SFDR [dB] & 99 & 90 & 90 & 90 & 90 & 90 & 90  \cr
154
S/H Bandwidth [MHz] & 200 & \multispan6 550 \strut \cr
155
Sampling rate [MSPS] & 20 & 25 & 40 & 65 & 80 &  105 & 125  \cr
156
Configuration & \multispan7 SPI \strut \cr
157
Package & \multispan7 \hfil 52-Lead (7mm $\times$ 8mm) QFN \hfil \strut \cr
1086 kaklik 158
}
1134 fluktuacia 159
\caption/t The summary of the currently available ADC types and theirs characteristics.
1086 kaklik 160
\endinsert
1083 kaklik 161
 
1154 hlavac 162
All parts in this category are compatible with one board layout. The main differences lay in the sampling frequency and in the signal to noise ratio, with the slowest having a maximum sampling frequency of 20 MHz. However, all of them have a minimal sampling frequency of 5 MSPS and all are configurable over a serial interface (SPI). SPI seems to be a standard interface used in high-end ADC chips made by the largest manufacturers (Analog Devices, Linear technology, Texas instruments, Maxim integrated, etc.).  We have selected two slowest types for our evaluation design. Following that, a PCB for this part have been designed.
1134 fluktuacia 163
We have decided that ADCdual01A modules will have a standard MLAB construction layout with four mounting holes in corners aligned in defined raster of 400 mils.
1083 kaklik 164
 
1154 hlavac 165
Data serial data outputs of ADC modules should be connected directly by LVDS signalling levels conducted by SATA cables to FPGAs for the basic primary signal processing. The ADC chips used in the modules have a selectable bit width of data output bus and thus the output SATA connectors have signals arranged to contain a single bit from every ADC channel.  This creates a signal concept enabling a selection of the proper bus bit-width according to the sampling rate (the higher bus bit-width downgrades signalling speed and vice versa.)
1105 kaklik 166
 
1154 hlavac 167
In order to connect the above mentioned signalling layout, miniSAS to multiple SATA cable should be used as described in Section~\ref[signal-cables].
1105 kaklik 168
 
1154 hlavac 169
KiCAD design suite had been chosen for PCB layout. However, the version, despite having integrated CERN Push \& Shove routing capability, is slightly unstable as it sometimes crushes due to an exception during routing. On the basis of these stability issues, the design had to be saved quite often. On the other hand, compared to commercially available solutions, such as MentorGraphics PADS or Cadence Orcad,  the Open-source KiCAD provides an acceptable option and it easily surpasses a widely used Eagle software.
1105 kaklik 170
 
1133 hlavac 171
As a part of work on the thesis, new PCB footprints for FMC, SATA, ADCs a and miniSAS connectors have been designed and were committed to KiCAD github library repository. They are now publicly available on the official KiCAD repository at GitHub.
1105 kaklik 172
 
1126 kaklik 173
ADCdual01A module has several digital data output formats. Difference between these modes lays in the number of differential pairs used.
1105 kaklik 174
 
175
\begitems
176
    * 1-lane mode
1114 kaklik 177
    * 2-lane mode
178
    * 4-lane mode
1105 kaklik 179
\enditems
180
 
1154 hlavac 181
All of the above-mentioned modes are supported by the module design. For the discussed data acquisition system, the 1-lane mode was selected. 1-lane mode allows a minimal number of differential pairs between ADCdual01A and FPGA. Digital signalling scheme used in 1-lane mode is shown in Figure~\ref[1-line-out].
1105 kaklik 182
 
183
\midinsert
184
\clabel[1-line-out]{Single line ADC output signals}
185
\picw=15cm \cinspic ./img/ADC_single_line_output.png
1122 fluktuacia 186
\caption/f Digital signalling schema for 1-line ADC digital output mode.
1105 kaklik 187
\endinsert
188
 
1134 fluktuacia 189
ADCdual01A parameters can be set either by jumper setup (referred to as a parallel programming  in the device's data sheet) or by SPI interface. SPI interface has been chosen for our system, because of the parallel programming's lack of options (test pattern output setup for example).
1105 kaklik 190
 
1133 hlavac 191
Complete schematic diagram of ADCdual01A module board is included in the appendix.
1105 kaklik 192
 
193
 
1073 kaklik 194
\secc ADC modules interface
195
 
1124 kaklik 196
\midinsert
1132 kaklik 197
\picw=10cm \cinspic ./img/FMC2DIFF_Top_Big.JPG
198
\picw=10cm \cinspic ./img/FMC2DIFF_Bottom_Big.JPG
199
\caption/f Realised PCB of FMC2DIFF01A module.
1124 kaklik 200
\endinsert
201
 
1154 hlavac 202
Both of the ADCdual01A modules were connected to FPGA ML605 board trough FMC2DIFF01A adapter board. The design of this adapter expects the presence of FMC LPC connector on host side and the board is, at the same time, not compatible with MLAB. It is, on the other hand, designed to meet the VITA 57 standard specifications for boards which support region 1 and region 3. VITA 57 regions are explained in Figrue~\ref[VITA57-regions].
203
This industry standard guarantees the compatibility with other FPGA boards that have FMC LPC connectors for Mezzanine Card. Schematic diagram of designed adapter board is included in the Appendix.
1073 kaklik 204
 
1133 hlavac 205
The primary purpose of the PCB is to enable the connection of ADC modules located outside the PC case with ML605 development board. (In PC box analog circuits cannot be realized without the use of massive RFI mitigation techniques).
1134 fluktuacia 206
Differential signalling connectors should be used for conducting digital signal over relatively long cables. The signal integrity sensitive links (clocks) are equipped with output driver and translator to LVPECL logic for better signal transmission quality.
1083 kaklik 207
 
1134 fluktuacia 208
LVPECL level signal connectors on FMC2DIFF01A board are dedicated to transmit the clock signals. We have selected  the SY55855V and SY55857L dual translators. Dual configuration in useful due to fact, that SATA cable contains two differential pairs.
1119 kaklik 209
 
1134 fluktuacia 210
The SY55855V is a fully differential, CML/PECL/LVPECL-to-LVDS translator. It achieves LVDS signalling up to 1.5Gbps, depending on the distance and the characteristics of the media and noise coupling sources.
211
LVDS is intended to drive 50 $\Omega$ impedance transmission line media such as PCB traces, backplanes, or cables. SY55855V inputs can be terminated with a single resistor between the true and the complement pins of a given input \cite[SY55855V-chip].
1119 kaklik 212
 
1154 hlavac 213
The SY55857L is a fully differential, a high-speed dual translator optimized for accepting any logic standard from the single-ended TTL/CMOS to differential LVDS, HSTL, or CML and translate it to LVPECL. Translation is guaranteed for speeds up to 2.5Gbps (2.5GHz toggle frequency). The SY55857L does not internally terminate its inputs, as different interfacing standards have different termination requirements\cite[SY55857L-chip].
1119 kaklik 214
 
1154 hlavac 215
Inputs of both used chips are terminated accordingly to the used logic. The LVDS input is terminated differentially by 100~$\Omega$ resistor between the positive and the negative inputs. PECL input is terminated by Thevenin resistor network. Thevenin termination method was selected as optimal one, due to the absence of a proper power voltage (1.3 V) for direct termination by 50~$\Omega$ resistors. Termination on FPGA side is realized directly by settings the proper digital logic type on input pins.
1119 kaklik 216
 
1073 kaklik 217
\midinsert
1126 kaklik 218
\clabel[ML605-development-board]{ML605 development board}
1073 kaklik 219
\picw=10cm \cinspic ./img/ML605-board.jpg
1094 fluktuacia 220
\caption/f FPGA ML605 development board.
1073 kaklik 221
\endinsert
222
 
1096 kaklik 223
\midinsert
224
\clabel[VITA57-regions]{VITA57 board geometry}
225
\picw=10cm \cinspic ./img/VITA57_regions.png
226
\caption/f Definition of VITA57 regions.
227
\endinsert
228
 
1137 kaklik 229
Three differential logic input/output, one PECL input and one PECL output SATA connectors and two miniSAS connectors are populated on this board.  This set of connectors allows a connection of any number of ADC modules within the range of 1 to 8. ADC data outputs should be connected to the miniSAS connectors, while other supporting signals should be routed directly to SATA connectors on adapter.
1116 kaklik 230
 
1154 hlavac 231
Lengths of the differential pairs routed on PCB of the module are not matched between the pairs. The length variation of differential pairs is not critical in our design according to facts discussed in Section~\ref[diff-signaling]. Nevertheless, signals within differential pairs themselves are matched for length. Internal signal trace length matching of differential pairs is mandatory in order to minimize jitter and avoid a dynamic logic hazard conditions on digital signals, that represents the worst scenario. Thus the clocks signals are routed in the most precise way on all designed boards.
1104 kaklik 232
 
1154 hlavac 233
The signal configuration used in our trial design is described in Tables~\ref[minisas-interface], \ref[SPI-system] and \ref[clock-interconnections].
1076 kaklik 234
 
1073 kaklik 235
 
1125 kaklik 236
\midinsert \clabel[minisas-interface]{miniSAS differential pairs connections}
1121 kaklik 237
\ctable {cccc}
238
{
239
miniSAS	&	SATA pair	&	FMC signal	&	Used as	\cr
240
P0	&	1	&	LA03	&	 not used 	\cr
241
P0	&	2	&	LA04	&	 not used 	\cr
242
P1	&	1	&	LA08	&	 not used 	\cr
243
P1	&	2	&	LA07	&	 not used 	\cr
244
P2	&	1	&	LA16	&	ADC1  CH1 (LTC2190)	\cr
245
P2	&	2	&	LA11	&	ADC1  CH2 (LTC2190) 	\cr
246
P3	&	1	&	LA17	&	ADC2 CH1 (LTC2271)	\cr
247
P3	&	2	&	LA15	&	ADC2 CH2 (LTC2271)	\cr
248
}
1133 hlavac 249
\caption/t miniSAS (FMC2DIFF01A J7) signal connections between modules.
1121 kaklik 250
\endinsert
251
 
1116 kaklik 252
 
1125 kaklik 253
\midinsert \clabel[SPI-system]{SPI configuration interface connections}
1121 kaklik 254
\ctable {ccc}
255
{
256
SPI connection J7	&	FMC signal	&	Connected to	\cr
257
SAS-AUX1	 &	LA14\_N	&	SPI DOUT	\cr
258
SAS-AUX2	 &	LA14\_P	&	SPI CLK	\cr
259
SAS-AUX3	 &	LA12\_N	&	CE ADC1	\cr
260
SAS-AUX4	 &	LA12\_P	&	CE ADC2	\cr
261
SAS-AUX5	 &	LA13\_N	&	soldered to GND	\cr
262
SAS-AUX6	 &	LA13\_P	&	not used	\cr
263
SAS-AUX7	 &	LA09\_N	&	not used	\cr
264
SAS-AUX8	 &	LA09\_P	&	soldered to GND	\cr
265
}
1154 hlavac 266
\caption/t SPI system interconnections.
1121 kaklik 267
\endinsert
268
 
1133 hlavac 269
SPI interface is used in an unusual way in this design. SPI Data outputs from ADCs are not connected anywhere and read back is not possible, thus the configuration written to registers in ADC module cannot be validated. We have not observed any problems with this system, but it may be a possible source of failures.
1121 kaklik 270
 
1126 kaklik 271
 
1125 kaklik 272
\midinsert \clabel[clock-interconnections]{System clock interconnections}
1121 kaklik 273
\ctable {lccc}
274
{
275
Signal	&	FMC signal	&	FMC2DIFF01A	&	ADCdual01A	\cr
276
DCO	&	CLK1\_M2C	&	J5-1	&	J13-1	\cr
277
FR	&	LA18\_CC	&	J10-1	&	J12-1	\cr
278
ENC	&	LA01\_CC	&	J2-1(PECL OUT)	&	J3-1	\cr
279
SDGPSDO01A LO	&	CLK0\_M2C	&	J3-1 (PECL IN)	&	N/A	\cr
280
}
1154 hlavac 281
\caption/t Clock system interconnections.
1121 kaklik 282
\endinsert
283
 
1133 hlavac 284
\secc FPGA function
1116 kaklik 285
 
1154 hlavac 286
Several tasks in the separate FPGA blocks are performed by FPGA. In the first block, the FPGA prepares a sampling clock for ADCdual01A modules by dividing the signal from the main local oscillator. This task represents a separate block in FPGA and runs asynchronously to other logical circuits. The second block is a SPI configuration module, which sends configuration words to ADC modules and it is activated by opening of Xillybus interface file. The third block represents the main module, which resolves ADC - PC communication itself and it communicates via PCIe, collect data from ADC hardware and creates data packet, Table~\ref[xillybus-interface]. The last block is activated after the ADC is configurated via SPI.
1116 kaklik 287
 
1154 hlavac 288
The communication over PCIe is managed by proprietary IP Core and Xillybus driver, which transfers data from FPGA registers to host PC. Data appear in a system device file named  "/dev/xillybus_data2_r" on the host computer. Binary data which appear in this file after its opening are shown in Table~\ref[xillybus-interface].
1116 kaklik 289
 
1133 hlavac 290
\midinsert
1127 kaklik 291
\def\tabiteml{ }\let\tabitemr=\tabiteml
1126 kaklik 292
\clabel[xillybus-interface]{Grabber binary output format}
293
\ctable {lccccccccc}{
1127 kaklik 294
\hfil & \multispan9 \hfil 160bit packet \hfil \strut \crl \tskip4pt
295
Data name &  FRAME  & \multispan2 \hfil ADC1 CH1 \hfil & \multispan2 \hfil ADC1 CH2 \hfil & \multispan2  \hfil ADC2 CH1 \hfil & \multispan2 \hfil ADC2 CH2 \hfil \strut  \cr
1073 kaklik 296
Data type & uint32 & int16 & int16 & int16 & int16 & int16 & int16 & int16 & int16 \cr
297
Content & saw signal & $t1$ &  $t_{1+1}$ &  $t1$ &  $t_{1+1}$ &  $t1$ &  $t_{1+1}$ &  $t1$ &  $t_{1+1}$ \cr
298
}
1154 hlavac 299
\caption/t System device "/dev/xillybus_data2_r" data format.
1073 kaklik 300
\endinsert
301
 
1154 hlavac 302
The data packet block which is carried on PCI Express is described in Table~\ref[xillybus-interface]. The data packet consist of several 32bit words. The first word contains FRAME number and it is filled with saw signal for now, with incremental step taking place every data packet transmission. The following data words contain samples from ADCs' first and second channel. Samples from every channel are transmitted in pairs of two samples. Number of ADC channels is expandable according to the number of physically connected channels. An CRC word may possibly be added in the future to the end of the transmission packet for data integrity validation.
1073 kaklik 303
 
1154 hlavac 304
FRAME word at the beginning of data packet, now filled with incrementing and overflowing saw signal, is used to ensure that no data samples ale lost during the data transfers from FPGA. FRAME signal may be used in the future for pairing the ADC samples data packet with another data packet. This new additional data packet should carry meta-data information about the sample time jitter, current accuracy of the local oscillator frequency etc.
1116 kaklik 305
 
1154 hlavac 306
Detailed description of the currently implemented FPGA functions can be found in a separate paper~\cite[fpga-middleware]. HDL source codes for FPGA at a state in which it was used are included on the enclosed CD. More recent development versions are publicly available from MLAB sources repository.
307
Detailed description of currently implemented FPGA functions can be found in separate paper~\cite[fpga-middleware]. HDL\glos{HDL}{Hardware description language} source codes for FPGA at state which was used are included on enclosed CD. Future development versions are publicly available from MLAB sources repository~\cite[mlab-sdrx].
1125 kaklik 308
 
1133 hlavac 309
\secc Data reading and recording
1073 kaklik 310
 
1136 fluktuacia 311
In order to read the data stream from the ADC drive, we use Gnuradio software. Gnuradio suite consists of gnuradio-companion package which is a graphical tool for creating signal-flow graphs and generating Python flow-graph source code. This tool has been used to create a basic RAW data grabber to record and interactively view waterfall plots using the data streams output from ADC modules.
1073 kaklik 312
 
313
\midinsert
1127 kaklik 314
\clabel[grabber-flow-graph]{Gnuradio flow graph for signal grabbing}
315
\picw=\pdfpagewidth \setbox0=\hbox{\inspic ./img/screenshots/Grabber.grc.png }
316
\par\nobreak \vskip\wd0 \vskip-\ht0
317
\centerline {\kern\ht0 \pdfsave\pdfrotate{90}\rlap{\box0}\pdfrestore}
318
\caption/f The ADC recorder flow graph created in gnuradio-companion.
1073 kaklik 319
\endinsert
320
 
321
\midinsert
322
\picw=15cm \cinspic ./img/screenshots/Grabber_running.png
1094 fluktuacia 323
\caption/f User interface window of a running ADC grabber.
1073 kaklik 324
\endinsert
325
 
1154 hlavac 326
The interactive grabber-viewer user interface shows live oscilloscope-like time-value display for all data channels and live time-frequency scrolling display (a waterfall view) for displaying the frequency components of the grabbed signal. The signal is grabbed to the file with the exactly same format as described in Table \ref[xillybus-interface].
1073 kaklik 327
 
1116 kaklik 328
 
329